Subject: Re: slon crash
Newsgroups: gmane.comp.db.postgresql.slony1.general
Date: 2005-12-09 16:33:22 GMT (3 years, 4 weeks, 18 hours and 11 minutes ago)
On 12/7/2005 11:20 AM, JP Fletcher wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > We had a slon daemon (v 1.1.2, pg748, AMD64) crash with the following > message: > > 2005-12-07 08:32:31 UTC ERROR remoteListenThread_154: timeout for event > selection > sched_mainloop: select(): Bad file descriptor > > I've seen another post that makes mention of this, though in the context > of seeing the error regularly, and concurrently with a scheduled > pg_dump. This is the only time we've seen it, and it only occurred on a > single node in a 4 node cluster. Any thoughts? The remote_listen thread of slon selects from the data providers sl_event table with an asynchronous query. If that query does not finish within 5 minutes, it bails out like that. Is there anything on the provider node that locks sl_event with and access exclusive lock? Or is that providers (node 154) sl_event table so bloated that 5 minutes to select some events is reasonable? Jan > > Regards > > JP > - -- > JP Fletcher > Database Administrator > Afilias Canada > voice: 416.646.3304 ext. 123 > fax: 416.646.3305 > mobile: 416.561.4763 > jpfletch@... > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iD8DBQFDlwu5aQwDW0M+H30RAsw+AKCEOFdut43o2bAv3OJRWB+rCgTitQCfebZ7 > oYQclP3+TTm2i5KvWP/YNiw= > =IZXW > -----END PGP SIGNATURE----- > _______________________________________________ > Slony1-general mailing list > Slony1-general@... > http://gborg.postgresql.org/mailman/listinfo/slony1-general -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@... #