Thu Oct 21 12:12:43 PDT 2010
- Previous message: [Slony1-bugs] [Bug 155] slon can segfault when the postgres backend abnormally terminates
- Next message: [Slony1-bugs] [Bug 160] slon can get into a state where it spins with "child terminated status"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=160 Summary: slon can get into a state where it spins with "child terminated status" Product: Slony-I Version: 2.0 Platform: All OS/Version: All Status: NEW Severity: critical Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 With 2.0.5 I've seen slon get into a state where it generates many megabytes per second of log messages of the form 2010-10-21 18:52:32 CUTCONFIG slon: child terminated status: 589833; pid: -1, current worker pid: 639202 2010-10-21 18:52:32 CUTCONFIG slon: child terminated status: 589833; pid: -1, current worker pid: 639202 there does not appear to be a working slon running just the watchdog. I had to send a kill -9 to the slon process to get it to stop. It is possible that this was caused by some abnormal event ie dropping the databases underneath slon but I'm not able to confirm that coincided with slon getting into that state. Note this was observed on AIX. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 155] slon can segfault when the postgres backend abnormally terminates
- Next message: [Slony1-bugs] [Bug 160] slon can get into a state where it spins with "child terminated status"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list