[pgpool-general: 4578] Re: find_primary_node failed ...

[Shay Cohavi]

Hi,
Attached in plain text....
please advise..how come the pgpool can't locate the primary node - even
when its up and running...

Thnaks,
cohavisi

On Tue, Mar 22, 2016 at 12:16 PM, Shay Cohavi <cohavisi at gmail.com> wrote:

> Hi,
>
> *(pgpool 3.4.2 and postgresql 9.3.5)*
>
> During stress tests on my setup, PGpool has failed to find_primary node
> after a failover!
> the primary node has started but pgpool keep searched for it.
> (pgpool has be restarted in order find the primary)
>
> can you please review the log (2016-03-22 03:03:XX) and advise why the
> primary node has been been detected??
>
> scenario:
>
> 1. killing the primary node.
> 2. pgpool performed a failover.
> 3. pgpool performs "follow master command".
>
>
> Thanks,
> cohavisi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160328/4c2c323d/attachment-0001.html>
-------------- next part --------------
[2016-03-22 03:02:34.742 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.753 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.764 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.774 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.785 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.795 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.806 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.816 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.826 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.837 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.847 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.858 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.868 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.879 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.890 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.900 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.911 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.921 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.932 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.942 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.953 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.963 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.974 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.984 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:34.995 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.005 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.016 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.026 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.037 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.047 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.058 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.068 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.079 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.089 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.100 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.110 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.121 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.131 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.142 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.152 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.163 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.173 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.184 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.194 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.205 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.215 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.225 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.236 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.246 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.257 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.267 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.278 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.288 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.299 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.309 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.320 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.330 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.341 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.351 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.362 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.372 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.383 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.393 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.404 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.414 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.425 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.435 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.446 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.456 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.467 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.477 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.488 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.498 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.509 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.519 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.530 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.540 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.551 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.561 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.572 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.582 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.593 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.603 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.614 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.624 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.635 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.645 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.656 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.666 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.677 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.687 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.698 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.708 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.719 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.729 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.740 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.750 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.761 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.771 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.782 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.792 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.803 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.813 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.824 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.834 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.845 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.855 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.866 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.876 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.887 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.897 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.908 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.918 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.929 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.939 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.950 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.960 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.971 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.981 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:35.992 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.002 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.013 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.023 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.034 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.044 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.055 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.065 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.076 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.086 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.097 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.107 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.118 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.128 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.139 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.149 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.160 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.170 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.181 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.191 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.202 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.212 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.223 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.233 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.244 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.254 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.265 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.275 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.286 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.296 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.307 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.317 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.328 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.338 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.349 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.359 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.370 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.380 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.391 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.401 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.412 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.422 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.433 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.443 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.454 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.464 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.475 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.485 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.496 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.506 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.516 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.527 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.537 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.548 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.558 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.569 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.579 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.590 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.600 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.611 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.621 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.632 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.642 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.653 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.663 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.674 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.684 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.695 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.705 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.716 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.726 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.737 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.747 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.758 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.768 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.779 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.789 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.800 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.810 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.820 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.831 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.841 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.852 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.862 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.873 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.883 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.894 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.904 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.915 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.925 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.936 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.946 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.957 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.967 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.978 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.988 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:36.999 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:37.009 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:37.020 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:37.030 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:37.041 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:37.051 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:37.062 IST] FATAL:  the database system is starting up
[2016-03-22 03:02:37.067 IST] LOG:  unexpected pageaddr F/1CC24000 in log segment 000000B60000000F000000BC, offset 12730368
[2016-03-22 03:02:37.067 IST] LOG:  consistent recovery state reached at F/BCC23570
[2016-03-22 03:02:37.067 IST] LOG:  database system is ready to accept read only connections
[2016-03-22 03:02:37.070 IST] LOG:  started streaming WAL from primary at F/BC000000 on timeline 182
[2016-03-22 03:03:03.447 IST] LOG:  trigger file found: /home/postgres/databases/fabrix/trigger
[2016-03-22 03:03:03.447 IST] FATAL:  terminating walreceiver process due to administrator command
[2016-03-22 03:03:03.447 IST] LOG:  invalid record length at F/C4000090
[2016-03-22 03:03:03.447 IST] LOG:  redo done at F/C4000028
[2016-03-22 03:03:03.447 IST] LOG:  last completed transaction was at log time 2016-03-22 03:02:58.226188+02
[2016-03-22 03:03:03.447 IST] LOG:  selected new timeline ID: 183
[2016-03-22 03:03:03.476 IST] LOG:  archive recovery complete
[2016-03-22 03:03:03.524 IST] LOG:  database system is ready to accept connections
[2016-03-22 03:03:03.524 IST] LOG:  autovacuum launcher started
-------------- next part --------------
2016-03-22 03:00:09: pid 55911: LOG:  child process with pid: 3156 exits with status 0
2016-03-22 03:00:09: pid 55911: LOG:  child process with pid: 3156 exited with success and will not be restarted
2016-03-22 03:00:09: pid 55911: LOG:  child process with pid: 12166 exits with status 512
2016-03-22 03:00:09: pid 55911: LOG:  fork a new child process with pid: 14061
2016-03-22 03:00:09: pid 55911: LOG:  child process with pid: 4224 exits with status 512
2016-03-22 03:00:09: pid 55911: LOG:  fork a new child process with pid: 14062
2016-03-22 03:00:11: pid 55911: LOG:  child process with pid: 3487 exits with status 512
2016-03-22 03:00:11: pid 55911: LOG:  fork a new child process with pid: 14121
2016-03-22 03:00:11: pid 55911: LOG:  child process with pid: 13564 exits with status 512
2016-03-22 03:00:11: pid 55911: LOG:  fork a new child process with pid: 14122
2016-03-22 03:00:13: pid 55911: LOG:  child process with pid: 14062 exits with status 512
2016-03-22 03:00:13: pid 55911: LOG:  fork a new child process with pid: 14235
2016-03-22 03:00:13: pid 55911: LOG:  child process with pid: 14122 exits with status 512
2016-03-22 03:00:13: pid 55911: LOG:  fork a new child process with pid: 14239
2016-03-22 03:00:15: pid 55911: LOG:  child process with pid: 7849 exits with status 512
2016-03-22 03:00:15: pid 55911: LOG:  fork a new child process with pid: 14257
2016-03-22 03:00:15: pid 55911: LOG:  child process with pid: 6534 exits with status 512
2016-03-22 03:00:15: pid 55911: LOG:  fork a new child process with pid: 14258
2016-03-22 03:00:16: pid 4193: LOG:  received failback request for node_id: 1 from pid [4193]
2016-03-22 03:00:16: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:16: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:16: pid 55911: LOG:  starting fail back. reconnect host 1.1.1.7(5432)
2016-03-22 03:00:16: pid 55911: LOG:  Do not restart children because we are failbacking node id 1 host1.1.1.7 port:5432 and we are in streaming replication mode
2016-03-22 03:00:16: pid 55911: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2016-03-22 03:00:16: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:00:16: pid 55911: LOG:  find_primary_node: primary node id is 0
2016-03-22 03:00:16: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:17: pid 55911: LOG:  failover: set new primary node: 0
2016-03-22 03:00:17: pid 55911: LOG:  failover: set new master node: 0
2016-03-22 03:00:17: pid 55911: LOG:  failback done. reconnect host 1.1.1.7(5432)
2016-03-22 03:00:17: pid 4194: LOG:  worker process received restart request
2016-03-22 03:00:17: pid 14239: LOG:  failback event detected
2016-03-22 03:00:17: pid 14239: DETAIL:  restarting myself
2016-03-22 03:00:17: pid 10127: LOG:  failback event detected
2016-03-22 03:00:17: pid 10127: DETAIL:  restarting myself
2016-03-22 03:00:17: pid 9904: LOG:  failback event detected
2016-03-22 03:00:17: pid 9904: DETAIL:  restarting myself
2016-03-22 03:00:17: pid 6213: LOG:  failback event detected
2016-03-22 03:00:17: pid 6213: DETAIL:  restarting myself
2016-03-22 03:00:17: pid 4279: LOG:  failback event detected
2016-03-22 03:00:17: pid 4279: DETAIL:  restarting myself
2016-03-22 03:00:17: pid 4244: LOG:  failback event detected
2016-03-22 03:00:17: pid 4244: DETAIL:  restarting myself
2016-03-22 03:00:17: pid 3538: LOG:  failback event detected
2016-03-22 03:00:17: pid 3538: DETAIL:  restarting myself
202016-03-22 03:00:17: pid 9527: LOG:  selecting backend connection
2016-03-22 03:00:17: pid 9527: DETAIL:  failback event detected, discarding existing connections
2016-03-22 03:00:17: pid 4269: LOG:  failback event detected
2016-03-22 03:00:17: pid 4269: DETAIL:  restarting myself
2016-03-22 03:00:17: pid 13581: LOG:  failback event detected
2016-03-22 03:00:17: pid 13581: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 4193: LOG:  restart request received in pcp child process
2016-03-22 03:00:18: pid 55911: LOG:  PCP child 4193 exits with status 256 in failover()
2016-03-22 03:00:18: pid 55911: LOG:  fork a new PCP child pid 14466 in failover()
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3377 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14467
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3443 exits with status 256
2016-03-22 03:00:18: pid 14467: LOG:  failback event detected
2016-03-22 03:00:18: pid 14467: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14468
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3472 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14469
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3532 exits with status 512
2016-03-22 03:00:18: pid 14469: LOG:  failback event detected
2016-03-22 03:00:18: pid 14469: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14470
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3538 exits with status 256
2016-03-22 03:00:18: pid 14470: LOG:  failback event detected
2016-03-22 03:00:18: pid 14470: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14471
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3561 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14472
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3603 exits with status 512
2016-03-22 03:00:18: pid 14472: LOG:  failback event detected
2016-03-22 03:00:18: pid 14472: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14473
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3609 exits with status 512
2016-03-22 03:00:18: pid 14473: LOG:  failback event detected
2016-03-22 03:00:18: pid 14473: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14474
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3651 exits with status 512
2016-03-22 03:00:18: pid 14474: LOG:  failback event detected
2016-03-22 03:00:18: pid 14474: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14475
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3687 exits with status 512
2016-03-22 03:00:18: pid 14475: LOG:  failback event detected
2016-03-22 03:00:18: pid 14475: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14476
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3723 exits with status 512
2016-03-22 03:00:18: pid 14476: LOG:  failback event detected
2016-03-22 03:00:18: pid 14476: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14477
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3731 exits with status 512
2016-03-22 03:00:18: pid 14477: LOG:  failback event detected
2016-03-22 03:00:18: pid 14477: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14478
2016-03-22 03:00:18: pid 55911: LOG:  worker child process with pid: 4194 exits with status 256
2016-03-22 03:00:18: pid 14478: LOG:  failback event detected
2016-03-22 03:00:18: pid 14478: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new worker child process with pid: 14479
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4199 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14480
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4208 exits with status 512
2016-03-22 03:00:18: pid 14480: LOG:  failback event detected
2016-03-22 03:00:18: pid 14480: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14482
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4210 exits with status 256
2016-03-22 03:00:18: pid 14482: LOG:  failback event detected
2016-03-22 03:00:18: pid 14482: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14483
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4213 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14484
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4217 exits with status 256
2016-03-22 03:00:18: pid 14484: LOG:  failback event detected
2016-03-22 03:00:18: pid 14484: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14485
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4225 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14486
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4229 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14487
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4236 exits with status 512
2016-03-22 03:00:18: pid 14487: LOG:  failback event detected
2016-03-22 03:00:18: pid 14487: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14488
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4238 exits with status 512
2016-03-22 03:00:18: pid 14488: LOG:  failback event detected
2016-03-22 03:00:18: pid 14488: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14489
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4242 exits with status 512
2016-03-22 03:00:18: pid 14489: LOG:  failback event detected
2016-03-22 03:00:18: pid 14489: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14490
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4244 exits with status 256
2016-03-22 03:00:18: pid 14490: LOG:  failback event detected
2016-03-22 03:00:18: pid 14490: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14491
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4255 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14492
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4256 exits with status 512
2016-03-22 03:00:18: pid 14492: LOG:  failback event detected
2016-03-22 03:00:18: pid 14492: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14493
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4269 exits with status 256
2016-03-22 03:00:18: pid 14493: LOG:  failback event detected
2016-03-22 03:00:18: pid 14493: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14494
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4274 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14495
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4278 exits with status 512
2016-03-22 03:00:18: pid 14495: LOG:  failback event detected
2016-03-22 03:00:18: pid 14495: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14496
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4279 exits with status 256
2016-03-22 03:00:18: pid 14496: LOG:  failback event detected
2016-03-22 03:00:18: pid 14496: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14497
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4280 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14498
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4289 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14499
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4294 exits with status 512
2016-03-22 03:00:18: pid 14499: LOG:  failback event detected
2016-03-22 03:00:18: pid 14499: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14500
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4300 exits with status 512
2016-03-22 03:00:18: pid 14500: LOG:  failback event detected
2016-03-22 03:00:18: pid 14500: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14501
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4301 exits with status 512
2016-03-22 03:00:18: pid 14501: LOG:  failback event detected
2016-03-22 03:00:18: pid 14501: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14502
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4302 exits with status 512
2016-03-22 03:00:18: pid 14502: LOG:  failback event detected
2016-03-22 03:00:18: pid 14502: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14503
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4314 exits with status 512
2016-03-22 03:00:18: pid 14503: LOG:  failback event detected
2016-03-22 03:00:18: pid 14503: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14504
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4316 exits with status 256
2016-03-22 03:00:18: pid 14504: LOG:  failback event detected
2016-03-22 03:00:18: pid 14504: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14505
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4317 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14506
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4328 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14507
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4333 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14508
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4343 exits with status 256
2016-03-22 03:00:18: pid 14508: LOG:  failback event detected
2016-03-22 03:00:18: pid 14508: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14509
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4344 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14510
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4874 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14511
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4875 exits with status 256
2016-03-22 03:00:18: pid 14511: LOG:  failback event detected
2016-03-22 03:00:18: pid 14511: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14512
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 5346 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14513
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 6026 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14514
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 6213 exits with status 256
2016-03-22 03:00:18: pid 14514: LOG:  failback event detected
2016-03-22 03:00:18: pid 14514: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14515
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 6375 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14516
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 6868 exits with status 512
2016-03-22 03:00:18: pid 14516: LOG:  failback event detected
2016-03-22 03:00:18: pid 14516: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14517
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 6920 exits with status 512
2016-03-22 03:00:18: pid 14517: LOG:  failback event detected
2016-03-22 03:00:18: pid 14517: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14518
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 7132 exits with status 512
2016-03-22 03:00:18: pid 14518: LOG:  failback event detected
2016-03-22 03:00:18: pid 14518: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14519
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 7133 exits with status 256
2016-03-22 03:00:18: pid 14519: LOG:  failback event detected
2016-03-22 03:00:18: pid 14519: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14520
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 7875 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14521
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 7981 exits with status 512
2016-03-22 03:00:18: pid 14521: LOG:  failback event detected
2016-03-22 03:00:18: pid 14521: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14522
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8036 exits with status 512
2016-03-22 03:00:18: pid 14522: LOG:  failback event detected
2016-03-22 03:00:18: pid 14522: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8074 exits with status 256
2016-03-22 03:00:18: pid 14523: LOG:  failback event detected
2016-03-22 03:00:18: pid 14523: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14524
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8414 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14525
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8466 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14526
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8786 exits with status 256
2016-03-22 03:00:18: pid 14526: LOG:  failback event detected
2016-03-22 03:00:18: pid 14526: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14527
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8823 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14528
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8955 exits with status 256
2016-03-22 03:00:18: pid 14528: LOG:  failback event detected
2016-03-22 03:00:18: pid 14528: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14529
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 9303 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14530
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 9496 exits with status 256
2016-03-22 03:00:18: pid 14530: LOG:  failback event detected
2016-03-22 03:00:18: pid 14530: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14531
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 9904 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14532
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10127 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14533
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10285 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14534
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10434 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14535
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10497 exits with status 512
2016-03-22 03:00:18: pid 14535: LOG:  failback event detected
2016-03-22 03:00:18: pid 14535: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14536
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10616 exits with status 256
2016-03-22 03:00:18: pid 14536: LOG:  failback event detected
2016-03-22 03:00:18: pid 14536: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14537
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10639 exits with status 256
2016-03-22 03:00:18: pid 13001: LOG:  failback event detected
2016-03-22 03:00:18: pid 13001: DETAIL:  restarting mysel2016-03-22 03:00:18: pid 8037: LOG:  failback event detected
2016-03-22 03:00:18: pid 8037: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 7643: LOG:  failback event detected
2016-03-22 03:00:18: pid 7643: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 14257: LOG:  failback event detected
2016-03-22 03:00:18: pid 14257: DETAIL:  restarting mysel2016-03-22 03:00:18: pid 10408: LOG:  failback event detected
2016-03-22 03:00:18: pid 10408: DETAIL:  restarting mysel202016-03-22 03:00:18: pid 4330: LOG:  failback event detected
2016-03-22 03:00:18: pid 4330: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14538
2016-03-22 03:00:18: pid 4295: LOG:  failback event detected
2016-03-22 03:00:18: pid 4295: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10778 exits with status 256
2016-03-22 03:00:18: pid 13563: LOG:  selecting backend connection
2016-03-22 03:00:18: pid 13563: DETAIL:  failback event detected, discarding existing connections
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14539
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10797 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14541
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3681 exits with status 256
2016-03-22 03:00:18: pid 10232: LOG:  failback event detected
2016-03-22 03:00:18: pid 10232: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14542
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3733 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14543
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4247 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14544
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4253 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14545
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 3690 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14546
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4214 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14547
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4295 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14548
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4306 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14549
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 4330 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14550
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 7643 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14551
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8037 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14552
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8600 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14553
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 8956 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14554
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 9394 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14555
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10232 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14556
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 10408 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14557
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11022 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14558
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11238 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14559
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11343 exits with status 512
2016-03-22 03:00:18: pid 14559: LOG:  failback event detected
2016-03-22 03:00:18: pid 14559: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14560
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11397 exits with status 256
2016-03-22 03:00:18: pid 14560: LOG:  failback event detected
2016-03-22 03:00:18: pid 14560: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14561
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11523 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14562
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11550 exits with status 512
2016-03-22 03:00:18: pid 14562: LOG:  failback event detected
2016-03-22 03:00:18: pid 14562: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14563
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11738 exits with status 512
2016-03-22 03:00:18: pid 14563: LOG:  failback event detected
2016-03-22 03:00:18: pid 14563: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14564
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 11923 exits with status 512
2016-03-22 03:00:18: pid 14564: LOG:  failback event detected
2016-03-22 03:00:18: pid 14564: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14565
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 12134 exits with status 512
2016-03-22 03:00:18: pid 14565: LOG:  failback event detected
2016-03-22 03:00:18: pid 14565: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14566
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 12333 exits with status 512
2016-03-22 03:00:18: pid 14566: LOG:  failback event detected
2016-03-22 03:00:18: pid 14566: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14567
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 12513 exits with status 512
2016-03-22 03:00:18: pid 14567: LOG:  failback event detected
2016-03-22 03:00:18: pid 14567: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14568
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 12668 exits with status 256
2016-03-22 03:00:18: pid 14568: LOG:  failback event detected
2016-03-22 03:00:18: pid 14568: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14569
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 12832 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14570
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13000 exits with status 256
2016-03-22 03:00:18: pid 14570: LOG:  failback event detected
2016-03-22 03:00:18: pid 14570: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14571
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13001 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14572
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13017 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14573
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13018 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14574
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13157 exits with status 512
2016-03-22 03:00:18: pid 14574: LOG:  failback event detected
2016-03-22 03:00:18: pid 14574: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14575
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13174 exits with status 512
2016-03-22 03:00:18: pid 14575: LOG:  failback event detected
2016-03-22 03:00:18: pid 14575: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14576
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13368 exits with status 512
2016-03-22 03:00:18: pid 14576: LOG:  failback event detected
2016-03-22 03:00:18: pid 14576: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14577
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13396 exits with status 256
2016-03-22 03:00:18: pid 14577: LOG:  failback event detected
2016-03-22 03:00:18: pid 14577: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14578
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13397 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14579
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13502 exits with status 512
2016-03-22 03:00:18: pid 14579: LOG:  failback event detected
2016-03-22 03:00:18: pid 14579: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14580
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 13581 exits with status 256
2016-03-22 03:00:18: pid 14580: LOG:  failback event detected
2016-03-22 03:00:18: pid 14580: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14581
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14061 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14582
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14121 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14583
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14239 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14584
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14257 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14585
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14258 exits with status 512
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14586
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14467 exits with status 256
2016-03-22 03:00:18: pid 14586: LOG:  failback event detected
2016-03-22 03:00:18: pid 14586: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14587
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14469 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14588
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14470 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14589
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14472 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14590
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14473 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14591
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14474 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14592
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14475 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14593
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14476 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14594
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14477 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14595
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14478 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14596
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14480 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14597
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14482 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14598
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14484 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14599
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14487 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14600
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14488 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14601
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14489 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14602
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14490 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14603
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14492 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14604
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14493 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14605
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14495 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14606
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14496 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14607
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14499 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14608
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14500 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14609
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14501 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14610
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14502 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14611
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14503 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14612
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14504 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14613
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14508 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14614
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14511 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14615
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14514 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14616
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14516 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14617
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14517 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14618
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14518 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14619
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14519 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14620
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14521 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14621
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14522 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14622
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14523 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14623
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14526 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14624
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14528 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14625
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14530 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14626
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14535 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14627
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14536 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14628
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14541 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14629
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14559 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14630
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14560 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14631
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14562 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14632
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14563 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14633
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14564 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14634
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14565 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14635
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14566 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14636
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14567 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14637
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14568 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14638
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14570 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14639
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14574 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14640
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14575 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14641
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14576 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14642
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14577 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14643
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14579 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14644
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14580 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14645
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 14586 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14646
2016-03-22 03:00:18: pid 9866: LOG:  failback event detected
2016-03-22 03:00:18: pid 9866: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 9866 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14653
2016-03-22 03:00:18: pid 7071: LOG:  failback event detected
2016-03-22 03:00:18: pid 7071: DETAIL:  restarting myself
2016-03-22 03:00:18: pid 55911: LOG:  child process with pid: 7071 exits with status 256
2016-03-22 03:00:18: pid 55911: LOG:  fork a new child process with pid: 14664
2016-03-22 03:00:19: pid 55911: LOG:  child process with pid: 9527 exits with status 512
2016-03-22 03:00:19: pid 55911: LOG:  fork a new child process with pid: 14667
2016-03-22 03:00:19: pid 55911: LOG:  child process with pid: 14644 exits with status 512
2016-03-22 03:00:19: pid 55911: LOG:  fork a new child process with pid: 14670
2016-03-22 03:00:20: pid 55911: LOG:  child process with pid: 13563 exits with status 512
2016-03-22 03:00:20: pid 55911: LOG:  fork a new child process with pid: 14672
2016-03-22 03:00:20: pid 4345: LOG:  failback event detected
2016-03-22 03:00:20: pid 4345: DETAIL:  restarting myself
2016-03-22 03:00:20: pid 55911: LOG:  child process with pid: 4345 exits with status 256
2016-03-22 03:00:20: pid 55911: LOG:  fork a new child process with pid: 14675
2016-03-22 03:00:21: pid 55911: LOG:  child process with pid: 14550 exits with status 512
2016-03-22 03:00:21: pid 55911: LOG:  fork a new child process with pid: 14699
2016-03-22 03:00:22: pid 55911: LOG:  child process with pid: 14653 exits with status 512
2016-03-22 03:00:22: pid 55911: LOG:  fork a new child process with pid: 14834
2016-03-22 03:00:22: pid 11344: LOG:  failback event detected
2016-03-22 03:00:22: pid 11344: DETAIL:  restarting myself
2016-03-22 03:00:22: pid 55911: LOG:  child process with pid: 11344 exits with status 256
2016-03-22 03:00:22: pid 55911: LOG:  fork a new child process with pid: 14837
2016-03-22 03:00:23: pid 55911: LOG:  child process with pid: 14597 exits with status 512
2016-03-22 03:00:23: pid 55911: LOG:  fork a new child process with pid: 14839
2016-03-22 03:00:23: pid 13702: LOG:  failback event detected
2016-03-22 03:00:23: pid 13702: DETAIL:  restarting myself
2016-03-22 03:00:23: pid 55911: LOG:  child process with pid: 12640 exits with status 256
2016-03-22 03:00:23: pid 55911: LOG:  fork a new child process with pid: 14842
2016-03-22 03:00:23: pid 55911: LOG:  child process with pid: 13702 exits with status 256
2016-03-22 03:00:23: pid 55911: LOG:  fork a new child process with pid: 14843
2016-03-22 03:00:24: pid 55911: LOG:  child process with pid: 14593 exits with status 512
2016-03-22 03:00:24: pid 55911: LOG:  fork a new child process with pid: 14860
2016-03-22 03:00:24: pid 3492: LOG:  failback event detected
2016-03-22 03:00:24: pid 3492: DETAIL:  restarting myself
2016-03-22 03:00:24: pid 4231: LOG:  failback event detected
2016-03-22 03:00:24: pid 4231: DETAIL:  restarting myself
2016-03-22 03:00:24: pid 11148: LOG:  failback event detected
2016-03-22 03:00:24: pid 11148: DETAIL:  restarting myself
2016-03-22 03:00:24: pid 11237: LOG:  failback event detected
2016-03-22 03:00:24: pid 11237: DETAIL:  restarting myself
2016-03-22 03:00:24: pid 10495: LOG:  failback event detected
2016-03-22 03:00:24: pid 10495: DETAIL:  restarting myself
2016-03-22 03:00:24: pid 55911: LOG:  child process with pid: 3492 exits with status 256
2016-03-22 03:00:24: pid 55911: LOG:  fork a new child process with pid: 14863
2016-03-22 03:00:24: pid 55911: LOG:  child process with pid: 4231 exits with status 256
2016-03-22 03:00:24: pid 55911: LOG:  fork a new child process with pid: 14864
2016-03-22 03:00:24: pid 55911: LOG:  child process with pid: 7701 exits with status 256
2016-03-22 03:00:24: pid 55911: LOG:  fork a new child process with pid: 14865
2016-03-22 03:00:24: pid 55911: LOG:  child process with pid: 10495 exits with status 256
2016-03-22 03:00:24: pid 55911: LOG:  fork a new child process with pid: 14866
2016-03-22 03:00:24: pid 55911: LOG:  child process with pid: 11148 exits with status 256
2016-03-22 03:00:24: pid 55911: LOG:  fork a new child process with pid: 14867
2016-03-22 03:00:24: pid 55911: LOG:  child process with pid: 11237 exits with status 256
2016-03-22 03:00:24: pid 55911: LOG:  fork a new child process with pid: 14868
2016-03-22 03:00:25: pid 6765: LOG:  failback event detected
2016-03-22 03:00:25: pid 6765: DETAIL:  restarting myself
2016-03-22 03:00:25: pid 13214: LOG:  failback event detected
2016-03-22 03:00:25: pid 13214: DETAIL:  restarting mysel202016-03-22 03:00:25: pid 4273: LOG:  failback event detected
2016-03-22 03:00:25: pid 4273: DETAIL:  restarting mysel202016-03-22 03:00:25: pid 3578: LOG:  failback event detected
2016-03-22 03:00:25: pid 3578: DETAIL:  restarting mysel2016-03-22 03:00:25: pid 13754: LOG:  failback event detected
2016-03-22 03:00:25: pid 13754: DETAIL:  restarting myself
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 3529 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14872
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 3578 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14873
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 3623 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14874
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 3728 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14875
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 4198 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14876
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 4273 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14877
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 6212 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14878
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 6765 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14879
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 7848 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14880
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 8413 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14881
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 10638 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14882
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 13214 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14883
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 13370 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14884
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 13754 exits with status 256
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14885
2016-03-22 03:00:25: pid 55911: LOG:  child process with pid: 14834 exits with status 512
2016-03-22 03:00:25: pid 55911: LOG:  fork a new child process with pid: 14886
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 14646 exits with status 512
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14888
2016-03-22 03:00:26: pid 3516: LOG:  failback event detected
2016-03-22 03:00:26: pid 3516: DETAIL:  restarting myself
2016-03-22 03:00:26: pid 3465: LOG:  failback event detected
2016-03-22 03:00:26: pid 3465: DETAIL:  restarting myself
2016-03-22 03:00:26: pid 4335: LOG:  failback event detected
2016-03-22 03:00:26: pid 4335: DETAIL:  restarting myself
2016-03-22 03:00:26: pid 4239: LOG:  failback event detected
2016-03-22 03:00:26: pid 4239: DETAIL:  restarting myself
f
2016-03-22 03:00:26: pid 9393: LOG:  failback event detected
2016-03-22 03:00:26: pid 9393: DETAIL:  restarting myself
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 3465 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14891
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 3516 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14892
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 3652 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14893
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 3677 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14894
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 4239 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14895
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 4250 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14896
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 4287 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14897
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 4335 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14898
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 9393 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14899
2016-03-22 03:00:26: pid 55911: LOG:  child process with pid: 11147 exits with status 256
2016-03-22 03:00:26: pid 55911: LOG:  fork a new child process with pid: 14900
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 14551 exits with status 512
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 14995
2016-03-22 03:00:27: pid 7670: LOG:  failback event detected
2016-03-22 03:00:27: pid 7670: DETAIL:  restarting myself
2016-03-22 03:00:27: pid 12512: LOG:  failback event detected
2016-03-22 03:00:27: pid 12512: DETAIL:  restarting mysel202016-03-22 03:00:27: pid 3716: LOG:  failback event detected
2016-03-22 03:00:27: pid 3716: DETAIL:  restarting myself
2016-03-22 03:00:27: pid 14235: LOG:  failback event detected
2016-03-22 03:00:27: pid 14235: DETAIL:  restarting myself
2016-03-22 03:00:27: pid 10837: LOG:  failback event detected
2016-03-22 03:00:27: pid 10837: DETAIL:  restarting myself
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 3459 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 14999
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 3680 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15000
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 3716 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15001
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 4196 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15002
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 4258 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15003
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 7670 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15004
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 9333 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15005
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 10837 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15006
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 12451 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15007
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 12512 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15008
2016-03-22 03:00:27: pid 55911: LOG:  child process with pid: 14235 exits with status 256
2016-03-22 03:00:27: pid 55911: LOG:  fork a new child process with pid: 15009
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 14864 exits with status 512
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15054
2016-03-22 03:00:28: pid 12269: LOG:  failback event detected
2016-03-22 03:00:28: pid 12269: DETAIL:  restarting myself
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 3635 exits with status 256
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15058
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 4249 exits with status 256
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15059
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 4285 exits with status 256
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15060
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 5626 exits with status 256
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15061
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 7307 exits with status 256
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15062
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 7467 exits with status 256
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15063
2016-03-22 03:00:28: pid 55911: LOG:  child process with pid: 12269 exits with status 256
2016-03-22 03:00:28: pid 55911: LOG:  fork a new child process with pid: 15064
2016-03-22 03:00:29: pid 55911: LOG:  child process with pid: 14884 exits with status 512
2016-03-22 03:00:29: pid 55911: LOG:  fork a new child process with pid: 15068
2016-03-22 03:00:29: pid 3400: LOG:  failback event detected
2016-03-22 03:00:29: pid 3400: DETAIL:  restarting myself
2016-03-22 03:00:29: pid 55911: LOG:  child process with pid: 3400 exits with status 256
2016-03-22 03:00:29: pid 55911: LOG:  fork a new child process with pid: 15072
2016-03-22 03:00:29: pid 55911: LOG:  child process with pid: 3641 exits with status 256
2016-03-22 03:00:29: pid 55911: LOG:  fork a new child process with pid: 15073
2016-03-22 03:00:30: pid 55911: LOG:  child process with pid: 14900 exits with status 512
2016-03-22 03:00:30: pid 55911: LOG:  fork a new child process with pid: 15075
2016-03-22 03:00:31: pid 55911: LOG:  child process with pid: 15008 exits with status 512
2016-03-22 03:00:31: pid 55911: LOG:  fork a new child process with pid: 15121
2016-03-22 03:00:32: pid 55911: LOG:  child process with pid: 14999 exits with status 512
2016-03-22 03:00:32: pid 55911: LOG:  fork a new child process with pid: 15211
2016-03-22 03:00:33: pid 55911: LOG:  child process with pid: 15075 exits with status 512
2016-03-22 03:00:33: pid 55911: LOG:  fork a new child process with pid: 15215
2016-03-22 03:00:34: pid 14672: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 15256 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:34: pid 55911: LOG:  child process with pid: 15121 exits with status 512
2016-03-22 03:00:34: pid 55911: LOG:  fork a new child process with pid: 15257
2016-03-22 03:00:34: pid 13926: LOG:  failback event detected
2016-03-22 03:00:34: pid 13926: DETAIL:  restarting myself
2016-03-22 03:00:34: pid 55911: LOG:  child process with pid: 13926 exits with status 256
2016-03-22 03:00:34: pid 55911: LOG:  fork a new child process with pid: 15261
2016-03-22 03:00:35: pid 55911: LOG:  child process with pid: 14583 exits with status 512
2016-03-22 03:00:35: pid 55911: LOG:  fork a new child process with pid: 15262
2016-03-22 03:00:36: pid 55911: LOG:  child process with pid: 14573 exits with status 512
2016-03-22 03:00:36: pid 55911: LOG:  fork a new child process with pid: 15289
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 14872 exits with status 512
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15389
2016-03-22 03:00:37: pid 6746: LOG:  failback event detected
2016-03-22 03:00:37: pid 6746: DETAIL:  restarting myself
2016-03-22 03:00:37: pid 12350: LOG:  failback event detected
2016-03-22 03:00:37: pid 12350: DETAIL:  restarting myself
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 6746 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15392
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 12350 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15393
2016-03-22 03:00:37: pid 4254: LOG:  failback event detected
2016-03-22 03:00:37: pid 4254: DETAIL:  restarting myself
2016-03-22 03:00:37: pid 11944: LOG:  failback event detected
2016-03-22 03:00:37: pid 11944: DETAIL:  restarting mysel2016-03-22 03:00:37: pid 4573: LOG:  failback event detected
2016-03-22 03:00:37: pid 4573: DETAIL:  restarting myself
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 4230 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15397
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 3608 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15398
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 4219 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15399
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 4220 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15400
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 4254 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15401
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 4310 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15402
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 4348 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15403
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 4573 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15404
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 7365 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15405
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 9867 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15406
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 11944 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15407
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 12268 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15408
2016-03-22 03:00:37: pid 55911: LOG:  child process with pid: 12349 exits with status 256
2016-03-22 03:00:37: pid 55911: LOG:  fork a new child process with pid: 15409
2016-03-22 03:00:37: pid 14466: LOG:  received failback request for node_id: 1 from pid [14466]
2016-03-22 03:00:37: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:37: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:37: pid 55911: LOG:  invalid failback request, status: [2] of node id : 1 is invalid for failback
2016-03-22 03:00:37: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:37: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:37: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:38: pid 55911: LOG:  child process with pid: 15262 exits with status 512
2016-03-22 03:00:38: pid 55911: LOG:  fork a new child process with pid: 15414
2016-03-22 03:00:38: pid 55911: LOG:  child process with pid: 15289 exits with status 512
2016-03-22 03:00:38: pid 55911: LOG:  fork a new child process with pid: 15416
2016-03-22 03:00:38: pid 55911: LOG:  child process with pid: 14587 exits with status 512
2016-03-22 03:00:38: pid 55911: LOG:  fork a new child process with pid: 15417
2016-03-22 03:00:41: pid 3552: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3552: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 5347: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 5347: DETAI2016-03-22 03:00:41: pid 6959: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 6959: DETAI2016-03-22 03:00:41: pid 3722: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3722: DETAI2016-03-22 03:00:41: pid 6959: LOG:  received degenerate backend request for node_id: 0 from pid [6959]
2016-03-22 03:00:41: pid 3722: LOG:  received degenerate backend request for node_id: 0 from pid [3722]
2016-03-22 03:00:41: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:41: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:41: pid 4304: LOG:  received degenerate backend request for node_id: 0 from pid [4304]
2016-03-22 03:00:41: pid 4305: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4305: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4305: LOG:  received degenerate backend request for node_id: 0 from pid [4305]
2016-03-22 03:00:41: pid 4206: LOG:  received degenerate backend request for node_id: 0 from pid [4206]
2016-03-22 03:00:41: pid 4312: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4312: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3509: LOG:  received degenerate backend request for node_id: 0 from pid [3509]
2016-03-22 03:00:41: pid 4312: LOG:  received degenerate backend request for node_id: 0 from pid [4312]
2016-03-22 03:00:41: pid 3445: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3445: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3445: LOG:  received degenerate backend request for node_id: 0 from pid [3445]
2016-03-22 03:00:41: pid 3419: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3419: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3419: LOG:  received degenerate backend request for node_id: 0 from pid [3419]
2016-03-22 03:00:41: pid 3455: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3455: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3455: LOG:  received degenerate backend request for node_id: 0 from pid [3455]
2016-03-22 03:00:41: pid 3699: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3699: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3699: LOG:  received degenerate backend request for node_id: 0 from pid [3699]
2016-03-22 03:00:41: pid 3441: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3441: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3441: LOG:  received degenerate backend request for node_id: 0 from pid [3441]
2016-03-22 03:00:41: pid 14672: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 14672: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 14672: LOG:  received degenerate backend request for node_id: 0 from pid [14672]
2016-03-22 03:00:41: pid 3741: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3741: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3741: LOG:  received degenerate backend request for node_id: 0 from pid [3741]
2016-03-22 03:00:41: pid 3460: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3460: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3460: LOG:  received degenerate backend request for node_id: 0 from pid [3460]
2016-03-22 03:00:41: pid 3715: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3715: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3715: LOG:  received degenerate backend request for node_id: 0 from pid [3715]
2016-03-22 03:00:41: pid 3572: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3572: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3572: LOG:  received degenerate backend request for node_id: 0 from pid [3572]
2016-03-22 03:00:41: pid 3569: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3569: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3569: LOG:  received degenerate backend request for node_id: 0 from pid [3569]
2016-03-22 03:00:41: pid 3473: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3473: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3473: LOG:  received degenerate backend request for node_id: 0 from pid [3473]
2016-03-22 03:00:41: pid 3490: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3490: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3490: LOG:  received degenerate backend request for node_id: 0 from pid [3490]
2016-03-22 03:00:41: pid 3670: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3670: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3670: LOG:  received degenerate backend request for node_id: 0 from pid [3670]
2016-03-22 03:00:41: pid 3412: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3412: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3412: LOG:  received degenerate backend request for node_id: 0 from pid [3412]
2016-03-22 03:00:41: pid 3570: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3570: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3570: LOG:  received degenerate backend request for node_id: 0 from pid [3570]
2016-03-22 03:00:41: pid 3364: LOG:  received degenerate backend request for node_id: 0 from pid [3364]
2016-03-22 03:00:41: pid 3559: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3559: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3559: LOG:  received degenerate backend request for node_id: 0 from pid [3559]
2016-03-22 03:00:41: pid 4349: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4349: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4349: LOG:  received degenerate backend request for node_id: 0 from pid [4349]
2016-03-22 03:00:41: pid 3702: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3702: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3702: LOG:  received degenerate backend request for node_id: 0 from pid [3702]
2016-03-22 03:00:41: pid 3448: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3448: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3448: LOG:  received degenerate backend request for node_id: 0 from pid [3448]
2016-03-22 03:00:41: pid 3645: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3645: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3645: LOG:  received degenerate backend request for node_id: 0 from pid [3645]
2016-03-22 03:00:41: pid 4209: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4209: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4209: LOG:  received degenerate backend request for node_id: 0 from pid [4209]
2016-03-22 03:00:41: pid 3712: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3712: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3712: LOG:  received degenerate backend request for node_id: 0 from pid [3712]
2016-03-22 03:00:41: pid 3589: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3589: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3589: LOG:  received degenerate backend request for node_id: 0 from pid [3589]
2016-03-22 03:00:41: pid 3587: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3587: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3587: LOG:  received degenerate backend request for node_id: 0 from pid [3587]
2016-03-22 03:00:41: pid 3730: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3730: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3730: LOG:  received degenerate backend request for node_id: 0 from pid [3730]
2016-03-22 03:00:41: pid 3688: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3688: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4277: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4277: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3688: LOG:  received degenerate backend request for node_id: 0 from pid [3688]
2016-03-22 03:00:41: pid 4277: LOG:  received degenerate backend request for node_id: 0 from pid [4277]
2016-03-22 03:00:41: pid 3454: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3454: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3454: LOG:  received degenerate backend request for node_id: 0 from pid [3454]
2016-03-22 03:00:41: pid 4329: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4329: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4329: LOG:  received degenerate backend request for node_id: 0 from pid [4329]
2016-03-22 03:00:41: pid 3610: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3610: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3610: LOG:  received degenerate backend request for node_id: 0 from pid [3610]
2016-03-22 03:00:41: pid 3425: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3425: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3425: LOG:  received degenerate backend request for node_id: 0 from pid [3425]
2016-03-22 03:00:41: pid 3737: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3737: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3737: LOG:  received degenerate backend request for node_id: 0 from pid [3737]
2016-03-22 03:00:41: pid 3550: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3550: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3550: LOG:  received degenerate backend request for node_id: 0 from pid [3550]
2016-03-22 03:00:41: pid 4251: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4251: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4251: LOG:  received degenerate backend request for node_id: 0 from pid [4251]
2016-03-22 03:00:41: pid 3564: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3564: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3564: LOG:  received degenerate backend request for node_id: 0 from pid [3564]
2016-03-22 03:00:41: pid 3549: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3549: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3549: LOG:  received degenerate backend request for node_id: 0 from pid [3549]
2016-03-22 03:00:41: pid 3696: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3696: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3696: LOG:  received degenerate backend request for node_id: 0 from pid [3696]
2016-03-22 03:00:41: pid 3458: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3458: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3458: LOG:  received degenerate backend request for node_id: 0 from pid [3458]
2016-03-22 03:00:41: pid 3442: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3442: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3442: LOG:  received degenerate backend request for node_id: 0 from pid [3442]
2016-03-22 03:00:41: pid 3431: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3431: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3431: LOG:  received degenerate backend request for node_id: 0 from pid [3431]
2016-03-22 03:00:41: pid 3632: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3632: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3632: LOG:  received degenerate backend request for node_id: 0 from pid [3632]
2016-03-22 03:00:41: pid 3453: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3453: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3453: LOG:  received degenerate backend request for node_id: 0 from pid [3453]
2016-03-22 03:00:41: pid 3447: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3447: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3447: LOG:  received degenerate backend request for node_id: 0 from pid [3447]
2016-03-22 03:00:41: pid 3408: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3408: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3408: LOG:  received degenerate backend request for node_id: 0 from pid [3408]
2016-03-22 03:00:41: pid 3729: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3729: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3729: LOG:  received degenerate backend request for node_id: 0 from pid [3729]
2016-03-22 03:00:41: pid 3611: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3611: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3611: LOG:  received degenerate backend request for node_id: 0 from pid [3611]
2016-03-22 03:00:41: pid 3675: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3675: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3675: LOG:  received degenerate backend request for node_id: 0 from pid [3675]
2016-03-22 03:00:41: pid 3409: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3409: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3409: LOG:  received degenerate backend request for node_id: 0 from pid [3409]
2016-03-22 03:00:41: pid 3528: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3528: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3528: LOG:  received degenerate backend request for node_id: 0 from pid [3528]
2016-03-22 03:00:41: pid 3378: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3378: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3378: LOG:  received degenerate backend request for node_id: 0 from pid [3378]
2016-03-22 03:00:41: pid 3672: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3672: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3672: LOG:  received degenerate backend request for node_id: 0 from pid [3672]
2016-03-22 03:00:41: pid 3593: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3593: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3593: LOG:  received degenerate backend request for node_id: 0 from pid [3593]
2016-03-22 03:00:41: pid 3381: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3381: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3381: LOG:  received degenerate backend request for node_id: 0 from pid [3381]
2016-03-22 03:00:41: pid 4351: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4351: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3522: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3522: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4351: LOG:  received degenerate backend request for node_id: 0 from pid [4351]
2016-03-22 03:00:41: pid 3522: LOG:  received degenerate backend request for node_id: 0 from pid [3522]
2016-03-22 03:00:41: pid 3599: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3599: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3599: LOG:  received degenerate backend request for node_id: 0 from pid [3599]
2016-03-22 03:00:41: pid 3530: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3530: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3530: LOG:  received degenerate backend request for node_id: 0 from pid [3530]
2016-03-22 03:00:41: pid 3420: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3420: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3420: LOG:  received degenerate backend request for node_id: 0 from pid [3420]
2016-03-22 03:00:41: pid 15404: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 3583: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3583: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 15404: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 15404: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 3583: LOG:  received degenerate backend request for node_id: 0 from pid [3583]
2016-03-22 03:00:41: pid 3606: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3606: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3606: LOG:  received degenerate backend request for node_id: 0 from pid [3606]
2016-03-22 03:00:41: pid 3586: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3586: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3586: LOG:  received degenerate backend request for node_id: 0 from pid [3586]
2016-03-22 03:00:41: pid 3388: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3388: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3388: LOG:  received degenerate backend request for node_id: 0 from pid [3388]
2016-03-22 03:00:41: pid 3367: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3367: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3402: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3402: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3402: LOG:  received degenerate backend request for node_id: 0 from pid [3402]
2016-03-22 03:00:41: pid 3566: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3566: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3566: LOG:  received degenerate backend request for node_id: 0 from pid [3566]
2016-03-22 03:00:41: pid 3397: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3397: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3397: LOG:  received degenerate backend request for node_id: 0 from pid [3397]
2016-03-22 03:00:41: pid 3476: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3476: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3476: LOG:  received degenerate backend request for node_id: 0 from pid [3476]
2016-03-22 03:00:41: pid 3393: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3393: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3393: LOG:  received degenerate backend request for node_id: 0 from pid [3393]
2016-03-22 03:00:41: pid 3627: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3627: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3627: LOG:  received degenerate backend request for node_id: 0 from pid [3627]
2016-03-22 03:00:41: pid 3466: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3466: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3466: LOG:  received degenerate backend request for node_id: 0 from pid [3466]
2016-03-22 03:00:41: pid 3499: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3499: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3499: LOG:  received degenerate backend request for node_id: 0 from pid [3499]
2016-03-22 03:00:41: pid 3717: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3717: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3717: LOG:  received degenerate backend request for node_id: 0 from pid [3717]
2016-03-22 03:00:41: pid 3423: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3423: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3423: LOG:  received degenerate backend request for node_id: 0 from pid [3423]
2016-03-22 03:00:41: pid 3577: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3577: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3577: LOG:  received degenerate backend request for node_id: 0 from pid [3577]
2016-03-22 03:00:41: pid 3365: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3365: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3365: LOG:  received degenerate backend request for node_id: 0 from pid [3365]
2016-03-22 03:00:41: pid 4308: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4308: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4308: LOG:  received degenerate backend request for node_id: 0 from pid [4308]
2016-03-22 03:00:41: pid 3618: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3618: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3618: LOG:  received degenerate backend request for node_id: 0 from pid [3618]
2016-03-22 03:00:41: pid 3452: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3452: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3452: LOG:  received degenerate backend request for node_id: 0 from pid [3452]
2016-03-22 03:00:41: pid 3407: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3407: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3407: LOG:  received degenerate backend request for node_id: 0 from pid [3407]
2016-03-22 03:00:41: pid 3406: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3406: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3406: LOG:  received degenerate backend request for node_id: 0 from pid [3406]
2016-03-22 03:00:41: pid 3411: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3411: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3411: LOG:  received degenerate backend request for node_id: 0 from pid [3411]
2016-03-22 03:00:41: pid 15404: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 15404: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 15404: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 4309: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 4309: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 4309: LOG:  received degenerate backend request for node_id: 0 from pid [4309]
2016-03-22 03:00:41: pid 3373: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3373: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3373: LOG:  received degenerate backend request for node_id: 0 from pid [3373]
2016-03-22 03:00:41: pid 3450: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3450: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3450: LOG:  received degenerate backend request for node_id: 0 from pid [3450]
2016-03-22 03:00:41: pid 3370: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3370: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3370: LOG:  received degenerate backend request for node_id: 0 from pid [3370]
2016-03-22 03:00:41: pid 3396: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3396: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3396: LOG:  received degenerate backend request for node_id: 0 from pid [3396]
2016-03-22 03:00:41: pid 15414: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 15414: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 15414: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 3477: LOG:  reading and processing packets
2016-03-22 03:00:41: pid 3477: DETAIL:  postmaster on DB node 0 was shutdown by administrative command
2016-03-22 03:00:41: pid 3477: LOG:  received degenerate backend request for node_id: 0 from pid [3477]
2016-03-22 03:00:41: pid 15063: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 15063: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 15063: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14875: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14875: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14875: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 15398: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 15398: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 15398: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14533: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14533: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14533: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14880: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14880: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14880: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14624: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14624: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14624: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14624: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14624: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14624: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14624: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14624: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14624: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14874: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14874: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14874: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14874: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14874: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14874: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 15398: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 15398: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 15398: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14609: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14609: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14609: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14637: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14637: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14637: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14525: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14525: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14525: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14699: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14699: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14699: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14837: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14837: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14837: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14837: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14837: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14837: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14837: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14837: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14837: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14893: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14893: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14893: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 4315: LOG:  failback event detected
2016-03-22 03:00:41: pid 4315: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 8227: LOG:  failback event detected
2016-03-22 03:00:41: pid 8227: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 4218: LOG:  failback event detected
2016-03-22 03:00:41: pid 4218: DETAIL:  restarting myself
f
2016-03-22 03:00:41: pid 3475: LOG:  failback event detected
2016-03-22 03:00:41: pid 3475: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 4288: LOG:  failback event detected
2016-03-22 03:00:41: pid 4288: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 4226: LOG:  failback event detected
2016-03-22 03:00:41: pid 4226: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 4227: LOG:  failback event detected
2016-03-22 03:00:41: pid 4227: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 3650: LOG:  failback event detected
2016-03-22 03:00:41: pid 3650: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14515: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14515: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14515: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14879: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14837: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14837: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14837: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14837: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14837: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14629: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14629: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14629: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14893: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14893: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14893: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 4315: LOG:  failback event detected
2016-03-22 03:00:41: pid 4315: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 8227: LOG:  failback event detected
2016-03-22 03:00:41: pid 8227: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 4218: LOG:  failback event detected
2016-03-22 03:00:41: pid 4218: DETAIL:  restarting myself
f
2016-03-22 03:00:41: pid 3475: LOG:  failback event detected
2016-03-22 03:00:41: pid 3475: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 4288: LOG:  failback event detected
2016-03-22 03:00:41: pid 4288: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 4226: LOG:  failback event detected
2016-03-22 03:00:41: pid 4226: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 4227: LOG:  failback event detected
2016-03-22 03:00:41: pid 4227: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 3650: LOG:  failback event detected
2016-03-22 03:00:41: pid 3650: DETAIL:  restarting myself
2016-03-22 03:00:41: pid 14594: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14594: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14594: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14515: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14515: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14515: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14879: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14879: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14879: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14622: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14622: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14622: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14545: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14545: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14545: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14520: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14520: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14520: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14468: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14468: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14468: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 14513: LOG:  pool_read_kind: error message from master backend:the database system is shutting down
2016-03-22 03:00:41: pid 14513: ERROR:  unable to read message kind
2016-03-22 03:00:41: pid 14513: DETAIL:  kind does not match between master(45) slot[1] (52)
2016-03-22 03:00:41: pid 55911: LOG:  starting degeneration. shutdown host 1.1.1.6(5432)
2016-03-22 03:00:41: pid 55911: LOG:  Restart all children
2016-03-22 03:00:41: pid 3365: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3370: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3378: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3381: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3388: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3393: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3396: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15417: LOG:  child process received shutdown request signal 322016-03-22 03:00:41: pid 3409: LOG:  child process received shutdown request signal 322016-03-22 03:00:41: pid 14561: LOG:  child process received shutdown request signal 22016-03-22 03:00:41: pid 3431: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14468: LOG:  child process received shutdown request signal 322016-03-22 03:00:41: pid 14547: LOG:  child process received shutdown request signal 2016-03-22 03:00:41: pid 3455: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3466: LOG:  child process received shutdown request signal 3
22016-03-22 03:00:41: pid 3476: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3450: LOG:  child process received shutdown request signal 3

