Tue Nov 8 03:51:57 PST 2005
- Previous message: [Slony1-general] lock set never returns.
- Next message: [Slony1-general] Slony1 1.1.2 does not compile on postgresql-8.1.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
3 nodes. Nodes 2 and 3 are slaves to node 1. Listen paths exist between all possible connections (6 paths). Below is a list of running processes on node 2. Slony on node1, for reasons unknown, decided to spawn a large number of processes on that machine. These machines are on the same switch and neither has network problems. Below is the connection list. I have full logs available at debug level 4 (set to that level when we had this problem in the past), but they don't seem to show anything interesting. 19772 ? S 7:19 postgres: slony ssdb 172.20.13.10(32983) notify interrupt waiting 19864 ? S 7:00 postgres: slony ssdb 172.20.13.10(33300) notify interrupt waiting 19909 ? S 6:44 postgres: slony ssdb 172.20.13.10(33616) notify interrupt waiting 19946 ? S 6:25 postgres: slony ssdb 172.20.13.10(33935) notify interrupt waiting 20023 ? S 6:08 postgres: slony ssdb 172.20.13.10(34305) notify interrupt waiting 20079 ? S 5:53 postgres: slony ssdb 172.20.13.10(34626) notify interrupt waiting 20138 ? S 5:40 postgres: slony ssdb 172.20.13.10(34948) notify interrupt waiting 20189 ? S 5:26 postgres: slony ssdb 172.20.13.10(35274) notify interrupt waiting 20273 ? S 5:13 postgres: slony ssdb 172.20.13.10(35598) notify interrupt waiting 20358 ? S 5:02 postgres: slony ssdb 172.20.13.10(35926) notify interrupt waiting 20426 ? S 4:52 postgres: slony ssdb 172.20.13.10(36256) notify interrupt waiting 20480 ? S 4:40 postgres: slony ssdb 172.20.13.10(36597) notify interrupt waiting 20527 ? S 4:29 postgres: slony ssdb 172.20.13.10(36933) notify interrupt waiting 20561 ? S 4:19 postgres: slony ssdb 172.20.13.10(37288) notify interrupt waiting 20589 ? S 4:08 postgres: slony ssdb 172.20.13.10(37640) notify interrupt waiting 20637 ? S 3:57 postgres: slony ssdb 172.20.13.10(38012) notify interrupt waiting 20682 ? S 3:49 postgres: slony ssdb 172.20.13.10(38348) notify interrupt waiting 20722 ? S 3:39 postgres: slony ssdb 172.20.13.10(38700) notify interrupt waiting 20795 ? S 3:31 postgres: slony ssdb 172.20.13.10(39058) notify interrupt waiting 20871 ? S 3:22 postgres: slony ssdb 172.20.13.10(39411) notify interrupt waiting 20937 ? S 3:14 postgres: slony ssdb 172.20.13.10(39779) notify interrupt waiting 20979 ? S 3:07 postgres: slony ssdb 172.20.13.10(40133) notify interrupt waiting 21069 ? S 2:56 postgres: slony ssdb 172.20.13.10(40637) notify interrupt waiting 21102 ? S 2:48 postgres: slony ssdb 172.20.13.10(41015) notify interrupt waiting 21156 ? S 2:40 postgres: slony ssdb 172.20.13.10(41400) notify interrupt waiting 21223 ? S 2:26 postgres: slony ssdb 172.20.13.10(42144) notify interrupt waiting 21271 ? S 2:19 postgres: slony ssdb 172.20.13.10(42509) notify interrupt waiting 21343 ? S 2:13 postgres: slony ssdb 172.20.13.10(42860) notify interrupt waiting 21399 ? S 2:06 postgres: slony ssdb 172.20.13.10(43223) notify interrupt waiting 21463 ? S 1:59 postgres: slony ssdb 172.20.13.10(43595) notify interrupt waiting 21498 ? S 1:53 postgres: slony ssdb 172.20.13.10(43968) notify interrupt waiting 21540 ? S 1:46 postgres: slony ssdb 172.20.13.10(44332) notify interrupt waiting 21597 ? S 1:40 postgres: slony ssdb 172.20.13.10(44707) notify interrupt waiting 21682 ? S 1:34 postgres: slony ssdb 172.20.13.10(45098) notify interrupt waiting 21738 ? S 1:29 postgres: slony ssdb 172.20.13.10(45465) notify interrupt waiting 21789 ? S 1:22 postgres: slony ssdb 172.20.13.10(45866) notify interrupt waiting 21904 ? S 1:15 postgres: slony ssdb 172.20.13.10(46340) notify interrupt waiting 21958 ? S 1:10 postgres: slony ssdb 172.20.13.10(46721) notify interrupt waiting 22025 ? S 1:04 postgres: slony ssdb 172.20.13.10(47091) notify interrupt waiting 22125 ? S 0:55 postgres: slony ssdb 172.20.13.10(47714) notify interrupt waiting 22218 ? S 0:50 postgres: slony ssdb 172.20.13.10(48095) notify interrupt waiting --
- Previous message: [Slony1-general] lock set never returns.
- Next message: [Slony1-general] Slony1 1.1.2 does not compile on postgresql-8.1.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list