Mon Aug 24 06:19:47 PDT 2015
- Previous message: [Slony1-general] Dropping a node when the node is gone ?
- Next message: [Slony1-general] Slony replication failed invalid memory alloc request size
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. Mike [image: Clutch Holdings, LLC] <http://www.clutch.com> Mike James | Manager of Infrastructure 267.419.6400, ext 204 | mike.james at clutch.com201 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20150824/fa458215/attachment.htm
- Previous message: [Slony1-general] Dropping a node when the node is gone ?
- Next message: [Slony1-general] Slony replication failed invalid memory alloc request size
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list