incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheng Yang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-1414) Redundant router: BACKUP switch cancelled due to lock timeout after a glitch in network
Date Tue, 26 Feb 2013 20:20:12 GMT
Sheng Yang created CLOUDSTACK-1414:
--------------------------------------

             Summary: Redundant router: BACKUP switch cancelled due to lock timeout after
a glitch in network
                 Key: CLOUDSTACK-1414
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1414
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.1.0
            Reporter: Sheng Yang
            Assignee: Sheng Yang
             Fix For: 4.1.0


The following error would show if the RvR switch to MASTER then back to BACKUP immediately.

It's due to time used to switch to MASTER is too long, mainly due to arping operation.

Feb 21 11:32:08 r-36994-VM Keepalived_vrrp: VRRP_Instance(inside_network)
Transition to MASTER STATE
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: VRRP_Instance(inside_network)
Entering MASTER STATE
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:09 r-36994-VM Keepalived_vrrp: Netlink: filter function error
Feb 21 11:32:43 r-36994-VM Keepalived_vrrp: VRRP_Instance(inside_network)
Received higher prio advert
Feb 21 11:32:43 r-36994-VM Keepalived_vrrp: VRRP_Instance(inside_network)
Entering BACKUP STATE
Feb 21 11:32:44 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:45 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:46 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:48 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:49 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:50 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:51 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:52 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:53 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:54 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:55 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:56 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:57 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:58 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:32:59 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:00 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:01 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:02 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:03 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:04 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:05 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:06 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:08 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:09 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:10 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:11 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:12 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:13 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:14 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:15 r-36994-VM cloud: Process /ramdisk/rrouter/backup.sh pid 1709
waiting for the lock biglock for another 1 second
Feb 21 11:33:15 r-36994-VM cloud: fail to acquire the lock biglock for process
/ramdisk/rrouter/backup.sh pid 1709 after 30 seconds time out!
Feb 21 11:33:15 r-36994-VM cloud: waiting for command: USER PID %CPU %MEM VSZ
RSS TTY STAT START TIME COMMAND root 1292 0.0 0.0 2656 1132 ? S 11:32 0:00
/bin/bash /ramd
Feb 21 11:33:15 r-36994-VM cloud: Failed job detail: USER       PID %CPU %MEM  
 VSZ   RSS TTY      STAT START   TIME COMMAND#012root      1709  0.0  0.0  
2656  1132 ?        S    11:32   0:00 /bin/bash /ramd

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message