There is nothing laughable about your situation, so I don't know what you LOL all the time.

Whoever installed that database and Slony system determined where the logs go. Check the system startup scripts ans syslog files/configuration for any hints. Unfortunately every Linux packager has his/her own mind where things are supposed to go. Not like in half organized FreeBSD territory, where you at least can guess where the logs may be.


Jan

--
Anyone who trades liberty for security deserves neither 
liberty nor security. -- Benjamin Franklin

Bambi Bellows <bbellows at dotomi.com> wrote:

>LOL.  Thank you for your advice.  I will talk to my boss about this on Monday.
>
>-----Original Message-----
>From: Scott Marlowe [mailto:scott.marlowe at gmail.com] 
>Sent: Saturday, June 22, 2013 5:19 PM
>To: Bambi Bellows
>Cc: Jan Wieck; slony1-general at lists.slony.info
>Subject: Re: [Slony1-general] Slony replication has stopped replicating
>
>On Sat, Jun 22, 2013 at 3:16 PM, Bambi Bellows <bbellows at dotomi.com> 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.
>>
>
>I'm not telling you to tell them to suck it, I'm telling you to tell
>them you need to fix it right. Take the system offline for as long as
>it takes to upgrade postgresql (a few minutes typically). Drop the
>current slony, install the latest 2.1.x, and restart replication from
>scratch. Running around with your hair on fire at this point isn't
>likely to result in a long term sustainable fix, but a slowly
>repeating cycle of endless horror as the system gets fixed, breaks,
>and gets fixed over and over.
>
>
>
>
>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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20130622/bd5861cb/attachment.htm