Jira (PDB-5211) Check whether PuppetDB still doesn't complete shutdown after migration fails

[Andrei Filipovici (Jira)]

Title: Message Title

Andrei Filipovici commented on PDB-5211   Re: Check whether PuppetDB still doesn't complete shutdown after migration fails Also the interesting thing is that PuppetDB is started in a loop, but it won't be able to start. So, if you do a: journalctl -u puppetdb | grep 'Failed to start puppetdb Service' you'll see a bunch of: Aug 13 09:53:34 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:53:43 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:53:53 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:02 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:12 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:21 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:31 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:40 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:50 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:54:59 well-clover systemd[1]: Failed to start puppetdb Service. Aug 13 09:55:08 well-clover systemd[1]: Failed to start puppetdb Service. Took a look at the puppetdb.service file located in /usr/lib/systemd/system/puppetdb.service and we saw the settings: TimeoutStartSec=14400 TimeoutStopSec=60 Restart=on-failure StartLimitBurst=5 They might be the cause of the continuous starting of PuppetDB. Add Comment   This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408706.1627410285000.106965.1628855640165%40Atlassian.JIRA.