cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sudha Ponnaganti (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-2324) [XenServer][SystemVM] [Automation] haproxy is not running on the virtual router
Date Thu, 09 May 2013 05:03:15 GMT

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

Sudha Ponnaganti updated CLOUDSTACK-2324:
-----------------------------------------

    Summary: [XenServer][SystemVM] [Automation] haproxy is not running on the virtual router
 (was: [XenServer][SystemVM] haproxy is not running on the virtual router)
    
> [XenServer][SystemVM] [Automation] haproxy is not running on the virtual router
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2324
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2324
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
>            Reporter: venkata swamybabu budumuru
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have at least one advanced zone with Xen cluster 
> 2. Have a latest systemVM template
> version I used here is : 
> Cloudstack Release 4.2.0 Wed Apr 10 07:46:46 UTC 2013
> 3. deploy a VM connected to isolated network (which will automatically spin a virtual
router)
> 4. verify whether haproxy is running on the virtual router or not
> Observations:
> (i) 
> root@r-28-VM:~# ps -aef | grep -i haproxy
> root      7689  7457  0 14:21 pts/1    00:00:00 grep -i haproxy
> (ii)
> find / -name *haproxy*
> /etc/haproxy
> /etc/haproxy/haproxy.cfg.new
> /etc/haproxy/haproxy.cfg
> /etc/logrotate.d/haproxy
> /var/lib/haproxy
> /var/log/haproxy.log
> (iii) here is the snippet from /var/log/messages of virtual router
> May  3 12:40:10 r-28-VM cloud: Starting ssh
> May  3 12:40:10 r-28-VM cloud: Starting haproxy
> May  3 12:40:10 r-28-VM cloud: Starting apache2
> May  3 12:40:10 r-28-VM cloud: Starting dnsmasq
> May  3 12:40:10 r-28-VM cloud: Starting cloud-passwd-srvr
> May  3 12:40:10 r-28-VM cloud: Stopping cloud
> May  3 12:40:11 r-28-VM cloud: Stopping nfs-common
> May  3 12:40:11 r-28-VM cloud: Stopping portmap
> May  3 12:40:11 r-28-VM cloud: Stopping keepalived
> May  3 12:40:11 r-28-VM cloud: Stopping conntrackd
> (iv)
> snippet from /var/log/cloud.log
> Fri May  3 12:38:50 UTC 2013 Enable service dnsmasq = 1
> Fri May  3 12:38:50 UTC 2013 Enable service haproxy = 1
> Attaching the /var/log folder from router VM and mgmt server logs to the bug.
> (vi) Because of the above issue, unable to create LB rules. when tried it throws the
following error in the SMlog of the xenserver.
> Here is the snippet from /var/log/SMLog on the xenserver.
> + local cfg=/tmp/169_254_2_213.cfg
> + scp -P 3922 -q -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa.cloud /tmp/169_254_2_213.cfg
root@169.254.2.213:/etc/haproxy/haproxy.cfg.new
> + return 0
> + '[' 0 -gt 0 ']'
> + ssh -p 3922 -q -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa.cloud root@169.254.2.213
'/root/loadbalancer.sh -i 169.254.2.213 -f /tmp/169_254_2_213.cfg -a 10.147.44.61:22:, -s
10.147.44.64:8081:0/0:,,'
> mv: cannot stat `/var/run/haproxy.pid': No such file or directory
> cat: /var/run/haproxy.pid.old: No such file or directory
> kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
> /root/reconfigLB.sh: line 28: haproxy: command not found
> cat: /var/run/haproxy.pid.old: No such file or directory
> kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
> mv: cannot stat `/var/run/haproxy.pid.old': No such file or directory
> + exit 1
> '

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