Actions
Incident #8617
closed
both pgpool2 instances stopped themselves
Status:
Closed
Priority:
Urgent
Assignee:
_InfraScience Systems Engineer
Category:
System Application
Target version:
Start date:
May 16, 2017
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Development, Pre-Production, Production
Description
After a local network failure, both the pgpool2 instances failed because they thought they were disconnected from the network.
The correct behaviour should be that they release the service without shutting down, so that when the network is available again they can resume the service.
Related issues
Updated by Andrea Dell'Amico almost 8 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
The service was manually restarted.
The behaviour we have experienced seems to be a bug of our running version that was solved on a more recent release. I'm installing the latest stable one in dev to see if it works with our configuration or if changes are needed.
Updated by Andrea Dell'Amico almost 8 years ago
- Related to Task #8622: Install a newer version of pgpool2 to fix the shutdown problem when the network goes away added
Actions