2016-03-22 03:00:41: pid 14866: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3490: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15404: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15004: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3522: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14539: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14602: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14628: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15063: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3549: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14896: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14590: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3586: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3606: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3570: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14558: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14995: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3420: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14534: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4293: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15054: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3559: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3594: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3550: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3688: LOG:  child process received shutdown request signal 3

2016-03-22 03:00:41: pid 3670: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4329: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14843: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 6867: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3589: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14603: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4304: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14873: LOG:  child process received shutdown request signal 322016-03-22 03:00:41: pid 14491: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15003: LOG:  child process received shutdown request signal 32016-03-22 03:00:41: pid 3577: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3627: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3599: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3722: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 55911: LOG:  execute command: /etc/pgpool-II/recovery/failove2016-03-22 03:00:41: pid 3715: LOG:  child proces2016-03-22 03:00:41: pid 3712: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3739: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14548: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14612: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4313: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14557: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3583: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4349: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3611: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4277: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3699: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 5731: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14604: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14672: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14637: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3552: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3477: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3587: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4309: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14675: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14610: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3645: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14589: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15405: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14860: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14584: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3729: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4251: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 6959: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4351: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14537: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14639: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3694: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3696: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15073: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14485: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3679: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14553: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15409: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14524: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14877: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3672: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15062: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15393: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14533: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14592: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14898: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3630: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15005: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14554: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3618: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14632: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14627: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14882: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 10128: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14625: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14607: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15064: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14606: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14525: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14837: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14626: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14531: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14585: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14897: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 4308: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 5347: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14885: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14549: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14617: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14670: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3717: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14507: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14619: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14881: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14618: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14571: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14546: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14505: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14510: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15407: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14621: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14513: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14471: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14642: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14613: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14532: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14578: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14509: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14620: LOG:  child process received shutdown request signal 322016-03-22 03:00:41: pid 14867: LOG:  child process received shutdown request signal 322016-03-22 03:00:41: pid 15061: LOG:  child process received shutdown request signal 32016-03-22 03:00:41: pid 14591: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14616: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14582: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14498: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14883: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14545: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14623: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14874: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14640: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14629: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14538: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14638: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14641: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14895: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15397: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14596: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15389: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14842: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15261: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15403: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15402: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15211: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3730: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14633: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14608: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 6596: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15001: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14543: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15416: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14868: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14605: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14600: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15060: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15059: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14569: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14622: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14594: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14886: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14615: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14645: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14699: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14544: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14624: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15058: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14634: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14611: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14664: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14878: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14893: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15000: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15401: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14614: LOG:  child process received shutdown request signal 3
+ FALLING_NODE=0
+ OLDPRIMARY_NODE=0
+ NEW_PRIMARY=1.1.1.7
+ PGDATA=/home/postgres/databases/fabrix
+ PGHOME=/home/postgres
+ log 'failover to 1.1.1.7 host. creating /home/postgres/databases/fabrix/trigger file.'
+ '[' '!' 'failover to 1.1.1.7 host. creating /home/postgres/databases/fabrix/trigger file.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:41.92] - failover to 1.1.1.7 host. creating /home/postgres/databases/fabrix/trigger file.'
+ '[' 0 = 0 ']'
+ '[' 0 -eq 0 ']'
+ su postgres -c 'ssh -T postgres at 1.1.1.7 touch /home/postgres/databases/fabrix/trigger'
+ exit 0
2016-03-22 03:00:42: pid 55911: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2016-03-22 03:00:42: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:00:42: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:00:42: pid 14479: ERROR:  failed to authenticate
2016-03-22 03:00:42: pid 14479: DETAIL:  invalid authentication message response type, Expecting 'R' and received 'E'
2016-03-22 03:00:43: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:00:43: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:00:43: pid 14479: ERROR:  Failed to check replication time lag
2016-03-22 03:00:43: pid 14479: DETAIL:  No persistent db connection for the node 0
2016-03-22 03:00:43: pid 14479: HINT:  check sr_check_user and sr_check_password
2016-03-22 03:00:43: pid 14479: CONTEXT:  while checking replication time lag
2016-03-22 03:00:43: pid 14479: ERROR:  failed to authenticate
2016-03-22 03:00:41: pid 15403: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15402: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15211: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 3730: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14633: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14608: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 6596: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15001: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14543: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15416: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14868: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14605: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14600: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15060: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15059: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14569: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14622: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14594: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14886: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14615: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14645: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14699: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14544: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14624: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15058: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14634: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14611: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14664: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14878: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14893: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14664: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14878: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14893: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15000: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 15401: LOG:  child process received shutdown request signal 3
2016-03-22 03:00:41: pid 14614: LOG:  child process received shutdown request signal 3
+ FALLING_NODE=0
+ OLDPRIMARY_NODE=0
+ NEW_PRIMARY=1.1.1.7
+ PGDATA=/home/postgres/databases/fabrix
+ PGHOME=/home/postgres
+ log 'failover to 1.1.1.7 host. creating /home/postgres/databases/fabrix/trigger file.'
+ '[' '!' 'failover to 1.1.1.7 host. creating /home/postgres/databases/fabrix/trigger file.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:41.92] - failover to 1.1.1.7 host. creating /home/postgres/databases/fabrix/trigger file.'
+ '[' 0 = 0 ']'
+ '[' 0 -eq 0 ']'
+ su postgres -c 'ssh -T postgres at 1.1.1.7 touch /home/postgres/databases/fabrix/trigger'
+ exit 0
2016-03-22 03:00:42: pid 55911: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2016-03-22 03:00:42: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:00:42: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:00:42: pid 14479: ERROR:  failed to authenticate
2016-03-22 03:00:42: pid 14479: DETAIL:  invalid authentication message response type, Expecting 'R' and received 'E'
2016-03-22 03:00:43: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:00:43: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:00:43: pid 14479: ERROR:  Failed to check replication time lag
2016-03-22 03:00:43: pid 14479: DETAIL:  No persistent db connection for the node 0
2016-03-22 03:00:43: pid 14479: HINT:  check sr_check_user and sr_check_password
2016-03-22 03:00:43: pid 14479: CONTEXT:  while checking replication time lag
2016-03-22 03:00:43: pid 14479: ERROR:  failed to authenticate
2016-03-22 03:00:43: pid 14479: DETAIL:  invalid authentication message response type, Expecting 'R' and received 'E'
2016-03-22 03:00:44: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:00:44: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:00:44: pid 55911: LOG:  find_primary_node: primary node id is 1
2016-03-22 03:00:44: pid 55911: LOG:  starting follow degeneration. shutdown host 1.1.1.6(5432)
2016-03-22 03:00:44: pid 55911: LOG:  failover: 1 follow backends have been degenerated
2016-03-22 03:00:44: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:44: pid 15674: LOG:  start triggering follow command.
2016-03-22 03:00:44: pid 15674: LOG:  execute command: /etc/pgpool-II/recovery/failback.sh 0 1.1.1.6 1.1.1.7 1 0 /home/postgres/databases/fabrix /home/postgres/databases/fabrix 5432
+ NODE_ID=0
+ HOST_NAME=1.1.1.6
+ NEW_MASTER_HOSTNAME_CHECK=1.1.1.7
+ NEW_MASTER_NODE_ID=1
+ OLD_MASTER_NODE_ID=0
+ DATABASE_CLUSTER_PATH=/home/postgres/databases/fabrix
+ MASTER_CLUSTER_PATH=/home/postgres/databases/fabrix
+ NEW_MASTER_PORT=5432
+ PGHOME=/home/postgres
+ ARCH=/home/postgres/archive
+ R_USER=fabrix
+ R_PASSWORD=fabrix
+ PG_STOP_COUNTER=300
++ cat /etc/pgpool-II/pgpool.conf
++ grep backend_hostname1
++ grep -v '#'
++ awk -F = '{print $2}'
++ tr -d ''\'''
+ NEW_MASTER_HOSTNAME=1.1.1.7
+ log ''
+ '[' '!' '' ']'
+ return 0
+ log '-------------------------- failback of 1.1.1.6 --------------------------'
+ '[' '!' '-------------------------- failback of 1.1.1.6 --------------------------' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.07] - -------------------------- failback of 1.1.1.6 --------------------------'
+ log ''
+ '[' '!' '' ']'
+ return 0
+ log 'new master hostname --reported by pgpool-- : 1.1.1.7'
+ '[' '!' 'new master hostname --reported by pgpool-- : 1.1.1.7' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.07] - new master hostname --reported by pgpool-- : 1.1.1.7'
+ log 'node_id: 0'
+ '[' '!' 'node_id: 0' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.07] - node_id: 0'
+ log 'hostname: 1.1.1.6'
+ '[' '!' 'hostname: 1.1.1.6' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.08] - hostname: 1.1.1.6'
+ log 'hostname of new master: 1.1.1.7'
+ '[' '!' 'hostname of new master: 1.1.1.7' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.08] - hostname of new master: 1.1.1.7'
+ log 'new master node id: 1'
+ '[' '!' 'new master node id: 1' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.08] - new master node id: 1'
+ log 'old master node id: 0'
+ '[' '!' 'old master node id: 0' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.08] - old master node id: 0'
+ log 'database cluster path: /home/postgres/databases/fabrix'
+ '[' '!' 'database cluster path: /home/postgres/databases/fabrix' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.08] - database cluster path: /home/postgres/databases/fabrix'
+ log 'master database cluster path: /home/postgres/databases/fabrix'
+ '[' '!' 'master database cluster path: /home/postgres/databases/fabrix' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.08] - master database cluster path: /home/postgres/databases/fabrix'
+ log 'master port: 5432'
+ '[' '!' 'master port: 5432' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.08] - master port: 5432'
+ su - postgres -c 'ssh 1.1.1.6 '\''
if [ -f /home/postgres/recovery.lock ];then
    rm -rf /home/postgres/recovery.lock;
    exit 0
else
    exit 99
fi'\'''
+ RET_VAL=99
+ log 'return value is : 99'
+ '[' '!' 'return value is : 99' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.25] - return value is : 99'
+ '[' 99 -eq 0 ']'
+ log 'deleting /home/postgres/pg.control file on 1.1.1.6 in order to monitor postgres via monit'
+ '[' '!' 'deleting /home/postgres/pg.control file on 1.1.1.6 in order to monitor postgres via monit' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.25] - deleting /home/postgres/pg.control file on 1.1.1.6 in order to monitor postgres via monit'
+ su - postgres -c 'ssh 1.1.1.6 '\''rm -f /home/postgres/pg.control'\'''
2016-03-22 03:00:44: pid 14479: ERROR:  Failed to check replication time lag
2016-03-22 03:00:44: pid 14479: DETAIL:  No persistent db connection for the node 0
2016-03-22 03:00:44: pid 14479: HINT:  check sr_check_user and sr_check_password
2016-03-22 03:00:44: pid 14479: CONTEXT:  while checking replication time lag
2016-03-22 03:00:44: pid 14479: ERROR:  failed to authenticate
2016-03-22 03:00:44: pid 14479: DETAIL:  invalid authentication message response type, Expecting 'R' and received 'E'
+ log 'deleting Archive directory in 1.1.1.6.'
+ '[' '!' 'deleting Archive directory in 1.1.1.6.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.43] - deleting Archive directory in 1.1.1.6.'
+ su - postgres -c 'ssh 1.1.1.6 '\''rm -rf /home/postgres/archive/*'\'''
2016-03-22 03:00:44: pid 55911: LOG:  failover: set new primary node: 1
2016-03-22 03:00:44: pid 55911: LOG:  failover: set new master node: 1
2016-03-22 03:00:44: pid 15838: LOG:  failback event detected
2016-03-22 03:00:44: pid 15838: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15839: LOG:  failback event detected
2016-03-22 03:00:44: pid 15839: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15841: LOG:  failback event detected
2016-03-22 03:00:44: pid 15841: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15843: LOG:  failback event detected
2016-03-22 03:00:44: pid 15843: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15845: LOG:  failback event detected
2016-03-22 03:00:44: pid 15845: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15848: LOG:  failback event detected
2016-03-22 03:00:44: pid 15848: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15849: LOG:  failback event detected
2016-03-22 03:00:44: pid 15849: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15850: LOG:  failback event detected
2016-03-22 03:00:44: pid 15850: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15853: LOG:  failback event detected
2016-03-22 03:00:44: pid 15853: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15856: LOG:  failback event detected
2016-03-22 03:00:44: pid 15856: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15842: ERROR:  unable to flush data to frontend
2016-03-22 03:00:44: pid 15858: LOG:  failback event detected
2016-03-22 03:00:44: pid 15858: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15844: ERROR:  unable to flush data to frontend
2016-03-22 03:00:44: pid 15860: LOG:  failback event detected
2016-03-22 03:00:44: pid 15860: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15846: ERROR:  unable to flush data to frontend
2016-03-22 03:00:44: pid 15861: LOG:  failback event detected
2016-03-22 03:00:44: pid 15861: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15847: ERROR:  unable to flush data to frontend
2016-03-22 03:00:44: pid 15863: LOG:  failback event detected
2016-03-22 03:00:44: pid 15863: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15842: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58296 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15864: LOG:  failback event detected
2016-03-22 03:00:44: pid 15864: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15840: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58300 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15846: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58298 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15866: LOG:  failback event detected
2016-03-22 03:00:44: pid 15866: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15867: LOG:  failback event detected
2016-03-22 03:00:44: pid 15867: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15851: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58301 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15868: LOG:  failback event detected
2016-03-22 03:00:44: pid 15868: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15854: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58302 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15870: LOG:  failback event detected
2016-03-22 03:00:44: pid 15870: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15871: LOG:  failback event detected
2016-03-22 03:00:44: pid 15871: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15855: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58303 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15873: LOG:  failback event detected
2016-03-22 03:00:44: pid 15873: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15862: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58306 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15844: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58305 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15878: LOG:  failback event detected
2016-03-22 03:00:44: pid 15878: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15847: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58299 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15881: LOG:  failback event detected
2016-03-22 03:00:44: pid 15881: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15883: LOG:  failback event detected
2016-03-22 03:00:44: pid 15883: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15885: LOG:  failback event detected
2016-03-22 03:00:44: pid 15885: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15889: LOG:  failback event detected
2016-03-22 03:00:44: pid 15889: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15890: LOG:  failback event detected
2016-03-22 03:00:44: pid 15890: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15893: LOG:  failback event detected
2016-03-22 03:00:44: pid 15893: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15869: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58309 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15876: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58308 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15872: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58311 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15895: LOG:  failback event detected
2016-03-22 03:00:44: pid 15895: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15880: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58313 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15879: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58312 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15896: LOG:  failback event detected
2016-03-22 03:00:44: pid 15896: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15875: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58310 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15882: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58314 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15899: LOG:  failback event detected
2016-03-22 03:00:44: pid 15899: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15884: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58315 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15901: LOG:  failback event detected
2016-03-22 03:00:44: pid 15901: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15886: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58316 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15902: LOG:  failback event detected
2016-03-22 03:00:44: pid 15902: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15887: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58317 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15903: LOG:  failback event detected
2016-03-22 03:00:44: pid 15903: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15888: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58318 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15904: LOG:  failback event detected
2016-03-22 03:00:44: pid 15904: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15905: LOG:  failback event detected
2016-03-22 03:00:44: pid 15905: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15908: LOG:  failback event detected
2016-03-22 03:00:44: pid 15908: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15891: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58319 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15910: LOG:  failback event detected
2016-03-22 03:00:44: pid 15910: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15894: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58321 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15892: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58320 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15897: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58322 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15916: LOG:  failback event detected
2016-03-22 03:00:44: pid 15916: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15900: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58323 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15906: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58324 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15923: LOG:  failback event detected
2016-03-22 03:00:44: pid 15923: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15926: LOG:  failback event detected
2016-03-22 03:00:44: pid 15926: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15909: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58325 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15927: LOG:  failback event detected
2016-03-22 03:00:44: pid 15927: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15911: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58326 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15912: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58328 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15913: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58327 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15914: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58329 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15917: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58331 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15915: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58330 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:44: pid 15937: LOG:  failback event detected
2016-03-22 03:00:44: pid 15937: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15941: LOG:  failback event detected
2016-03-22 03:00:44: pid 15941: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15943: LOG:  failback event detected
2016-03-22 03:00:44: pid 15943: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15945: LOG:  failback event detected
2016-03-22 03:00:44: pid 15945: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15947: LOG:  failback event detected
2016-03-22 03:00:44: pid 15947: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15950: LOG:  failback event detected
2016-03-22 03:00:44: pid 15950: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15954: LOG:  failback event detected
2016-03-22 03:00:44: pid 15954: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15956: LOG:  failback event detected
2016-03-22 03:00:44: pid 15956: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15976: LOG:  failback event detected
2016-03-22 03:00:44: pid 15976: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15978: LOG:  failback event detected
2016-03-22 03:00:44: pid 15978: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15979: LOG:  failback event detected
2016-03-22 03:00:44: pid 15979: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15981: LOG:  failback event detected
2016-03-22 03:00:44: pid 15981: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15982: LOG:  failback event detected
2016-03-22 03:00:44: pid 15982: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15987: LOG:  failback event detected
2016-03-22 03:00:44: pid 15987: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15992: LOG:  failback event detected
2016-03-22 03:00:44: pid 15992: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15994: LOG:  failback event detected
2016-03-22 03:00:44: pid 15994: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15997: LOG:  failback event detected
2016-03-22 03:00:44: pid 15997: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 15998: LOG:  failback event detected
2016-03-22 03:00:44: pid 15998: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16000: LOG:  failback event detected
2016-03-22 03:00:44: pid 16000: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16005: LOG:  failback event detected
2016-03-22 03:00:44: pid 16005: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16011: LOG:  failback event detected
2016-03-22 03:00:44: pid 16011: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16012: LOG:  failback event detected
2016-03-22 03:00:44: pid 16012: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16015: LOG:  failback event detected
2016-03-22 03:00:44: pid 16015: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16017: LOG:  failback event detected
2016-03-22 03:00:44: pid 16017: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16020: LOG:  failback event detected
2016-03-22 03:00:44: pid 16020: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16021: LOG:  failback event detected
2016-03-22 03:00:44: pid 16021: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16027: LOG:  failback event detected
2016-03-22 03:00:44: pid 16027: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16033: LOG:  failback event detected
2016-03-22 03:00:44: pid 16033: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16038: LOG:  failback event detected
2016-03-22 03:00:44: pid 16038: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16039: LOG:  failback event detected
2016-03-22 03:00:44: pid 16039: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16045: LOG:  failback event detected
2016-03-22 03:00:44: pid 16045: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16047: LOG:  failback event detected
2016-03-22 03:00:44: pid 16047: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16053: LOG:  failback event detected
2016-03-22 03:00:44: pid 16053: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16056: LOG:  failback event detected
2016-03-22 03:00:44: pid 16056: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16057: LOG:  failback event detected
2016-03-22 03:00:44: pid 16057: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16058: LOG:  failback event detected
2016-03-22 03:00:44: pid 16058: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16069: LOG:  failback event detected
2016-03-22 03:00:44: pid 16069: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16071: LOG:  failback event detected
2016-03-22 03:00:44: pid 16071: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16074: LOG:  failback event detected
2016-03-22 03:00:44: pid 16074: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16083: LOG:  failback event detected
2016-03-22 03:00:44: pid 16083: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16084: LOG:  failback event detected
2016-03-22 03:00:44: pid 16084: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16085: LOG:  failback event detected
2016-03-22 03:00:44: pid 16085: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16089: LOG:  failback event detected
2016-03-22 03:00:44: pid 16089: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16090: LOG:  failback event detected
2016-03-22 03:00:44: pid 16090: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16097: LOG:  failback event detected
2016-03-22 03:00:44: pid 16097: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16099: LOG:  failback event detected
2016-03-22 03:00:44: pid 16099: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16102: LOG:  failback event detected
2016-03-22 03:00:44: pid 16102: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16106: LOG:  failback event detected
2016-03-22 03:00:44: pid 16106: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16115: LOG:  failback event detected
2016-03-22 03:00:44: pid 16115: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16121: LOG:  failback event detected
2016-03-22 03:00:44: pid 16121: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16123: LOG:  failback event detected
2016-03-22 03:00:44: pid 16123: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16125: LOG:  failback event detected
2016-03-22 03:00:44: pid 16125: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16126: LOG:  failback event detected
2016-03-22 03:00:44: pid 16126: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16128: LOG:  failback event detected
2016-03-22 03:00:44: pid 16128: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16129: LOG:  failback event detected
2016-03-22 03:00:44: pid 16129: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16130: LOG:  failback event detected
2016-03-22 03:00:44: pid 16130: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16132: LOG:  failback event detected
2016-03-22 03:00:44: pid 16132: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16134: LOG:  failback event detected
2016-03-22 03:00:44: pid 16134: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16136: LOG:  failback event detected
2016-03-22 03:00:44: pid 16136: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16137: LOG:  failback event detected
2016-03-22 03:00:44: pid 16137: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16138: LOG:  failback event detected
2016-03-22 03:00:44: pid 16138: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16139: LOG:  failback event detected
2016-03-22 03:00:44: pid 16139: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16142: LOG:  failback event detected
2016-03-22 03:00:44: pid 16142: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16144: LOG:  failback event detected
2016-03-22 03:00:44: pid 16144: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16146: LOG:  failback event detected
2016-03-22 03:00:44: pid 16146: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16149: LOG:  failback event detected
2016-03-22 03:00:44: pid 16149: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16156: LOG:  failback event detected
2016-03-22 03:00:44: pid 16156: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16157: LOG:  failback event detected
2016-03-22 03:00:44: pid 16157: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16162: LOG:  failback event detected
2016-03-22 03:00:44: pid 16162: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16164: LOG:  failback event detected
2016-03-22 03:00:44: pid 16164: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16166: LOG:  failback event detected
2016-03-22 03:00:44: pid 16166: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16168: LOG:  failback event detected
2016-03-22 03:00:44: pid 16168: DETAIL:  restarting myself
2016-03-22 03:00:44: pid 16169: LOG:  failback event detected
2016-03-22 03:00:44: pid 16169: DETAIL:  restarting myself
failover done. shutdown host 1.1.1.6(5432)2016-03-22 03:00:44: pid 14479: ERROR:  Failed to check replication time lag
2016-03-22 03:00:44: pid 14479: DETAIL:  No persistent db connection for the node 0
2016-03-22 03:00:44: pid 14479: HINT:  check sr_check_user and sr_check_password
2016-03-22 03:00:44: pid 14479: CONTEXT:  while checking replication time lag
2016-03-22 03:00:44: pid 14479: LOG:  worker process received restart request
2016-03-22 03:00:44: pid 55911: LOG:  failover done. shutdown host 1.1.1.6(5432)
2016-03-22 03:00:44: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:44: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:44: pid 16172: LOG:  failback event detected
2016-03-22 03:00:44: pid 16172: DETAIL:  restarting myself
+ log 'starting backup on new master node: 1.1.1.7'
+ '[' '!' 'starting backup on new master node: 1.1.1.7' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:44.84] - starting backup on new master node: 1.1.1.7'
+ su - postgres -c 'ssh 1.1.1.7 /home/postgres/pg_utils/start_backup.sh'
+ psql -c 'select pg_start_backup('\''clone'\'',true);'
2016-03-22 03:00:45: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:45: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:45: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:45: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:45: pid 16160: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58355 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:45: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:45: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:46: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:46: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:46: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:46: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:46: pid 16171: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58386 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:46: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:46: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:47: pid 16105: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58417 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:47: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:47: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:47: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:47: pid 55911: LOG:  watchdog became a new lock holder
 pg_start_backup
-----------------
 F/A5851440
(1 row)

+ log 'stopping 1.1.1.6 node.'
+ '[' '!' 'stopping 1.1.1.6 node.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:47.13] - stopping 1.1.1.6 node.'
+ su - postgres -c 'ssh 1.1.1.6 '\''pg_ctl -D /home/postgres/databases/fabrix stop -m fast'\'''
2016-03-22 03:00:47: pid 16151: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58418 statement: "ROLLBACK" message: "there is no transaction in progress"
waiting for server to shut down....2016-03-22 03:00:47: pid 16044: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58454 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:47: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:47: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:47: pid 16095: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58456 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:47: pid 16061: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58457 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:47: pid 16037: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58458 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:47: pid 15935: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58459 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:47: pid 16161: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58460 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:48: pid 16124: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58461 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:48: pid 16091: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58462 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:48: pid 15988: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58463 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:48: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:48: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:48: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:48: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:48: pid 16163: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58464 statement: "ROLLBACK" message: "there is no transaction in progress"
.2016-03-22 03:00:48: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:48: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:49: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:49: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:49: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:49: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:49: pid 16034: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58469 statement: "ROLLBACK" message: "there is no transaction in progress"
 done
server stopped
+ COUNTER=0
+ [[ -n True ]]
+ su - postgres -c 'ssh postgres at HOST_NAME ps -ef|grep -v grep|grep "/usr/bin/postgres -D"'
+ RET_VAL=1
+ '[' 1 -eq 0 ']'
+ '[' '!' 1 -eq 0 ']'
+ log 'Postgres stopped.....'
+ '[' '!' 'Postgres stopped.....' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:49.40] - Postgres stopped.....'
+ break
+ log 'performing rsync between source:1.1.1.7 and target:1.1.1.6'
+ '[' '!' 'performing rsync between source:1.1.1.7 and target:1.1.1.6' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:00:49.40] - performing rsync between source:1.1.1.7 and target:1.1.1.6'
+ su - postgres -c 'ssh 1.1.1.7 rsync -av --timeout=40 --exclude pg_xlog --exclude postgresql.conf --exclude postgres.out --exclude postmaster.pid --exclude recovery.done /home/postgres/databases/fabrix/*  1.1.1.6:/home/postgres/databases/fabrix/ && exit 0 || exit 99'
2016-03-22 03:00:49: pid 16065: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58507 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:49: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:49: pid 55911: LOG:  watchdog became a new lock holder
sending incremental file list
postmaster.opts
base/1/
base/1/pg_internal.init
base/12901/
base/12901/pg_internal.init
base/16385/
base/16385/12634
base/16385/12634_fsm
base/16385/12634_vm
base/16385/12636
base/16385/12638
base/16385/12639
base/16385/12656
base/16385/12667
base/16385/16437
base/16385/16439
base/16385/16439_fsm
base/16385/16558
base/16385/16560
base/16385/16561
base/16385/16564
base/16385/16569
base/16385/16576
base/16385/16579
base/16385/16580
base/16385/16581
base/16385/16582
base/16385/16583
base/16385/16584
base/16385/16585
base/16385/16586
base/16385/16587
base/16385/16588
base/16385/16589
base/16385/16590
base/16385/16591
base/16385/16592
base/16385/16724
base/16385/16726
base/16385/16726_fsm
base/16385/16753
base/16385/16760
base/16385/16786
base/16385/16788
base/16385/16803
base/16385/16810
base/16385/16811
base/16385/16813
base/16385/16813_fsm
base/16385/16824
base/16385/16831
base/16385/16887
base/16385/16889
base/16385/16894
base/16385/16896
base/16385/16897
base/16385/16898
base/16385/16900
base/16385/16900_fsm
base/16385/16937
base/16385/16939
base/16385/16940
base/16385/16941
base/16385/16942
base/16385/16943
base/16385/16944
base/16385/16945
base/16385/16946
base/16385/16947
base/16385/16948
base/16385/16949
base/16385/16950
base/16385/16951
base/16385/16968
base/16385/16970
base/16385/16981
base/16385/16988
2016-03-22 03:00:50: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:50: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:50: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:50: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:50: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:50: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:51: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:51: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:51: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:51: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:51: pid 16113: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58518 statement: "ROLLBACK" message: "there is no transaction in progress"
base/16385/16989.1
2016-03-22 03:00:51: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:51: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:52: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:52: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:52: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:52: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:52: pid 16042: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58557 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:52: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:52: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:52: pid 16108: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58562 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:52: pid 16006: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58563 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 16064: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58564 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 15933: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58565 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 16066: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58566 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:53: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:53: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:53: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:53: pid 16078: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58567 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:53: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:54: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:54: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:54: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:54: pid 55911: LOG:  watchdog became a new lock holder
base/16385/16989_fsm
base/16385/17042
2016-03-22 03:00:55: pid 14466: LOG:  restart request received in pcp child process
2016-03-22 03:00:55: pid 55911: LOG:  PCP child 14466 exits with status 256 in failover()
2016-03-22 03:00:55: pid 55911: LOG:  fork a new PCP child pid 16960 in failover()
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3364 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3364 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3365 exits with status 0
base/16385/16947
base/16385/16948
base/16385/16949
base/16385/16950
base/16385/16951
base/16385/16968
base/16385/16970
base/16385/16981
base/16385/16988
2016-03-22 03:00:50: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:50: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:50: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:50: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:50: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:50: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:51: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:51: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:51: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:51: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:51: pid 16113: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58518 state
ment: "ROLLBACK" message: "there is no transaction in progress"
base/16385/16989.1
2016-03-22 03:00:51: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:51: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:52: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:52: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:52: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:52: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:52: pid 16042: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58557 state
ment: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:52: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:52: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:52: pid 16108: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58562 state
ment: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:52: pid 16006: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58563 state
ment: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 16064: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58564 state
ment: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 15933: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58565 state
ment: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 16066: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58566 state
ment: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:53: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:53: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:53: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:53: pid 16078: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58567 state
ment: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:53: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:00:53: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:00:54: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:00:54: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:00:54: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:00:54: pid 55911: LOG:  watchdog became a new lock holder
base/16385/16989_fsm
base/16385/17042
2016-03-22 03:00:55: pid 14466: LOG:  restart request received in pcp child process
2016-03-22 03:00:55: pid 55911: LOG:  PCP child 14466 exits with status 256 in failover()
2016-03-22 03:00:55: pid 55911: LOG:  fork a new PCP child pid 16960 in failover()
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3364 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3364 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3365 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3365 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3367 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3367 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3370 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3370 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3373 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3373 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3378 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3378 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3381 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3381 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3388 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3388 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3393 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3393 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3396 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3396 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3397 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3397 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3402 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3402 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3406 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3406 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3407 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3407 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3408 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3408 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3409 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3409 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3411 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3411 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3412 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3412 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3419 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3419 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3420 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3420 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3423 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3423 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3425 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3425 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3431 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3431 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3441 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3441 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3442 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3442 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3445 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3445 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3447 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3447 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3448 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3448 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3450 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3450 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3452 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3452 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3453 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3453 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3454 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3454 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3455 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3455 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3456 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3456 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3458 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3458 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3460 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3460 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3466 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3466 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3473 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3473 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3475 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3475 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3476 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3476 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3477 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3477 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3490 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3490 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3499 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3499 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3509 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3509 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3522 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3522 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3528 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3528 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3530 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3530 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3549 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3549 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3550 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3550 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3552 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3552 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3559 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3559 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3564 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3564 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3566 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3566 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3569 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3569 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3570 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3570 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3572 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3572 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3577 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3577 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3583 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3583 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3586 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3586 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3587 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3587 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3589 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3589 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3593 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3593 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3594 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3594 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3599 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3599 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3606 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3606 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3610 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3610 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3611 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3611 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3618 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3618 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3627 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3627 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3630 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3630 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3632 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3632 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3645 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3645 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3650 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3650 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3655 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3655 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3670 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3670 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3672 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3672 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3675 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3675 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3679 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3679 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3688 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3688 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3694 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3694 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3696 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3696 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3699 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3699 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3702 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3702 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3712 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3712 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3715 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3715 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3717 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3717 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3722 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3722 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3729 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3729 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3730 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3730 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3737 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3737 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3739 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3739 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3741 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 3741 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4205 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4205 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4206 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4206 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4209 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4209 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4211 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4211 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4218 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4218 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4226 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4226 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4227 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4227 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4251 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4251 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4277 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4277 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4288 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4288 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4293 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4293 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4304 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4304 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4305 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4305 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4308 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4308 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4309 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4309 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4312 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4312 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4313 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4313 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4315 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4315 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4329 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4329 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4334 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4334 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4336 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4336 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4349 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4349 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4351 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 4351 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 5347 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 5347 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 5461 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 5461 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 5731 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 5731 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 6596 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 6596 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 6867 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 6867 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 6959 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 6959 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 8227 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 8227 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 8386 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 8386 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 10128 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 10128 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 10796 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 10796 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 11218 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 11218 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 11718 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 11718 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 13158 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 13158 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 13503 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 13503 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14468 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14468 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14471 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14471 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  worker child process with pid: 14479 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new worker child process with pid: 16961
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14483 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14483 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14485 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14485 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14486 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14486 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14491 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14491 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14494 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14494 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14497 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14497 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14498 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14498 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14505 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14505 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14506 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14506 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14507 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14507 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14509 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14509 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14510 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14510 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14512 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14512 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14513 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14513 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14515 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14515 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14520 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14520 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14524 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14524 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14525 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14525 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14527 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14527 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14529 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14529 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14531 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14531 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14532 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14532 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14533 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14533 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14534 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14534 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14537 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14537 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14538 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14538 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14539 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14539 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14542 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14542 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14543 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14543 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14544 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14544 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14545 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14545 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14546 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14546 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14547 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14547 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14548 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14548 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14549 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14549 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14552 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14552 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14553 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14553 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14554 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14554 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14555 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14555 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14556 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14556 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14557 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14557 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14558 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14558 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14561 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14561 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14569 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14569 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14571 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14571 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14572 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14572 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14578 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14578 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14581 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14581 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14582 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14582 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14584 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14584 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14585 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14585 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14588 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14588 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14589 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14589 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14590 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14590 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14591 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14591 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14592 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14592 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14594 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14594 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14595 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14595 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14596 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14596 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14598 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14598 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14599 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14599 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14600 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14600 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14601 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14601 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14602 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14602 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14603 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14603 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14604 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14604 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14605 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14605 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14606 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14606 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14607 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14607 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14608 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14608 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14609 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14609 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14610 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14610 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14611 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14611 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14612 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14612 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14613 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14613 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14614 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14614 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14615 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14615 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14616 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14616 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14617 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14617 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14618 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14618 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14619 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14619 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14620 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14620 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14621 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14621 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14622 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14622 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14623 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14623 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14624 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14624 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14625 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14625 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14626 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14626 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14627 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14627 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14628 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14628 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14629 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14629 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14630 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14630 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14631 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14631 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14632 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14632 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14633 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14633 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14634 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14634 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14635 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14635 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14636 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14636 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14637 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14637 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14638 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14638 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14639 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14639 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14640 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14640 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14641 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14641 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14642 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14642 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14643 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14643 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14645 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14645 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14664 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14664 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14667 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14667 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14670 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14670 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14672 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14672 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14675 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14675 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14699 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14699 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14837 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14837 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14839 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14839 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14842 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14842 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14843 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14843 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14860 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14860 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14863 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14863 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14865 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14865 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14866 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14866 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14867 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14867 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14868 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14868 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14873 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14873 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14874 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14874 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14875 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14875 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14876 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14876 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14877 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14877 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14878 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14878 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14879 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14879 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14880 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14880 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14881 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14881 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14882 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14882 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14883 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14883 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14885 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14885 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14886 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14886 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14888 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14888 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14891 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14891 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14892 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14892 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14893 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14893 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14894 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14894 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14895 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14895 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14896 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14896 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14897 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14897 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14898 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14898 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14899 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14899 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14995 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 14995 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15000 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15000 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15001 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15001 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15002 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15002 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15003 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15003 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15004 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15004 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15005 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15005 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15006 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15006 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15007 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15007 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15009 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15009 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15054 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15054 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15058 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15058 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15059 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15059 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15060 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15060 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15061 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15061 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15062 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15062 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15063 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15063 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15064 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15064 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15068 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15068 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15072 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15072 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15073 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15073 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15211 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15211 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15215 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15215 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15257 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15257 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15261 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15261 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15389 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15389 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15392 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15392 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15393 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15393 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15397 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15397 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15398 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15398 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15399 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15399 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15400 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15400 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15401 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15401 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15402 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15402 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15403 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15403 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15404 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15404 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15405 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15405 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15406 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15406 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15407 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15407 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15408 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15408 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15409 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15409 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15414 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15414 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15416 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15416 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15417 exits with status 0
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15417 exited with success and will not be restarted
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15838 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16962
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15839 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16963
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15841 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16964
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15843 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16965
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15845 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16966
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15848 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16967
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15849 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16968
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15850 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16969
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15853 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16970
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15856 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16971
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15858 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16972
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15860 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16973
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15861 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16974
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15863 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16975
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15864 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16976
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15865 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16977
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15866 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16978
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15867 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16979
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15868 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16980
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15870 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16981
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15871 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16982
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15873 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16983
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15877 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16984
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15878 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16985
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15881 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16986
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15883 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16987
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15885 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16988
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15889 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16989
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15890 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16990
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15893 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16991
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15895 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16992
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15896 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16993
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15899 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16994
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15901 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16995
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15902 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16996
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15903 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16997
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15904 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16998
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15905 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 16999
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15908 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17000
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15910 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17001
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15916 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17002
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15918 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17003
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15923 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17004
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15926 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17005
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15927 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17006
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15937 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17007
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15941 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17008
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15943 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17009
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15945 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17010
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15947 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17011
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15950 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17012
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15954 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17013
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15956 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17014
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15976 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17015
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15978 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17016
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15979 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17017
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15981 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17018
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15982 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17019
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15987 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17020
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15992 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17021
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15994 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17022
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15997 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17023
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 15998 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17024
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16000 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17025
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16005 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17026
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16011 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17027
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16012 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17028
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16014 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17029
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16015 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17030
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16017 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17031
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16020 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17032
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16021 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17033
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16026 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17034
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16027 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17035
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16033 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17036
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16038 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17037
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16039 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17038
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16045 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17039
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16047 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17040
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16053 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17041
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16056 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17042
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16057 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17043
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16058 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17044
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16063 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17045
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16069 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17046
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16071 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17047
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16074 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17048
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16083 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17049
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16084 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17050
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16085 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17051
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16086 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17052
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16089 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17053
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16090 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17054
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16097 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17055
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16099 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17056
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16102 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17057
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16106 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17058
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16115 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17059
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16116 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17060
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16117 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17061
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16120 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17062
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16121 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17063
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16123 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17064
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16125 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17065
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16126 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17066
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16128 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17067
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16129 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17068
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16130 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17069
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16132 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17070
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16134 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17071
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16136 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17072
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16137 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17073
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16138 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17074
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16139 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17075
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16142 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17076
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16144 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17077
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16146 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17078
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16149 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17079
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16156 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17080
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16157 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17081
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16162 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17082
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16164 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17083
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16166 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17084
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16168 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17085
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16169 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17086
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16172 exits with status 256
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17087
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16052 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17091
2016-03-22 03:00:55: pid 55911: LOG:  child process with pid: 16075 exits with status 512
2016-03-22 03:00:55: pid 55911: LOG:  fork a new child process with pid: 17102
2016-03-22 03:00:57: pid 55911: LOG:  child process with pid: 17102 exits with status 512
2016-03-22 03:00:57: pid 55911: LOG:  fork a new child process with pid: 17233
2016-03-22 03:00:57: pid 55911: LOG:  child process with pid: 17038 exits with status 512
2016-03-22 03:00:57: pid 55911: LOG:  fork a new child process with pid: 17234
2016-03-22 03:00:58: pid 16122: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58690 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:00:59: pid 55911: LOG:  child process with pid: 17081 exits with status 512
2016-03-22 03:00:59: pid 55911: LOG:  fork a new child process with pid: 17282
base/16385/17044
2016-03-22 03:01:01: pid 55911: LOG:  child process with pid: 17014 exits with status 512
2016-03-22 03:01:01: pid 55911: LOG:  fork a new child process with pid: 17409
base/16385/17045
2016-03-22 03:01:02: pid 17052: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58814 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:03: pid 17086: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58815 statement: "ROLLBACK" message: "there is no transaction in progress"
base/16385/17046
2016-03-22 03:01:03: pid 55911: LOG:  child process with pid: 17409 exits with status 512
2016-03-22 03:01:03: pid 55911: LOG:  fork a new child process with pid: 17422
2016-03-22 03:01:03: pid 55911: LOG:  child process with pid: 17025 exits with status 512
2016-03-22 03:01:03: pid 55911: LOG:  fork a new child process with pid: 17423
base/16385/17047
2016-03-22 03:01:05: pid 55911: LOG:  child process with pid: 16988 exits with status 512
2016-03-22 03:01:05: pid 55911: LOG:  fork a new child process with pid: 17499
2016-03-22 03:01:05: pid 55911: LOG:  child process with pid: 17423 exits with status 512
2016-03-22 03:01:05: pid 55911: LOG:  fork a new child process with pid: 17500
base/16385/17048
2016-03-22 03:01:06: pid 17042: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58900 statement: "ROLLBACK" message: "there is no transaction in progress"
base/16385/17049
base/16385/17051
2016-03-22 03:01:07: pid 55911: LOG:  child process with pid: 17499 exits with status 512
2016-03-22 03:01:07: pid 55911: LOG:  fork a new child process with pid: 17612
2016-03-22 03:01:07: pid 55911: LOG:  child process with pid: 15985 exits with status 512
2016-03-22 03:01:07: pid 55911: LOG:  fork a new child process with pid: 17613
2016-03-22 03:01:08: pid 16077: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58943 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:09: pid 55911: LOG:  child process with pid: 16982 exits with status 512
2016-03-22 03:01:09: pid 55911: LOG:  fork a new child process with pid: 17629
2016-03-22 03:01:09: pid 55911: LOG:  child process with pid: 16055 exits with status 512
2016-03-22 03:01:09: pid 55911: LOG:  fork a new child process with pid: 17630
2016-03-22 03:01:10: pid 17003: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 58988 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:11: pid 55911: LOG:  child process with pid: 17630 exits with status 512
2016-03-22 03:01:11: pid 55911: LOG:  fork a new child process with pid: 17764
2016-03-22 03:01:11: pid 55911: LOG:  child process with pid: 17233 exits with status 512
2016-03-22 03:01:11: pid 55911: LOG:  fork a new child process with pid: 17765
2016-03-22 03:01:13: pid 16023: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59037 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:13: pid 17066: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59038 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:13: pid 55911: LOG:  child process with pid: 15924 exits with status 512
2016-03-22 03:01:13: pid 55911: LOG:  fork a new child process with pid: 17784
2016-03-22 03:01:13: pid 55911: LOG:  child process with pid: 17612 exits with status 512
2016-03-22 03:01:13: pid 55911: LOG:  fork a new child process with pid: 17785
2016-03-22 03:01:15: pid 17629: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59082 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:16: pid 55911: LOG:  child process with pid: 17023 exits with status 512
2016-03-22 03:01:16: pid 55911: LOG:  fork a new child process with pid: 17798
2016-03-22 03:01:16: pid 16114: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59122 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:18: pid 55911: LOG:  child process with pid: 17798 exits with status 512
2016-03-22 03:01:18: pid 55911: LOG:  fork a new child process with pid: 17929
2016-03-22 03:01:18: pid 16096: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59130 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:18: pid 55911: LOG:  child process with pid: 17043 exits with status 512
2016-03-22 03:01:18: pid 55911: LOG:  fork a new child process with pid: 17930
2016-03-22 03:01:20: pid 55911: LOG:  child process with pid: 15980 exits with status 512
2016-03-22 03:01:20: pid 55911: LOG:  fork a new child process with pid: 17943
2016-03-22 03:01:20: pid 55911: LOG:  child process with pid: 16158 exits with status 512
2016-03-22 03:01:20: pid 55911: LOG:  fork a new child process with pid: 17944
base/16385/17051_fsm
base/16385/17060
2016-03-22 03:01:22: pid 55911: LOG:  child process with pid: 16119 exits with status 512
2016-03-22 03:01:22: pid 55911: LOG:  fork a new child process with pid: 18101
2016-03-22 03:01:22: pid 55911: LOG:  child process with pid: 15971 exits with status 512
2016-03-22 03:01:22: pid 55911: LOG:  fork a new child process with pid: 18102
2016-03-22 03:01:23: pid 16110: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59253 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:24: pid 55911: LOG:  child process with pid: 16167 exits with status 512
2016-03-22 03:01:24: pid 55911: LOG:  fork a new child process with pid: 18175
2016-03-22 03:01:24: pid 55911: LOG:  child process with pid: 15970 exits with status 512
2016-03-22 03:01:24: pid 55911: LOG:  fork a new child process with pid: 18176
base/16385/17067
2016-03-22 03:01:26: pid 55911: LOG:  child process with pid: 17031 exits with status 512
2016-03-22 03:01:26: pid 55911: LOG:  fork a new child process with pid: 18196
2016-03-22 03:01:26: pid 55911: LOG:  child process with pid: 18175 exits with status 512
2016-03-22 03:01:26: pid 55911: LOG:  fork a new child process with pid: 18197
base/16385/17088
2016-03-22 03:01:27: pid 18176: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59342 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:27: pid 16068: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59343 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:27: pid 16127: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59344 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:28: pid 18196: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59353 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:28: pid 17943: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59356 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:28: pid 55911: LOG:  child process with pid: 17765 exits with status 512
2016-03-22 03:01:28: pid 55911: LOG:  fork a new child process with pid: 18305
2016-03-22 03:01:28: pid 55911: LOG:  child process with pid: 16112 exits with status 512
2016-03-22 03:01:28: pid 55911: LOG:  fork a new child process with pid: 18306
2016-03-22 03:01:30: pid 55911: LOG:  child process with pid: 16974 exits with status 512
2016-03-22 03:01:30: pid 55911: LOG:  fork a new child process with pid: 18351
2016-03-22 03:01:32: pid 55911: LOG:  child process with pid: 18306 exits with status 512
2016-03-22 03:01:32: pid 55911: LOG:  fork a new child process with pid: 18450
2016-03-22 03:01:32: pid 55911: LOG:  child process with pid: 17007 exits with status 512
2016-03-22 03:01:32: pid 55911: LOG:  fork a new child process with pid: 18451
base/16385/17088_fsm
base/16385/17088_vm
base/16385/17123
2016-03-22 03:01:33: pid 15960: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59477 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:34: pid 55911: LOG:  child process with pid: 17021 exits with status 512
2016-03-22 03:01:34: pid 55911: LOG:  fork a new child process with pid: 18461
2016-03-22 03:01:34: pid 55911: LOG:  child process with pid: 17784 exits with status 512
2016-03-22 03:01:34: pid 55911: LOG:  fork a new child process with pid: 18462
2016-03-22 03:01:36: pid 55911: LOG:  child process with pid: 16991 exits with status 512
2016-03-22 03:01:36: pid 55911: LOG:  fork a new child process with pid: 18532
2016-03-22 03:01:36: pid 55911: LOG:  child process with pid: 16100 exits with status 512
2016-03-22 03:01:36: pid 55911: LOG:  fork a new child process with pid: 18533
base/16385/17125
base/16385/17126
2016-03-22 03:01:38: pid 16079: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59566 statement: "ROLLBACK" message: "there is no transaction in progress"
base/16385/17127
2016-03-22 03:01:38: pid 55911: LOG:  child process with pid: 16046 exits with status 512
2016-03-22 03:01:38: pid 55911: LOG:  fork a new child process with pid: 18638
base/16385/17128
base/16385/17129
2016-03-22 03:01:40: pid 55911: LOG:  child process with pid: 16001 exits with status 512
2016-03-22 03:01:40: pid 55911: LOG:  fork a new child process with pid: 18663
2016-03-22 03:01:40: pid 55911: LOG:  child process with pid: 15944 exits with status 512
2016-03-22 03:01:40: pid 55911: LOG:  fork a new child process with pid: 18666
base/16385/17130
base/16385/17131
base/16385/17132
2016-03-22 03:01:42: pid 55911: LOG:  child process with pid: 17072 exits with status 512
2016-03-22 03:01:42: pid 55911: LOG:  fork a new child process with pid: 18800
2016-03-22 03:01:42: pid 55911: LOG:  child process with pid: 18461 exits with status 512
2016-03-22 03:01:42: pid 55911: LOG:  fork a new child process with pid: 18801
2016-03-22 03:01:43: pid 18532: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59689 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:44: pid 55911: LOG:  child process with pid: 18801 exits with status 512
2016-03-22 03:01:44: pid 55911: LOG:  fork a new child process with pid: 18826
2016-03-22 03:01:44: pid 55911: LOG:  child process with pid: 17070 exits with status 512
2016-03-22 03:01:44: pid 55911: LOG:  fork a new child process with pid: 18827
2016-03-22 03:01:46: pid 55911: LOG:  child process with pid: 17029 exits with status 512
2016-03-22 03:01:46: pid 55911: LOG:  fork a new child process with pid: 18876
2016-03-22 03:01:48: pid 17010: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59777 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:48: pid 55911: LOG:  child process with pid: 16019 exits with status 512
2016-03-22 03:01:48: pid 55911: LOG:  fork a new child process with pid: 19010
2016-03-22 03:01:50: pid 55911: LOG:  child process with pid: 17017 exits with status 512
2016-03-22 03:01:50: pid 55911: LOG:  fork a new child process with pid: 19020
2016-03-22 03:01:50: pid 55911: LOG:  child process with pid: 16140 exits with status 512
2016-03-22 03:01:50: pid 55911: LOG:  fork a new child process with pid: 19021
base/16385/17132.1
2016-03-22 03:01:52: pid 55911: LOG:  child process with pid: 16984 exits with status 512
2016-03-22 03:01:52: pid 55911: LOG:  fork a new child process with pid: 19144
2016-03-22 03:01:53: pid 16966: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59863 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:54: pid 55911: LOG:  child process with pid: 16054 exits with status 512
2016-03-22 03:01:54: pid 55911: LOG:  fork a new child process with pid: 19204
2016-03-22 03:01:54: pid 55911: LOG:  child process with pid: 18451 exits with status 512
2016-03-22 03:01:54: pid 55911: LOG:  fork a new child process with pid: 19205
base/16385/17132.2
2016-03-22 03:01:56: pid 55911: LOG:  child process with pid: 17002 exits with status 512
2016-03-22 03:01:56: pid 55911: LOG:  fork a new child process with pid: 19218
2016-03-22 03:01:56: pid 55911: LOG:  child process with pid: 17077 exits with status 512
2016-03-22 03:01:56: pid 55911: LOG:  fork a new child process with pid: 19219
2016-03-22 03:01:58: pid 15995: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59986 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:58: pid 16170: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 59989 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:01:58: pid 55911: LOG:  child process with pid: 16145 exits with status 512
2016-03-22 03:01:58: pid 55911: LOG:  fork a new child process with pid: 19333
base/16385/17132_fsm
base/16385/17132_vm
base/16385/17242
2016-03-22 03:02:00: pid 55911: LOG:  child process with pid: 16098 exits with status 512
2016-03-22 03:02:00: pid 55911: LOG:  fork a new child process with pid: 19383
2016-03-22 03:02:00: pid 55911: LOG:  child process with pid: 17282 exits with status 512
2016-03-22 03:02:00: pid 55911: LOG:  fork a new child process with pid: 19384
base/16385/17244
base/16385/17349
base/16385/17351
2016-03-22 03:02:02: pid 55911: LOG:  child process with pid: 16040 exits with status 512
2016-03-22 03:02:02: pid 55911: LOG:  fork a new child process with pid: 19483
2016-03-22 03:02:02: pid 55911: LOG:  child process with pid: 16135 exits with status 512
2016-03-22 03:02:02: pid 55911: LOG:  fork a new child process with pid: 19484
2016-03-22 03:02:03: pid 19383: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 60075 statement: "ROLLBACK" message: "there is no transaction in progress"
base/16385/17351_fsm
base/16385/17366
2016-03-22 03:02:04: pid 55911: LOG:  child process with pid: 17080 exits with status 512
2016-03-22 03:02:04: pid 55911: LOG:  fork a new child process with pid: 19497
base/16385/17373
2016-03-22 03:02:04: pid 55911: LOG:  child process with pid: 17060 exits with status 512
2016-03-22 03:02:04: pid 55911: LOG:  fork a new child process with pid: 19498
base/16385/17788
base/16385/17790
base/16385/17790_fsm
base/16385/17790_vm
base/16385/17806
base/16385/17808
base/16385/17809
base/16385/17810
base/16385/18444
base/16385/18726
base/16385/18728
base/16385/18728_fsm
base/16385/18771
base/16385/18773
base/16385/18774
base/16385/18775
base/16385/18776
base/16385/18777
base/16385/18778
base/16385/18779
base/16385/18780
base/16385/19673
base/16385/19716
base/16385/19718
base/16385/19719
base/16385/19806
base/16385/19808
base/16385/19823
base/16385/19830
base/16385/19831
base/16385/19833
base/16385/19833_fsm
base/16385/19861
base/16385/19868
base/16385/21054
base/16385/21066
base/16385/21068
base/16385/21069
base/16385/21070
base/16385/21072
base/16385/21084
base/16385/22081
base/16385/22083
base/16385/22083_fsm
base/16385/22109
base/16385/22111
base/16385/22114
base/16385/pg_internal.init
global/
global/pg_control
global/pg_internal.init
pg_clog/0009
pg_multixact/offsets/0000
pg_notify/
pg_notify/0000
pg_stat/
pg_stat_tmp/
pg_stat_tmp/db_0.stat
pg_stat_tmp/global.stat
pg_subtrans/
pg_subtrans/0097

sent 1220939454 bytes  received 3086739 bytes  16000342.39 bytes/sec
total size is 8953107071  speedup is 7.31
+ RET_VAL=0
+ log 'deleting Archive directory in 1.1.1.7.'
+ '[' '!' 'deleting Archive directory in 1.1.1.7.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:05.98] - deleting Archive directory in 1.1.1.7.'
+ su - postgres -c 'ssh 1.1.1.7 '\''rm -rf /home/postgres/archive/*'\'''
2016-03-22 03:02:06: pid 55911: LOG:  child process with pid: 16025 exits with status 512
2016-03-22 03:02:06: pid 55911: LOG:  fork a new child process with pid: 19589
2016-03-22 03:02:06: pid 55911: LOG:  child process with pid: 16103 exits with status 512
2016-03-22 03:02:06: pid 55911: LOG:  fork a new child process with pid: 19590
+ log 'stopping backup on new master node: 1.1.1.7'
+ '[' '!' 'stopping backup on new master node: 1.1.1.7' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:06.79] - stopping backup on new master node: 1.1.1.7'
+ su - postgres -c 'ssh 1.1.1.7 /home/postgres/pg_utils/stop_backup.sh'
+ psql -c 'select pg_stop_backup();'
2016-03-22 03:02:08: pid 17013: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 1 backend pid: 60325 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:02:08: pid 55911: LOG:  child process with pid: 16985 exits with status 512
2016-03-22 03:02:08: pid 55911: LOG:  fork a new child process with pid: 19722
2016-03-22 03:02:10: pid 55911: LOG:  child process with pid: 16107 exits with status 512
2016-03-22 03:02:10: pid 55911: LOG:  fork a new child process with pid: 19738
2016-03-22 03:02:10: pid 55911: LOG:  child process with pid: 15975 exits with status 512
2016-03-22 03:02:10: pid 55911: LOG:  fork a new child process with pid: 19739
NOTICE:  pg_stop_backup complete, all required WAL segments have been archived
 pg_stop_backup
----------------
 F/BA8B6110
(1 row)

+ log 'rsync return value is : 0'
+ '[' '!' 'rsync return value is : 0' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:11.97] - rsync return value is : 0'
+ check_rsync 0
+ '[' '!' 0 ']'
+ '[' '!' 0 -eq 0 ']'
+ log 'Deleting /home/postgres/databases/fabrix/pg_xlog/ content on 1.1.1.6.'
+ '[' '!' 'Deleting /home/postgres/databases/fabrix/pg_xlog/ content on 1.1.1.6.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:11.97] - Deleting /home/postgres/databases/fabrix/pg_xlog/ content on 1.1.1.6.'
+ su - postgres -c 'rm -rf 1.1.1.6:/home/postgres/databases/fabrix/pg_xlog/*'
+ log 'performing rsync of xlog dir between source:1.1.1.7 and target:1.1.1.6'
+ '[' '!' 'performing rsync of xlog dir between source:1.1.1.7 and target:1.1.1.6' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:12.01] - performing rsync of xlog dir between source:1.1.1.7 and target:1.1.1.6'
+ su - postgres -c 'ssh 1.1.1.7 rsync -av --timeout=40 /home/postgres/databases/fabrix/pg_xlog  1.1.1.6:/home/postgres/databases/fabrix/ --delete && exit 0 || exit 99'
sending incremental file list
pg_xlog/
deleting pg_xlog/000000B50000001000000020
deleting pg_xlog/000000B5000000100000001F
deleting pg_xlog/000000B5000000100000001E
deleting pg_xlog/000000B5000000100000001D
deleting pg_xlog/000000B5000000100000001C
deleting pg_xlog/000000B5000000100000001B
deleting pg_xlog/000000B5000000100000001A
deleting pg_xlog/000000B50000001000000019
deleting pg_xlog/000000B50000001000000018
deleting pg_xlog/000000B50000001000000017
deleting pg_xlog/000000B50000001000000016
deleting pg_xlog/000000B50000001000000015
deleting pg_xlog/000000B50000001000000014
deleting pg_xlog/000000B50000001000000013
deleting pg_xlog/000000B50000001000000012
deleting pg_xlog/000000B50000001000000011
deleting pg_xlog/000000B50000001000000010
deleting pg_xlog/000000B5000000100000000F
deleting pg_xlog/000000B5000000100000000E
deleting pg_xlog/000000B5000000100000000D
deleting pg_xlog/000000B5000000100000000C
deleting pg_xlog/000000B5000000100000000B
deleting pg_xlog/000000B5000000100000000A
deleting pg_xlog/000000B50000001000000009
deleting pg_xlog/000000B50000001000000008
deleting pg_xlog/000000B50000001000000007
deleting pg_xlog/000000B50000001000000006
deleting pg_xlog/000000B50000001000000005
deleting pg_xlog/000000B50000001000000004
deleting pg_xlog/000000B50000001000000003
deleting pg_xlog/000000B50000001000000002
deleting pg_xlog/000000B50000001000000001
deleting pg_xlog/000000B50000001000000000
deleting pg_xlog/000000B50000000F000000FF
deleting pg_xlog/000000B50000000F000000FE
deleting pg_xlog/000000B50000000F000000FD
deleting pg_xlog/000000B50000000F000000FC
deleting pg_xlog/000000B50000000F000000FB
deleting pg_xlog/000000B50000000F000000FA
deleting pg_xlog/000000B50000000F000000F9
deleting pg_xlog/000000B50000000F000000F8
deleting pg_xlog/000000B50000000F000000F7
deleting pg_xlog/000000B50000000F000000F6
deleting pg_xlog/000000B50000000F000000F5
deleting pg_xlog/000000B50000000F000000F4
deleting pg_xlog/000000B50000000F000000F3
deleting pg_xlog/000000B50000000F000000F2
deleting pg_xlog/000000B50000000F000000F1
deleting pg_xlog/000000B50000000F000000F0
deleting pg_xlog/000000B50000000F000000EF
deleting pg_xlog/000000B50000000F000000EE
deleting pg_xlog/000000B50000000F000000ED
deleting pg_xlog/000000B50000000F000000EC
deleting pg_xlog/000000B50000000F000000EB
deleting pg_xlog/000000B50000000F000000EA
deleting pg_xlog/000000B50000000F000000E9
deleting pg_xlog/000000B50000000F000000E8
deleting pg_xlog/000000B50000000F000000E7
deleting pg_xlog/000000B50000000F000000E6
deleting pg_xlog/000000B50000000F000000E5
deleting pg_xlog/000000B50000000F000000E4
deleting pg_xlog/000000B50000000F000000E3
deleting pg_xlog/000000B50000000F000000E2
deleting pg_xlog/000000B50000000F000000E1
deleting pg_xlog/000000B50000000F000000E0
deleting pg_xlog/000000B50000000F000000DF
deleting pg_xlog/000000B50000000F000000DE
deleting pg_xlog/000000B50000000F000000DD
deleting pg_xlog/000000B50000000F000000DC
deleting pg_xlog/000000B50000000F000000DB
deleting pg_xlog/000000B50000000F000000DA
deleting pg_xlog/000000B50000000F000000D9
deleting pg_xlog/000000B50000000F000000D8
deleting pg_xlog/000000B50000000F000000D7
deleting pg_xlog/000000B50000000F000000D6
deleting pg_xlog/000000B50000000F000000D5
deleting pg_xlog/000000B50000000F000000D4
deleting pg_xlog/000000B50000000F000000D3
deleting pg_xlog/000000B50000000F000000D2
deleting pg_xlog/000000B50000000F000000A0
deleting pg_xlog/000000B50000000F0000009F
deleting pg_xlog/000000B50000000F0000009E
deleting pg_xlog/000000B50000000F0000009D
deleting pg_xlog/000000B50000000F0000009C
deleting pg_xlog/000000B50000000F0000009B
deleting pg_xlog/000000B50000000F0000009A
deleting pg_xlog/000000B50000000F00000099
deleting pg_xlog/000000B50000000F00000094
deleting pg_xlog/000000B50000000F00000093
deleting pg_xlog/000000B50000000F00000092
deleting pg_xlog/000000B50000000F00000091
deleting pg_xlog/000000B50000000F00000090
deleting pg_xlog/000000B50000000F0000008F
deleting pg_xlog/000000B50000000F0000008E
deleting pg_xlog/000000B50000000F0000008D
deleting pg_xlog/000000B50000000F0000008C
deleting pg_xlog/000000B50000000F0000008B
deleting pg_xlog/000000B50000000F0000008A
deleting pg_xlog/000000B50000000F00000089
deleting pg_xlog/000000B50000000F00000088
deleting pg_xlog/000000B50000000F00000087
deleting pg_xlog/000000B50000000F00000086
deleting pg_xlog/000000B50000000F00000085
deleting pg_xlog/000000B50000000F00000084
deleting pg_xlog/000000B50000000F00000083
deleting pg_xlog/000000B50000000F00000082
deleting pg_xlog/000000B50000000F00000081
deleting pg_xlog/000000B50000000F00000080
deleting pg_xlog/000000B50000000F0000007F
deleting pg_xlog/000000B50000000F0000007E
deleting pg_xlog/000000B50000000F0000007D
deleting pg_xlog/000000B50000000F0000007C
deleting pg_xlog/000000B50000000F0000007B
deleting pg_xlog/000000B50000000F0000007A
deleting pg_xlog/000000B50000000F00000079
deleting pg_xlog/000000B50000000F00000078
deleting pg_xlog/000000B50000000F00000077
deleting pg_xlog/000000B50000000F00000076
2016-03-22 03:02:12: pid 55911: LOG:  child process with pid: 17051 exits with status 512
2016-03-22 03:02:12: pid 55911: LOG:  fork a new child process with pid: 19977
deleting pg_xlog/000000B50000000F00000075
deleting pg_xlog/000000B50000000F00000074
deleting pg_xlog/000000B50000000F00000073
2016-03-22 03:02:12: pid 55911: LOG:  child process with pid: 15973 exits with status 512
2016-03-22 03:02:12: pid 55911: LOG:  fork a new child process with pid: 19978
deleting pg_xlog/000000B50000000F00000072
deleting pg_xlog/000000B50000000F00000071
deleting pg_xlog/000000B50000000F00000070
deleting pg_xlog/000000B50000000F0000006F
deleting pg_xlog/000000B50000000F0000006E
deleting pg_xlog/000000B50000000F0000006D
deleting pg_xlog/000000B50000000F0000006C
deleting pg_xlog/000000B50000000F0000006B
deleting pg_xlog/000000B50000000F0000006A
deleting pg_xlog/000000B50000000F00000069
deleting pg_xlog/000000B50000000F00000068
deleting pg_xlog/000000B50000000F00000067.00005CD8.backup
deleting pg_xlog/000000B50000000F00000067
pg_xlog/000000B50000000F00000095
pg_xlog/000000B50000000F00000096
pg_xlog/000000B50000000F00000097
pg_xlog/000000B50000000F00000098
pg_xlog/000000B6.history
pg_xlog/000000B60000000F000000A1
pg_xlog/000000B60000000F000000A2
pg_xlog/000000B60000000F000000A3
pg_xlog/000000B60000000F000000A4
pg_xlog/000000B60000000F000000A5
pg_xlog/000000B60000000F000000A5.00851440.backup
pg_xlog/000000B60000000F000000A6
pg_xlog/000000B60000000F000000A7
pg_xlog/000000B60000000F000000A8
pg_xlog/000000B60000000F000000A9
pg_xlog/000000B60000000F000000AA
pg_xlog/000000B60000000F000000AB
2016-03-22 03:02:14: pid 55911: LOG:  child process with pid: 17076 exits with status 512
2016-03-22 03:02:14: pid 55911: LOG:  fork a new child process with pid: 19988
2016-03-22 03:02:14: pid 55911: LOG:  child process with pid: 17004 exits with status 512
2016-03-22 03:02:14: pid 55911: LOG:  fork a new child process with pid: 19989
pg_xlog/000000B60000000F000000AC
pg_xlog/000000B60000000F000000AD
pg_xlog/000000B60000000F000000AE
pg_xlog/000000B60000000F000000AF
pg_xlog/000000B60000000F000000B0
pg_xlog/000000B60000000F000000B1
pg_xlog/000000B60000000F000000B2
pg_xlog/000000B60000000F000000B3
pg_xlog/000000B60000000F000000B4
pg_xlog/000000B60000000F000000B5
pg_xlog/000000B60000000F000000B6
pg_xlog/000000B60000000F000000B7
pg_xlog/000000B60000000F000000B8
pg_xlog/000000B60000000F000000B9
pg_xlog/000000B60000000F000000BA
2016-03-22 03:02:16: pid 55911: LOG:  child process with pid: 15928 exits with status 512
2016-03-22 03:02:16: pid 55911: LOG:  fork a new child process with pid: 20010
pg_xlog/000000B60000000F000000BB
pg_xlog/000000B60000000F000000BC
pg_xlog/000000B60000000F000000BD
pg_xlog/000000B60000000F000000BE
pg_xlog/000000B60000000F000000BF
pg_xlog/000000B60000000F000000C0
pg_xlog/000000B60000000F000000C1
pg_xlog/000000B60000000F000000C2
pg_xlog/000000B60000000F000000C3
pg_xlog/000000B60000000F000000C4
pg_xlog/000000B60000000F000000C5
pg_xlog/000000B60000000F000000C6
pg_xlog/000000B60000000F000000C7
pg_xlog/000000B60000000F000000C8
2016-03-22 03:02:18: pid 55911: LOG:  child process with pid: 17000 exits with status 512
2016-03-22 03:02:18: pid 55911: LOG:  fork a new child process with pid: 20143
2016-03-22 03:02:18: pid 55911: LOG:  child process with pid: 15922 exits with status 512
2016-03-22 03:02:18: pid 55911: LOG:  fork a new child process with pid: 20144
pg_xlog/000000B60000000F000000C9
pg_xlog/000000B60000000F000000CA
pg_xlog/000000B60000000F000000CB
pg_xlog/000000B60000000F000000CC
pg_xlog/000000B60000000F000000CD
pg_xlog/000000B60000000F000000CE
pg_xlog/000000B60000000F000000CF
pg_xlog/000000B60000000F000000D0
pg_xlog/000000B60000000F000000D1
pg_xlog/000000B60000000F000000D2
pg_xlog/000000B60000000F000000D3
pg_xlog/000000B60000000F000000D4
pg_xlog/000000B60000000F000000D5
pg_xlog/000000B60000000F000000D6
2016-03-22 03:02:20: pid 55911: LOG:  child process with pid: 16990 exits with status 512
2016-03-22 03:02:20: pid 55911: LOG:  fork a new child process with pid: 20182
2016-03-22 03:02:20: pid 55911: LOG:  child process with pid: 18102 exits with status 512
2016-03-22 03:02:20: pid 55911: LOG:  fork a new child process with pid: 20183
pg_xlog/000000B60000000F000000D7
pg_xlog/000000B60000000F000000D8
pg_xlog/000000B60000000F000000D9
pg_xlog/000000B60000000F000000DA
pg_xlog/000000B60000000F000000DB
pg_xlog/000000B60000000F000000DC
pg_xlog/000000B60000000F000000DD
pg_xlog/000000B60000000F000000DE
pg_xlog/000000B60000000F000000DF
pg_xlog/000000B60000000F000000E0
pg_xlog/000000B60000000F000000E1
pg_xlog/000000B60000000F000000E2
pg_xlog/000000B60000000F000000E3
pg_xlog/000000B60000000F000000E4
2016-03-22 03:02:23: pid 55911: LOG:  child process with pid: 16150 exits with status 512
2016-03-22 03:02:23: pid 55911: LOG:  fork a new child process with pid: 20288
2016-03-22 03:02:23: pid 55911: LOG:  child process with pid: 16076 exits with status 512
2016-03-22 03:02:23: pid 55911: LOG:  fork a new child process with pid: 20289
pg_xlog/000000B60000000F000000E5
pg_xlog/000000B60000000F000000E6
pg_xlog/000000B60000000F000000E7
pg_xlog/000000B60000000F000000E8
pg_xlog/000000B60000000F000000E9
pg_xlog/000000B60000000F000000EA
pg_xlog/000000B60000000F000000EB
pg_xlog/000000B60000000F000000EC
pg_xlog/000000B60000000F000000ED
pg_xlog/000000B60000000F000000EE
pg_xlog/000000B60000000F000000EF
pg_xlog/000000B60000000F000000F0
pg_xlog/000000B60000000F000000F1
pg_xlog/000000B60000000F000000F2
2016-03-22 03:02:25: pid 55911: LOG:  child process with pid: 17049 exits with status 512
2016-03-22 03:02:25: pid 55911: LOG:  fork a new child process with pid: 20350
2016-03-22 03:02:25: pid 55911: LOG:  child process with pid: 17022 exits with status 512
2016-03-22 03:02:25: pid 55911: LOG:  fork a new child process with pid: 20351
pg_xlog/000000B60000000F000000F3
pg_xlog/000000B60000000F000000F4
pg_xlog/000000B60000000F000000F5
pg_xlog/000000B60000000F000000F6
pg_xlog/000000B60000000F000000F7
pg_xlog/000000B60000000F000000F8
pg_xlog/000000B60000000F000000F9
pg_xlog/000000B60000000F000000FA
pg_xlog/000000B60000000F000000FB
pg_xlog/000000B60000000F000000FC
pg_xlog/000000B60000000F000000FD
pg_xlog/000000B60000000F000000FE
pg_xlog/000000B60000000F000000FF
pg_xlog/000000B60000001000000000
2016-03-22 03:02:27: pid 55911: LOG:  child process with pid: 15993 exits with status 512
2016-03-22 03:02:27: pid 55911: LOG:  fork a new child process with pid: 20361
pg_xlog/000000B60000001000000001
2016-03-22 03:02:27: pid 55911: LOG:  child process with pid: 16010 exits with status 512
2016-03-22 03:02:27: pid 55911: LOG:  fork a new child process with pid: 20362
pg_xlog/000000B60000001000000002
pg_xlog/000000B60000001000000003
pg_xlog/000000B60000001000000004
pg_xlog/000000B60000001000000005
pg_xlog/000000B60000001000000006
pg_xlog/000000B60000001000000007
pg_xlog/000000B60000001000000008
pg_xlog/000000B60000001000000009
pg_xlog/000000B6000000100000000A
pg_xlog/000000B6000000100000000B
pg_xlog/000000B6000000100000000C
pg_xlog/000000B6000000100000000D
pg_xlog/000000B6000000100000000E
pg_xlog/000000B6000000100000000F
2016-03-22 03:02:29: pid 55911: LOG:  child process with pid: 16092 exits with status 512
2016-03-22 03:02:29: pid 55911: LOG:  fork a new child process with pid: 20470
2016-03-22 03:02:29: pid 55911: LOG:  child process with pid: 18827 exits with status 512
2016-03-22 03:02:29: pid 55911: LOG:  fork a new child process with pid: 20471
pg_xlog/000000B60000001000000010
pg_xlog/000000B60000001000000011
pg_xlog/000000B60000001000000012
pg_xlog/000000B60000001000000013
pg_xlog/000000B60000001000000014
pg_xlog/000000B60000001000000015
pg_xlog/000000B60000001000000016
pg_xlog/000000B60000001000000017
pg_xlog/000000B60000001000000018
pg_xlog/000000B60000001000000019
pg_xlog/000000B6000000100000001A
pg_xlog/000000B6000000100000001B
pg_xlog/000000B6000000100000001C
pg_xlog/000000B6000000100000001D
2016-03-22 03:02:31: pid 55911: LOG:  child process with pid: 17028 exits with status 512
2016-03-22 03:02:31: pid 55911: LOG:  fork a new child process with pid: 20516
2016-03-22 03:02:31: pid 55911: LOG:  child process with pid: 15989 exits with status 512
2016-03-22 03:02:31: pid 55911: LOG:  fork a new child process with pid: 20517
pg_xlog/000000B6000000100000001E
pg_xlog/000000B6000000100000001F
pg_xlog/000000B60000001000000020
pg_xlog/000000B60000001000000021
pg_xlog/000000B60000001000000022
pg_xlog/000000B60000001000000023
pg_xlog/000000B60000001000000024
pg_xlog/archive_status/
deleting pg_xlog/archive_status/000000B50000000F000000A0.done
deleting pg_xlog/archive_status/000000B50000000F0000009F.done
deleting pg_xlog/archive_status/000000B50000000F0000009E.done
deleting pg_xlog/archive_status/000000B50000000F0000009D.done
deleting pg_xlog/archive_status/000000B50000000F0000009C.done
deleting pg_xlog/archive_status/000000B50000000F0000009B.done
deleting pg_xlog/archive_status/000000B50000000F0000009A.done
deleting pg_xlog/archive_status/000000B50000000F00000099.done
deleting pg_xlog/archive_status/000000B50000000F00000094.done
deleting pg_xlog/archive_status/000000B50000000F00000093.done
deleting pg_xlog/archive_status/000000B50000000F00000092.done
deleting pg_xlog/archive_status/000000B50000000F00000091.done
deleting pg_xlog/archive_status/000000B50000000F00000090.done
deleting pg_xlog/archive_status/000000B50000000F0000008F.done
deleting pg_xlog/archive_status/000000B50000000F0000008E.done
deleting pg_xlog/archive_status/000000B50000000F0000008D.done
deleting pg_xlog/archive_status/000000B50000000F0000008C.done
deleting pg_xlog/archive_status/000000B50000000F0000008B.done
deleting pg_xlog/archive_status/000000B50000000F0000008A.done
deleting pg_xlog/archive_status/000000B50000000F00000089.done
deleting pg_xlog/archive_status/000000B50000000F00000088.done
deleting pg_xlog/archive_status/000000B50000000F00000087.done
deleting pg_xlog/archive_status/000000B50000000F00000086.done
deleting pg_xlog/archive_status/000000B50000000F00000085.done
deleting pg_xlog/archive_status/000000B50000000F00000084.done
deleting pg_xlog/archive_status/000000B50000000F00000083.done
deleting pg_xlog/archive_status/000000B50000000F00000082.done
deleting pg_xlog/archive_status/000000B50000000F00000081.done
deleting pg_xlog/archive_status/000000B50000000F00000080.done
deleting pg_xlog/archive_status/000000B50000000F0000007F.done
deleting pg_xlog/archive_status/000000B50000000F0000007E.done
deleting pg_xlog/archive_status/000000B50000000F0000007D.done
deleting pg_xlog/archive_status/000000B50000000F0000007C.done
deleting pg_xlog/archive_status/000000B50000000F0000007B.done
deleting pg_xlog/archive_status/000000B50000000F0000007A.done
deleting pg_xlog/archive_status/000000B50000000F00000079.done
deleting pg_xlog/archive_status/000000B50000000F00000078.done
deleting pg_xlog/archive_status/000000B50000000F00000077.done
deleting pg_xlog/archive_status/000000B50000000F00000076.done
deleting pg_xlog/archive_status/000000B50000000F00000075.done
deleting pg_xlog/archive_status/000000B50000000F00000074.done
deleting pg_xlog/archive_status/000000B50000000F00000073.done
deleting pg_xlog/archive_status/000000B50000000F00000072.done
deleting pg_xlog/archive_status/000000B50000000F00000071.done
deleting pg_xlog/archive_status/000000B50000000F00000070.done
deleting pg_xlog/archive_status/000000B50000000F0000006F.done
deleting pg_xlog/archive_status/000000B50000000F0000006E.done
deleting pg_xlog/archive_status/000000B50000000F0000006D.done
deleting pg_xlog/archive_status/000000B50000000F0000006C.done
deleting pg_xlog/archive_status/000000B50000000F0000006B.done
deleting pg_xlog/archive_status/000000B50000000F0000006A.done
deleting pg_xlog/archive_status/000000B50000000F00000069.done
deleting pg_xlog/archive_status/000000B50000000F00000068.done
deleting pg_xlog/archive_status/000000B50000000F00000067.done
deleting pg_xlog/archive_status/000000B50000000F00000067.00005CD8.backup.done
pg_xlog/archive_status/000000B00000000E000000E5.done
pg_xlog/archive_status/000000B00000000E000000E6.done
pg_xlog/archive_status/000000B00000000E000000E7.done
pg_xlog/archive_status/000000B00000000E000000E8.done
pg_xlog/archive_status/000000B00000000E000000E9.done
pg_xlog/archive_status/000000B10000000E000000E5.done
pg_xlog/archive_status/000000B10000000E000000E6.done
pg_xlog/archive_status/000000B10000000E000000E7.done
pg_xlog/archive_status/000000B10000000E000000E8.done
pg_xlog/archive_status/000000B10000000E000000E9.done
pg_xlog/archive_status/000000B10000000E000000EA.done
pg_xlog/archive_status/000000B10000000E000000EB.done
pg_xlog/archive_status/000000B10000000E000000EC.done
pg_xlog/archive_status/000000B10000000E000000ED.done
pg_xlog/archive_status/000000B10000000E000000EE.done
pg_xlog/archive_status/000000B10000000E000000EF.done
pg_xlog/archive_status/000000B10000000E000000F0.done
pg_xlog/archive_status/000000B10000000E000000F1.done
pg_xlog/archive_status/000000B10000000E000000F2.done
pg_xlog/archive_status/000000B10000000E000000F3.done
pg_xlog/archive_status/000000B10000000E000000F4.done
pg_xlog/archive_status/000000B10000000E000000F5.done
pg_xlog/archive_status/000000B10000000E000000F6.done
pg_xlog/archive_status/000000B10000000E000000F7.done
pg_xlog/archive_status/000000B10000000E000000F8.done
pg_xlog/archive_status/000000B10000000E000000F9.done
pg_xlog/archive_status/000000B10000000E000000FA.done
pg_xlog/archive_status/000000B10000000E000000FB.done
pg_xlog/archive_status/000000B10000000E000000FC.done
pg_xlog/archive_status/000000B10000000E000000FD.done
pg_xlog/archive_status/000000B10000000E000000FE.done
pg_xlog/archive_status/000000B10000000E000000FF.done
pg_xlog/archive_status/000000B10000000F00000000.done
pg_xlog/archive_status/000000B10000000F00000001.done
pg_xlog/archive_status/000000B10000000F00000002.done
pg_xlog/archive_status/000000B10000000F00000003.done
pg_xlog/archive_status/000000B10000000F00000004.done
pg_xlog/archive_status/000000B10000000F00000005.done
pg_xlog/archive_status/000000B10000000F00000006.done
pg_xlog/archive_status/000000B10000000F00000007.done
pg_xlog/archive_status/000000B10000000F00000008.done
pg_xlog/archive_status/000000B20000000E000000E5.done
pg_xlog/archive_status/000000B20000000E000000E6.done
pg_xlog/archive_status/000000B20000000E000000E7.done
pg_xlog/archive_status/000000B20000000E000000E8.done
pg_xlog/archive_status/000000B20000000E000000E9.done
pg_xlog/archive_status/000000B20000000E000000EA.done
pg_xlog/archive_status/000000B20000000E000000EB.done
pg_xlog/archive_status/000000B20000000E000000EC.done
pg_xlog/archive_status/000000B20000000E000000ED.done
pg_xlog/archive_status/000000B20000000E000000EE.done
pg_xlog/archive_status/000000B20000000E000000EF.done
pg_xlog/archive_status/000000B20000000E000000F0.done
pg_xlog/archive_status/000000B20000000E000000F1.done
pg_xlog/archive_status/000000B20000000E000000F2.done
pg_xlog/archive_status/000000B20000000E000000F3.done
pg_xlog/archive_status/000000B20000000E000000F4.done
pg_xlog/archive_status/000000B20000000E000000F5.done
pg_xlog/archive_status/000000B20000000E000000F6.done
pg_xlog/archive_status/000000B20000000E000000F7.done
pg_xlog/archive_status/000000B20000000E000000F8.done
pg_xlog/archive_status/000000B20000000E000000F9.done
pg_xlog/archive_status/000000B20000000E000000FA.done
pg_xlog/archive_status/000000B20000000E000000FB.done
pg_xlog/archive_status/000000B20000000E000000FC.done
pg_xlog/archive_status/000000B20000000E000000FD.done
pg_xlog/archive_status/000000B20000000E000000FE.done
pg_xlog/archive_status/000000B20000000E000000FF.done
pg_xlog/archive_status/000000B20000000F00000000.done
pg_xlog/archive_status/000000B20000000F00000001.done
pg_xlog/archive_status/000000B20000000F00000002.done
pg_xlog/archive_status/000000B20000000F00000003.done
pg_xlog/archive_status/000000B20000000F00000004.done
pg_xlog/archive_status/000000B20000000F00000005.done
pg_xlog/archive_status/000000B20000000F00000006.done
pg_xlog/archive_status/000000B20000000F00000007.done
pg_xlog/archive_status/000000B20000000F00000008.done
pg_xlog/archive_status/000000B20000000F00000009.done
pg_xlog/archive_status/000000B20000000F0000000A.done
pg_xlog/archive_status/000000B20000000F0000000B.done
pg_xlog/archive_status/000000B20000000F0000000C.done
pg_xlog/archive_status/000000B20000000F0000000D.done
pg_xlog/archive_status/000000B20000000F0000000E.done
pg_xlog/archive_status/000000B20000000F0000000F.done
pg_xlog/archive_status/000000B20000000F00000010.done
pg_xlog/archive_status/000000B20000000F00000011.done
pg_xlog/archive_status/000000B20000000F00000012.done
pg_xlog/archive_status/000000B20000000F00000013.done
pg_xlog/archive_status/000000B20000000F00000014.done
pg_xlog/archive_status/000000B20000000F00000015.done
pg_xlog/archive_status/000000B20000000F00000016.done
pg_xlog/archive_status/000000B20000000F00000017.done
pg_xlog/archive_status/000000B20000000F00000018.done
pg_xlog/archive_status/000000B20000000F00000019.done
pg_xlog/archive_status/000000B20000000F0000001A.done
pg_xlog/archive_status/000000B20000000F0000001B.done
pg_xlog/archive_status/000000B20000000F0000001C.done
pg_xlog/archive_status/000000B20000000F0000001D.done
pg_xlog/archive_status/000000B20000000F0000001E.done
pg_xlog/archive_status/000000B20000000F0000001F.done
pg_xlog/archive_status/000000B20000000F00000020.done
pg_xlog/archive_status/000000B20000000F00000021.done
pg_xlog/archive_status/000000B20000000F00000022.done
pg_xlog/archive_status/000000B20000000F00000023.done
pg_xlog/archive_status/000000B20000000F00000024.done
pg_xlog/archive_status/000000B20000000F00000025.done
pg_xlog/archive_status/000000B20000000F00000026.done
pg_xlog/archive_status/000000B20000000F00000027.done
pg_xlog/archive_status/000000B30000000E000000E5.done
pg_xlog/archive_status/000000B30000000E000000E6.done
pg_xlog/archive_status/000000B30000000E000000E7.done
pg_xlog/archive_status/000000B30000000E000000E8.done
pg_xlog/archive_status/000000B30000000E000000E9.done
pg_xlog/archive_status/000000B30000000E000000EA.done
pg_xlog/archive_status/000000B30000000E000000EB.done
pg_xlog/archive_status/000000B30000000E000000EC.done
pg_xlog/archive_status/000000B30000000E000000ED.done
pg_xlog/archive_status/000000B30000000E000000EE.done
pg_xlog/archive_status/000000B30000000E000000EF.done
pg_xlog/archive_status/000000B30000000E000000F0.done
pg_xlog/archive_status/000000B30000000E000000F1.done
pg_xlog/archive_status/000000B30000000E000000F2.done
pg_xlog/archive_status/000000B30000000E000000F3.done
pg_xlog/archive_status/000000B30000000E000000F4.done
pg_xlog/archive_status/000000B30000000E000000F5.done
pg_xlog/archive_status/000000B30000000E000000F6.done
pg_xlog/archive_status/000000B30000000E000000F7.done
pg_xlog/archive_status/000000B30000000E000000F8.done
pg_xlog/archive_status/000000B30000000E000000F9.done
pg_xlog/archive_status/000000B30000000E000000FA.done
pg_xlog/archive_status/000000B30000000E000000FB.done
pg_xlog/archive_status/000000B30000000E000000FC.done
pg_xlog/archive_status/000000B30000000E000000FD.done
pg_xlog/archive_status/000000B30000000E000000FE.done
pg_xlog/archive_status/000000B30000000E000000FF.done
pg_xlog/archive_status/000000B30000000F00000000.done
pg_xlog/archive_status/000000B30000000F00000001.done
pg_xlog/archive_status/000000B30000000F00000002.done
pg_xlog/archive_status/000000B30000000F00000003.done
pg_xlog/archive_status/000000B30000000F00000004.done
pg_xlog/archive_status/000000B30000000F00000005.done
pg_xlog/archive_status/000000B30000000F00000006.done
pg_xlog/archive_status/000000B30000000F00000007.done
pg_xlog/archive_status/000000B30000000F00000008.done
pg_xlog/archive_status/000000B30000000F00000009.done
pg_xlog/archive_status/000000B30000000F0000000A.done
pg_xlog/archive_status/000000B30000000F0000000B.done
pg_xlog/archive_status/000000B30000000F0000000C.done
pg_xlog/archive_status/000000B30000000F0000000D.done
pg_xlog/archive_status/000000B30000000F0000000E.done
pg_xlog/archive_status/000000B30000000F0000000F.done
pg_xlog/archive_status/000000B30000000F00000010.done
pg_xlog/archive_status/000000B30000000F00000011.done
pg_xlog/archive_status/000000B30000000F00000012.done
pg_xlog/archive_status/000000B30000000F00000013.done
pg_xlog/archive_status/000000B30000000F00000014.done
pg_xlog/archive_status/000000B30000000F00000015.done
pg_xlog/archive_status/000000B30000000F00000016.done
pg_xlog/archive_status/000000B30000000F00000017.done
pg_xlog/archive_status/000000B30000000F00000018.done
pg_xlog/archive_status/000000B30000000F00000019.done
pg_xlog/archive_status/000000B30000000F0000001A.done
pg_xlog/archive_status/000000B30000000F0000001B.done
pg_xlog/archive_status/000000B30000000F0000001C.done
pg_xlog/archive_status/000000B30000000F0000001D.done
pg_xlog/archive_status/000000B30000000F0000001E.done
pg_xlog/archive_status/000000B30000000F0000001F.done
pg_xlog/archive_status/000000B30000000F00000020.done
pg_xlog/archive_status/000000B30000000F00000021.done
pg_xlog/archive_status/000000B30000000F00000022.done
pg_xlog/archive_status/000000B30000000F00000023.done
pg_xlog/archive_status/000000B30000000F00000024.done
pg_xlog/archive_status/000000B30000000F00000025.done
pg_xlog/archive_status/000000B30000000F00000026.done
pg_xlog/archive_status/000000B30000000F00000027.done
pg_xlog/archive_status/000000B30000000F00000028.done
pg_xlog/archive_status/000000B30000000F00000029.done
pg_xlog/archive_status/000000B30000000F0000002A.done
pg_xlog/archive_status/000000B30000000F0000002B.done
pg_xlog/archive_status/000000B30000000F0000002C.done
pg_xlog/archive_status/000000B30000000F0000002D.done
pg_xlog/archive_status/000000B30000000F0000002E.done
pg_xlog/archive_status/000000B30000000F0000002F.done
pg_xlog/archive_status/000000B30000000F00000030.done
pg_xlog/archive_status/000000B30000000F00000031.done
pg_xlog/archive_status/000000B30000000F00000032.done
pg_xlog/archive_status/000000B30000000F00000033.done
pg_xlog/archive_status/000000B30000000F00000034.done
pg_xlog/archive_status/000000B30000000F00000035.done
pg_xlog/archive_status/000000B30000000F00000036.done
pg_xlog/archive_status/000000B30000000F00000037.done
pg_xlog/archive_status/000000B30000000F00000038.done
pg_xlog/archive_status/000000B30000000F00000039.done
pg_xlog/archive_status/000000B30000000F0000003A.done
pg_xlog/archive_status/000000B30000000F0000003B.done
pg_xlog/archive_status/000000B30000000F0000003C.done
pg_xlog/archive_status/000000B30000000F0000003D.done
pg_xlog/archive_status/000000B30000000F0000003E.done
pg_xlog/archive_status/000000B30000000F0000003F.done
pg_xlog/archive_status/000000B30000000F00000040.done
pg_xlog/archive_status/000000B30000000F00000041.done
pg_xlog/archive_status/000000B30000000F00000042.done
pg_xlog/archive_status/000000B30000000F00000043.done
pg_xlog/archive_status/000000B30000000F00000044.done
pg_xlog/archive_status/000000B30000000F00000045.done
pg_xlog/archive_status/000000B30000000F00000046.done
pg_xlog/archive_status/000000B40000000F00000054.done
pg_xlog/archive_status/000000B40000000F00000055.done
pg_xlog/archive_status/000000B40000000F00000056.done
pg_xlog/archive_status/000000B40000000F0000005F.done
pg_xlog/archive_status/000000B40000000F00000060.done
pg_xlog/archive_status/000000B40000000F00000061.done
pg_xlog/archive_status/000000B40000000F00000062.done
pg_xlog/archive_status/000000B40000000F00000063.done
pg_xlog/archive_status/000000B40000000F00000064.done
pg_xlog/archive_status/000000B50000000F0000005E.done
pg_xlog/archive_status/000000B50000000F00000095.done
pg_xlog/archive_status/000000B50000000F00000096.done
pg_xlog/archive_status/000000B50000000F00000097.done
pg_xlog/archive_status/000000B50000000F00000098.done
pg_xlog/archive_status/000000B50000000F000000A1.done
pg_xlog/archive_status/000000B6.history.done
pg_xlog/archive_status/000000B60000000F000000A1.done
pg_xlog/archive_status/000000B60000000F000000A2.done
pg_xlog/archive_status/000000B60000000F000000A3.done
pg_xlog/archive_status/000000B60000000F000000A4.done
pg_xlog/archive_status/000000B60000000F000000A5.00851440.backup.done
pg_xlog/archive_status/000000B60000000F000000A5.done
pg_xlog/archive_status/000000B60000000F000000A6.done
pg_xlog/archive_status/000000B60000000F000000A7.done
pg_xlog/archive_status/000000B60000000F000000A8.done
pg_xlog/archive_status/000000B60000000F000000A9.done
pg_xlog/archive_status/000000B60000000F000000AA.done
pg_xlog/archive_status/000000B60000000F000000AB.done
pg_xlog/archive_status/000000B60000000F000000AC.done
pg_xlog/archive_status/000000B60000000F000000AD.done
pg_xlog/archive_status/000000B60000000F000000AE.done
pg_xlog/archive_status/000000B60000000F000000AF.done
pg_xlog/archive_status/000000B60000000F000000B0.done
pg_xlog/archive_status/000000B60000000F000000B1.done
pg_xlog/archive_status/000000B60000000F000000B2.done
pg_xlog/archive_status/000000B60000000F000000B3.done
pg_xlog/archive_status/000000B60000000F000000B4.done
pg_xlog/archive_status/000000B60000000F000000B5.done
pg_xlog/archive_status/000000B60000000F000000B6.done
pg_xlog/archive_status/000000B60000000F000000B7.done
pg_xlog/archive_status/000000B60000000F000000B8.done
pg_xlog/archive_status/000000B60000000F000000B9.done
pg_xlog/archive_status/000000B60000000F000000BA.done

sent 2214978035 bytes  received 105679 bytes  108052864.10 bytes/sec
total size is 6728389367  speedup is 3.04
+ RET_VAL=0
+ log 'rsync return value is : 0'
+ '[' '!' 'rsync return value is : 0' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:32.36] - rsync return value is : 0'
+ check_rsync 0
+ '[' '!' 0 ']'
+ '[' '!' 0 -eq 0 ']'
+ log 'setting node 1.1.1.6 as secondary!'
+ '[' '!' 'setting node 1.1.1.6 as secondary!' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:32.36] - setting node 1.1.1.6 as secondary!'
+ su - postgres -c 'ssh 1.1.1.6 '\''cd /home/postgres/databases/fabrix;rm -f recovery.done;rm -f trigger;'\'''
+ log 'creating new recovery.conf file in /tmp'
+ '[' '!' 'creating new recovery.conf file in /tmp' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:32.53] - creating new recovery.conf file in /tmp'
+ cat
+ log 'transfering /tmp/recovery.conf into 1.1.1.6:/home/postgres/databases/fabrix/ dir.'
+ '[' '!' 'transfering /tmp/recovery.conf into 1.1.1.6:/home/postgres/databases/fabrix/ dir.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:32.53] - transfering /tmp/recovery.conf into 1.1.1.6:/home/postgres/databases/fabrix/ dir.'
+ su - postgres -c 'scp /tmp/recovery_sample.conf 1.1.1.6:/home/postgres/databases/fabrix/recovery.conf'
+ log 'starting 1.1.1.6 node.'
+ '[' '!' 'starting 1.1.1.6 node.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:32.75] - starting 1.1.1.6 node.'
+ su - postgres -c 'ssh 1.1.1.6 '\''pg_ctl -D /home/postgres/databases/fabrix start --log=/home/postgres/databases/fabrix/postgres.out'\'''
server starting
+ log 'creating /home/postgres/pg.control file on 1.1.1.6 in order to control the postgres'\''s monit resource.'
+ '[' '!' 'creating /home/postgres/pg.control file on 1.1.1.6 in order to control the postgres'\''s monit resource.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:32.92] - creating /home/postgres/pg.control file on 1.1.1.6 in order to control the postgres'\''s monit resource.'
+ su - postgres -c 'ssh 1.1.1.6 '\''touch /home/postgres/pg.control'\'''
+ log 'Failback Done!'
+ '[' '!' 'Failback Done!' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:33.08] - Failback Done!'
+ log ' '
+ '[' '!' ' ' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:33.08] -  '
+ log '--------------------------          END           --------------------------'
+ '[' '!' '--------------------------          END           --------------------------' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:33.08] - --------------------------          END           --------------------------'
+ log ' '
+ '[' '!' ' ' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:02:33.09] -  '
+ exit 0
2016-03-22 03:02:33: pid 55911: LOG:  child process with pid: 15674 exits with status 0
2016-03-22 03:02:33: pid 55911: LOG:  child process with pid: 15674 exited with success and will not be restarted
2016-03-22 03:02:33: pid 55911: LOG:  child process with pid: 16159 exits with status 512
2016-03-22 03:02:33: pid 55911: LOG:  fork a new child process with pid: 20753
2016-03-22 03:02:35: pid 55911: LOG:  child process with pid: 20351 exits with status 512
2016-03-22 03:02:35: pid 55911: LOG:  fork a new child process with pid: 20917
2016-03-22 03:02:35: pid 55911: LOG:  child process with pid: 15965 exits with status 512
2016-03-22 03:02:35: pid 55911: LOG:  fork a new child process with pid: 20919
2016-03-22 03:02:37: pid 16960: LOG:  received failback request for node_id: 0 from pid [16960]
2016-03-22 03:02:37: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:02:37: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:02:37: pid 55911: LOG:  starting fail back. reconnect host 1.1.1.6(5432)
2016-03-22 03:02:37: pid 55911: LOG:  Do not restart children because we are failbacking node id 0 host1.1.1.6 port:5432 and we are in streaming replication mode
2016-03-22 03:02:37: pid 55911: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2016-03-22 03:02:37: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:02:37: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:02:37: pid 55911: LOG:  find_primary_node: primary node id is 1
2016-03-22 03:02:37: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:02:38: pid 55911: LOG:  failover: set new primary node: 1
2016-03-22 03:02:38: pid 55911: LOG:  failover: set new master node: 0
2016-03-22 03:02:38: pid 55911: LOG:  failback done. reconnect host 1.1.1.6(5432)
2016-03-22 03:02:38: pid 16961: LOG:  worker process received restart request
2016-03-22 03:02:38: pid 20362: LOG:  cannot get connection pool for user: "fabrix" database: "manager", while discarding connection pool
2016-03-22 03:02:38: pid 20362: ERROR:  unable to read message kind
2016-03-22 03:02:38: pid 20362: DETAIL:  kind does not match between master(0) slot[1] (53)
2016-03-22 03:02:38: pid 20362: LOG:  failback event detected
2016-03-22 03:02:38: pid 20362: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15996: LOG:  failback event detected
2016-03-22 03:02:38: pid 15996: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 19739: LOG:  failback event detected
2016-03-22 03:02:38: pid 19739: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15938: LOG:  failback event detected
2016-03-22 03:02:38: pid 15938: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15964: LOG:  failback event detected
2016-03-22 03:02:38: pid 15964: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16093: LOG:  failback event detected
2016-03-22 03:02:38: pid 16093: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17079: LOG:  failback event detected
2016-03-22 03:02:38: pid 17079: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16989: LOG:  selecting backend connection
2016-03-22 03:02:38: pid 16989: DETAIL:  failback event detected, discarding existing connections
2016-03-22 03:02:38: pid 17075: LOG:  failback event detected
2016-03-22 03:02:38: pid 17075: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16082: LOG:  failback event detected
2016-03-22 03:02:38: pid 16082: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 19989: LOG:  failback event detected
2016-03-22 03:02:38: pid 19989: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17069: LOG:  failback event detected
2016-03-22 03:02:38: pid 17069: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16999: LOG:  failback event detected
2016-03-22 03:02:38: pid 16999: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16995: LOG:  selecting backend connection
2016-03-22 03:02:38: pid 16995: DETAIL:  failback event detected, discarding existing connections
2016-03-22 03:02:38: pid 15952: LOG:  failback event detected
2016-03-22 03:02:38: pid 15952: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17234: LOG:  failback event detected
2016-03-22 03:02:38: pid 17234: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15984: LOG:  failback event detected
2016-03-22 03:02:38: pid 15984: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15986: LOG:  failback event detected
2016-03-22 03:02:38: pid 15986: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16004: LOG:  failback event detected
2016-03-22 03:02:38: pid 16004: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16975: LOG:  failback event detected
2016-03-22 03:02:38: pid 16975: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16980: LOG:  failback event detected
2016-03-22 03:02:38: pid 16980: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17048: LOG:  failback event detected
2016-03-22 03:02:38: pid 17048: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17065: LOG:  failback event detected
2016-03-22 03:02:38: pid 17065: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15949: LOG:  failback event detected
2016-03-22 03:02:38: pid 15949: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16971: LOG:  failback event detected
2016-03-22 03:02:38: pid 16971: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16013: LOG:  failback event detected
2016-03-22 03:02:38: pid 16013: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17764: LOG:  failback event detected
2016-03-22 03:02:38: pid 17764: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17059: LOG:  failback event detected
2016-03-22 03:02:38: pid 17059: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17074: LOG:  failback event detected
2016-03-22 03:02:38: pid 17074: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16104: LOG:  failback event detected
2016-03-22 03:02:38: pid 16104: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16111: LOG:  failback event detected
2016-03-22 03:02:38: pid 16111: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 19484: LOG:  failback event detected
2016-03-22 03:02:38: pid 19484: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16094: LOG:  failback event detected
2016-03-22 03:02:38: pid 16094: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16008: LOG:  failback event detected
2016-03-22 03:02:38: pid 16008: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17064: LOG:  selecting backend connection
2016-03-22 03:02:38: pid 17064: DETAIL:  failback event detected, discarding existing connections
2016-03-22 03:02:38: pid 16972: LOG:  failback event detected
2016-03-22 03:02:38: pid 16972: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16031: LOG:  failback event detected
2016-03-22 03:02:38: pid 16031: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16009: LOG:  failback event detected
2016-03-22 03:02:38: pid 16009: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16043: LOG:  failback event detected
2016-03-22 03:02:38: pid 16043: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15930: LOG:  failback event detected
2016-03-22 03:02:38: pid 15930: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 15931: LOG:  failback event detected
2016-03-22 03:02:38: pid 15931: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 19738: LOG:  failback event detected
2016-03-22 03:02:38: pid 19738: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16007: LOG:  failback event detected
2016-03-22 03:02:38: pid 16007: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17785: LOG:  failback event detected
2016-03-22 03:02:38: pid 17785: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 16165: LOG:  failback event detected
2016-03-22 03:02:38: pid 16165: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17422: LOG:  failback event detected
2016-03-22 03:02:38: pid 17422: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17034: LOG:  selecting backend connection
2016-03-22 03:02:38: pid 17034: DETAIL:  failback event detected, discarding existing connections
2016-03-22 03:02:38: pid 19218: LOG:  failback event detected
2016-03-22 03:02:38: pid 19218: DETAIL:  restarting myself
2016-03-22 03:02:38: pid 17016: LOG:  failback event detected
2016-03-22 03:02:38: pid 17016: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 16960: LOG:  restart request received in pcp child process
2016-03-22 03:02:39: pid 55911: LOG:  PCP child 16960 exits with status 256 in failover()
2016-03-22 03:02:39: pid 55911: LOG:  fork a new PCP child pid 21319 in failover()
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15857 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21321
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15919 exits with status 256
2016-03-22 03:02:39: pid 21321: LOG:  failback event detected
2016-03-22 03:02:39: pid 21321: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21322
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15920 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21323
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15925 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21324
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15929 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21325
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15930 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21326
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15931 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21327
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15932 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21328
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15934 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21329
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15938 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21330
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15939 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21331
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15940 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21332
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15942 exits with status 512
2016-03-22 03:02:39: pid 21332: LOG:  failback event detected
2016-03-22 03:02:39: pid 21332: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21333
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15946 exits with status 256
2016-03-22 03:02:39: pid 21333: LOG:  failback event detected
2016-03-22 03:02:39: pid 21333: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21334
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15949 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21335
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15952 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21336
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15962 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21337
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15964 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21338
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15967 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21339
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15968 exits with status 256
2016-03-22 03:02:39: pid 21339: LOG:  failback event detected
2016-03-22 03:02:39: pid 21339: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21340
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15972 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21341
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15983 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21342
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15984 exits with status 256
2016-03-22 03:02:39: pid 21342: LOG:  failback event detected
2016-03-22 03:02:39: pid 21342: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21343
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15986 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21344
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15996 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21345
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16004 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21346
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16007 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21347
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16008 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21348
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16009 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21349
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16013 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21350
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16016 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21351
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16022 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21352
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16028 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21353
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16030 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21354
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16031 exits with status 256
2016-03-22 03:02:39: pid 21354: LOG:  failback event detected
2016-03-22 03:02:39: pid 21354: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21355
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16043 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21356
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16048 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21357
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16049 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21358
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16060 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21359
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16081 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21360
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16082 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21361
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16087 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21362
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16093 exits with status 256
2016-03-22 03:02:39: pid 17083: LOG:  failback event detected
2016-03-22 03:02:39: pid 17083: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 20753: LOG:  failback event detected
2016-03-22 03:02:39: pid 20753: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 15963: LOG:  failback event detected
2016-03-22 03:02:39: pid 15963: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 15977: LOG:  failback event detected
2016-03-22 03:02:39: pid 15977: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 20917: LOG:  failback event detected
2016-03-22 03:02:39: pid 20917: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 15955: LOG:  failback event detected
2016-03-22 03:02:39: pid 15955: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21363
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16094 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21365
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16101 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21366
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15953 exits with status 256
2016-03-22 03:02:39: pid 21366: LOG:  failback event detected
2016-03-22 03:02:39: pid 21366: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21367
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15959 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21368
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15955 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21369
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15963 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21370
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 15977 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21371
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16036 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21372
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16050 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21373
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16062 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21374
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16072 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21375
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16104 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21376
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16111 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21377
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16131 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21378
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16143 exits with status 256
2016-03-22 03:02:39: pid 21378: LOG:  failback event detected
2016-03-22 03:02:39: pid 21378: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21379
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16147 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21380
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16153 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21381
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16154 exits with status 256
2016-03-22 03:02:39: pid 21381: LOG:  failback event detected
2016-03-22 03:02:39: pid 21381: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21382
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16165 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21383
2016-03-22 03:02:39: pid 55911: LOG:  worker child process with pid: 16961 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new worker child process with pid: 21384
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16964 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21385
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16965 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21387
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16968 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21388
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16970 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21389
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16971 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21390
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16972 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21391
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16975 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21392
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16977 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21393
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16978 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21394
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16979 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21395
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16980 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21396
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16986 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21397
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16992 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21398
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16993 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21399
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16994 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21400
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16997 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21401
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16999 exits with status 256
2016-03-22 03:02:39: pid 21401: LOG:  failback event detected
2016-03-22 03:02:39: pid 21401: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21402
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17001 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21403
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17006 exits with status 256
2016-03-22 03:02:39: pid 21403: LOG:  failback event detected
2016-03-22 03:02:39: pid 21403: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21404
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17008 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21405
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17009 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21406
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17011 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21407
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17016 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21408
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17018 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21409
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17019 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21410
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17024 exits with status 256
2016-03-22 03:02:39: pid 21410: LOG:  failback event detected
2016-03-22 03:02:39: pid 21410: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21411
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17026 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21412
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17027 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21413
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17030 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21414
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17032 exits with status 512
2016-03-22 03:02:39: pid 21414: LOG:  failback event detected
2016-03-22 03:02:39: pid 21414: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21415
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17033 exits with status 256
2016-03-22 03:02:39: pid 21415: LOG:  failback event detected
2016-03-22 03:02:39: pid 21415: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21416
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17036 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21417
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17037 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21418
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17044 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21419
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17046 exits with status 256
2016-03-22 03:02:39: pid 21419: LOG:  failback event detected
2016-03-22 03:02:39: pid 21419: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21420
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17048 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21421
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17050 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21422
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17054 exits with status 256
2016-03-22 03:02:39: pid 21422: LOG:  failback event detected
2016-03-22 03:02:39: pid 21422: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21423
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17056 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21424
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17057 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21425
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17058 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21426
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17059 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21427
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17061 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21428
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17062 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21429
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17063 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21430
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17065 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21431
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17067 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21432
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17069 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21433
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17071 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21434
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17074 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21435
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17075 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21436
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17079 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21437
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17082 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21438
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17083 exits with status 256
2016-03-22 03:02:39: pid 21438: LOG:  failback event detected
2016-03-22 03:02:39: pid 21438: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21439
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17084 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21440
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17085 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21441
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17234 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21442
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17422 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21443
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17500 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21444
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17613 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21445
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17764 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21446
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17785 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21447
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17929 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21448
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17930 exits with status 256
2016-03-22 03:02:39: pid 21448: LOG:  failback event detected
2016-03-22 03:02:39: pid 21448: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21449
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17944 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21450
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 18197 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21451
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 18638 exits with status 256
2016-03-22 03:02:39: pid 21451: LOG:  failback event detected
2016-03-22 03:02:39: pid 21451: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21452
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 18663 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21453
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 18800 exits with status 256
2016-03-22 03:02:39: pid 21453: LOG:  failback event detected
2016-03-22 03:02:39: pid 21453: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21454
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 18826 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21455
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 18876 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21456
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19010 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21457
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19021 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21458
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19144 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21459
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19204 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21460
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19205 exits with status 256
2016-03-22 03:02:39: pid 21460: LOG:  failback event detected
2016-03-22 03:02:39: pid 21460: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21461
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19218 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21462
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19219 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21463
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19333 exits with status 512
2016-03-22 03:02:39: pid 21463: LOG:  failback event detected
2016-03-22 03:02:39: pid 21463: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21464
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19484 exits with status 256
2016-03-22 03:02:39: pid 21464: LOG:  failback event detected
2016-03-22 03:02:39: pid 21464: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21465
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19497 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21466
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19589 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21467
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19590 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21468
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19738 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21469
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19739 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21470
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19977 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21471
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19988 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21472
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 19989 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21473
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20182 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21474
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20183 exits with status 256
2016-03-22 03:02:39: pid 21474: LOG:  failback event detected
2016-03-22 03:02:39: pid 21474: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21475
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20288 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21476
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20289 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21477
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20350 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21478
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20361 exits with status 512
2016-03-22 03:02:39: pid 21478: LOG:  failback event detected
2016-03-22 03:02:39: pid 21478: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21479
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20362 exits with status 256
2016-03-22 03:02:39: pid 21479: LOG:  failback event detected
2016-03-22 03:02:39: pid 21479: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21480
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20470 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21481
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20516 exits with status 256
2016-03-22 03:02:39: pid 21481: LOG:  failback event detected
2016-03-22 03:02:39: pid 21481: DETAIL:  restarting myself
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21482
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20753 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21483
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 20917 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21484
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21321 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21485
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21332 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21486
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21333 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21487
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21339 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21488
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21342 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21489
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21354 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21490
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21366 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21491
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21378 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21492
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21381 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21493
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21401 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21494
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21403 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21495
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21410 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21496
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21414 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21497
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21415 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21498
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21419 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21499
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21422 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21500
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21438 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21501
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21448 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21502
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21450 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21503
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21451 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21504
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21453 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21505
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21460 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21506
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21463 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21507
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21464 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21508
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21474 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21509
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21478 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21510
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21479 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21511
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 21481 exits with status 256
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21512
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 16995 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21513
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17064 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21514
2016-03-22 03:02:39: pid 55911: LOG:  child process with pid: 17034 exits with status 512
2016-03-22 03:02:39: pid 55911: LOG:  fork a new child process with pid: 21515
2016-03-22 03:02:40: pid 55911: LOG:  child process with pid: 16989 exits with status 512
2016-03-22 03:02:40: pid 55911: LOG:  fork a new child process with pid: 21523
2016-03-22 03:02:41: pid 55911: LOG:  child process with pid: 21357 exits with status 512
2016-03-22 03:02:41: pid 55911: LOG:  fork a new child process with pid: 21527
2016-03-22 03:02:42: pid 55911: LOG:  child process with pid: 21361 exits with status 512
2016-03-22 03:02:42: pid 55911: LOG:  fork a new child process with pid: 21566
2016-03-22 03:02:43: pid 55911: LOG:  child process with pid: 21523 exits with status 512
2016-03-22 03:02:43: pid 55911: LOG:  fork a new child process with pid: 21665
2016-03-22 03:02:44: pid 55911: LOG:  child process with pid: 21505 exits with status 512
2016-03-22 03:02:44: pid 55911: LOG:  fork a new child process with pid: 21669
2016-03-22 03:02:45: pid 55911: LOG:  child process with pid: 21527 exits with status 512
2016-03-22 03:02:45: pid 55911: LOG:  fork a new child process with pid: 21673
2016-03-22 03:02:45: pid 15957: LOG:  failback event detected
2016-03-22 03:02:45: pid 15957: DETAIL:  restarting myself
2016-03-22 03:02:45: pid 16152: LOG:  failback event detected
2016-03-22 03:02:45: pid 16152: DETAIL:  restarting myself
2016-03-22 03:02:45: pid 55911: LOG:  child process with pid: 16041 exits with status 256
2016-03-22 03:02:45: pid 55911: LOG:  fork a new child process with pid: 21675
2016-03-22 03:02:45: pid 55911: LOG:  child process with pid: 15957 exits with status 256
2016-03-22 03:02:45: pid 55911: LOG:  fork a new child process with pid: 21676
2016-03-22 03:02:45: pid 55911: LOG:  child process with pid: 16051 exits with status 256
2016-03-22 03:02:45: pid 55911: LOG:  fork a new child process with pid: 21677
2016-03-22 03:02:45: pid 55911: LOG:  child process with pid: 16152 exits with status 256
2016-03-22 03:02:45: pid 55911: LOG:  fork a new child process with pid: 21678
2016-03-22 03:02:45: pid 55911: LOG:  child process with pid: 19978 exits with status 256
2016-03-22 03:02:45: pid 55911: LOG:  fork a new child process with pid: 21679
2016-03-22 03:02:46: pid 55911: LOG:  child process with pid: 21431 exits with status 512
2016-03-22 03:02:46: pid 55911: LOG:  fork a new child process with pid: 21682
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 21669 exits with status 512
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21686
2016-03-22 03:02:47: pid 17020: LOG:  failback event detected
2016-03-22 03:02:47: pid 17020: DETAIL:  restarting myself
2016-03-22 03:02:47: pid 18533: LOG:  failback event detected
2016-03-22 03:02:47: pid 18533: DETAIL:  restarting myself
2016-03-22 03:02:47: pid 16018: LOG:  failback event detected
2016-03-22 03:02:47: pid 16018: DETAIL:  restarting myself
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 17020 exits with status 256
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21688
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 16018 exits with status 256
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21689
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 17015 exits with status 256
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21690
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 17040 exits with status 256
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21691
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 18533 exits with status 256
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21692
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 19483 exits with status 256
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21693
2016-03-22 03:02:47: pid 55911: LOG:  child process with pid: 20517 exits with status 256
2016-03-22 03:02:47: pid 55911: LOG:  fork a new child process with pid: 21694
2016-03-22 03:02:48: pid 55911: LOG:  child process with pid: 21673 exits with status 512
2016-03-22 03:02:48: pid 55911: LOG:  fork a new child process with pid: 21818
2016-03-22 03:02:48: pid 19498: LOG:  failback event detected
2016-03-22 03:02:48: pid 19498: DETAIL:  restarting myself
2016-03-22 03:02:48: pid 55911: LOG:  child process with pid: 19498 exits with status 256
2016-03-22 03:02:48: pid 55911: LOG:  fork a new child process with pid: 21820
2016-03-22 03:02:49: pid 17073: LOG:  failback event detected
2016-03-22 03:02:49: pid 17073: DETAIL:  restarting myself
2016-03-22 03:02:49: pid 55911: LOG:  child process with pid: 21682 exits with status 512
2016-03-22 03:02:49: pid 55911: LOG:  fork a new child process with pid: 21824
2016-03-22 03:02:49: pid 55911: LOG:  child process with pid: 17073 exits with status 256
2016-03-22 03:02:49: pid 55911: LOG:  fork a new child process with pid: 21825
2016-03-22 03:02:49: pid 55911: LOG:  child process with pid: 16148 exits with status 256
2016-03-22 03:02:49: pid 55911: LOG:  fork a new child process with pid: 21826
2016-03-22 03:02:49: pid 55911: LOG:  child process with pid: 18666 exits with status 256
2016-03-22 03:02:49: pid 55911: LOG:  fork a new child process with pid: 21827
2016-03-22 03:02:50: pid 55911: LOG:  child process with pid: 21489 exits with status 512
2016-03-22 03:02:50: pid 55911: LOG:  fork a new child process with pid: 21831
2016-03-22 03:02:51: pid 55911: LOG:  child process with pid: 21689 exits with status 512
2016-03-22 03:02:51: pid 55911: LOG:  fork a new child process with pid: 21855
2016-03-22 03:02:51: pid 16109: LOG:  failback event detected
2016-03-22 03:02:51: pid 16109: DETAIL:  restarting myself
2016-03-22 03:02:51: pid 55911: LOG:  child process with pid: 16109 exits with status 256
2016-03-22 03:02:51: pid 55911: LOG:  fork a new child process with pid: 21858
2016-03-22 03:02:52: pid 55911: LOG:  child process with pid: 21485 exits with status 512
2016-03-22 03:02:52: pid 55911: LOG:  fork a new child process with pid: 21860
2016-03-22 03:02:53: pid 55911: LOG:  child process with pid: 21827 exits with status 512
2016-03-22 03:02:53: pid 55911: LOG:  fork a new child process with pid: 21967
2016-03-22 03:02:54: pid 55911: LOG:  child process with pid: 21855 exits with status 512
2016-03-22 03:02:54: pid 55911: LOG:  fork a new child process with pid: 22007
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 21860 exits with status 512
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22018
2016-03-22 03:02:55: pid 17012: LOG:  failback event detected
2016-03-22 03:02:55: pid 17012: DETAIL:  restarting myself
2016-03-22 03:02:55: pid 17055: LOG:  failback event detected
2016-03-22 03:02:55: pid 17055: DETAIL:  restarting myself
2016-03-22 03:02:55: pid 18101: LOG:  failback event detected
2016-03-22 03:02:55: pid 18101: DETAIL:  restarting myself
2016-03-22 03:02:55: pid 19384: LOG:  failback event detected
2016-03-22 03:02:55: pid 19384: DETAIL:  restarting myself
2016-03-22 03:02:55: pid 20143: LOG:  failback event detected
2016-03-22 03:02:55: pid 20143: DETAIL:  restarting myself
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 16067 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22021
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 16963 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22022
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 17012 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22023
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 17039 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22024
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 17055 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22025
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 18101 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22026
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 19384 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22027
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 20143 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22028
2016-03-22 03:02:55: pid 55911: LOG:  child process with pid: 20919 exits with status 256
2016-03-22 03:02:55: pid 55911: LOG:  fork a new child process with pid: 22029
2016-03-22 03:02:56: pid 55911: LOG:  child process with pid: 21967 exits with status 512
2016-03-22 03:02:56: pid 55911: LOG:  fork a new child process with pid: 22034
2016-03-22 03:02:56: pid 16967: LOG:  failback event detected
2016-03-22 03:02:56: pid 16967: DETAIL:  restarting myself
2016-03-22 03:02:56: pid 55911: LOG:  child process with pid: 16967 exits with status 256
2016-03-22 03:02:56: pid 55911: LOG:  fork a new child process with pid: 22037
2016-03-22 03:02:57: pid 55911: LOG:  child process with pid: 21858 exits with status 512
2016-03-22 03:02:57: pid 55911: LOG:  fork a new child process with pid: 22039
2016-03-22 03:02:58: pid 55911: LOG:  child process with pid: 22018 exits with status 512
2016-03-22 03:02:58: pid 55911: LOG:  fork a new child process with pid: 22138
2016-03-22 03:02:58: pid 16983: LOG:  failback event detected
2016-03-22 03:02:58: pid 16983: DETAIL:  restarting myself
2016-03-22 03:02:58: pid 55911: LOG:  child process with pid: 16983 exits with status 256
2016-03-22 03:02:58: pid 55911: LOG:  fork a new child process with pid: 22141
2016-03-22 03:02:58: pid 55911: LOG:  child process with pid: 17045 exits with status 256
2016-03-22 03:02:58: pid 55911: LOG:  fork a new child process with pid: 22142
2016-03-22 03:02:59: pid 55911: LOG:  child process with pid: 21825 exits with status 512
2016-03-22 03:02:59: pid 55911: LOG:  fork a new child process with pid: 22145
2016-03-22 03:03:02: pid 19383: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 19383: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 19383: LOG:  received degenerate backend request for node_id: 1 from pid [19383]
2016-03-22 03:03:02: pid 16170: LOG:  received degenerate backend request for node_id: 1 from pid [16170]
2016-03-22 03:03:02: pid 18532: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 18532: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15960: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15960: DETAI2016-03-22 03:03:02: pid 17943: LOG:  received degenerate backend r2016-03-22 03:03:02: pid 15995: LOG:  r2016-03-22 03:03:02: pid 15960: LOG:  received degenerate backend request for node_id: 1 from pid [15960]
2016-03-22 03:03:02: pid 16118: LOG:  reading and processing packets
2012016-03-22 03:03:02: pid 16068: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16068: 2016-03-22 03:03:02: pid 18176: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 18176: DETAI2016-03-22 03:03:02: pid 16118: LOG:  received degenerate backend r2016-03-22 03:03:02: pid 16068: LOG:  r2016-03-22 03:03:02: pid 16110: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16110: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16096: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16096: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 21435: FATAL:  failed to read kind from backend
2016-03-22 03:03:02: pid 21435: DETAIL:  kind mismatch among backends. Possible last query was: " DISCARD ALL" kind details are: 0[C] 1[E: terminating connection due to administrator command]
2016-03-22 03:03:02: pid 21435: HINT:  check data consistency among db nodes
2016-03-22 03:03:02: pid 18196: LOG:  received degenerate backend request for node_id: 1 from pid [18196]
2016-03-22 03:03:02: pid 17013: LOG:  received degenerate backend request for node_id: 1 from pid [17013]
2016-03-22 03:03:02: pid 16023: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16023: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 17042: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 17042: DETAI2016-03-22 03:03:02: pid 16023: LOG:  received degenerate backend request for node_id: 1 from pid [16023]
2016-03-22 03:03:02: pid 16122: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16122: DETAI2016-03-22 03:03:02: pid 15933: LOG:  reading and processing packet2016-03-22 03:03:02: pid 16066: LOG:  received degenerate backend request for node_id: 1 from pid [16066]
2016-03-22 03:03:02: pid 16114: LOG:  received degenerate backend request for node_id: 1 from pid [16114]
2016-03-22 03:03:02: pid 16042: LOG:  received degenerate backend request for node_id: 1 from pid [16042]
2016-03-22 03:03:02: pid 17052: LOG:  received degenerate backend request for node_id: 1 from pid [17052]
2016-03-22 03:03:02: pid 16133: LOG:  received degenerate backend request for node_id: 1 from pid [16133]
2016-03-22 03:03:02: pid 17005: LOG:  received degenerate backend request for node_id: 1 from pid [17005]
2016-03-22 03:03:02: pid 16078: LOG:  received degenerate backend request for node_id: 1 from pid [16078]
eceived degenerate backend request for node_id: 1 from pid [15854]
2016-03-22 03:03:02: pid 16064: LOG:  received degenerate backend request for node_id: 1 from pid [16064]
eceived degenerate backend request for node_id: 1 from pid [17003]
2016-03-22 03:03:02: pid 15842: LOG:  received degenerate backend request for node_id: 1 from pid [15842]
2016-03-22 03:03:02: pid 15869: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15869: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15869: LOG:  received degenerate backend request for node_id: 1 from pid [15869]
2016-03-22 03:03:02: pid 17087: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 17087: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 17087: LOG:  received degenerate backend request for node_id: 1 from pid [17087]
2016-03-22 03:03:02: pid 15846: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15846: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15846: LOG:  received degenerate backend request for node_id: 1 from pid [15846]
2016-03-22 03:03:02: pid 16095: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16095: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16095: LOG:  received degenerate backend request for node_id: 1 from pid [16095]
2016-03-22 03:03:02: pid 21452: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21452: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21452: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 15855: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15855: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15855: LOG:  received degenerate backend request for node_id: 1 from pid [15855]
2016-03-22 03:03:02: pid 16124: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16124: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16124: LOG:  received degenerate backend request for node_id: 1 from pid [16124]
2016-03-22 03:03:02: pid 15911: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15911: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15911: LOG:  received degenerate backend request for node_id: 1 from pid [15911]
2016-03-22 03:03:02: pid 16044: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16044: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16044: LOG:  received degenerate backend request for node_id: 1 from pid [16044]
2016-03-22 03:03:02: pid 15847: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15847: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15847: LOG:  received degenerate backend request for node_id: 1 from pid [15847]
2016-03-22 03:03:02: pid 15917: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15917: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16034: LOG:  received degenerate backend request for node_id: 1 from pid [16034]
2016-03-22 03:03:02: pid 15917: LOG:  received degenerate backend request for node_id: 1 from pid [15917]
2016-03-22 03:03:02: pid 15914: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15914: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15914: LOG:  received degenerate backend request for node_id: 1 from pid [15914]
2016-03-22 03:03:02: pid 16061: LOG:  received degenerate backend request for node_id: 1 from pid [16061]
2016-03-22 03:03:02: pid 15875: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15875: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15875: LOG:  received degenerate backend request for node_id: 1 from pid [15875]
2016-03-22 03:03:02: pid 15874: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15874: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15874: LOG:  received degenerate backend request for node_id: 1 from pid [15874]
2016-03-22 03:03:02: pid 15872: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15872: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15872: LOG:  received degenerate backend request for node_id: 1 from pid [15872]
2016-03-22 03:03:02: pid 15886: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15886: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15886: LOG:  received degenerate backend request for node_id: 1 from pid [15886]
2016-03-22 03:03:02: pid 15912: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15912: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15912: LOG:  received degenerate backend request for node_id: 1 from pid [15912]
2016-03-22 03:03:02: pid 15879: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15879: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15879: LOG:  received degenerate backend request for node_id: 1 from pid [15879]
2016-03-22 03:03:02: pid 16151: LOG:  received degenerate backend request for node_id: 1 from pid [16151]
2016-03-22 03:03:02: pid 15880: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15880: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15880: LOG:  received degenerate backend request for node_id: 1 from pid [15880]
2016-03-22 03:03:02: pid 15876: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15876: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15876: LOG:  received degenerate backend request for node_id: 1 from pid [15876]
2016-03-22 03:03:02: pid 16059: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16059: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16059: LOG:  received degenerate backend request for node_id: 1 from pid [16059]
2016-03-22 03:03:02: pid 15894: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15894: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15894: LOG:  received degenerate backend request for node_id: 1 from pid [15894]
2016-03-22 03:03:02: pid 16105: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16105: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16105: LOG:  received degenerate backend request for node_id: 1 from pid [16105]
2016-03-22 03:03:02: pid 16163: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16163: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16163: LOG:  received degenerate backend request for node_id: 1 from pid [16163]
2016-03-22 03:03:02: pid 16171: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16171: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16171: LOG:  received degenerate backend request for node_id: 1 from pid [16171]
2016-03-22 03:03:02: pid 15887: LOG:  received degenerate backend request for node_id: 1 from pid [15887]
2016-03-22 03:03:02: pid 15906: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15906: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15906: LOG:  received degenerate backend request for node_id: 1 from pid [15906]
2016-03-22 03:03:02: pid 15891: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15891: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15891: LOG:  received degenerate backend request for node_id: 1 from pid [15891]
2016-03-22 03:03:02: pid 16161: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16161: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16161: LOG:  received degenerate backend request for node_id: 1 from pid [16161]
2016-03-22 03:03:02: pid 15913: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15913: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15913: LOG:  received degenerate backend request for node_id: 1 from pid [15913]
2016-03-22 03:03:02: pid 15909: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15909: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15909: LOG:  received degenerate backend request for node_id: 1 from pid [15909]
2016-03-22 03:03:02: pid 16088: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16088: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16088: LOG:  received degenerate backend request for node_id: 1 from pid [16088]
2016-03-22 03:03:02: pid 16006: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16006: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16006: LOG:  received degenerate backend request for node_id: 1 from pid [16006]
2016-03-22 03:03:02: pid 15915: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15915: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15915: LOG:  received degenerate backend request for node_id: 1 from pid [15915]
2016-03-22 03:03:02: pid 15888: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15888: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15888: LOG:  received degenerate backend request for node_id: 1 from pid [15888]
2016-03-22 03:03:02: pid 15884: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15884: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15884: LOG:  received degenerate backend request for node_id: 1 from pid [15884]
2016-03-22 03:03:02: pid 15882: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15882: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15882: LOG:  received degenerate backend request for node_id: 1 from pid [15882]
2016-03-22 03:03:02: pid 16160: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16160: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16160: LOG:  received degenerate backend request for node_id: 1 from pid [16160]
2016-03-22 03:03:02: pid 21452: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21452: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21452: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 15935: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15935: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15935: LOG:  received degenerate backend request for node_id: 1 from pid [15935]
2016-03-22 03:03:02: pid 15892: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15892: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15892: LOG:  received degenerate backend request for node_id: 1 from pid [15892]
2016-03-22 03:03:02: pid 15851: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15851: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15851: LOG:  received degenerate backend request for node_id: 1 from pid [15851]
2016-03-22 03:03:02: pid 15897: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15897: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15897: LOG:  received degenerate backend request for node_id: 1 from pid [15897]
2016-03-22 03:03:02: pid 21452: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21452: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21452: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16108: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 16108: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 16108: LOG:  received degenerate backend request for node_id: 1 from pid [16108]
2016-03-22 03:03:02: pid 15844: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15844: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15844: LOG:  received degenerate backend request for node_id: 1 from pid [15844]
2016-03-22 03:03:02: pid 15900: LOG:  reading and processing packets
2016-03-22 03:03:02: pid 15900: DETAIL:  postmaster on DB node 1 was shutdown by administrative command
2016-03-22 03:03:02: pid 15900: LOG:  received degenerate backend request for node_id: 1 from pid [15900]
2016-03-22 03:03:02: pid 21452: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21452: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21452: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21434: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21434: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21434: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21665: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21665: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21665: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21510: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21510: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21510: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21344: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21344: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21344: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21690: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21690: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21690: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21690: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21690: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21690: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21375: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21375: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21375: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21693: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21693: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21693: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21693: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21693: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21693: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 17068: LOG:  failback event detected
2016-03-22 03:03:02: pid 17068: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21514: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21514: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21514: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21421: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21421: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21421: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16962: LOG:  failback event detected
2016-03-22 03:03:02: pid 16962: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21408: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21408: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21408: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21399: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21399: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21399: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16981: LOG:  failback event detected
2016-03-22 03:03:02: pid 16981: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21394: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21394: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21394: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 22021: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 22021: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 22021: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21430: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21430: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21430: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21509: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21509: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21509: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21408: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21408: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21408: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21376: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21376: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21376: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21376: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21376: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21376: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21382: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21382: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21382: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16987: LOG:  failback event detected
2016-03-22 03:03:02: pid 16987: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 20010: LOG:  failback event detected
2016-03-22 03:03:02: pid 20010: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 16029: LOG:  failback event detected
2016-03-22 03:03:02: pid 16029: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 15999: LOG:  failback event detected
2016-03-22 03:03:02: pid 15999: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21382: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21382: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21382: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16998: LOG:  failback event detected
2016-03-22 03:03:02: pid 16998: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 17091: LOG:  failback event detected
2016-03-22 03:03:02: pid 17091: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 16141: LOG:  failback event detected
2016-03-22 03:03:02: pid 16141: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21336: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21336: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21336: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 18462: LOG:  failback event detected
2016-03-22 03:03:02: pid 18462: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21503: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21503: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21503: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16003: LOG:  failback event detected
2016-03-22 03:03:02: pid 16003: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 20471: LOG:  failback event detected
2016-03-22 03:03:02: pid 20471: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21348: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21348: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21348: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21348: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21348: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21348: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21348: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21348: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21348: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21325: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21325: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21325: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21325: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21325: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21325: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21325: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21325: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21325: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21350: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21350: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21350: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 18450: LOG:  failback event detected
2016-03-22 03:03:02: pid 18450: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21404: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21404: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21404: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21566: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21566: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21566: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21428: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21428: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21428: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21428: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21428: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21428: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 21394: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21394: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21394: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16032: LOG:  failback event detected
2016-03-22 03:03:02: pid 16032: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21394: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21394: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21394: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 16002: LOG:  failback event detected
2016-03-22 03:03:02: pid 16002: DETAIL:  restarting myself
2016-03-22 03:03:02: pid 21394: LOG:  pool_read_kind: error message from 1 th backend:the database system is shutting down
2016-03-22 03:03:02: pid 21394: ERROR:  unable to read message kind
2016-03-22 03:03:02: pid 21394: DETAIL:  kind does not match between master(52) slot[1] (45)
2016-03-22 03:03:02: pid 55911: LOG:  starting degeneration. shutdown host 1.1.1.7(5432)
2016-03-22 03:03:02: pid 55911: LOG:  Restart all children
2016-03-22 03:03:02: pid 15844: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22022: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21385: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22037: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21390: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21393: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21397: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21447: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21398: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21335: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21400: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15966: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22028: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 17052: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15912: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15887: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 17042: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 18532: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15892: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16064: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15900: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16066: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21405: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16133: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15915: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16127: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22142: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21461: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15894: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21409: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21432: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21351: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16163: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 17005: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21420: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21486: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21331: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21416: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21491: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21691: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 20144: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16059: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15906: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15909: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21430: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15897: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21818: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16113: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16068: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 17003: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15913: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21690: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 17041: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15911: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21329: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21418: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21379: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21493: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16118: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16124: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21347: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21466: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15948: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21368: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21439: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16110: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21484: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15935: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15914: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16078: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21362: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 15960: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16122: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21434: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21402: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21454: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21406: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16105: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21349: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21373: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21399: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22034: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21423: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21678: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21472: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21675: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21417: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21465: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16170: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21441: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21508: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21443: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21407: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21477: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21826: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16034: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 17087: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16044: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16037: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21509: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21462: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21437: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21380: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22039: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16096: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21444: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21367: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 17053: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21692: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21376: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16061: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21494: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21346: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21404: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21425: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21483: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21374: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21382: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22029: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 19383: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16070: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21514: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16088: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22021: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21831: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21512: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16079: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21480: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 16171: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21421: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21504: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21501: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21487: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21446: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21566: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21436: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21490: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21499: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22027: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21476: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21470: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21338: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21383: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21365: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22026: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22145: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21327: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21350: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21502: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21352: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21326: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21340: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21449: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21686: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21503: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21442: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21820: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21348: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 22025: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21353: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21665: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21688: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21341: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21693: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21482: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21372: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21471: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21323: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21426: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21469: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21513: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21468: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21510: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21496: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21511: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21676: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21429: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21500: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21369: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21495: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21360: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21336: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21467: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21515: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21445: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21359: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21457: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21408: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21322: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21337: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21330: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21492: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:02: pid 21824: LOG:  child process received shutdown request signal 3
+ FALLING_NODE=1
+ OLDPRIMARY_NODE=1
+ NEW_PRIMARY=1.1.1.6
+ PGDATA=/home/postgres/databases/fabrix
+ PGHOME=/home/postgres
+ log 'failover to 1.1.1.6 host. creating /home/postgres/databases/fabrix/trigger file.'
+ '[' '!' 'failover to 1.1.1.6 host. creating /home/postgres/databases/fabrix/trigger file.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:02.76] - failover to 1.1.1.6 host. creating /home/postgres/databases/fabrix/trigger file.'
+ '[' 1 = 1 ']'
+ '[' 0 -eq 0 ']'
+ su postgres -c 'ssh -T postgres at 1.1.1.6 touch /home/postgres/databases/fabrix/trigger'
+ exit 0
2016-03-22 03:03:02: pid 55911: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2016-03-22 03:03:02: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:02: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:03:03: pid 21384: ERROR:  failed to authenticate
2016-03-22 03:03:03: pid 21384: DETAIL:  invalid authentication message response type, Expecting 'R' and received 'E'
2016-03-22 03:03:03: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:03: pid 55911: LOG:  find_primary_node: primary node id is 0
2016-03-22 03:03:03: pid 55911: LOG:  starting follow degeneration. shutdown host 1.1.1.7(5432)
2016-03-22 03:03:03: pid 55911: LOG:  failover: 1 follow backends have been degenerated
2016-03-22 03:03:03: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:03: pid 22378: LOG:  start triggering follow command.
2016-03-22 03:03:03: pid 22378: LOG:  execute command: /etc/pgpool-II/recovery/failback.sh 1 1.1.1.7 1.1.1.6 0 0 /home/postgres/databases/fabrix /home/postgres/databases/fabrix 5432
+ NODE_ID=1
+ HOST_NAME=1.1.1.7
+ NEW_MASTER_HOSTNAME_CHECK=1.1.1.6
+ NEW_MASTER_NODE_ID=0
+ OLD_MASTER_NODE_ID=0
+ DATABASE_CLUSTER_PATH=/home/postgres/databases/fabrix
+ MASTER_CLUSTER_PATH=/home/postgres/databases/fabrix
+ NEW_MASTER_PORT=5432
+ PGHOME=/home/postgres
+ ARCH=/home/postgres/archive
+ R_USER=fabrix
+ R_PASSWORD=fabrix
+ PG_STOP_COUNTER=300
++ cat /etc/pgpool-II/pgpool.conf
++ grep backend_hostname0
++ grep -v '#'
++ awk -F = '{print $2}'
++ tr -d ''\'''
+ NEW_MASTER_HOSTNAME=1.1.1.6
+ log ''
+ '[' '!' '' ']'
+ return 0
+ log '-------------------------- failback of 1.1.1.7 --------------------------'
+ '[' '!' '-------------------------- failback of 1.1.1.7 --------------------------' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.91] - -------------------------- failback of 1.1.1.7 --------------------------'
+ log ''
+ '[' '!' '' ']'
+ return 0
+ log 'new master hostname --reported by pgpool-- : 1.1.1.6'
+ '[' '!' 'new master hostname --reported by pgpool-- : 1.1.1.6' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.91] - new master hostname --reported by pgpool-- : 1.1.1.6'
+ log 'node_id: 1'
+ '[' '!' 'node_id: 1' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.91] - node_id: 1'
+ log 'hostname: 1.1.1.7'
+ '[' '!' 'hostname: 1.1.1.7' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.91] - hostname: 1.1.1.7'
+ log 'hostname of new master: 1.1.1.6'
+ '[' '!' 'hostname of new master: 1.1.1.6' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.91] - hostname of new master: 1.1.1.6'
+ log 'new master node id: 0'
+ '[' '!' 'new master node id: 0' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.91] - new master node id: 0'
+ log 'old master node id: 0'
+ '[' '!' 'old master node id: 0' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.92] - old master node id: 0'
+ log 'database cluster path: /home/postgres/databases/fabrix'
+ '[' '!' 'database cluster path: /home/postgres/databases/fabrix' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.92] - database cluster path: /home/postgres/databases/fabrix'
+ log 'master database cluster path: /home/postgres/databases/fabrix'
+ '[' '!' 'master database cluster path: /home/postgres/databases/fabrix' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.92] - master database cluster path: /home/postgres/databases/fabrix'
+ log 'master port: 5432'
+ '[' '!' 'master port: 5432' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:03.92] - master port: 5432'
+ su - postgres -c 'ssh 1.1.1.7 '\''
if [ -f /home/postgres/recovery.lock ];then
    rm -rf /home/postgres/recovery.lock;
    exit 0
else
    exit 99
fi'\'''
+ RET_VAL=99
+ log 'return value is : 99'
+ '[' '!' 'return value is : 99' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:04.17] - return value is : 99'
+ '[' 99 -eq 0 ']'
+ log 'deleting /home/postgres/pg.control file on 1.1.1.7 in order to monitor postgres via monit'
+ '[' '!' 'deleting /home/postgres/pg.control file on 1.1.1.7 in order to monitor postgres via monit' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:04.17] - deleting /home/postgres/pg.control file on 1.1.1.7 in order to monitor postgres via monit'
+ su - postgres -c 'ssh 1.1.1.7 '\''rm -f /home/postgres/pg.control'\'''
2016-03-22 03:03:04: pid 21384: ERROR:  Failed to check replication time lag
2016-03-22 03:03:04: pid 21384: DETAIL:  No persistent db connection for the node 1
2016-03-22 03:03:04: pid 21384: HINT:  check sr_check_user and sr_check_password
2016-03-22 03:03:04: pid 21384: CONTEXT:  while checking replication time lag
+ log 'deleting Archive directory in 1.1.1.7.'
+ '[' '!' 'deleting Archive directory in 1.1.1.7.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:04.33] - deleting Archive directory in 1.1.1.7.'
+ su - postgres -c 'ssh 1.1.1.7 '\''rm -rf /home/postgres/archive/*'\'''
2016-03-22 03:03:04: pid 55911: LOG:  failover: set new primary node: 0
2016-03-22 03:03:04: pid 55911: LOG:  failover: set new master node: 0
2016-03-22 03:03:04: pid 22481: LOG:  failback event detected
2016-03-22 03:03:04: pid 22481: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22484: LOG:  failback event detected
2016-03-22 03:03:04: pid 22484: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22487: LOG:  failback event detected
2016-03-22 03:03:04: pid 22487: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22489: LOG:  failback event detected
2016-03-22 03:03:04: pid 22489: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22490: LOG:  failback event detected
2016-03-22 03:03:04: pid 22490: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22492: LOG:  failback event detected
2016-03-22 03:03:04: pid 22492: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22479: ERROR:  unable to flush data to frontend
2016-03-22 03:03:04: pid 22497: LOG:  failback event detected
2016-03-22 03:03:04: pid 22497: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22480: ERROR:  unable to flush data to frontend
2016-03-22 03:03:04: pid 22501: LOG:  failback event detected
2016-03-22 03:03:04: pid 22501: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22503: LOG:  failback event detected
2016-03-22 03:03:04: pid 22503: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22482: ERROR:  unable to flush data to frontend
2016-03-22 03:03:04: pid 22486: ERROR:  unable to flush data to frontend
2016-03-22 03:03:04: pid 22480: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22485 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22482: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22488 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22511: LOG:  failback event detected
2016-03-22 03:03:04: pid 22511: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22493: ERROR:  unable to flush data to frontend
2016-03-22 03:03:04: pid 22512: LOG:  failback event detected
2016-03-22 03:03:04: pid 22512: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22514: LOG:  failback event detected
2016-03-22 03:03:04: pid 22514: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22494: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22498 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22495: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22500 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22479: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22502 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22499: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22505 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22519: LOG:  failback event detected
2016-03-22 03:03:04: pid 22519: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22521: LOG:  failback event detected
2016-03-22 03:03:04: pid 22521: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22506: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22510 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22504: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22509 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22522: LOG:  failback event detected
2016-03-22 03:03:04: pid 22522: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22524: LOG:  failback event detected
2016-03-22 03:03:04: pid 22524: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22525: LOG:  failback event detected
2016-03-22 03:03:04: pid 22525: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22526: LOG:  failback event detected
2016-03-22 03:03:04: pid 22526: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22529: LOG:  failback event detected
2016-03-22 03:03:04: pid 22529: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22530: LOG:  failback event detected
2016-03-22 03:03:04: pid 22530: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22532: LOG:  failback event detected
2016-03-22 03:03:04: pid 22532: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22534: LOG:  failback event detected
2016-03-22 03:03:04: pid 22534: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22536: LOG:  failback event detected
2016-03-22 03:03:04: pid 22536: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22537: LOG:  failback event detected
2016-03-22 03:03:04: pid 22537: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22538: LOG:  failback event detected
2016-03-22 03:03:04: pid 22538: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22541: LOG:  failback event detected
2016-03-22 03:03:04: pid 22541: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22542: LOG:  failback event detected
2016-03-22 03:03:04: pid 22542: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22543: LOG:  failback event detected
2016-03-22 03:03:04: pid 22543: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22544: LOG:  failback event detected
2016-03-22 03:03:04: pid 22544: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22547: LOG:  failback event detected
2016-03-22 03:03:04: pid 22547: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22549: LOG:  failback event detected
2016-03-22 03:03:04: pid 22549: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22557: LOG:  failback event detected
2016-03-22 03:03:04: pid 22557: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22559: LOG:  failback event detected
2016-03-22 03:03:04: pid 22559: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22561: LOG:  failback event detected
2016-03-22 03:03:04: pid 22561: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22562: LOG:  failback event detected
2016-03-22 03:03:04: pid 22562: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22563: LOG:  failback event detected
2016-03-22 03:03:04: pid 22563: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22564: LOG:  failback event detected
2016-03-22 03:03:04: pid 22564: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22565: LOG:  failback event detected
2016-03-22 03:03:04: pid 22565: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22567: LOG:  failback event detected
2016-03-22 03:03:04: pid 22567: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22568: LOG:  failback event detected
2016-03-22 03:03:04: pid 22568: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22572: LOG:  failback event detected
2016-03-22 03:03:04: pid 22572: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22578: LOG:  failback event detected
2016-03-22 03:03:04: pid 22578: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22546: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22573 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22531: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22576 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22598: LOG:  failback event detected
2016-03-22 03:03:04: pid 22598: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22603: LOG:  failback event detected
2016-03-22 03:03:04: pid 22603: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22550: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22579 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22535: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22580 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22527: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22582 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22560: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22583 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22558: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22585 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22515: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22588 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22517: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22590 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22493: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22596 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22551: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22594 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22528: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22592 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22520: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22602 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22556: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22597 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22540: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22599 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22621: LOG:  failback event detected
2016-03-22 03:03:04: pid 22621: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22523: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22604 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22533: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22605 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22516: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22600 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22553: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22608 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22508: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22607 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22507: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22610 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22548: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22613 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22631: LOG:  failback event detected
2016-03-22 03:03:04: pid 22631: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22571: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22612 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:04: pid 22636: LOG:  failback event detected
2016-03-22 03:03:04: pid 22636: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22641: LOG:  failback event detected
2016-03-22 03:03:04: pid 22641: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22644: LOG:  failback event detected
2016-03-22 03:03:04: pid 22644: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22653: LOG:  failback event detected
2016-03-22 03:03:04: pid 22653: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22661: LOG:  failback event detected
2016-03-22 03:03:04: pid 22661: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22668: LOG:  failback event detected
2016-03-22 03:03:04: pid 22668: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22680: LOG:  failback event detected
2016-03-22 03:03:04: pid 22680: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22692: LOG:  failback event detected
2016-03-22 03:03:04: pid 22692: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22699: LOG:  failback event detected
2016-03-22 03:03:04: pid 22699: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22709: LOG:  failback event detected
2016-03-22 03:03:04: pid 22709: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22711: LOG:  failback event detected
2016-03-22 03:03:04: pid 22711: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22717: LOG:  failback event detected
2016-03-22 03:03:04: pid 22717: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22719: LOG:  failback event detected
2016-03-22 03:03:04: pid 22719: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22728: LOG:  failback event detected
2016-03-22 03:03:04: pid 22728: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22731: LOG:  failback event detected
2016-03-22 03:03:04: pid 22731: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22734: LOG:  failback event detected
2016-03-22 03:03:04: pid 22734: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22736: LOG:  failback event detected
2016-03-22 03:03:04: pid 22736: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22739: LOG:  failback event detected
2016-03-22 03:03:04: pid 22739: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22740: LOG:  failback event detected
2016-03-22 03:03:04: pid 22740: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22741: LOG:  failback event detected
2016-03-22 03:03:04: pid 22741: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22743: LOG:  failback event detected
2016-03-22 03:03:04: pid 22743: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22745: LOG:  failback event detected
2016-03-22 03:03:04: pid 22745: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22746: LOG:  failback event detected
2016-03-22 03:03:04: pid 22746: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22749: LOG:  failback event detected
2016-03-22 03:03:04: pid 22749: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22751: LOG:  failback event detected
2016-03-22 03:03:04: pid 22751: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22752: LOG:  failback event detected
2016-03-22 03:03:04: pid 22752: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22753: LOG:  failback event detected
2016-03-22 03:03:04: pid 22753: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22759: LOG:  failback event detected
2016-03-22 03:03:04: pid 22759: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22761: LOG:  failback event detected
2016-03-22 03:03:04: pid 22761: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22762: LOG:  failback event detected
2016-03-22 03:03:04: pid 22762: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22764: LOG:  failback event detected
2016-03-22 03:03:04: pid 22764: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22768: LOG:  failback event detected
2016-03-22 03:03:04: pid 22768: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22769: LOG:  failback event detected
2016-03-22 03:03:04: pid 22769: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22771: LOG:  failback event detected
2016-03-22 03:03:04: pid 22771: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22778: LOG:  failback event detected
2016-03-22 03:03:04: pid 22778: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22781: LOG:  failback event detected
2016-03-22 03:03:04: pid 22781: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22783: LOG:  failback event detected
2016-03-22 03:03:04: pid 22783: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22786: LOG:  failback event detected
2016-03-22 03:03:04: pid 22786: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22787: LOG:  failback event detected
2016-03-22 03:03:04: pid 22787: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22791: LOG:  failback event detected
2016-03-22 03:03:04: pid 22791: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22795: LOG:  failback event detected
2016-03-22 03:03:04: pid 22795: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22797: LOG:  failback event detected
2016-03-22 03:03:04: pid 22797: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22799: LOG:  failback event detected
2016-03-22 03:03:04: pid 22799: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22800: LOG:  failback event detected
2016-03-22 03:03:04: pid 22800: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22806: LOG:  failback event detected
2016-03-22 03:03:04: pid 22806: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22824: LOG:  failback event detected
2016-03-22 03:03:04: pid 22824: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22833: LOG:  failback event detected
2016-03-22 03:03:04: pid 22833: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22834: LOG:  failback event detected
2016-03-22 03:03:04: pid 22834: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22836: LOG:  failback event detected
2016-03-22 03:03:04: pid 22836: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22842: LOG:  failback event detected
2016-03-22 03:03:04: pid 22842: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 22843: LOG:  failback event detected
2016-03-22 03:03:04: pid 22843: DETAIL:  restarting myself
failover done. shutdown host 1.1.1.7(5432)2016-03-22 03:03:04: pid 22844: LOG:  failback event detected
2016-03-22 03:03:04: pid 22844: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:04: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:04: pid 22845: LOG:  failback event detected
2016-03-22 03:03:04: pid 22845: DETAIL:  restarting myself
2016-03-22 03:03:04: pid 21384: LOG:  received degenerate backend request for node_id: 0 from pid [21384]
2016-03-22 03:03:04: pid 21384: WARNING:  child_exit: called from invalid process. ignored.
2016-03-22 03:03:04: pid 21384: ERROR:  unable to read data from DB node 0
2016-03-22 03:03:04: pid 21384: DETAIL:  socket read failed with an error "Connection reset by peer"
2016-03-22 03:03:04: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:04: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:04: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:04: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:05: pid 22841: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22852 statement: "ROLLBACK" message: "there is no transaction in progress"
+ log 'starting backup on new master node: 1.1.1.6'
+ '[' '!' 'starting backup on new master node: 1.1.1.6' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:05.34] - starting backup on new master node: 1.1.1.6'
+ su - postgres -c 'ssh 1.1.1.6 /home/postgres/pg_utils/start_backup.sh'
2016-03-22 03:03:05: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:05: pid 55911: LOG:  watchdog became a new lock holder
+ psql -c 'select pg_start_backup('\''clone'\'',true);'
2016-03-22 03:03:05: pid 21384: ERROR:  Failed to check replication time lag
2016-03-22 03:03:05: pid 21384: DETAIL:  No persistent db connection for the node 1
2016-03-22 03:03:05: pid 21384: HINT:  check sr_check_user and sr_check_password
2016-03-22 03:03:05: pid 21384: CONTEXT:  while checking replication time lag
2016-03-22 03:03:05: pid 21384: LOG:  worker process received restart request
2016-03-22 03:03:05: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:05: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:05: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:05: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:06: pid 22838: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22910 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:06: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:06: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:06: pid 22775: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22957 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:06: pid 22816: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22958 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:06: pid 22812: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22959 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:06: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:06: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:06: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:06: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:07: pid 22807: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22968 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:07: pid 22814: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22969 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:07: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:07: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:07: pid 22770: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 22998 statement: "ROLLBACK" message: "there is no transaction in progress"
 pg_start_backup
-----------------
 F/C89B0E18
(1 row)

+ log 'stopping 1.1.1.7 node.'
+ '[' '!' 'stopping 1.1.1.7 node.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:07.53] - stopping 1.1.1.7 node.'
+ su - postgres -c 'ssh 1.1.1.7 '\''pg_ctl -D /home/postgres/databases/fabrix stop -m fast'\'''
pg_ctl: PID file "/home/postgres/databases/fabrix/postmaster.pid" does not exist
Is server running?
+ COUNTER=0
+ [[ -n True ]]
+ su - postgres -c 'ssh postgres at HOST_NAME ps -ef|grep -v grep|grep "/usr/bin/postgres -D"'
+ RET_VAL=1
+ '[' 1 -eq 0 ']'
+ '[' '!' 1 -eq 0 ']'
+ log 'Postgres stopped.....'
+ '[' '!' 'Postgres stopped.....' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:07.80] - Postgres stopped.....'
+ break
+ log 'performing rsync between source:1.1.1.6 and target:1.1.1.7'
+ '[' '!' 'performing rsync between source:1.1.1.6 and target:1.1.1.7' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:07.80] - performing rsync between source:1.1.1.6 and target:1.1.1.7'
+ su - postgres -c 'ssh 1.1.1.6 rsync -av --timeout=40 --exclude pg_xlog --exclude postgresql.conf --exclude postgres.out --exclude postmaster.pid --exclude recovery.done /home/postgres/databases/fabrix/*  1.1.1.7:/home/postgres/databases/fabrix/ && exit 0 || exit 99'
2016-03-22 03:03:07: pid 22790: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23216 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:07: pid 22792: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23219 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:07: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:07: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:07: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:07: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:07: pid 22705: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23221 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:07: pid 22774: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23222 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:07: pid 22756: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23223 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:08: pid 22617: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23225 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:08: pid 22837: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23226 statement: "ROLLBACK" message: "there is no transaction in progress"
sending incremental file list
backup_label
postmaster.opts
base/1/
base/12901/
base/12901/pg_internal.init
base/16385/
base/16385/16439
base/16385/16558
base/16385/16560
base/16385/16561
base/16385/16564
base/16385/16569
base/16385/16576
base/16385/16579
base/16385/16580
base/16385/16581
base/16385/16582
base/16385/16583
base/16385/16584
base/16385/16585
base/16385/16586
base/16385/16587
base/16385/16588
base/16385/16589
base/16385/16590
base/16385/16591
base/16385/16592
base/16385/16887
base/16385/16889
base/16385/16894
base/16385/16896
base/16385/16897
base/16385/16898
base/16385/16900
base/16385/16937
base/16385/16939
base/16385/16940
base/16385/16941
base/16385/16942
base/16385/16943
base/16385/16944
base/16385/16945
base/16385/16946
base/16385/16947
base/16385/16948
base/16385/16949
base/16385/16950
base/16385/16951
2016-03-22 03:03:08: pid 22628: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23227 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:08: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:08: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:08: pid 22618: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23233 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:08: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:08: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:08: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:08: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:09: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:09: pid 55911: LOG:  watchdog became a new lock holder
base/16385/16989.1
2016-03-22 03:03:09: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:09: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:09: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:09: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:10: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:10: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:10: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:10: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:10: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:10: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:11: pid 22802: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23268 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:11: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:11: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:11: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:11: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:11: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:11: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:12: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:12: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:12: pid 22721: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23414 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:12: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:12: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:12: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:12: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:12: pid 22632: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23415 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:13: pid 22813: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23416 statement: "ROLLBACK" message: "there is no transaction in progress"
base/16385/16989_fsm
base/16385/17042
2016-03-22 03:03:13: pid 22826: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23417 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:13: pid 22685: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23418 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:13: pid 22767: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 23419 statement: "ROLLBACK" message: "there is no transaction in progress"
2016-03-22 03:03:13: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:13: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:13: pid 55911: LOG:  failover: no backends are degenerated
2016-03-22 03:03:13: pid 55911: LOG:  watchdog leaving from interlocking
2016-03-22 03:03:13: pid 55911: LOG:  watchdog notifying to end interlocking
2016-03-22 03:03:13: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:14: pid 55911: LOG:  watchdog notifying to start interlocking
2016-03-22 03:03:14: pid 55911: LOG:  watchdog became a new lock holder
2016-03-22 03:03:14: pid 55911: LOG:  starting degeneration. shutdown host 1.1.1.6(5432)
2016-03-22 03:03:14: pid 55911: LOG:  failover: no valid backends node found
2016-03-22 03:03:14: pid 55911: LOG:  Restart all children
2016-03-22 03:03:14: pid 22493: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22507: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22517: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22527: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22535: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22545: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22551: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22553: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22566: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22555: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22558: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22570: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22574: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22577: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22591: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22601: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22614: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22609: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22619: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22648: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22650: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22658: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 55911: LOG:  execute command: /etc/pgpool-II/recovery/failover.sh 0 0
2016-03-22 03:03:14: pid 22656: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22770: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22617: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22628: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22623: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22721: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22620: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22813: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22723: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22725: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22663: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22695: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22698: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22667: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22796: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22670: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22729: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22780: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22705: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22584: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22810: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22677: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22673: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22640: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22693: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22676: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22792: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22812: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22807: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22823: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22654: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22841: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22646: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22664: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22744: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22827: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22840: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22707: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22704: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22730: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22655: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22735: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22611: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22732: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22643: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22627: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22784: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22688: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22647: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22633: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22832: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22685: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22775: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22829: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22684: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22793: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22758: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22756: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22839: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22757: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22696: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22754: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22801: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22671: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22804: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22645: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22774: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22831: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22649: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22742: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22678: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22811: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22660: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22669: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22767: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22782: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22652: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22815: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22718: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22687: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22674: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22805: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22785: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22638: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22788: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22722: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22794: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22790: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22755: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22690: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22816: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22828: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22651: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22700: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22748: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22820: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22818: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22639: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22747: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22738: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22675: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22714: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22776: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22803: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22710: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22777: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22702: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22737: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22642: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22750: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22622: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22657: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22686: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22712: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22703: LOG:  child process received shutdown request signal 3
+ FALLING_NODE=0
+ OLDPRIMARY_NODE=0
+ NEW_PRIMARY=
+ PGDATA=
2016-03-22 03:03:14: pid 22686: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22712: LOG:  child process received shutdown request signal 3
2016-03-22 03:03:14: pid 22703: LOG:  child process received shutdown request signal 3
+ FALLING_NODE=0
+ OLDPRIMARY_NODE=0
+ NEW_PRIMARY=
+ PGDATA=
+ PGHOME=/home/postgres
+ log 'failover to  host. creating /trigger file.'
+ '[' '!' 'failover to  host. creating /trigger file.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:15.05] - failover to  host. creating /trigger file.'
+ '[' 0 = 0 ']'
+ '[' 0 -eq 0 ']'
+ su postgres -c 'ssh -T postgres@ touch /trigger'
+ exit 0
2016-03-22 03:03:15: pid 55911: LOG:  execute command: /etc/pgpool-II/recovery/failover.sh 1 0
+ FALLING_NODE=1
+ OLDPRIMARY_NODE=0
+ NEW_PRIMARY=
+ PGDATA=
+ PGHOME=/home/postgres
+ log 'failover to  host. creating /trigger file.'
+ '[' '!' 'failover to  host. creating /trigger file.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:15.10] - failover to  host. creating /trigger file.'
+ '[' 1 = 0 ']'
+ exit 0
2016-03-22 03:03:15: pid 55911: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
+ OLDPRIMARY_NODE=0
+ NEW_PRIMARY=
+ PGDATA=
+ PGHOME=/home/postgres
+ log 'failover to  host. creating /trigger file.'
+ '[' '!' 'failover to  host. creating /trigger file.' ']'
++ /bin/date '+%m/%d/%y %H:%M:%S.%2N'
+ /bin/echo '[03/22/16 03:03:15.10] - failover to  host. creating /trigger file.'
+ '[' 1 = 0 ']'
+ exit 0
2016-03-22 03:03:15: pid 55911: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2016-03-22 03:03:15: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:15: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:03:16: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:16: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:03:17: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:17: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:03:18: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:18: pid 55911: LOG:  find_primary_node: checking backend no 1

base/16385/17044
2016-03-22 03:03:19: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:19: pid 55911: LOG:  find_primary_node: checking backend no 1

base/16385/17045
2016-03-22 03:03:20: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:20: pid 55911: LOG:  find_primary_node: checking backend no 1

base/16385/17046
2016-03-22 03:03:21: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:21: pid 55911: LOG:  find_primary_node: checking backend no 1

base/16385/17047
2016-03-22 03:03:22: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:22: pid 55911: LOG:  find_primary_node: checking backend no 1

base/16385/17048
2016-03-22 03:03:23: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:23: pid 55911: LOG:  find_primary_node: checking backend no 1

base/16385/17049
base/16385/17051
2016-03-22 03:03:24: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:24: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:03:25: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:25: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:03:26: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:26: pid 55911: LOG:  find_primary_node: checking backend no 1

2016-03-22 03:03:27: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:27: pid 55911: LOG:  find_primary_node: checking backend no 1

base/16385/17051_fsm
base/16385/17060
2016-03-22 03:03:28: pid 55911: LOG:  find_primary_node: checking backend no 0

2016-03-22 03:03:28: pid 55911: LOG:  find_primary_node: checking backend no 1
.
.
.
.
.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool.conf
Type: application/octet-stream
Size: 21165 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160328/4c2c323d/attachment-0001.obj>