Fri Feb 22 10:23:20 PST 2008
- Previous message: [Slony1-general] Slony locks tables that are not even in replication sets?
- Next message: [Slony1-general] Slave died, no access till next week, master logs filling up. What should I do
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I came to work today and seems like the slave server died. (power trip? No it was not connected to a UPS :-() I've not been able to locate/determine if the slave is really dead or otherwise and it's the weekend in Asia and there's no one in the office till Next week. As of now, the master is still trying to contact the slave (slon is still running on the master) and log_1 and log_2 is filling up. And yesterday, I just created a job to manually force the log_switch to occur. So, right now, I'm at a loss as to what i can do.
- Previous message: [Slony1-general] Slony locks tables that are not even in replication sets?
- Next message: [Slony1-general] Slave died, no access till next week, master logs filling up. What should I do
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list