search for: fail_count

...c61ef 100644 --- a/usr/kinit/ipconfig/bootp_proto.c +++ b/usr/kinit/ipconfig/bootp_proto.c @@ -212,5 +212,11 @@ int bootp_init_if(struct netdev *dev) dev->bootp.xid = (uint32_t) lrand48(); dev->open_time = time(NULL); + /* + * 'process_timeout_event(main.c)' will increment 'fail_count' + * only once independent of a failure. + */ + dev->bootp.fail_count = ~0; + return 0; } diff --git a/usr/kinit/ipconfig/dhcp_proto.c b/usr/kinit/ipconfig/dhcp_proto.c index afd2eca..91dd695 100644 --- a/usr/kinit/ipconfig/dhcp_proto.c +++ b/usr/kinit/ipconfig/dhcp_proto.c @@ -49,7 +49...

...: client/ctdb_client.c:759 control timed out. reqid:129 opcode:43 dstnode:0 2015/05/18 14:24:23.375232 [ 6031]: client/ctdb_client.c:870 ctdb_control_recv failed 2015/05/18 14:24:23.375240 [ 6031]: Async operation failed with state 3, opcode:0 2015/05/18 14:24:23.375257 [ 6031]: Async wait failed - fail_count=1 2015/05/18 14:24:23.375263 [ 6031]: server/ctdb_takeover.c:1475 Async control CTDB_CONTROL_RELEASE_IP failed. We saw a different pattern yesterday when the smb.conf was edited ahead of the path being created and node 0 became unhealthy for a moment. Node 0: 2015/05/18 14:24:17.694058 [ 5972]: E...

...t' 2014/10/29 11:13:48.484782 [recoverd:6488266]: Async operation failed with ret=-1 res=-1 opcode=33 2014/10/29 11:13:48.484837 [recoverd:6488266]: Failed to freeze node 1 during recovery. Set it as ban culprit for 2 credits 2014/10/29 11:13:48.484890 [recoverd:6488266]: Async wait failed - fail_count=1 2014/10/29 11:13:48.485047 [recoverd:6488266]: server/ctdb_recoverd.c:410 Unable to freeze nodes. Recovery failed. 2014/10/29 11:13:48.485095 [recoverd:6488266]: server/ctdb_recoverd.c:1881 Unable to set recovery mode to active on cluster 2014/10/29 11:13:48.503273 [3932342]: Freeze priority 1...

...lient/ctdb_client.c:759 control timed out. reqid:67831 opcode:80 dstnode:1 2014/07/03 16:10:39.962203 [33287]: client/ctdb_client.c:870 ctdb_control_recv failed 2014/07/03 16:10:39.962219 [33287]: Async operation failed with state 3, opcode:80 2014/07/03 16:10:39.962235 [33287]: Async wait failed - fail_count=1 2014/07/03 16:10:39.962251 [33287]: server/ctdb_recoverd.c:251 Failed to read node capabilities. 2014/07/03 16:10:39.962264 [33287]: server/ctdb_recoverd.c:3041 Unable to update node capabilities. 2014/07/03 16:11:00.984133 [33287]: client/ctdb_client.c:759 control timed out. reqid:67841 opcode:8...

.... The addresses never come up and I recieve these messages in the log 2012/06/28 10:54:43.313227 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28 10:54:43.313918 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28 10:54:43.313929 [ 1820]: Async wait failed - fail_count=2 2012/06/28 10:54:43.313934 [ 1820]: server/ctdb_takeover.c:1517 Async control CTDB_CONTROL_TAKEOVER_IP failed 2012/06/28 10:54:43.313941 [ 1820]: server/ctdb_recoverd.c:1588 Unable to setup public takeover addresses 2012/06/28 10:54:44.316099 [ 1820]: Taking out recovery lock from recovery dae...

...2147483471 opcode:80 dstnode:1 May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: ../ctdb/server/ctdb_client.c:791 ctdb_control_recv failed May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: Async operation failed with state 3, opcode:80 May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: Async wait failed - fail_count=1 May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: ../ctdb/server/ctdb_client.c:1931 Failed to read node capabilities. May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: ../ctdb/server/ctdb_recoverd.c:370 Failed to get node capabilities May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: ../ctdb/server/ctd...

...> May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: > ../ctdb/server/ctdb_client.c:791 ctdb_control_recv failed > May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: Async operation failed > with state 3, opcode:80 > May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: Async wait failed - > fail_count=1 > May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: > ../ctdb/server/ctdb_client.c:1931 Failed to read node capabilities. > May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: > ../ctdb/server/ctdb_recoverd.c:370 Failed to get node capabilities > May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[1...

...Freeze priority 1 2014/02/26 12:10:33.515860 [6553670]: Freeze priority 2 2014/02/26 12:10:33.657076 [6553670]: Freeze priority 3 2014/02/26 12:10:35.301189 [recoverd:12320780]: Async operation failed with ret=0 res=-1 opcode=67 2014/02/26 12:10:35.301275 [recoverd:12320780]: Async wait failed - fail_count=1 2014/02/26 12:10:35.301327 [recoverd:12320780]: server/ctdb_recoverd.c:1468 Unable to wipe database. Recovery failed. 2014/02/26 12:10:35.301968 [recoverd:12320780]: server/ctdb_recoverd.c:1915 Failed to recover database 0x3ef19640 I'm not sure which of these messages is important to look...