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.


Jan

> 
> -----Original Message-----
> From: Jan Wieck [mailto:JanWieck at Yahoo.com] 
> Sent: Saturday, June 22, 2013 3:53 PM
> To: Bambi Bellows
> Cc: slony1-general at lists.slony.info
> Subject: Re: [Slony1-general] Slony replication has stopped replicating
> 
> On 06/22/13 14:48, Bambi Bellows wrote:
>> Hi Gang!
>> 
>> Slony replication has stopped replicating, and I'm not sure why, or how
>> to get it replicating again.  I have bounced Slony on the master and all
>> the remote nodes, but no luck.  Is there a Slony expert out there who
>> can help point me in the right direction?
>> 
>> Version info:
>> 
>> slonik version 2.1.0.b2
>> 
>> psql (9.0.4)
> 
> Slony 2.1 is on 2.1.3 and PostgreSQL 9.0 is on 9.0.13. Is there a
> particular reason why you keep running software that is known to have
> plenty of bugs?
> 
> 
> Jan
> 
> 


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