info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
weird log on postgres instances
19 views
Skip to first unread message
sj86...@gmail.com
Sep 2, 2016, 2:26:26 PM9/2/16
to
Hi, I have a host that has multiple slave pg instances in. All the instances seems to be syncing with out any problem according to Master's pg_stat_replication.
But, I found weird lines from slave's logs, for all the instances in the same host, that looks something like
2016-09-02 06:59:04.783 GMT user= db= host= pid=16788 sessid=57c92338.4194LOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 11:21:18.594 GMT user= db= host= pid=16788 sessid=57c92338.4194FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 11:21:18.612 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8690
2016-09-02 11:21:33.687 GMT user= db= host= pid=28211 sessid=57c960bd.6e33LOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 11:45:46.959 GMT user= db= host= pid=28211 sessid=57c960bd.6e33FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 11:45:46.998 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8770
2016-09-02 11:45:57.129 GMT user= db= host= pid=29300 sessid=57c96675.7274LOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 13:47:43.795 GMT user= db= host= pid=29300 sessid=57c96675.7274FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 13:47:43.812 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8AF0
2016-09-02 13:47:58.907 GMT user= db= host= pid=6203 sessid=57c9830e.183bLOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 14:49:19.615 GMT user= db= host= pid=6203 sessid=57c9830e.183bFATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 14:49:19.643 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8CB0
2016-09-02 14:49:34.734 GMT user= db= host= pid=5999 sessid=57c9917e.176fLOG: started streaming WAL from primary at 0/4E000000 on timeline 1
I can't track down what are the causes for all the slave instances to have above lines in log, but won't affect in replication status..
Any hint or advice can be very helpful, Thanks in advance.
But, I found weird lines from slave's logs, for all the instances in the same host, that looks something like
2016-09-02 06:59:04.783 GMT user= db= host= pid=16788 sessid=57c92338.4194LOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 11:21:18.594 GMT user= db= host= pid=16788 sessid=57c92338.4194FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 11:21:18.612 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8690
2016-09-02 11:21:33.687 GMT user= db= host= pid=28211 sessid=57c960bd.6e33LOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 11:45:46.959 GMT user= db= host= pid=28211 sessid=57c960bd.6e33FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 11:45:46.998 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8770
2016-09-02 11:45:57.129 GMT user= db= host= pid=29300 sessid=57c96675.7274LOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 13:47:43.795 GMT user= db= host= pid=29300 sessid=57c96675.7274FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 13:47:43.812 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8AF0
2016-09-02 13:47:58.907 GMT user= db= host= pid=6203 sessid=57c9830e.183bLOG: started streaming WAL from primary at 0/4E000000 on timeline 1
2016-09-02 14:49:19.615 GMT user= db= host= pid=6203 sessid=57c9830e.183bFATAL: could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
2016-09-02 14:49:19.643 GMT user= db= host= pid=16778 sessid=57c92338.418aLOG: invalid record length at 0/4EEC8CB0
2016-09-02 14:49:34.734 GMT user= db= host= pid=5999 sessid=57c9917e.176fLOG: started streaming WAL from primary at 0/4E000000 on timeline 1
I can't track down what are the causes for all the slave instances to have above lines in log, but won't affect in replication status..
Any hint or advice can be very helpful, Thanks in advance.
0 new messages