> i know that PuppetDB is the way to go for the future but currently i am > forced to use Puppet 2.7 with the Stored Configuration feature. > So the problem is that whenever i restart the PostgreSQL database or the > network service, the Puppet Master running under Apache with Passenger does > not reconnect to the PostgreSQL server so i have to restart Apache. > It may be possible to monitor the Puppet Masters connection using the HTTP > API and e.g. querying for the facts to know when Apache needs to be > restarted but this would be a rather complex solution. > > Is it somehow possible to patch the used Active Record implementation to > achieve the automatic reconnect whenever a connection error is detected?
Yes, quite simply it is possible for _you_ to patch it (I won't even touch the _how_ here, I bet its a PITA), but I doubt the main devs will invest time into this since the code is no longer maintained (hasn't been properly for a year or more since PuppetDB has been in the picture). Perhaps you might get lucky and someone in the community has a patch for this you can apply manually, but its an annoying divergence to maintain patches yourself. What's more, ActiveRecord storeconfigs has been dropped in Puppet 4 completely afaik so it is no longer even an option. Also 2.7.x is EOL fyi, so you're working against the grain here in many ways, sorry mate :-). I'm sure this is already very evident in your day to day work with 2.7. ken. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTndYqvM9NuUyg8oQiY9ZJVkAGuQrLYJo-v%3DH0m89D8v0w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
