No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-37017 Excessive Users Are Connected to a Database

ALM-37017 Excessive Users Are Connected to a Database

Description

This alarm is generated when excessive users are connected to a database on a Coordinator instance in a cluster.

Attribute

Alarm ID

Alarm Severity

Auto Clear

37017

Major

Yes

Parameters

Name

Meaning

ServiceName

Identifies the service for which the alarm is generated.

RoleName

Identifies the role for which the alarm is generated.

HostName

Identifies the host for which the alarm is generated.

Instance

Identifies the instance for which the alarm is generated.

databaseName

Identifies the name of the database to connect to.

dbUserName

Identifies the name of users connected to a database.

Impact on the System

Common users cannot access the database on the Coordinator instance.

Possible Causes

Excessive users are connected to the database on the current Coordinator node.

Procedure

  1. Log in to the FusionInsight Manager.

    1. Log in to the ManageOne OM plane using a browser, then choose Alarms.
      • Login address: https://URL for the homepage of the ManageOne OM plane:31943. Example: https://oc.type.com:31943.
      • Default username: admin, default password: Huawei12#$.
    2. In the alarm list, locate and click the target alarm name in the Name column. The Alarm Details and Handling Recommendations dialog box is displayed.
    3. Locate the value in the IP Address/URL/Domain Name column, which is the float IP address of the FusionInsight Manager.
    4. Log in to the FusionInsight Manager using a browser.
      • Login address: https://float IP address of the FusionInsight Manager:28443/web. Example: https://10.10.192.100:28443/web.
      • Default username: admin, default password: obtain it from the system administrator.

  2. On FusionInsight Manager, click Alarms. On the alarm list, locate the alarm and obtain the information about the node and instance for which the alarm is generated from Location in the Alarm Details area.
  3. Run the following command to access the alarmed Coordinator instance as the database administrator (who has the permission to create other database users, for example, user omm).

    Default user: omm, default password: Bigdata123@.

    gsql -d postgres -p 25308

  4. Check the maximum number of users connected to the databases on the Coordinator instance. In the following example, a maximum of three users can connect to the abc database on the Coordinator instance.

    select * from pg_database;
    datname  | datdba | encoding | datcollate | datctype | datistemplate | datallowconn | datconnlimit | datlastsysoid | datfrozenxid | dattablespace |                    datacl -----------+--------+----------+------------+----------+---------------+--------------+--------------+---------------+--------------+---------------+---------------------------------------------- template1 |     10 |        0 | C          | C        | t             | t            |           -1 |         13506 |         1336 |          1663 | {=c/xijie_trunk,xijie_trunk=CTc/xijie_trunk} template0 |     10 |        0 | C          | C        | t             | f            |           -1 |         13506 |         1335 |          1663 | {=c/xijie_trunk,xijie_trunk=CTc/xijie_trunk} postgres  |     10 |        0 | C          | C        | f             | t            |           -1 |         13506 |         1337 |          1663 | abc       |     10 |        0 | C          | C        | f             | t            |            3 |         13506 |         1336 |          1663 | (4 rows)

  5. Disconnect some users or increase the number of users who can connect to the database. Perform the following operations to increase the number of users.

    update pg_database set datconnlimit=9 where datname='abc';

    UPDATE 1
    select * from pg_database;
    datname  | datdba | encoding | datcollate | datctype | datistemplate | datallowconn | datconnlimit | datlastsysoid | datfrozenxid | dattablespace |                    datacl -----------+--------+----------+------------+----------+---------------+--------------+--------------+---------------+--------------+---------------+---------------------------------------------- template1 |     10 |        0 | C          | C        | t             | t            |           -1 |         13506 |         1336 |          1663 | {=c/xijie_trunk,xijie_trunk=CTc/xijie_trunk} template0 |     10 |        0 | C          | C        | t             | f            |           -1 |         13506 |         1335 |          1663 | {=c/xijie_trunk,xijie_trunk=CTc/xijie_trunk} postgres  |     10 |        0 | C          | C        | f             | t            |           -1 |         13506 |         1337 |          1663 | abc       |     10 |        0 | C          | C        | f             | t            |            9 |         13506 |         1336 |          1663 | (4 rows)

  6. Connect to the abc database and check whether the alarm persists.

    • If yes, go to 7.
    • If no, no further action is required.

Collect fault information.

  1. On FusionInsight Manager, choose System > Log Download.
  2. Select MPPDB from the Services drop-down list box and click OK.
  3. Set Start Time for log collection to 1 hour ahead of the alarm generation time and End Time to 1 hour after the alarm generation time, and click Download.
  4. Contact Technical Support and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 48260

Downloads: 33

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next