Hi Sean,
We are able to see continuous deadlocks created in Nagios.
Nagiosxi is not able to open while deadlocks available in postgres logs.
I have executed dbrepair script, deadlocks have lost, webconsole opening successfully.
But still deadlocks keep visiting ….what to do for this....
ERROR: deadlock detected
Re: ERROR: deadlock detected
Before DBrepair execution.
[root@p01 pg_log]# tail -f postgresql-Mon.log
DETAIL: Process 11728 waits for ShareLock on transaction 1853508055; blocked by process 14612.
Process 14612 waits for ShareLock on transaction 1853515079; blocked by process 11728.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 24188 waits for ShareLock on transaction 1853508055; blocked by process 14612.
Process 14612 waits for ShareLock on transaction 1853514025; blocked by process 24188.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 14612 waits for ShareLock on transaction 1853513647; blocked by process 29952.
Process 29952 waits for ShareLock on transaction 1853508055; blocked by process 14612.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 26001 waits for ShareLock on transaction 1853513647; blocked by process 29952.
Process 29952 waits for ShareLock on transaction 1853510138; blocked by process 26001.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 29952 waits for ShareLock on transaction 1853511484; blocked by process 29693.
Process 29693 waits for ShareLock on transaction 1853513647; blocked by process 29952.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 29693 waits for ShareLock on transaction 1853515212; blocked by process 6744.
Process 6744 waits for ShareLock on transaction 1853511484; blocked by process 29693.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 24584 waits for ExclusiveLock on tuple (195,53) of relation 145442 of database 16385; blocked by process 31034.
Process 31034 waits for ShareLock on transaction 1853508396; blocked by process 24079.
Process 24079 waits for ShareLock on transaction 1853515212; blocked by process 6744.
Process 6744 waits for ExclusiveLock on tuple (195,53) of relation 145442 of database 1
After DBrepair execution.
[root@p01 pg_log]# tail -f postgresql-Mon.log
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 9956 waits for ShareLock on transaction 1854514081; blocked by process 23882.
Process 23882 waits for ShareLock on transaction 1854514075; blocked by process 9956.
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
How to provide attachments privately here without disclosing to public ?
[root@p01 pg_log]# tail -f postgresql-Mon.log
DETAIL: Process 11728 waits for ShareLock on transaction 1853508055; blocked by process 14612.
Process 14612 waits for ShareLock on transaction 1853515079; blocked by process 11728.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 24188 waits for ShareLock on transaction 1853508055; blocked by process 14612.
Process 14612 waits for ShareLock on transaction 1853514025; blocked by process 24188.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 14612 waits for ShareLock on transaction 1853513647; blocked by process 29952.
Process 29952 waits for ShareLock on transaction 1853508055; blocked by process 14612.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 26001 waits for ShareLock on transaction 1853513647; blocked by process 29952.
Process 29952 waits for ShareLock on transaction 1853510138; blocked by process 26001.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 29952 waits for ShareLock on transaction 1853511484; blocked by process 29693.
Process 29693 waits for ShareLock on transaction 1853513647; blocked by process 29952.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 29693 waits for ShareLock on transaction 1853515212; blocked by process 6744.
Process 6744 waits for ShareLock on transaction 1853511484; blocked by process 29693.
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 24584 waits for ExclusiveLock on tuple (195,53) of relation 145442 of database 16385; blocked by process 31034.
Process 31034 waits for ShareLock on transaction 1853508396; blocked by process 24079.
Process 24079 waits for ShareLock on transaction 1853515212; blocked by process 6744.
Process 6744 waits for ExclusiveLock on tuple (195,53) of relation 145442 of database 1
After DBrepair execution.
[root@p01 pg_log]# tail -f postgresql-Mon.log
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
ERROR: deadlock detected
DETAIL: Process 9956 waits for ShareLock on transaction 1854514081; blocked by process 23882.
Process 23882 waits for ShareLock on transaction 1854514075; blocked by process 9956.
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
How to provide attachments privately here without disclosing to public ?
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: ERROR: deadlock detected
Hi,
Since you are running Postgres, did run a vaccum on the database? You'll find the commands for you distro available on the kb article below.
https://support.nagios.com/kb/article.p ... POSTGRESQL
After that, let the system run and send over a fresh copy of the system profile, if the issue persists.
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 share this in a private message and then reply to this post to bring it up in the queue.
You can send them over in a PM or alternatively you can open a support ticket for the issue.How to provide attachments privately here without disclosing to public?
Since you are running Postgres, did run a vaccum on the database? You'll find the commands for you distro available on the kb article below.
https://support.nagios.com/kb/article.p ... POSTGRESQL
After that, let the system run and send over a fresh copy of the system profile, if the issue persists.
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 share this in a private message and then reply to this post to bring it up in the queue.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!