You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2017/12/23 08:52:00 UTC
[jira] [Resolved] (CLOUDSTACK-9837) Upon stoping and starting an
InternalLbVM device from CloudStack, HAProxy service on the device is not
being started properly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohit Yadav resolved CLOUDSTACK-9837.
-------------------------------------
Resolution: Cannot Reproduce
On master with the new debian9 systemvmtemplate I could not reproduce the issue. I created a VPC with a LB and check haproxy status:
Before stop:
root@b-79-VM:~# systemctl is-active haproxy
active
Ran cloudmonkey commands to stop and start the VM:
(local) 🐵 > stop internalloadbalancervm id=8bff51ac-3d6a-410b-8971-b7525b066d88
(local) 🐵 > start internalloadbalancervm id=8bff51ac-3d6a-410b-8971-b7525b066d88
After stop+start:
root@b-79-VM:~# systemctl is-active haproxy
active
Please re-open if you can reproduce on master with the new debian9 systemvmtemplate.
> Upon stoping and starting an InternalLbVM device from CloudStack, HAProxy service on the device is not being started properly
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9837
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9837
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server, SystemVM
> Affects Versions: 4.10.0.0
> Reporter: Mani Prashanth Varma Manthena
> Assignee: Rohit Yadav
> Priority: Critical
>
> Upon stoping and starting an InternalLbVM device from CloudStack, HAProxy service on the device is not being started properly (i.e. not in running state).
> {noformat:title=service haproxy status}
> root@b-70-VM:~# service haproxy status
> haproxy not running.
> {noformat}
> {noformat:title=netstat output}
> root@b-70-VM:~# netstat -tlpn
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1836/rpcbind
> tcp 0 0 169.254.2.251:3922 0.0.0.0:* LISTEN 2748/sshd
> tcp6 0 0 :::111 :::* LISTEN 1836/rpcbind
> {noformat}
> {noformat:title= /var/log/messages output}
> Mar 14 12:41:19 b-70-VM kernel: [ 4.405107] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
> Mar 14 12:41:19 b-70-VM kernel: [ 4.464582] EXT4-fs (vda6): mounted filesystem with ordered data mode. Opts: (null)
> Mar 14 12:41:19 b-70-VM kernel: [ 4.516924] EXT4-fs (vda8): mounted filesystem with ordered data mode. Opts: (null)
> Mar 14 12:41:19 b-70-VM kernel: [ 4.558946] EXT4-fs (vda11): mounted filesystem with ordered data mode. Opts: (null)
> Mar 14 12:41:19 b-70-VM kernel: [ 4.638375] EXT4-fs (vda7): mounted filesystem with ordered data mode. Opts: (null)
> Mar 14 12:41:19 b-70-VM kernel: [ 4.701705] EXT4-fs (vda9): mounted filesystem with ordered data mode. Opts: (null)
> Mar 14 12:41:19 b-70-VM kernel: [ 4.740521] EXT4-fs (vda10): mounted filesystem with ordered data mode. Opts: (null)
> Mar 14 12:41:19 b-70-VM kernel: [ 11.586397] NET: Registered protocol family 15
> Mar 14 12:41:19 b-70-VM kernel: [ 11.593899] alg: No test for cipher_null (cipher_null-generic)
> Mar 14 12:41:19 b-70-VM kernel: [ 11.593917] alg: No test for ecb(cipher_null) (ecb-cipher_null)
> Mar 14 12:41:19 b-70-VM kernel: [ 11.593968] alg: No test for digest_null (digest_null-generic)
> Mar 14 12:41:19 b-70-VM kernel: [ 11.593981] alg: No test for compress_null (compress_null-generic)
> Mar 14 12:41:19 b-70-VM kernel: [ 11.607264] sha1_ssse3: Neither AVX nor SSSE3 is available/usable.
> Mar 14 12:41:19 b-70-VM kernel: [ 11.796542] ip_tables: (C) 2000-2006 Netfilter Core Team
> Mar 14 12:41:19 b-70-VM kernel: [ 11.971487] ip6_tables: (C) 2000-2006 Netfilter Core Team
> Mar 14 12:41:19 b-70-VM cloud: Starting ssh
> Mar 14 12:41:19 b-70-VM cloud: Starting haproxy
> Mar 14 12:41:20 b-70-VM cloud: Stopping cloud
> Mar 14 12:41:20 b-70-VM cloud: Stopping dnsmasq
> Mar 14 12:41:20 b-70-VM cloud: Stopping cloud-passwd-srvr
> Mar 14 12:41:20 b-70-VM cloud: Stopping apache2
> Mar 14 12:41:21 b-70-VM cloud: Waiting for VM boot up done for one second
> Mar 14 12:41:21 b-70-VM cloud: Stopping nfs-common
> Mar 14 12:41:21 b-70-VM cloud: Stopping portmap
> Mar 14 12:41:21 b-70-VM cloud: Boot up process done
> Mar 14 13:42:20 b-70-VM kernel: [ 3673.315888] device eth0 entered promiscuous mode
> Mar 14 13:43:01 b-70-VM kernel: [ 3714.667895] device eth0 left promiscuous mode
> {noformat}
> work around:
> Manually start the HAProxy service on the InternalLB/VPCInlineLB device.
> {noformat:title=Starting HAProxy service}
> root@b-70-VM:~# service haproxy start
> [....] Starting haproxy: haproxy[WARNING] 072/141946 (3417) : config : 'option forwardfor' ignored for proxy '10_1_1_151-22' as it requires HTTP mode.
> [WARNING] 072/141946 (3418) : config : 'option forwardfor' ignored for proxy '10_1_1_151-22' as it requires HTTP mode.
> . ok
> root@b-70-VM:~#
> root@b-70-VM:~# netstat -tlpn
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1836/rpcbind
> tcp 0 0 10.1.1.151:80 0.0.0.0:* LISTEN 3419/haproxy
> tcp 0 0 10.1.1.249:8081 0.0.0.0:* LISTEN 3419/haproxy
> tcp 0 0 169.254.2.251:3922 0.0.0.0:* LISTEN 2748/sshd
> tcp 0 0 10.1.1.151:22 0.0.0.0:* LISTEN 3419/haproxy
> tcp6 0 0 :::111 :::* LISTEN 1836/rpcbind
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)