how to determine problems on red Database Maintenance

[DonForigua]

Hi

i have the message "Database Maintenance" in red but the status is ok

Code: Select all

mysql  Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline 5.1

Connection id:          3619304
Current database:       nagios
Current user:           nagiosxi@napoles
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server:                 MySQL
Server version:         5.1.73-log Source distribution
Protocol version:       10
Connection:             172.22.xxx via TCP/IP
Server characterset:    latin1
Db     characterset:    latin1
Client characterset:    utf8
Conn.  characterset:    utf8
TCP port:               3306
Uptime:                 25 days 8 hours 35 min 41 sec

Threads: 62  Questions: 1295031673  Slow queries: 3806  Opens: 26112701  Flush tables: 1  Open tables: 64  Queries per second avg: 591.84
--------------

xxxxxx:/root> # mysql -h 172.22.xxxx -unagiosxi -p'n@gweb' nagiosxi -e 'status;'
--------------
mysql  Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline 5.1

Connection id:          3619305
Current database:       nagiosxi
Current user:           nagiosxi@napoles
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server:                 MySQL
Server version:         5.1.73-log Source distribution
Protocol version:       10
Connection:             xxxxx via TCP/IP
Server characterset:    latin1
Db     characterset:    latin1
Client characterset:    utf8
Conn.  characterset:    utf8
TCP port:               3306
Uptime:                 25 days 8 hours 35 min 47 sec

Threads: 62  Questions: 1295031798  Slow queries: 3806  Opens: 26112701  Flush tables: 1  Open tables: 64  Queries per second avg: 591.83
--------------

i've stopped the services and delete all lock files and restart but the status is red and nagios does not monitor since 4:30 am

[DonForigua]

Hi the nagios core interface says me

Code: Select all

Whoops!

Error: Could not read object configuration data!

Here are some things you should check in order to resolve this error:

    Verify configuration options using the -v command-line option to check for errors.
    Check the Nagios log file for messages relating to startup or status data errors. 

checking the log

Code: Select all

