On 08/24/2015 09:19 AM, Mike James wrote: > We have a slony slave in AWS. During an Amazon maintenance, the instance > was rebooted and now the daemon won't start. The log file has this error > message: > > > 2015-08-24 06:50:03 UTC INFO remoteWorkerThread_1: syncing set 1 with > 102 table(s) from provider 1 > 2015-08-24 06:50:33 UTC ERROR remoteWorkerThread_1_1: error at end of > COPY IN: ERROR: invalid memory alloc request size 1970234207 > CONTEXT: COPY sl_log_1, line 97033: > > I'm not sure whether this is a Postgres error or a slony error. We're > running Postgres 9.3.5 and slony 2.2.1. Any help much appreciated.
Try upgrading to slony 2.2.4 This MIGHT be bug http://www.slony.info/bugzilla/show_bug.cgi?id=327 Memory corruption bugs sometimes manifest themselves with slightly different symptoms. > > Mike > Clutch Holdings, LLC <http://www.clutch.com> Mike James | Manager of > Infrastructure > 267.419.6400, ext 204 | [email protected] <mailto:[email protected]> > 201 S Maple St. | Suite 250 | Ambler, PA 19002 > Clutch.com <http://www.clutch.com> | Twitter > <https://twitter.com/clutchsuccess> | LinkedIn > <https://www.linkedin.com/company/2837209> | YouTube > <https://www.youtube.com/user/clutchsuccess> | Clutch Support Center > <http://clientsupport.clutch.com/> > > The only end to end consumer management platform that empowers > consumer-focused businesses to identify, target, message, and engage > their best customers. > > > > _______________________________________________ > 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
