Ask Your Question
0

When I start a VM, why it has "two" processes related with it?

asked 2012-06-18 08:05:56 -0500

guestly gravatar image

I start sever VMs by Nova+Quantum+Openvswitch environment, here is result of execute command ps -ef:

ps -ef | grep dnsmasq

nobody 10008 1 0 Jun15 ? 00:00:13 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-87a6f352-35.pid --listen-address=192.168.151.1 --except-interface=lo --dhcp-range=192.168.151.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-87a6f352-35.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 10009 10008 0 Jun15 ? 00:00:05 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-87a6f352-35.pid --listen-address=192.168.151.1 --except-interface=lo --dhcp-range=192.168.151.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-87a6f352-35.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 22662 1891 0 15:42 pts/12 00:00:00 grep --color=auto dnsmasq nobody 27412 1 0 Jun15 ? 00:00:11 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-e7863e30-1c.pid --listen-address=192.168.153.1 --except-interface=lo --dhcp-range=192.168.153.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-e7863e30-1c.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 27413 27412 0 Jun15 ? 00:00:01 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-e7863e30-1c.pid --listen-address=192.168.153.1 --except-interface=lo --dhcp-range=192.168.153.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-e7863e30-1c.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro nobody 27825 1 0 Jun15 ? 00:00:12 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-3faffe59-5d.pid --listen-address=192.168.152.1 --except-interface=lo --dhcp-range=192.168.152.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-3faffe59-5d.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 27826 27825 0 Jun15 ? 00:00:00 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-3faffe59-5d.pid --listen-address=192.168.152.1 --except-interface=lo --dhcp-range=192.168.152.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-3faffe59-5d.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro

for each gw*, it has a process of dnsmasq(i.e. pid=10008) and the other process(i.e.pid=10009 and ppid=10008), why?

edit retag flag offensive close merge delete

4 answers

Sort by ยป oldest newest most voted
0

answered 2012-06-18 19:59:20 -0500

danwent gravatar image

This is normal. One is the parent process (owned by user 'nobody') and one is the child (owned by user 'root').

dan

On Mon, Jun 18, 2012 at 1:05 AM, Havent < question200751@answers.launchpad.net > wrote:

New question #200751 on quantum: https://answers.launchpad.net/quantum/+question/200751 (https://answers.launchpad.net/quantum...)

I start sever VMs by Nova+Quantum+Openvswitch environment, here is result of execute command ps -ef:

ps -ef | grep dnsmasq

nobody 10008 1 0 Jun15 ? 00:00:13 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-87a6f352-35.pid --listen-address=192.168.151.1 --except-interface=lo --dhcp-range=192.168.151.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-87a6f352-35.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 10009 10008 0 Jun15 ? 00:00:05 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-87a6f352-35.pid --listen-address=192.168.151.1 --except-interface=lo --dhcp-range=192.168.151.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-87a6f352-35.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 22662 1891 0 15:42 pts/12 00:00:00 grep --color=auto dnsmasq nobody 27412 1 0 Jun15 ? 00:00:11 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-e7863e30-1c.pid --listen-address=192.168.153.1 --except-interface=lo --dhcp-range=192.168.153.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-e7863e30-1c.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 27413 27412 0 Jun15 ? 00:00:01 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-e7863e30-1c.pid --listen-address=192.168.153.1 --except-interface=lo --dhcp-range=192.168.153.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-e7863e30-1c.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro nobody 27825 1 0 Jun15 ? 00:00:12 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-3faffe59-5d.pid --listen-address=192.168.152.1 --except-interface=lo --dhcp-range=192.168.152.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-3faffe59-5d.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro root 27826 27825 0 Jun15 ? 00:00:00 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-gw-3faffe59-5d.pid --listen-address=192.168.152.1 --except-interface=lo --dhcp-range=192.168.152.2,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-gw-3faffe59-5d.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro

for each gw*, it has a process of dnsmasq(i.e. pid=10008) and the other process(i.e.pid=10009 and ppid=10008), why?


You received this question notification because you are an answer contact for quantum.


~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: http://www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~

edit flag offensive delete link more
0

answered 2012-06-19 01:01:14 -0500

guestly gravatar image

Thanks Dan! But furthermore, what is the purpose of doing this? Does this situation only appear in nova or in any cases? When requests of DHCP client for IP address arrive, which process replies them, the parent or the child?

edit flag offensive delete link more
0

answered 2012-06-19 06:41:08 -0500

danwent gravatar image

On Mon, Jun 18, 2012 at 6:05 PM, Havent < question200751@answers.launchpad.net > wrote:

Question #200751 on quantum changed: https://answers.launchpad.net/quantum/+question/200751 (https://answers.launchpad.net/quantum...)

Status: Answered => Open

Havent is still having a problem: Thanks Dan! But furthermore, what is the purpose of doing this? Does this situation only appear in nova or in any cases? When requests of DHCP client for IP address arrive, which process replies them, the parent or the child?

to be honest, I'm not sure whether this is just an artifact of how rootwrap works, or if its some kind of intentional active/backup mechanism. Maybe send an email to the main list, as QuantumManager just uses the same logic as nova-network.

dan

>


You received this question notification because you are an answer contact for quantum.


~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: http://www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~

edit flag offensive delete link more
0

answered 2012-06-19 07:39:55 -0500

guestly gravatar image

Thanks dan wendlandt, that solved my question.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-06-18 08:05:56 -0500

Seen: 58 times

Last updated: Jun 19 '12