[1645608291] SERVICE ALERT: TDY0059_SRVCENCONBD;Physical Memory TDY0059_SRVCENCONBD;WARNING;HARD;3;Physical Memory: 90%used(14782MB/16383MB) (>90%) : WARNING
[1645608294] SERVICE ALERT: sgz0099_sgztts2;CPU Used sgz0099;OK;SOFT;2;8 CPU, average load 0.0% < 85% : OK
[1645608296] SERVICE ALERT: FLP0282_SRVOCPSTORAGE04DESA;Physical memory FLP0282_SRVOCPSTORAGE04DESA;WARNING;SOFT;2;Physical memory: 90%used(13387MB/14859MB) (>90%) : WARNING
[1645608296] SERVICE ALERT: FLP0252_SRVOCPMASTER03;Process Chronyd  FLP0252_SRVOCPMASTER03;OK;SOFT;2;1 process matching chronyd (> 0)
[1645608296] SERVICE ALERT: TFM0811_TFM0811;Virtual Memory TFM0811;OK;SOFT;2;Virtual Memory: 24%used(19575MB/81715MB) (<90%) : OK
[1645608297] SERVICE ALERT: CDTRIBOCHAXGW02;ntpd CDTRIBOCHAXGW02;OK;SOFT;2;1 process named ntpd (> 0)
[1645608297] SERVICE ALERT: SFD0017_ALCALDIAS4;CPU Used SFD0017_ALCALDIAS4;OK;SOFT;2;8 CPU, average load 0.2% < 80% : OK
[1645608298] SERVICE ALERT: SCK0068_TRIASFILE-CERT1;Process snmp.exe en SCK0068_TRIASFILE-CERT1;OK;SOFT;2;1 process matching snmp.exe (> 0)
[1645608299] SERVICE ALERT: SOK0062_COBOSCCMSS01;Process vmtoolsd.exe SOK0062_COBOSCCMSS01;OK;SOFT;2;1 process matching vmtoolsd.exe (> 0)
[1645608301] SERVICE ALERT: FLP0263_SRVOCPBASTION;Process Crond FLP0263_ SRVOCPBASTION;OK;SOFT;2;1 process matching crond (> 0)
[1645608301] SERVICE ALERT: SCK0060_WSIGNALLIANZPRD;Process snmpd SCK0060_WSIGNALLIANZPRD;OK;SOFT;2;1 process matching snmpd (> 0)
[1645608302] SERVICE ALERT: CSP0052_CSP0052_ODB1;Process snmpd CSP0052_CSP0052_ODB1;OK;SOFT;2;1 process matching snmpd (> 0)
[1645608302] SERVICE FLAPPING ALERT: WFM0151_WFM0151;Physical Memory WFM0151_WFM0151;STARTED; Service appears to have started flapping (23.0% change >= 20.0% threshold)
[1645608302] SERVICE ALERT: WFM0151_WFM0151;Physical Memory WFM0151_WFM0151;OK;HARD;3;Physical Memory: 80%used(13093MB/16384MB) (<80%) : OK
[1645608303] SERVICE ALERT: FLP0243_LENIN;Process Crond FLP0243_LENIN;OK;SOFT;2;1 process matching crond (> 0)
[1645624999] Caught SIGTERM, shutting down...
[1645625403] Nagios 4.4.6 starting... (PID=21890)
[1645625403] Local time is Wed Feb 23 09:10:03 -05 2022
[1645625403] LOG VERSION: 2.0
[1645625403] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1645625403] qh: core query handler registered
[1645625403] qh: echo service query handler registered
[1645625403] qh: help for the query handler registered
[1645625403] wproc: Successfully registered manager as @wproc with query handler
[1645625403] wproc: Registry request: name=Core Worker 21891;pid=21891
[1645625403] wproc: Registry request: name=Core Worker 21893;pid=21893
[1645625403] wproc: Registry request: name=Core Worker 21892;pid=21892
[1645625403] wproc: Registry request: name=Core Worker 21894;pid=21894
[1645625403] wproc: Registry request: name=Core Worker 21895;pid=21895
[1645625403] wproc: Registry request: name=Core Worker 21896;pid=21896
[1645625403] wproc: Registry request: name=Core Worker 21897;pid=21897
[1645625403] wproc: Registry request: name=Core Worker 21899;pid=21899
...
...
[1645625403] NDO-3: NDO 3.0.7 (c) Copyright 2009-2020 Nagios - Nagios Core Development Team
[1645627193] Caught SIGTERM, shutting down...
[1645627688] Nagios 4.4.6 starting... (PID=4498)
[1645627688] Local time is Wed Feb 23 09:48:08 -05 2022
[1645627688] LOG VERSION: 2.0
[1645627688] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1645627688] qh: core query handler registered
[1645627688] qh: echo service query handler registered
[1645627688] qh: help for the query handler registered
[1645627688] wproc: Successfully registered manager as @wproc with query handler
[1645627688] wproc: Registry request: name=Core Worker 4499;pid=4499
[1645627688] wproc: Registry request: name=Core Worker 4500;pid=4500
[1645627688] wproc: Registry request: name=Core Worker 4501;pid=4501
[1645627688] wproc: Registry request: name=Core Worker 4504;pid=4504
[1645627688] wproc: Registry request: name=Core Worker 4505;pid=4505
[1645627688] wproc: Registry request: name=Core Worker 4508;pid=4508
[1645627688] wproc: Registry request: name=Core Worker 4503;pid=4503
[1645627688] wproc: Registry request: name=Core Worker 4502;pid=4502
[1645627688] wproc: Registry request: name=Core Worker 4506;pid=4506
[1645627688] wproc: Registry request: name=Core Worker 4507;pid=4507
[1645627688] wproc: Registry request: name=Core Worker 4509;pid=4509
[1645627688] wproc: Registry request: name=Core Worker 4510;pid=4510
[1645627688] wproc: Registry request: name=Core Worker 4512;pid=4512
[1645627688] wproc: Registry request: name=Core Worker 4511;pid=4511
[1645627688] wproc: Registry request: name=Core Worker 4513;pid=4513
[1645627688] wproc: Registry request: name=Core Worker 4515;pid=4515
[1645627688] wproc: Registry request: name=Core Worker 4516;pid=4516
[1645627688] wproc: Registry request: name=Core Worker 4514;pid=4514
[1645627688] wproc: Registry request: name=Core Worker 4518;pid=4518
[1645627688] wproc: Registry request: name=Core Worker 4519;pid=4519
[1645627688] wproc: Registry request: name=Core Worker 4520;pid=4520
[1645627688] wproc: Registry request: name=Core Worker 4517;pid=4517
[1645627688] wproc: Registry request: name=Core Worker 4521;pid=4521
[1645627688] wproc: Registry request: name=Core Worker 4522;pid=4522
[1645627688] wproc: Registry request: name=Core Worker 4523;pid=4523
[1645627688] wproc: Registry request: name=Core Worker 4524;pid=4524
[1645627688] wproc: Registry request: name=Core Worker 4525;pid=4525
[1645627688] wproc: Registry request: name=Core Worker 4528;pid=4528
[1645627688] wproc: Registry request: name=Core Worker 4526;pid=4526
[1645627688] wproc: Registry request: name=Core Worker 4527;pid=4527
[1645627688] wproc: Registry request: name=Core Worker 4529;pid=4529
[1645627688] wproc: Registry request: name=Core Worker 4531;pid=4531
[1645627688] wproc: Registry request: name=Core Worker 4530;pid=4530
[1645627688] wproc: Registry request: name=Core Worker 4532;pid=4532
[1645627688] wproc: Registry request: name=Core Worker 4533;pid=4533
[1645627688] wproc: Registry request: name=Core Worker 4534;pid=4534
[1645627688] NDO-3: NDO 3.0.7 (c) Copyright 2009-2020 Nagios - Nagios Core Development Team

[pbroste]

Hello @DonForigua

Thanks for reaching out, want to start off by getting a copy of your System Profile from your environment so we can see what is going on. Before that, let's run through the following mysqlcheck:

Code: Select all

mysqlcheck --user=root --password=nagiosxi --all-databases --auto-repair --verbose

Please let us know the results and PM your updated system profile for us to review.

To send us your system profile.

• Login to the Nagios XI GUI using a web browser.
• Click the "Admin" > "System Profile" Menu
• Click the "Download Profile" button
• Save the profile.zip file and send via Private Message

Thanks,
Perry

[DonForigua]

Hello

The problem was that the db server had a /tmp full.

are there a metod for detect sql errors?

[pbroste]

Hello @DonForigue

Thanks for following up, the option to take a look at the service check 'check_xi_service_status: mysqld' is found in the Configuration Wizards in the Configurations section.

Recommend review the table size and truncate if necessary:

Code: Select all

echo "SELECT table_name AS 'Table', round(((data_length + index_length) / 1024 / 1024), 2) 'Size in MB' FROM information_schema.TABLES WHERE table_schema IN ('nagios', 'nagiosql', 'nagiosxi');" | mysql -h 127.0.0.1 -uroot -pnagiosxi --table

mysql -u ndoutils -pn@gweb nagios -e 'TRUNCATE TABLE nagios_logentries'
mysql -u ndoutils -pn@gweb nagios -e 'TRUNCATE TABLE nagios_notifications'

Thanks,
Perry