I need some help deciphering these messages. I restarted my replication
today and I'm seeing this error messages.

Slave node:

NOTICE:  truncate cascades to table "daily_invoice_items"
CONTEXT:  SQL statement "TRUNCATE "public"."daily_invoices" CASCADE;"
COPY sl_log_2, line 32581: "1 1690966522 27 2388208268 public
daily_invoices T 0 {}"
2019-07-04 22:20:21 UTC ERROR  remoteWorkerThread_1_1: error writing to
sl_log: SSL error: sslv3 alert unexpected message

2019-07-04 22:20:21 UTC ERROR  remoteWorkerThread_1_1: error ending copy to
sl_log:connection not open

2019-07-04 22:20:21 UTC ERROR  remoteWorkerThread_1_1: error at end of COPY
OUT: 2019-07-04 22:20:21 UTC ERROR  remoteWorkerThread_1_1: error at end of
COPY IN: connection not open


Meanwhile, the master node log shows this message:

NOTICE:  Slony-I: cleanup stale sl_nodelock entry for pid=21542
CONTEXT:  SQL statement "SELECT
"_clients_sb4_reportv3_xmax1".cleanupNodelock()"
PL/pgSQL function _clients_sb4_reportv3_xmax1.cleanupevent(interval) line
82 at PERFORM
NOTICE:  Slony-I: cleanup stale sl_nodelock entry for pid=21543
CONTEXT:  SQL statement "SELECT
"_clients_sb4_reportv3_xmax1".cleanupNodelock()"
PL/pgSQL function _clients_sb4_reportv3_xmax1.cleanupevent(interval) line
82 at PERFORM
NOTICE:  Slony-I: could not lock sl_log_1 - sl_log_1 not truncated
CONTEXT:  PL/pgSQL function
_clients_sb4_reportv3_xmax1.cleanupevent(interval) line 95 at assignment
2019-07-04 22:34:28 UTC INFO   cleanupThread:    0.035 seconds for
cleanupEvent()
2019-07-04 22:34:28 UTC INFO   cleanupThread:    0.041 seconds for vacuuming


Mike JamesManager of Infrastructure267-419-6400, x204
clutch.com
identify • understand • motivate
_______________________________________________
Slony1-general mailing list
Slony1-general@lists.slony.info
http://lists.slony.info/mailman/listinfo/slony1-general

Reply via email to