Nagios DB issue after nagiosxi upgrade

[GDMSAI P-IT]

Hello all, I'm having an issue with nagiosxi after upgrading xi. I have looked at previous similar issues and tried those suggestions, but I'm still having no luck. Any help would be appreciated.

OS: AlmaLinux release 8.7 (Stone Smilodon)
XI: nagiosxi-5.9.3-1

I have ran the following:
/usr/local/nagiosxi/scripts/repairmysql.sh nagios
/usr/local/nagiosxi/scripts/repairmysql.sh nagiosxi
/usr/local/nagiosxi/scripts/repairmysql.sh nagiosql
/usr/local/nagiosxi/scripts/repair_databases.sh
DB's come back clean

mariadb log shows me:
2023-04-13 7:01:21 193982 [Warning] Aborted connection 193982 to db: 'nagiosxi' user: 'nagiosxi' host: 'localhost' (Lock wait timeout exceeded; try restarting transaction)
2023-04-13 7:01:21 193983 [Warning] Aborted connection 193983 to db: 'nagiosxi' user: 'nagiosxi' host: 'localhost' (Lock wait timeout exceeded; try restarting transaction)
2023-04-13 7:01:22 193984 [Warning] Aborted connection 193984 to db: 'nagiosxi' user: 'nagiosxi' host: 'localhost' (Lock wait timeout exceeded; try restarting transaction)
2023-04-13 7:01:40 194080 [Warning] Aborted connection 194080 to db: 'nagiosxi' user: 'nagiosxi' host: 'localhost' (Lock wait timeout exceeded; try restarting transaction)
2023-04-13 7:01:41 194081 [Warning] Aborted connection 194081 to db: 'nagiosxi' user: 'nagiosxi' host: 'localhost' (Lock wait timeout exceeded; try restarting transaction)
2023-04-13 7:01:41 194082 [Warning] Aborted connection 194082 to db: 'nagiosxi' user: 'nagiosxi' host: 'localhost' (Lock wait timeout exceeded; try restarting transaction)

I'm seeing new errors in the mariadb log now and I'm thinking it may have to do w/tweaks I tried yesterday to fix the issue:
2023-04-13 7:27:05 199586 [ERROR] InnoDB: preallocating 188743680 bytes for file ./nagiosxi/#sql-ca02_30ba2.ibd failed with error 28
2023-04-13 7:27:49 199586 [ERROR] InnoDB: preallocating 251658240 bytes for file ./nagiosxi/#sql-ca02_30ba2.ibd failed with error 28
2023-04-13 7:38:48 202740 [ERROR] InnoDB: preallocating 440401920 bytes for file ./nagiosxi/xi_eventqueue.ibd failed with error 28
2023-04-13 7:38:48 202740 [ERROR] mysqld: The table 'xi_eventqueue' is full
2023-04-13 7:38:48 202741 [ERROR] InnoDB: preallocating 440401920 bytes for file ./nagiosxi/xi_eventqueue.ibd failed with error 28
2023-04-13 7:38:48 202741 [ERROR] mysqld: The table 'xi_eventqueue' is full
2023-04-13 7:38:49 202742 [ERROR] InnoDB: preallocating 440401920 bytes for file ./nagiosxi/xi_eventqueue.ibd failed with error 28
2023-04-13 7:38:49 202742 [ERROR] mysqld: The table 'xi_eventqueue' is full
2023-04-13 7:38:49 202743 [ERROR] InnoDB: preallocating 440401920 bytes for file ./nagiosxi/xi_eventqueue.ibd failed with error 28
2023-04-13 7:38:49 202743 [ERROR] mysqld: The table 'xi_eventqueue' is full
2023-04-13 7:38:49 202744 [ERROR] InnoDB: preallocating 440401920 bytes for file ./nagiosxi/xi_eventqueue.ibd failed with error 28
2023-04-13 7:38:49 202744 [ERROR] mysqld: The table 'xi_eventqueue' is full
2023-04-13 7:38:49 202745 [ERROR] InnoDB: preallocating 440401920 bytes for file ./nagiosxi/xi_eventqueue.ibd failed with error 28
2023-04-13 7:38:49 202745 [ERROR] mysqld: The table 'xi_eventqueue' is full

I ran these tweaks yesterday:
https://support.nagios.com/kb/article/n ... e-611.html

Any help would be appreciated

[GDMSAI P-IT]

I just ran: /usr/local/nagiosxi/scripts/remove_historical_data.sh

[GDMSAI P-IT]

I was thinking my issue was ndo2db.service, but read that was replaced in the upgrade.

[GDMSAI P-IT]

I ended up reverting back to original working Nagios snapshot and will revisit

[KayesPotrinak]

Based on the information provided, it seems that the issue could be related to preallocating space for the database files. One possible solution could be to try freeing up some space on the system or increasing the available storage. Another potential solution might be to adjust the database settings or configurations. Have you tried reaching out to the Nagios support team or community forums for further assistance? It might also be helpful to provide more specific details about the error messages and any other relevant information to help troubleshoot the issue.

[raftmore]

I adjusted the database settings and configurations. It actually worked. Many thanks.

redactle

[rubberytake]

I adjusted the database settings and configurations. It actually worked. Many thanks.

1v1 lol

Hey what exactly did you adjust?