You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/09/04 01:57:52 UTC

[jira] [Resolved] (CLOUDSTACK-4601) Redundant router: cron jobs of check_heartbeat.sh lacks of correct PATH for service and ifconfig command

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheng Yang resolved CLOUDSTACK-4601.
------------------------------------

    Resolution: Fixed
      Assignee: Sheng Yang
    
> Redundant router: cron jobs of check_heartbeat.sh lacks of correct PATH for service and ifconfig command
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4601
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4601
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Sheng Yang
>            Assignee: Sheng Yang
>
> If we triggered the check_heartbeat.sh manually, then from ramdisk/rrouter/keepalived.log we found that the script reports ifconfig: not found and
> /ramdisk/rrouter/check_heartbeat.sh: line 11: service: command not found
> /ramdisk/rrouter/check_heartbeat.sh: line 12: service: command not found
> ------------------------------------------------------
> Status: FAULT (keepalived process is dead)
> Keepalived process is dead!
> /ramdisk/rrouter/check_heartbeat.sh: line 11: service: command not found
> /ramdisk/rrouter/check_heartbeat.sh: line 12: service: command not found
> + grep -v eth1
> + grep -v eth0
> + cut -d : -f 2
> + grep BROADCAST
> + ip link
> + read i
> + ifconfig eth2 down
> /ramdisk/rrouter/disable_pubic.sh: 1: ifconfig: not found
> + read i
> Status: FAULT (keepalived process is dead)
> z^H^Z
> [9]+ Stopped tail -f /ramdisk/rrouter/keepalived.log 
> ------------------------------------------------------
> That's due to the cron job lacks of PATH in each user's crontab(though it's in /etc/crontab).

--
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