On 06/22/2013 06:16 PM, Bambi Bellows wrote: > LOL. You guys are killin me. Meantime, can someone point me to where the > log file destination might be hidden? Because I can't even find out what > broke and why. And as much as it's great to blame my predecessors, they > aren't here anymore, and I'm out of my depth on Slony... ob.vi.ous.ly. And > telling my boss to suck it is not really an option for me.
How is slony being started? Is the startup script redirecting the output of slon somewhere (to a logfile, or /dev/null ?) One option might be to restart slon so that it redirects its output to a logfile that you can then view. Are you using a slon.conf ? If so does it specify a destination for logs? > -----Original Message----- > From: Scott Marlowe [mailto:[email protected]] > Sent: Saturday, June 22, 2013 5:11 PM > To: Jan Wieck > Cc: Bambi Bellows; [email protected] > Subject: Re: [Slony1-general] Slony replication has stopped replicating > > On Sat, Jun 22, 2013 at 2:27 PM, Jan Wieck<[email protected]> wrote: >> On 06/22/13 16:56, Bambi Bellows wrote: >>> LOL. Thanks Jan. No, I inherited these systems, and upgrading is not >>> really an option for the database... I am, however, trying to find where >>> the log files are. They aren't in the /opt/logs/postgres directory, and >>> they aren't in the postgres logs directory. I have two sudo finds running, >>> but, so far, no luck. Gotta say, haven't been having the best of luck so >>> far on anything slony-related. >> Slony related? >> >> I would say the whole thing you inherited is a complete mess and Slony >> is a casualty of that. There is nothing so far that I can see could be >> blamed on Slony. Only a grossly outdated and unmanaged server setup. >> >> Sorry to be so blunt, but I just don't tolerate it when Slony or >> PostgreSQL are blamed for server admin negligence and incompetence. >> >> This is apparently not your fault, but your predecessor's fault. So >> don't take it personal. > Yeah when I'm handed a grand mess like this I just tell the bosses you > can either let me fix it the way it needs to be fixed, or watch it > break over and over. Your choice, but I'm not getting up at 2am to fix > things you didn't let me fix right. > > > > > This email and any files included with it may contain privileged, > proprietary and/or confidential information that is for the sole use > of the intended recipient(s). Any disclosure, copying, distribution, > posting, or use of the information contained in or attached to this > email is prohibited unless permitted by the sender. If you have > received this email in error, please immediately notify the sender > via return email, telephone, or fax and destroy this original transmission > and its included files without reading or saving it in any manner. > Thank you. > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://lists.slony.info/mailman/listinfo/slony1-general > > _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
