You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "Karan ." <di...@gmail.com> on 2013/09/29 20:41:36 UTC
Management Server does not start when interface cable is unplugged.
Hi
I'll be giving a short demo on CLOUDSTACK in my organization and for this
I have a very basic setup of Cloudstack 4.1.1 where I am using one laptop
as management server as well as agent . Also, I am using basic networking.
>From logs I have observed that whenever my network cable is unplugged, MS
doesn't start and throws following exception:
2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
(Timer-1:null) Start configuring cluster manager :
ClusterManagerImpl_EnhancerByCloudStack_d07fda90
2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
(Timer-1:null) Cluster node IP : 192.168.1.4
2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
(Timer-1:null) Unhandled exception
javax.naming.ConfigurationException: cluster node IP should be valid local
address where the server is running, please check your configuration
at
com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
at
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
at
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Just for starting MS I have to attach my laptop to a network. Please
suggest me a way where I can start MS without being connected to any
network since I have a single host setup. I have tried bringing my
interface up using 'ip link set eth0 up' but eth0 status is always DOWN
unless I plug it into a network.
Regards
Karan Pugla
Re: Management Server does not start when interface cable is unplugged.
Posted by "Karan ." <di...@gmail.com>.
Since I am new to cloudstack I started with a basic installation with MS
and agent on my laptop. As I get familiar with it I added more
hosts(cloudstack-agents) to it. These hosts are at my office.
On Mon, Sep 30, 2013 at 2:17 AM, Karan . <di...@gmail.com> wrote:
> I mean the hosts on which hypervisors are running. The cloudstack agents.
>
>
> On Mon, Sep 30, 2013 at 2:15 AM, Rafael Weingartner <
> rafaelweingartner@gmail.com> wrote:
>
>> what do you mean with "manage the agents in office lab"?
>>
>>
>> 2013/9/29 Karan . <di...@gmail.com>
>>
>> > Thanks Rafael this is one possible solution. But this is the complete
>> > scenario I am facing.
>> > When I am at my office I use my laptop(which has MS and agent on it) to
>> > manage the agents in office lab. Now I want that when I am back at home
>> I
>> > can still start the MS on my laptop and tinker around with cloudstack
>> but
>> > this time I am not connected to any network .
>> >
>> > The solution I can see here is that when I am at office I should set
>> host
>> > in cloud.configuration to 192.168.1.4 and at home I should set it to
>> > 127.0.0.1 . right?
>> >
>> >
>> > Regards
>> >
>> > Karan
>> >
>> >
>> > On Mon, Sep 30, 2013 at 1:52 AM, Karan . <di...@gmail.com>
>> wrote:
>> >
>> > > 192.168.1.4 is my CS server ip and yes I can ping it. Currently, I
>> have
>> > > only one machine in my setup and I have assigned this ip to it and I
>> am
>> > > running MS as well as agent over it.
>> > > I would like to know how I can run CLOUDSTACK in a single node setup
>> > > without being connected to any network and gateways.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
>> > > rafaelweingartner@gmail.com> wrote:
>> > >
>> > >> better, what is the CS server ip address?
>> > >>
>> > >>
>> > >> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
>> > >>
>> > >> > from the server that CS is running can you ping this address:
>> > >> 192.168.1.4?
>> > >> >
>> > >> >
>> > >> > 2013/9/29 Karan . <di...@gmail.com>
>> > >> >
>> > >> > Hi Marty,
>> > >> >>
>> > >> >> Interface already has static ip assigned to it. In fact, this is
>> how
>> > >> >> cloudstack has configured my /etc/network/interfaces
>> > >> >>
>> > >> >> auto lo
>> > >> >> iface lo inet loopback
>> > >> >>
>> > >> >> auto eth0
>> > >> >> iface eth0 inet manual
>> > >> >>
>> > >> >> auto cloudbr0
>> > >> >> iface cloudbr0 inet static
>> > >> >> bridge_ports eth0
>> > >> >> address 192.168.1.4
>> > >> >> netmask 255.255.255.0
>> > >> >> gateway 192.168.1.1
>> > >> >>
>> > >> >> And this is the output for 'ip link '
>> > >> >>
>> > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
>> UNKNOWN
>> > >> mode
>> > >> >> DEFAULT
>> > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>> > pfifo_fast
>> > >> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
>> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>> > noqueue
>> > >> >> state DOWN mode DEFAULT
>> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> > >> >>
>> > >> >> And 'ip address'
>> > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
>> UNKNOWN
>> > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> > >> >> inet 127.0.0.1/8 scope host lo
>> > >> >> inet6 ::1/128 scope host
>> > >> >> valid_lft forever preferred_lft forever
>> > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>> > pfifo_fast
>> > >> >> master cloudbr0 state DOWN qlen 1000
>> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>> > noqueue
>> > >> >> state DOWN
>> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> > >> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> Regards
>> > >> >> Karan Pugla
>> > >> >>
>> > >> >>
>> > >> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <
>> msweet.dev@gmail.com>
>> > >> >> wrote:
>> > >> >>
>> > >> >> > Hi Karan,
>> > >> >> >
>> > >> >> > Try assigning a static address to the interface then bring it up
>> > >> using
>> > >> >> > ifup. This should in theory not close down the IP address once
>> link
>> > >> has
>> > >> >> > been lost.
>> > >> >> >
>> > >> >> > Hope this helps,
>> > >> >> > Marty
>> > >> >> >
>> > >> >> >
>> > >> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <
>> digitalkaran@gmail.com>
>> > >> >> wrote:
>> > >> >> >
>> > >> >> > > Hi
>> > >> >> > >
>> > >> >> > > I'll be giving a short demo on CLOUDSTACK in my organization
>> and
>> > >> for
>> > >> >> > this
>> > >> >> > > I have a very basic setup of Cloudstack 4.1.1 where I am
>> using
>> > >> one
>> > >> >> > laptop
>> > >> >> > > as management server as well as agent . Also, I am using basic
>> > >> >> > networking.
>> > >> >> > > From logs I have observed that whenever my network cable is
>> > >> >> unplugged, MS
>> > >> >> > > doesn't start and throws following exception:
>> > >> >> > >
>> > >> >> > > 2013-09-29 23:09:09,693 INFO
>> [cloud.cluster.ClusterManagerImpl]
>> > >> >> > > (Timer-1:null) Start configuring cluster manager :
>> > >> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
>> > >> >> > > 2013-09-29 23:09:09,753 INFO
>> [cloud.cluster.ClusterManagerImpl]
>> > >> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
>> > >> >> > > 2013-09-29 23:09:09,756 ERROR
>> [utils.component.ComponentContext]
>> > >> >> > > (Timer-1:null) Unhandled exception
>> > >> >> > > javax.naming.ConfigurationException: cluster node IP should be
>> > >> valid
>> > >> >> > local
>> > >> >> > > address where the server is running, please check your
>> > >> configuration
>> > >> >> > > at
>> > >> >> > >
>> > >> >> > >
>> > >> >> >
>> > >> >>
>> > >>
>> >
>> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
>> > >> >> > > at
>> > >> >> > >
>> > >> >> > >
>> > >> >> >
>> > >> >>
>> > >>
>> >
>> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>> > >> >> > > at
>> > >> >> > >
>> > >> >>
>> > >>
>> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
>> > >> >> > > at java.util.TimerThread.mainLoop(Timer.java:555)
>> > >> >> > > at java.util.TimerThread.run(Timer.java:505)
>> > >> >> > >
>> > >> >> > > Just for starting MS I have to attach my laptop to a network.
>> > >> Please
>> > >> >> > > suggest me a way where I can start MS without being connected
>> to
>> > >> any
>> > >> >> > > network since I have a single host setup. I have tried
>> bringing
>> > my
>> > >> >> > > interface up using 'ip link set eth0 up' but eth0 status is
>> > always
>> > >> >> DOWN
>> > >> >> > > unless I plug it into a network.
>> > >> >> > >
>> > >> >> > >
>> > >> >> > > Regards
>> > >> >> > > Karan Pugla
>> > >> >> > >
>> > >> >> >
>> > >> >>
>> > >> >
>> > >> >
>> > >> >
>> > >> > --
>> > >> > Rafael Weingartner
>> > >> >
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Rafael Weingartner
>> > >>
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Rafael Weingartner
>>
>
>
Re:[SOLVED] Management Server does not start when interface cable
is unplugged.
Posted by Jayapal Reddy Uradi <ja...@citrix.com>.
Added SOLVED tag to subject.
-Jayapal
On 30-Sep-2013, at 9:24 AM, Karan . <di...@gmail.com> wrote:
> Ok got it. Thanks Rafael and everyone for your time and help
>
> Regards
> Karan Pugla
> On 30-Sep-2013 6:51 AM, "Rafael Weingartner" <ra...@gmail.com>
> wrote:
>
>> Well, I am also not a CS expert. But I have taken a look at the CS source
>> code.
>>
>> It seems that the value on the database "cloud.configuration" is used when
>> you have multiple CS servers. That IP address should be the IP of the
>> "master" node. So, when other node goes up they know where to find the
>> master server.
>>
>> So, if you have just one CS node, you could without any problems use
>> localhost or 127.0.0.1.
>>
>> Now the value on the db.properties,
>>
>> "cluster.node.IP", it seems that this IP is used to build some links when
>> the server is rendering the web pages and to tell the master the IP of the
>> "slave".
>>
>> Bottom line, these IP addresses are used just for CS management purpose and
>> as long you just have 1 CS node, you can use both parameters with localhost
>> value, either on your home or at your company to manage the servers.
>>
>>
>>
>> 2013/9/29 Karan . <di...@gmail.com>
>>>
>>> Thank you so much Rafael. I changed cluster.node.IP to 127.0.0.1 in
>>> db.properties and host in cloud.configuration and MS has started now.
>>>
>>> Can you please explain when one should use interface ip in
>> cluster.node.IP
>>> ? What difference it makes when one use 127.0.0.1 instead of real
>> interface
>>> ip ?
>>>
>>> Regards
>>> Karam Pugla
>>>
>>>
>>> On Mon, Sep 30, 2013 at 2:22 AM, Rafael Weingartner <
>>> rafaelweingartner@gmail.com> wrote:
>>>
>>>> Ok, I got it.
>>>> Even though the managed hosts are on the 192.162.1.0/24 network, you
>> can
>>>> still use the localhost as the parameter on CS.
>>>> Since it is just used on CS for management purpose, specially when you
>> have
>>>> more than one CS Web server deployment.
>>>>
>>>>
>>>> 2013/9/29 Karan . <di...@gmail.com>
>>>>
>>>>> I mean the hosts on which hypervisors are running. The cloudstack
>> agents.
>>>>>
>>>>>
>>>>> On Mon, Sep 30, 2013 at 2:15 AM, Rafael Weingartner <
>>>>> rafaelweingartner@gmail.com> wrote:
>>>>>
>>>>>> what do you mean with "manage the agents in office lab"?
>>>>>>
>>>>>>
>>>>>> 2013/9/29 Karan . <di...@gmail.com>
>>>>>>
>>>>>>> Thanks Rafael this is one possible solution. But this is the
>> complete
>>>>>>> scenario I am facing.
>>>>>>> When I am at my office I use my laptop(which has MS and agent on
>> it)
>>>>> to
>>>>>>> manage the agents in office lab. Now I want that when I am back
>> at
>>>>> home I
>>>>>>> can still start the MS on my laptop and tinker around with
>>>> cloudstack
>>>>>> but
>>>>>>> this time I am not connected to any network .
>>>>>>>
>>>>>>> The solution I can see here is that when I am at office I
>> should
>>>> set
>>>>>> host
>>>>>>> in cloud.configuration to 192.168.1.4 and at home I should set it
>> to
>>>>>>> 127.0.0.1 . right?
>>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Karan
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Sep 30, 2013 at 1:52 AM, Karan . <digitalkaran@gmail.com
>>>
>>>>> wrote:
>>>>>>>
>>>>>>>> 192.168.1.4 is my CS server ip and yes I can ping it.
>> Currently, I
>>>>> have
>>>>>>>> only one machine in my setup and I have assigned this ip to it
>> and
>>>> I
>>>>>> am
>>>>>>>> running MS as well as agent over it.
>>>>>>>> I would like to know how I can run CLOUDSTACK in a single node
>>>> setup
>>>>>>>> without being connected to any network and gateways.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
>>>>>>>> rafaelweingartner@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> better, what is the CS server ip address?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
>>>>>>>>>
>>>>>>>>>> from the server that CS is running can you ping this
>> address:
>>>>>>>>> 192.168.1.4?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/9/29 Karan . <di...@gmail.com>
>>>>>>>>>>
>>>>>>>>>> Hi Marty,
>>>>>>>>>>>
>>>>>>>>>>> Interface already has static ip assigned to it. In fact,
>> this
>>>> is
>>>>>> how
>>>>>>>>>>> cloudstack has configured my /etc/network/interfaces
>>>>>>>>>>>
>>>>>>>>>>> auto lo
>>>>>>>>>>> iface lo inet loopback
>>>>>>>>>>>
>>>>>>>>>>> auto eth0
>>>>>>>>>>> iface eth0 inet manual
>>>>>>>>>>>
>>>>>>>>>>> auto cloudbr0
>>>>>>>>>>> iface cloudbr0 inet static
>>>>>>>>>>> bridge_ports eth0
>>>>>>>>>>> address 192.168.1.4
>>>>>>>>>>> netmask 255.255.255.0
>>>>>>>>>>> gateway 192.168.1.1
>>>>>>>>>>>
>>>>>>>>>>> And this is the output for 'ip link '
>>>>>>>>>>>
>>>>>>>>>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
>>>>> UNKNOWN
>>>>>>>>> mode
>>>>>>>>>>> DEFAULT
>>>>>>>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>>>>>>>>>> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>>>>>>> pfifo_fast
>>>>>>>>>>> master cloudbr0 state DOWN mode DEFAULT qlen 1000
>>>>>>>>>>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>>>>>>>>>>> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
>> qdisc
>>>>>>> noqueue
>>>>>>>>>>> state DOWN mode DEFAULT
>>>>>>>>>>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>>>>>>>>>>>
>>>>>>>>>>> And 'ip address'
>>>>>>>>>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
>>>>> UNKNOWN
>>>>>>>>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>>>>>>>>>> inet 127.0.0.1/8 scope host lo
>>>>>>>>>>> inet6 ::1/128 scope host
>>>>>>>>>>> valid_lft forever preferred_lft forever
>>>>>>>>>>> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>>>>>>> pfifo_fast
>>>>>>>>>>> master cloudbr0 state DOWN qlen 1000
>>>>>>>>>>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>>>>>>>>>>> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
>> qdisc
>>>>>>> noqueue
>>>>>>>>>>> state DOWN
>>>>>>>>>>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>>>>>>>>>>> inet 192.168.1.4/24 brd 192.168.1.255 scope global
>>>> cloudbr0
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>> Karan Pugla
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <
>>>>> msweet.dev@gmail.com
>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Karan,
>>>>>>>>>>>>
>>>>>>>>>>>> Try assigning a static address to the interface then
>> bring it
>>>>> up
>>>>>>>>> using
>>>>>>>>>>>> ifup. This should in theory not close down the IP address
>>>> once
>>>>>> link
>>>>>>>>> has
>>>>>>>>>>>> been lost.
>>>>>>>>>>>>
>>>>>>>>>>>> Hope this helps,
>>>>>>>>>>>> Marty
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Sep 29, 2013 at 7:41 PM, Karan . <
>>>>> digitalkaran@gmail.com
>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'll be giving a short demo on CLOUDSTACK in my
>>>> organization
>>>>>> and
>>>>>>>>> for
>>>>>>>>>>>> this
>>>>>>>>>>>>> I have a very basic setup of Cloudstack 4.1.1 where I
>> am
>>>>>> using
>>>>>>>>> one
>>>>>>>>>>>> laptop
>>>>>>>>>>>>> as management server as well as agent . Also, I am
>> using
>>>>> basic
>>>>>>>>>>>> networking.
>>>>>>>>>>>>> From logs I have observed that whenever my network
>> cable is
>>>>>>>>>>> unplugged, MS
>>>>>>>>>>>>> doesn't start and throws following exception:
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2013-09-29 23:09:09,693 INFO
>>>>>> [cloud.cluster.ClusterManagerImpl]
>>>>>>>>>>>>> (Timer-1:null) Start configuring cluster manager :
>>>>>>>>>>>>> ClusterManagerImpl_EnhancerByCloudStack_d07fda90
>>>>>>>>>>>>> 2013-09-29 23:09:09,753 INFO
>>>>>> [cloud.cluster.ClusterManagerImpl]
>>>>>>>>>>>>> (Timer-1:null) Cluster node IP : 192.168.1.4
>>>>>>>>>>>>> 2013-09-29 23:09:09,756 ERROR
>>>>>> [utils.component.ComponentContext]
>>>>>>>>>>>>> (Timer-1:null) Unhandled exception
>>>>>>>>>>>>> javax.naming.ConfigurationException: cluster node IP
>> should
>>>>> be
>>>>>>>>> valid
>>>>>>>>>>>> local
>>>>>>>>>>>>> address where the server is running, please check your
>>>>>>>>> configuration
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
>>>>>>>>>>>>> at
>> java.util.TimerThread.mainLoop(Timer.java:555)
>>>>>>>>>>>>> at java.util.TimerThread.run(Timer.java:505)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Just for starting MS I have to attach my laptop to a
>>>> network.
>>>>>>>>> Please
>>>>>>>>>>>>> suggest me a way where I can start MS without being
>>>> connected
>>>>>> to
>>>>>>>>> any
>>>>>>>>>>>>> network since I have a single host setup. I have tried
>>>>> bringing
>>>>>>> my
>>>>>>>>>>>>> interface up using 'ip link set eth0 up' but eth0
>> status is
>>>>>>> always
>>>>>>>>>>> DOWN
>>>>>>>>>>>>> unless I plug it into a network.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards
>>>>>>>>>>>>> Karan Pugla
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Rafael Weingartner
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Rafael Weingartner
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Rafael Weingartner
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Rafael Weingartner
>>>>
>>
>>
>>
>>
>> --
>> Rafael Weingartner
>>
Re: Management Server does not start when interface cable is unplugged.
Posted by "Karan ." <di...@gmail.com>.
Ok got it. Thanks Rafael and everyone for your time and help
Regards
Karan Pugla
On 30-Sep-2013 6:51 AM, "Rafael Weingartner" <ra...@gmail.com>
wrote:
> Well, I am also not a CS expert. But I have taken a look at the CS source
> code.
>
> It seems that the value on the database "cloud.configuration" is used when
> you have multiple CS servers. That IP address should be the IP of the
> "master" node. So, when other node goes up they know where to find the
> master server.
>
> So, if you have just one CS node, you could without any problems use
> localhost or 127.0.0.1.
>
> Now the value on the db.properties,
>
> "cluster.node.IP", it seems that this IP is used to build some links when
> the server is rendering the web pages and to tell the master the IP of the
> "slave".
>
> Bottom line, these IP addresses are used just for CS management purpose and
> as long you just have 1 CS node, you can use both parameters with localhost
> value, either on your home or at your company to manage the servers.
>
>
>
> 2013/9/29 Karan . <di...@gmail.com>
> >
> > Thank you so much Rafael. I changed cluster.node.IP to 127.0.0.1 in
> > db.properties and host in cloud.configuration and MS has started now.
> >
> > Can you please explain when one should use interface ip in
> cluster.node.IP
> > ? What difference it makes when one use 127.0.0.1 instead of real
> interface
> > ip ?
> >
> > Regards
> > Karam Pugla
> >
> >
> > On Mon, Sep 30, 2013 at 2:22 AM, Rafael Weingartner <
> > rafaelweingartner@gmail.com> wrote:
> >
> > > Ok, I got it.
> > > Even though the managed hosts are on the 192.162.1.0/24 network, you
> can
> > > still use the localhost as the parameter on CS.
> > > Since it is just used on CS for management purpose, specially when you
> have
> > > more than one CS Web server deployment.
> > >
> > >
> > > 2013/9/29 Karan . <di...@gmail.com>
> > >
> > > > I mean the hosts on which hypervisors are running. The cloudstack
> agents.
> > > >
> > > >
> > > > On Mon, Sep 30, 2013 at 2:15 AM, Rafael Weingartner <
> > > > rafaelweingartner@gmail.com> wrote:
> > > >
> > > > > what do you mean with "manage the agents in office lab"?
> > > > >
> > > > >
> > > > > 2013/9/29 Karan . <di...@gmail.com>
> > > > >
> > > > > > Thanks Rafael this is one possible solution. But this is the
> complete
> > > > > > scenario I am facing.
> > > > > > When I am at my office I use my laptop(which has MS and agent on
> it)
> > > > to
> > > > > > manage the agents in office lab. Now I want that when I am back
> at
> > > > home I
> > > > > > can still start the MS on my laptop and tinker around with
> > > cloudstack
> > > > > but
> > > > > > this time I am not connected to any network .
> > > > > >
> > > > > > The solution I can see here is that when I am at office I
> should
> > > set
> > > > > host
> > > > > > in cloud.configuration to 192.168.1.4 and at home I should set it
> to
> > > > > > 127.0.0.1 . right?
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Karan
> > > > > >
> > > > > >
> > > > > > On Mon, Sep 30, 2013 at 1:52 AM, Karan . <digitalkaran@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > 192.168.1.4 is my CS server ip and yes I can ping it.
> Currently, I
> > > > have
> > > > > > > only one machine in my setup and I have assigned this ip to it
> and
> > > I
> > > > > am
> > > > > > > running MS as well as agent over it.
> > > > > > > I would like to know how I can run CLOUDSTACK in a single node
> > > setup
> > > > > > > without being connected to any network and gateways.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
> > > > > > > rafaelweingartner@gmail.com> wrote:
> > > > > > >
> > > > > > >> better, what is the CS server ip address?
> > > > > > >>
> > > > > > >>
> > > > > > >> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
> > > > > > >>
> > > > > > >> > from the server that CS is running can you ping this
> address:
> > > > > > >> 192.168.1.4?
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > 2013/9/29 Karan . <di...@gmail.com>
> > > > > > >> >
> > > > > > >> > Hi Marty,
> > > > > > >> >>
> > > > > > >> >> Interface already has static ip assigned to it. In fact,
> this
> > > is
> > > > > how
> > > > > > >> >> cloudstack has configured my /etc/network/interfaces
> > > > > > >> >>
> > > > > > >> >> auto lo
> > > > > > >> >> iface lo inet loopback
> > > > > > >> >>
> > > > > > >> >> auto eth0
> > > > > > >> >> iface eth0 inet manual
> > > > > > >> >>
> > > > > > >> >> auto cloudbr0
> > > > > > >> >> iface cloudbr0 inet static
> > > > > > >> >> bridge_ports eth0
> > > > > > >> >> address 192.168.1.4
> > > > > > >> >> netmask 255.255.255.0
> > > > > > >> >> gateway 192.168.1.1
> > > > > > >> >>
> > > > > > >> >> And this is the output for 'ip link '
> > > > > > >> >>
> > > > > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> > > > UNKNOWN
> > > > > > >> mode
> > > > > > >> >> DEFAULT
> > > > > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > > > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > > > pfifo_fast
> > > > > > >> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> > > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
> qdisc
> > > > > > noqueue
> > > > > > >> >> state DOWN mode DEFAULT
> > > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > > >> >>
> > > > > > >> >> And 'ip address'
> > > > > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> > > > UNKNOWN
> > > > > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > > > > >> >> inet 127.0.0.1/8 scope host lo
> > > > > > >> >> inet6 ::1/128 scope host
> > > > > > >> >> valid_lft forever preferred_lft forever
> > > > > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > > > pfifo_fast
> > > > > > >> >> master cloudbr0 state DOWN qlen 1000
> > > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
> qdisc
> > > > > > noqueue
> > > > > > >> >> state DOWN
> > > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > > >> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global
> > > cloudbr0
> > > > > > >> >>
> > > > > > >> >>
> > > > > > >> >>
> > > > > > >> >> Regards
> > > > > > >> >> Karan Pugla
> > > > > > >> >>
> > > > > > >> >>
> > > > > > >> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <
> > > > msweet.dev@gmail.com
> > > > > >
> > > > > > >> >> wrote:
> > > > > > >> >>
> > > > > > >> >> > Hi Karan,
> > > > > > >> >> >
> > > > > > >> >> > Try assigning a static address to the interface then
> bring it
> > > > up
> > > > > > >> using
> > > > > > >> >> > ifup. This should in theory not close down the IP address
> > > once
> > > > > link
> > > > > > >> has
> > > > > > >> >> > been lost.
> > > > > > >> >> >
> > > > > > >> >> > Hope this helps,
> > > > > > >> >> > Marty
> > > > > > >> >> >
> > > > > > >> >> >
> > > > > > >> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <
> > > > digitalkaran@gmail.com
> > > > > >
> > > > > > >> >> wrote:
> > > > > > >> >> >
> > > > > > >> >> > > Hi
> > > > > > >> >> > >
> > > > > > >> >> > > I'll be giving a short demo on CLOUDSTACK in my
> > > organization
> > > > > and
> > > > > > >> for
> > > > > > >> >> > this
> > > > > > >> >> > > I have a very basic setup of Cloudstack 4.1.1 where I
> am
> > > > > using
> > > > > > >> one
> > > > > > >> >> > laptop
> > > > > > >> >> > > as management server as well as agent . Also, I am
> using
> > > > basic
> > > > > > >> >> > networking.
> > > > > > >> >> > > From logs I have observed that whenever my network
> cable is
> > > > > > >> >> unplugged, MS
> > > > > > >> >> > > doesn't start and throws following exception:
> > > > > > >> >> > >
> > > > > > >> >> > > 2013-09-29 23:09:09,693 INFO
> > > > > [cloud.cluster.ClusterManagerImpl]
> > > > > > >> >> > > (Timer-1:null) Start configuring cluster manager :
> > > > > > >> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> > > > > > >> >> > > 2013-09-29 23:09:09,753 INFO
> > > > > [cloud.cluster.ClusterManagerImpl]
> > > > > > >> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> > > > > > >> >> > > 2013-09-29 23:09:09,756 ERROR
> > > > > [utils.component.ComponentContext]
> > > > > > >> >> > > (Timer-1:null) Unhandled exception
> > > > > > >> >> > > javax.naming.ConfigurationException: cluster node IP
> should
> > > > be
> > > > > > >> valid
> > > > > > >> >> > local
> > > > > > >> >> > > address where the server is running, please check your
> > > > > > >> configuration
> > > > > > >> >> > > at
> > > > > > >> >> > >
> > > > > > >> >> > >
> > > > > > >> >> >
> > > > > > >> >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
>
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> > > > > > >> >> > > at
> > > > > > >> >> > >
> > > > > > >> >> > >
> > > > > > >> >> >
> > > > > > >> >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
>
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> > > > > > >> >> > > at
> > > > > > >> >> > >
> > > > > > >> >>
> > > > > > >>
> > > > >
> > >
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > > > > > >> >> > > at
> java.util.TimerThread.mainLoop(Timer.java:555)
> > > > > > >> >> > > at java.util.TimerThread.run(Timer.java:505)
> > > > > > >> >> > >
> > > > > > >> >> > > Just for starting MS I have to attach my laptop to a
> > > network.
> > > > > > >> Please
> > > > > > >> >> > > suggest me a way where I can start MS without being
> > > connected
> > > > > to
> > > > > > >> any
> > > > > > >> >> > > network since I have a single host setup. I have tried
> > > > bringing
> > > > > > my
> > > > > > >> >> > > interface up using 'ip link set eth0 up' but eth0
> status is
> > > > > > always
> > > > > > >> >> DOWN
> > > > > > >> >> > > unless I plug it into a network.
> > > > > > >> >> > >
> > > > > > >> >> > >
> > > > > > >> >> > > Regards
> > > > > > >> >> > > Karan Pugla
> > > > > > >> >> > >
> > > > > > >> >> >
> > > > > > >> >>
> > > > > > >> >
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > --
> > > > > > >> > Rafael Weingartner
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >> Rafael Weingartner
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Rafael Weingartner
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Rafael Weingartner
> > >
>
>
>
>
> --
> Rafael Weingartner
>
Re: Management Server does not start when interface cable is unplugged.
Posted by Rafael Weingartner <ra...@gmail.com>.
Well, I am also not a CS expert. But I have taken a look at the CS source
code.
It seems that the value on the database "cloud.configuration" is used when
you have multiple CS servers. That IP address should be the IP of the
"master" node. So, when other node goes up they know where to find the
master server.
So, if you have just one CS node, you could without any problems use
localhost or 127.0.0.1.
Now the value on the db.properties,
"cluster.node.IP", it seems that this IP is used to build some links when
the server is rendering the web pages and to tell the master the IP of the
"slave".
Bottom line, these IP addresses are used just for CS management purpose and
as long you just have 1 CS node, you can use both parameters with localhost
value, either on your home or at your company to manage the servers.
2013/9/29 Karan . <di...@gmail.com>
>
> Thank you so much Rafael. I changed cluster.node.IP to 127.0.0.1 in
> db.properties and host in cloud.configuration and MS has started now.
>
> Can you please explain when one should use interface ip in cluster.node.IP
> ? What difference it makes when one use 127.0.0.1 instead of real
interface
> ip ?
>
> Regards
> Karam Pugla
>
>
> On Mon, Sep 30, 2013 at 2:22 AM, Rafael Weingartner <
> rafaelweingartner@gmail.com> wrote:
>
> > Ok, I got it.
> > Even though the managed hosts are on the 192.162.1.0/24 network, you can
> > still use the localhost as the parameter on CS.
> > Since it is just used on CS for management purpose, specially when you
have
> > more than one CS Web server deployment.
> >
> >
> > 2013/9/29 Karan . <di...@gmail.com>
> >
> > > I mean the hosts on which hypervisors are running. The cloudstack
agents.
> > >
> > >
> > > On Mon, Sep 30, 2013 at 2:15 AM, Rafael Weingartner <
> > > rafaelweingartner@gmail.com> wrote:
> > >
> > > > what do you mean with "manage the agents in office lab"?
> > > >
> > > >
> > > > 2013/9/29 Karan . <di...@gmail.com>
> > > >
> > > > > Thanks Rafael this is one possible solution. But this is the
complete
> > > > > scenario I am facing.
> > > > > When I am at my office I use my laptop(which has MS and agent on
it)
> > > to
> > > > > manage the agents in office lab. Now I want that when I am back at
> > > home I
> > > > > can still start the MS on my laptop and tinker around with
> > cloudstack
> > > > but
> > > > > this time I am not connected to any network .
> > > > >
> > > > > The solution I can see here is that when I am at office I should
> > set
> > > > host
> > > > > in cloud.configuration to 192.168.1.4 and at home I should set it
to
> > > > > 127.0.0.1 . right?
> > > > >
> > > > >
> > > > > Regards
> > > > >
> > > > > Karan
> > > > >
> > > > >
> > > > > On Mon, Sep 30, 2013 at 1:52 AM, Karan . <di...@gmail.com>
> > > wrote:
> > > > >
> > > > > > 192.168.1.4 is my CS server ip and yes I can ping it.
Currently, I
> > > have
> > > > > > only one machine in my setup and I have assigned this ip to it
and
> > I
> > > > am
> > > > > > running MS as well as agent over it.
> > > > > > I would like to know how I can run CLOUDSTACK in a single node
> > setup
> > > > > > without being connected to any network and gateways.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
> > > > > > rafaelweingartner@gmail.com> wrote:
> > > > > >
> > > > > >> better, what is the CS server ip address?
> > > > > >>
> > > > > >>
> > > > > >> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
> > > > > >>
> > > > > >> > from the server that CS is running can you ping this address:
> > > > > >> 192.168.1.4?
> > > > > >> >
> > > > > >> >
> > > > > >> > 2013/9/29 Karan . <di...@gmail.com>
> > > > > >> >
> > > > > >> > Hi Marty,
> > > > > >> >>
> > > > > >> >> Interface already has static ip assigned to it. In fact,
this
> > is
> > > > how
> > > > > >> >> cloudstack has configured my /etc/network/interfaces
> > > > > >> >>
> > > > > >> >> auto lo
> > > > > >> >> iface lo inet loopback
> > > > > >> >>
> > > > > >> >> auto eth0
> > > > > >> >> iface eth0 inet manual
> > > > > >> >>
> > > > > >> >> auto cloudbr0
> > > > > >> >> iface cloudbr0 inet static
> > > > > >> >> bridge_ports eth0
> > > > > >> >> address 192.168.1.4
> > > > > >> >> netmask 255.255.255.0
> > > > > >> >> gateway 192.168.1.1
> > > > > >> >>
> > > > > >> >> And this is the output for 'ip link '
> > > > > >> >>
> > > > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> > > UNKNOWN
> > > > > >> mode
> > > > > >> >> DEFAULT
> > > > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > > pfifo_fast
> > > > > >> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
qdisc
> > > > > noqueue
> > > > > >> >> state DOWN mode DEFAULT
> > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > >> >>
> > > > > >> >> And 'ip address'
> > > > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> > > UNKNOWN
> > > > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > > > >> >> inet 127.0.0.1/8 scope host lo
> > > > > >> >> inet6 ::1/128 scope host
> > > > > >> >> valid_lft forever preferred_lft forever
> > > > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > > pfifo_fast
> > > > > >> >> master cloudbr0 state DOWN qlen 1000
> > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
qdisc
> > > > > noqueue
> > > > > >> >> state DOWN
> > > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > > >> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global
> > cloudbr0
> > > > > >> >>
> > > > > >> >>
> > > > > >> >>
> > > > > >> >> Regards
> > > > > >> >> Karan Pugla
> > > > > >> >>
> > > > > >> >>
> > > > > >> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <
> > > msweet.dev@gmail.com
> > > > >
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >> > Hi Karan,
> > > > > >> >> >
> > > > > >> >> > Try assigning a static address to the interface then
bring it
> > > up
> > > > > >> using
> > > > > >> >> > ifup. This should in theory not close down the IP address
> > once
> > > > link
> > > > > >> has
> > > > > >> >> > been lost.
> > > > > >> >> >
> > > > > >> >> > Hope this helps,
> > > > > >> >> > Marty
> > > > > >> >> >
> > > > > >> >> >
> > > > > >> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <
> > > digitalkaran@gmail.com
> > > > >
> > > > > >> >> wrote:
> > > > > >> >> >
> > > > > >> >> > > Hi
> > > > > >> >> > >
> > > > > >> >> > > I'll be giving a short demo on CLOUDSTACK in my
> > organization
> > > > and
> > > > > >> for
> > > > > >> >> > this
> > > > > >> >> > > I have a very basic setup of Cloudstack 4.1.1 where I
am
> > > > using
> > > > > >> one
> > > > > >> >> > laptop
> > > > > >> >> > > as management server as well as agent . Also, I am using
> > > basic
> > > > > >> >> > networking.
> > > > > >> >> > > From logs I have observed that whenever my network
cable is
> > > > > >> >> unplugged, MS
> > > > > >> >> > > doesn't start and throws following exception:
> > > > > >> >> > >
> > > > > >> >> > > 2013-09-29 23:09:09,693 INFO
> > > > [cloud.cluster.ClusterManagerImpl]
> > > > > >> >> > > (Timer-1:null) Start configuring cluster manager :
> > > > > >> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> > > > > >> >> > > 2013-09-29 23:09:09,753 INFO
> > > > [cloud.cluster.ClusterManagerImpl]
> > > > > >> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> > > > > >> >> > > 2013-09-29 23:09:09,756 ERROR
> > > > [utils.component.ComponentContext]
> > > > > >> >> > > (Timer-1:null) Unhandled exception
> > > > > >> >> > > javax.naming.ConfigurationException: cluster node IP
should
> > > be
> > > > > >> valid
> > > > > >> >> > local
> > > > > >> >> > > address where the server is running, please check your
> > > > > >> configuration
> > > > > >> >> > > at
> > > > > >> >> > >
> > > > > >> >> > >
> > > > > >> >> >
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> >
com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> > > > > >> >> > > at
> > > > > >> >> > >
> > > > > >> >> > >
> > > > > >> >> >
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> >
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> > > > > >> >> > > at
> > > > > >> >> > >
> > > > > >> >>
> > > > > >>
> > > >
> > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > > > > >> >> > > at
java.util.TimerThread.mainLoop(Timer.java:555)
> > > > > >> >> > > at java.util.TimerThread.run(Timer.java:505)
> > > > > >> >> > >
> > > > > >> >> > > Just for starting MS I have to attach my laptop to a
> > network.
> > > > > >> Please
> > > > > >> >> > > suggest me a way where I can start MS without being
> > connected
> > > > to
> > > > > >> any
> > > > > >> >> > > network since I have a single host setup. I have tried
> > > bringing
> > > > > my
> > > > > >> >> > > interface up using 'ip link set eth0 up' but eth0
status is
> > > > > always
> > > > > >> >> DOWN
> > > > > >> >> > > unless I plug it into a network.
> > > > > >> >> > >
> > > > > >> >> > >
> > > > > >> >> > > Regards
> > > > > >> >> > > Karan Pugla
> > > > > >> >> > >
> > > > > >> >> >
> > > > > >> >>
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> > Rafael Weingartner
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Rafael Weingartner
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Rafael Weingartner
> > > >
> > >
> >
> >
> >
> > --
> > Rafael Weingartner
> >
--
Rafael Weingartner
Re: Management Server does not start when interface cable is unplugged.
Posted by "Karan ." <di...@gmail.com>.
Thank you so much Rafael. I changed cluster.node.IP to 127.0.0.1 in
db.properties and host in cloud.configuration and MS has started now.
Can you please explain when one should use interface ip in cluster.node.IP
? What difference it makes when one use 127.0.0.1 instead of real interface
ip ?
Regards
Karam Pugla
On Mon, Sep 30, 2013 at 2:22 AM, Rafael Weingartner <
rafaelweingartner@gmail.com> wrote:
> Ok, I got it.
> Even though the managed hosts are on the 192.162.1.0/24 network, you can
> still use the localhost as the parameter on CS.
> Since it is just used on CS for management purpose, specially when you have
> more than one CS Web server deployment.
>
>
> 2013/9/29 Karan . <di...@gmail.com>
>
> > I mean the hosts on which hypervisors are running. The cloudstack agents.
> >
> >
> > On Mon, Sep 30, 2013 at 2:15 AM, Rafael Weingartner <
> > rafaelweingartner@gmail.com> wrote:
> >
> > > what do you mean with "manage the agents in office lab"?
> > >
> > >
> > > 2013/9/29 Karan . <di...@gmail.com>
> > >
> > > > Thanks Rafael this is one possible solution. But this is the complete
> > > > scenario I am facing.
> > > > When I am at my office I use my laptop(which has MS and agent on it)
> > to
> > > > manage the agents in office lab. Now I want that when I am back at
> > home I
> > > > can still start the MS on my laptop and tinker around with
> cloudstack
> > > but
> > > > this time I am not connected to any network .
> > > >
> > > > The solution I can see here is that when I am at office I should
> set
> > > host
> > > > in cloud.configuration to 192.168.1.4 and at home I should set it to
> > > > 127.0.0.1 . right?
> > > >
> > > >
> > > > Regards
> > > >
> > > > Karan
> > > >
> > > >
> > > > On Mon, Sep 30, 2013 at 1:52 AM, Karan . <di...@gmail.com>
> > wrote:
> > > >
> > > > > 192.168.1.4 is my CS server ip and yes I can ping it. Currently, I
> > have
> > > > > only one machine in my setup and I have assigned this ip to it and
> I
> > > am
> > > > > running MS as well as agent over it.
> > > > > I would like to know how I can run CLOUDSTACK in a single node
> setup
> > > > > without being connected to any network and gateways.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
> > > > > rafaelweingartner@gmail.com> wrote:
> > > > >
> > > > >> better, what is the CS server ip address?
> > > > >>
> > > > >>
> > > > >> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
> > > > >>
> > > > >> > from the server that CS is running can you ping this address:
> > > > >> 192.168.1.4?
> > > > >> >
> > > > >> >
> > > > >> > 2013/9/29 Karan . <di...@gmail.com>
> > > > >> >
> > > > >> > Hi Marty,
> > > > >> >>
> > > > >> >> Interface already has static ip assigned to it. In fact, this
> is
> > > how
> > > > >> >> cloudstack has configured my /etc/network/interfaces
> > > > >> >>
> > > > >> >> auto lo
> > > > >> >> iface lo inet loopback
> > > > >> >>
> > > > >> >> auto eth0
> > > > >> >> iface eth0 inet manual
> > > > >> >>
> > > > >> >> auto cloudbr0
> > > > >> >> iface cloudbr0 inet static
> > > > >> >> bridge_ports eth0
> > > > >> >> address 192.168.1.4
> > > > >> >> netmask 255.255.255.0
> > > > >> >> gateway 192.168.1.1
> > > > >> >>
> > > > >> >> And this is the output for 'ip link '
> > > > >> >>
> > > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> > UNKNOWN
> > > > >> mode
> > > > >> >> DEFAULT
> > > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > pfifo_fast
> > > > >> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > noqueue
> > > > >> >> state DOWN mode DEFAULT
> > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > >> >>
> > > > >> >> And 'ip address'
> > > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> > UNKNOWN
> > > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > > >> >> inet 127.0.0.1/8 scope host lo
> > > > >> >> inet6 ::1/128 scope host
> > > > >> >> valid_lft forever preferred_lft forever
> > > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > pfifo_fast
> > > > >> >> master cloudbr0 state DOWN qlen 1000
> > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > > noqueue
> > > > >> >> state DOWN
> > > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > > >> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global
> cloudbr0
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >> Regards
> > > > >> >> Karan Pugla
> > > > >> >>
> > > > >> >>
> > > > >> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <
> > msweet.dev@gmail.com
> > > >
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >> > Hi Karan,
> > > > >> >> >
> > > > >> >> > Try assigning a static address to the interface then bring it
> > up
> > > > >> using
> > > > >> >> > ifup. This should in theory not close down the IP address
> once
> > > link
> > > > >> has
> > > > >> >> > been lost.
> > > > >> >> >
> > > > >> >> > Hope this helps,
> > > > >> >> > Marty
> > > > >> >> >
> > > > >> >> >
> > > > >> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <
> > digitalkaran@gmail.com
> > > >
> > > > >> >> wrote:
> > > > >> >> >
> > > > >> >> > > Hi
> > > > >> >> > >
> > > > >> >> > > I'll be giving a short demo on CLOUDSTACK in my
> organization
> > > and
> > > > >> for
> > > > >> >> > this
> > > > >> >> > > I have a very basic setup of Cloudstack 4.1.1 where I am
> > > using
> > > > >> one
> > > > >> >> > laptop
> > > > >> >> > > as management server as well as agent . Also, I am using
> > basic
> > > > >> >> > networking.
> > > > >> >> > > From logs I have observed that whenever my network cable is
> > > > >> >> unplugged, MS
> > > > >> >> > > doesn't start and throws following exception:
> > > > >> >> > >
> > > > >> >> > > 2013-09-29 23:09:09,693 INFO
> > > [cloud.cluster.ClusterManagerImpl]
> > > > >> >> > > (Timer-1:null) Start configuring cluster manager :
> > > > >> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> > > > >> >> > > 2013-09-29 23:09:09,753 INFO
> > > [cloud.cluster.ClusterManagerImpl]
> > > > >> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> > > > >> >> > > 2013-09-29 23:09:09,756 ERROR
> > > [utils.component.ComponentContext]
> > > > >> >> > > (Timer-1:null) Unhandled exception
> > > > >> >> > > javax.naming.ConfigurationException: cluster node IP should
> > be
> > > > >> valid
> > > > >> >> > local
> > > > >> >> > > address where the server is running, please check your
> > > > >> configuration
> > > > >> >> > > at
> > > > >> >> > >
> > > > >> >> > >
> > > > >> >> >
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> > > > >> >> > > at
> > > > >> >> > >
> > > > >> >> > >
> > > > >> >> >
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> > > > >> >> > > at
> > > > >> >> > >
> > > > >> >>
> > > > >>
> > >
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > > > >> >> > > at java.util.TimerThread.mainLoop(Timer.java:555)
> > > > >> >> > > at java.util.TimerThread.run(Timer.java:505)
> > > > >> >> > >
> > > > >> >> > > Just for starting MS I have to attach my laptop to a
> network.
> > > > >> Please
> > > > >> >> > > suggest me a way where I can start MS without being
> connected
> > > to
> > > > >> any
> > > > >> >> > > network since I have a single host setup. I have tried
> > bringing
> > > > my
> > > > >> >> > > interface up using 'ip link set eth0 up' but eth0 status is
> > > > always
> > > > >> >> DOWN
> > > > >> >> > > unless I plug it into a network.
> > > > >> >> > >
> > > > >> >> > >
> > > > >> >> > > Regards
> > > > >> >> > > Karan Pugla
> > > > >> >> > >
> > > > >> >> >
> > > > >> >>
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > Rafael Weingartner
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Rafael Weingartner
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Rafael Weingartner
> > >
> >
>
>
>
> --
> Rafael Weingartner
>
Re: Management Server does not start when interface cable is unplugged.
Posted by Rafael Weingartner <ra...@gmail.com>.
Ok, I got it.
Even though the managed hosts are on the 192.162.1.0/24 network, you can
still use the localhost as the parameter on CS.
Since it is just used on CS for management purpose, specially when you have
more than one CS Web server deployment.
2013/9/29 Karan . <di...@gmail.com>
> I mean the hosts on which hypervisors are running. The cloudstack agents.
>
>
> On Mon, Sep 30, 2013 at 2:15 AM, Rafael Weingartner <
> rafaelweingartner@gmail.com> wrote:
>
> > what do you mean with "manage the agents in office lab"?
> >
> >
> > 2013/9/29 Karan . <di...@gmail.com>
> >
> > > Thanks Rafael this is one possible solution. But this is the complete
> > > scenario I am facing.
> > > When I am at my office I use my laptop(which has MS and agent on it)
> to
> > > manage the agents in office lab. Now I want that when I am back at
> home I
> > > can still start the MS on my laptop and tinker around with cloudstack
> > but
> > > this time I am not connected to any network .
> > >
> > > The solution I can see here is that when I am at office I should set
> > host
> > > in cloud.configuration to 192.168.1.4 and at home I should set it to
> > > 127.0.0.1 . right?
> > >
> > >
> > > Regards
> > >
> > > Karan
> > >
> > >
> > > On Mon, Sep 30, 2013 at 1:52 AM, Karan . <di...@gmail.com>
> wrote:
> > >
> > > > 192.168.1.4 is my CS server ip and yes I can ping it. Currently, I
> have
> > > > only one machine in my setup and I have assigned this ip to it and I
> > am
> > > > running MS as well as agent over it.
> > > > I would like to know how I can run CLOUDSTACK in a single node setup
> > > > without being connected to any network and gateways.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
> > > > rafaelweingartner@gmail.com> wrote:
> > > >
> > > >> better, what is the CS server ip address?
> > > >>
> > > >>
> > > >> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
> > > >>
> > > >> > from the server that CS is running can you ping this address:
> > > >> 192.168.1.4?
> > > >> >
> > > >> >
> > > >> > 2013/9/29 Karan . <di...@gmail.com>
> > > >> >
> > > >> > Hi Marty,
> > > >> >>
> > > >> >> Interface already has static ip assigned to it. In fact, this is
> > how
> > > >> >> cloudstack has configured my /etc/network/interfaces
> > > >> >>
> > > >> >> auto lo
> > > >> >> iface lo inet loopback
> > > >> >>
> > > >> >> auto eth0
> > > >> >> iface eth0 inet manual
> > > >> >>
> > > >> >> auto cloudbr0
> > > >> >> iface cloudbr0 inet static
> > > >> >> bridge_ports eth0
> > > >> >> address 192.168.1.4
> > > >> >> netmask 255.255.255.0
> > > >> >> gateway 192.168.1.1
> > > >> >>
> > > >> >> And this is the output for 'ip link '
> > > >> >>
> > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> UNKNOWN
> > > >> mode
> > > >> >> DEFAULT
> > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > pfifo_fast
> > > >> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > noqueue
> > > >> >> state DOWN mode DEFAULT
> > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > >> >>
> > > >> >> And 'ip address'
> > > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> UNKNOWN
> > > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > > >> >> inet 127.0.0.1/8 scope host lo
> > > >> >> inet6 ::1/128 scope host
> > > >> >> valid_lft forever preferred_lft forever
> > > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > pfifo_fast
> > > >> >> master cloudbr0 state DOWN qlen 1000
> > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > > noqueue
> > > >> >> state DOWN
> > > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > > >> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >> Regards
> > > >> >> Karan Pugla
> > > >> >>
> > > >> >>
> > > >> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <
> msweet.dev@gmail.com
> > >
> > > >> >> wrote:
> > > >> >>
> > > >> >> > Hi Karan,
> > > >> >> >
> > > >> >> > Try assigning a static address to the interface then bring it
> up
> > > >> using
> > > >> >> > ifup. This should in theory not close down the IP address once
> > link
> > > >> has
> > > >> >> > been lost.
> > > >> >> >
> > > >> >> > Hope this helps,
> > > >> >> > Marty
> > > >> >> >
> > > >> >> >
> > > >> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <
> digitalkaran@gmail.com
> > >
> > > >> >> wrote:
> > > >> >> >
> > > >> >> > > Hi
> > > >> >> > >
> > > >> >> > > I'll be giving a short demo on CLOUDSTACK in my organization
> > and
> > > >> for
> > > >> >> > this
> > > >> >> > > I have a very basic setup of Cloudstack 4.1.1 where I am
> > using
> > > >> one
> > > >> >> > laptop
> > > >> >> > > as management server as well as agent . Also, I am using
> basic
> > > >> >> > networking.
> > > >> >> > > From logs I have observed that whenever my network cable is
> > > >> >> unplugged, MS
> > > >> >> > > doesn't start and throws following exception:
> > > >> >> > >
> > > >> >> > > 2013-09-29 23:09:09,693 INFO
> > [cloud.cluster.ClusterManagerImpl]
> > > >> >> > > (Timer-1:null) Start configuring cluster manager :
> > > >> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> > > >> >> > > 2013-09-29 23:09:09,753 INFO
> > [cloud.cluster.ClusterManagerImpl]
> > > >> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> > > >> >> > > 2013-09-29 23:09:09,756 ERROR
> > [utils.component.ComponentContext]
> > > >> >> > > (Timer-1:null) Unhandled exception
> > > >> >> > > javax.naming.ConfigurationException: cluster node IP should
> be
> > > >> valid
> > > >> >> > local
> > > >> >> > > address where the server is running, please check your
> > > >> configuration
> > > >> >> > > at
> > > >> >> > >
> > > >> >> > >
> > > >> >> >
> > > >> >>
> > > >>
> > >
> >
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> > > >> >> > > at
> > > >> >> > >
> > > >> >> > >
> > > >> >> >
> > > >> >>
> > > >>
> > >
> >
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> > > >> >> > > at
> > > >> >> > >
> > > >> >>
> > > >>
> > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > > >> >> > > at java.util.TimerThread.mainLoop(Timer.java:555)
> > > >> >> > > at java.util.TimerThread.run(Timer.java:505)
> > > >> >> > >
> > > >> >> > > Just for starting MS I have to attach my laptop to a network.
> > > >> Please
> > > >> >> > > suggest me a way where I can start MS without being connected
> > to
> > > >> any
> > > >> >> > > network since I have a single host setup. I have tried
> bringing
> > > my
> > > >> >> > > interface up using 'ip link set eth0 up' but eth0 status is
> > > always
> > > >> >> DOWN
> > > >> >> > > unless I plug it into a network.
> > > >> >> > >
> > > >> >> > >
> > > >> >> > > Regards
> > > >> >> > > Karan Pugla
> > > >> >> > >
> > > >> >> >
> > > >> >>
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Rafael Weingartner
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Rafael Weingartner
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Rafael Weingartner
> >
>
--
Rafael Weingartner
Re: Management Server does not start when interface cable is unplugged.
Posted by "Karan ." <di...@gmail.com>.
I mean the hosts on which hypervisors are running. The cloudstack agents.
On Mon, Sep 30, 2013 at 2:15 AM, Rafael Weingartner <
rafaelweingartner@gmail.com> wrote:
> what do you mean with "manage the agents in office lab"?
>
>
> 2013/9/29 Karan . <di...@gmail.com>
>
> > Thanks Rafael this is one possible solution. But this is the complete
> > scenario I am facing.
> > When I am at my office I use my laptop(which has MS and agent on it) to
> > manage the agents in office lab. Now I want that when I am back at home I
> > can still start the MS on my laptop and tinker around with cloudstack
> but
> > this time I am not connected to any network .
> >
> > The solution I can see here is that when I am at office I should set
> host
> > in cloud.configuration to 192.168.1.4 and at home I should set it to
> > 127.0.0.1 . right?
> >
> >
> > Regards
> >
> > Karan
> >
> >
> > On Mon, Sep 30, 2013 at 1:52 AM, Karan . <di...@gmail.com> wrote:
> >
> > > 192.168.1.4 is my CS server ip and yes I can ping it. Currently, I have
> > > only one machine in my setup and I have assigned this ip to it and I
> am
> > > running MS as well as agent over it.
> > > I would like to know how I can run CLOUDSTACK in a single node setup
> > > without being connected to any network and gateways.
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
> > > rafaelweingartner@gmail.com> wrote:
> > >
> > >> better, what is the CS server ip address?
> > >>
> > >>
> > >> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
> > >>
> > >> > from the server that CS is running can you ping this address:
> > >> 192.168.1.4?
> > >> >
> > >> >
> > >> > 2013/9/29 Karan . <di...@gmail.com>
> > >> >
> > >> > Hi Marty,
> > >> >>
> > >> >> Interface already has static ip assigned to it. In fact, this is
> how
> > >> >> cloudstack has configured my /etc/network/interfaces
> > >> >>
> > >> >> auto lo
> > >> >> iface lo inet loopback
> > >> >>
> > >> >> auto eth0
> > >> >> iface eth0 inet manual
> > >> >>
> > >> >> auto cloudbr0
> > >> >> iface cloudbr0 inet static
> > >> >> bridge_ports eth0
> > >> >> address 192.168.1.4
> > >> >> netmask 255.255.255.0
> > >> >> gateway 192.168.1.1
> > >> >>
> > >> >> And this is the output for 'ip link '
> > >> >>
> > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> > >> mode
> > >> >> DEFAULT
> > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > pfifo_fast
> > >> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > noqueue
> > >> >> state DOWN mode DEFAULT
> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > >> >>
> > >> >> And 'ip address'
> > >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> > >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > >> >> inet 127.0.0.1/8 scope host lo
> > >> >> inet6 ::1/128 scope host
> > >> >> valid_lft forever preferred_lft forever
> > >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > pfifo_fast
> > >> >> master cloudbr0 state DOWN qlen 1000
> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > noqueue
> > >> >> state DOWN
> > >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> > >> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
> > >> >>
> > >> >>
> > >> >>
> > >> >> Regards
> > >> >> Karan Pugla
> > >> >>
> > >> >>
> > >> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <msweet.dev@gmail.com
> >
> > >> >> wrote:
> > >> >>
> > >> >> > Hi Karan,
> > >> >> >
> > >> >> > Try assigning a static address to the interface then bring it up
> > >> using
> > >> >> > ifup. This should in theory not close down the IP address once
> link
> > >> has
> > >> >> > been lost.
> > >> >> >
> > >> >> > Hope this helps,
> > >> >> > Marty
> > >> >> >
> > >> >> >
> > >> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <digitalkaran@gmail.com
> >
> > >> >> wrote:
> > >> >> >
> > >> >> > > Hi
> > >> >> > >
> > >> >> > > I'll be giving a short demo on CLOUDSTACK in my organization
> and
> > >> for
> > >> >> > this
> > >> >> > > I have a very basic setup of Cloudstack 4.1.1 where I am
> using
> > >> one
> > >> >> > laptop
> > >> >> > > as management server as well as agent . Also, I am using basic
> > >> >> > networking.
> > >> >> > > From logs I have observed that whenever my network cable is
> > >> >> unplugged, MS
> > >> >> > > doesn't start and throws following exception:
> > >> >> > >
> > >> >> > > 2013-09-29 23:09:09,693 INFO
> [cloud.cluster.ClusterManagerImpl]
> > >> >> > > (Timer-1:null) Start configuring cluster manager :
> > >> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> > >> >> > > 2013-09-29 23:09:09,753 INFO
> [cloud.cluster.ClusterManagerImpl]
> > >> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> > >> >> > > 2013-09-29 23:09:09,756 ERROR
> [utils.component.ComponentContext]
> > >> >> > > (Timer-1:null) Unhandled exception
> > >> >> > > javax.naming.ConfigurationException: cluster node IP should be
> > >> valid
> > >> >> > local
> > >> >> > > address where the server is running, please check your
> > >> configuration
> > >> >> > > at
> > >> >> > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >>
> >
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> > >> >> > > at
> > >> >> > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >>
> >
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> > >> >> > > at
> > >> >> > >
> > >> >>
> > >>
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > >> >> > > at java.util.TimerThread.mainLoop(Timer.java:555)
> > >> >> > > at java.util.TimerThread.run(Timer.java:505)
> > >> >> > >
> > >> >> > > Just for starting MS I have to attach my laptop to a network.
> > >> Please
> > >> >> > > suggest me a way where I can start MS without being connected
> to
> > >> any
> > >> >> > > network since I have a single host setup. I have tried bringing
> > my
> > >> >> > > interface up using 'ip link set eth0 up' but eth0 status is
> > always
> > >> >> DOWN
> > >> >> > > unless I plug it into a network.
> > >> >> > >
> > >> >> > >
> > >> >> > > Regards
> > >> >> > > Karan Pugla
> > >> >> > >
> > >> >> >
> > >> >>
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Rafael Weingartner
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Rafael Weingartner
> > >>
> > >
> > >
> >
>
>
>
> --
> Rafael Weingartner
>
Re: Management Server does not start when interface cable is unplugged.
Posted by Rafael Weingartner <ra...@gmail.com>.
what do you mean with "manage the agents in office lab"?
2013/9/29 Karan . <di...@gmail.com>
> Thanks Rafael this is one possible solution. But this is the complete
> scenario I am facing.
> When I am at my office I use my laptop(which has MS and agent on it) to
> manage the agents in office lab. Now I want that when I am back at home I
> can still start the MS on my laptop and tinker around with cloudstack but
> this time I am not connected to any network .
>
> The solution I can see here is that when I am at office I should set host
> in cloud.configuration to 192.168.1.4 and at home I should set it to
> 127.0.0.1 . right?
>
>
> Regards
>
> Karan
>
>
> On Mon, Sep 30, 2013 at 1:52 AM, Karan . <di...@gmail.com> wrote:
>
> > 192.168.1.4 is my CS server ip and yes I can ping it. Currently, I have
> > only one machine in my setup and I have assigned this ip to it and I am
> > running MS as well as agent over it.
> > I would like to know how I can run CLOUDSTACK in a single node setup
> > without being connected to any network and gateways.
> >
> >
> >
> >
> >
> > On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
> > rafaelweingartner@gmail.com> wrote:
> >
> >> better, what is the CS server ip address?
> >>
> >>
> >> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
> >>
> >> > from the server that CS is running can you ping this address:
> >> 192.168.1.4?
> >> >
> >> >
> >> > 2013/9/29 Karan . <di...@gmail.com>
> >> >
> >> > Hi Marty,
> >> >>
> >> >> Interface already has static ip assigned to it. In fact, this is how
> >> >> cloudstack has configured my /etc/network/interfaces
> >> >>
> >> >> auto lo
> >> >> iface lo inet loopback
> >> >>
> >> >> auto eth0
> >> >> iface eth0 inet manual
> >> >>
> >> >> auto cloudbr0
> >> >> iface cloudbr0 inet static
> >> >> bridge_ports eth0
> >> >> address 192.168.1.4
> >> >> netmask 255.255.255.0
> >> >> gateway 192.168.1.1
> >> >>
> >> >> And this is the output for 'ip link '
> >> >>
> >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> >> mode
> >> >> DEFAULT
> >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> pfifo_fast
> >> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> noqueue
> >> >> state DOWN mode DEFAULT
> >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >> >>
> >> >> And 'ip address'
> >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >> >> inet 127.0.0.1/8 scope host lo
> >> >> inet6 ::1/128 scope host
> >> >> valid_lft forever preferred_lft forever
> >> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> pfifo_fast
> >> >> master cloudbr0 state DOWN qlen 1000
> >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> noqueue
> >> >> state DOWN
> >> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
> >> >>
> >> >>
> >> >>
> >> >> Regards
> >> >> Karan Pugla
> >> >>
> >> >>
> >> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <ms...@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > Hi Karan,
> >> >> >
> >> >> > Try assigning a static address to the interface then bring it up
> >> using
> >> >> > ifup. This should in theory not close down the IP address once link
> >> has
> >> >> > been lost.
> >> >> >
> >> >> > Hope this helps,
> >> >> > Marty
> >> >> >
> >> >> >
> >> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <di...@gmail.com>
> >> >> wrote:
> >> >> >
> >> >> > > Hi
> >> >> > >
> >> >> > > I'll be giving a short demo on CLOUDSTACK in my organization and
> >> for
> >> >> > this
> >> >> > > I have a very basic setup of Cloudstack 4.1.1 where I am using
> >> one
> >> >> > laptop
> >> >> > > as management server as well as agent . Also, I am using basic
> >> >> > networking.
> >> >> > > From logs I have observed that whenever my network cable is
> >> >> unplugged, MS
> >> >> > > doesn't start and throws following exception:
> >> >> > >
> >> >> > > 2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
> >> >> > > (Timer-1:null) Start configuring cluster manager :
> >> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> >> >> > > 2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
> >> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> >> >> > > 2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
> >> >> > > (Timer-1:null) Unhandled exception
> >> >> > > javax.naming.ConfigurationException: cluster node IP should be
> >> valid
> >> >> > local
> >> >> > > address where the server is running, please check your
> >> configuration
> >> >> > > at
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >>
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> >> >> > > at
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >>
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> >> >> > > at
> >> >> > >
> >> >>
> >> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> >> >> > > at java.util.TimerThread.mainLoop(Timer.java:555)
> >> >> > > at java.util.TimerThread.run(Timer.java:505)
> >> >> > >
> >> >> > > Just for starting MS I have to attach my laptop to a network.
> >> Please
> >> >> > > suggest me a way where I can start MS without being connected to
> >> any
> >> >> > > network since I have a single host setup. I have tried bringing
> my
> >> >> > > interface up using 'ip link set eth0 up' but eth0 status is
> always
> >> >> DOWN
> >> >> > > unless I plug it into a network.
> >> >> > >
> >> >> > >
> >> >> > > Regards
> >> >> > > Karan Pugla
> >> >> > >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Rafael Weingartner
> >> >
> >>
> >>
> >>
> >> --
> >> Rafael Weingartner
> >>
> >
> >
>
--
Rafael Weingartner
Re: Management Server does not start when interface cable is unplugged.
Posted by "Karan ." <di...@gmail.com>.
Thanks Rafael this is one possible solution. But this is the complete
scenario I am facing.
When I am at my office I use my laptop(which has MS and agent on it) to
manage the agents in office lab. Now I want that when I am back at home I
can still start the MS on my laptop and tinker around with cloudstack but
this time I am not connected to any network .
The solution I can see here is that when I am at office I should set host
in cloud.configuration to 192.168.1.4 and at home I should set it to
127.0.0.1 . right?
Regards
Karan
On Mon, Sep 30, 2013 at 1:52 AM, Karan . <di...@gmail.com> wrote:
> 192.168.1.4 is my CS server ip and yes I can ping it. Currently, I have
> only one machine in my setup and I have assigned this ip to it and I am
> running MS as well as agent over it.
> I would like to know how I can run CLOUDSTACK in a single node setup
> without being connected to any network and gateways.
>
>
>
>
>
> On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
> rafaelweingartner@gmail.com> wrote:
>
>> better, what is the CS server ip address?
>>
>>
>> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
>>
>> > from the server that CS is running can you ping this address:
>> 192.168.1.4?
>> >
>> >
>> > 2013/9/29 Karan . <di...@gmail.com>
>> >
>> > Hi Marty,
>> >>
>> >> Interface already has static ip assigned to it. In fact, this is how
>> >> cloudstack has configured my /etc/network/interfaces
>> >>
>> >> auto lo
>> >> iface lo inet loopback
>> >>
>> >> auto eth0
>> >> iface eth0 inet manual
>> >>
>> >> auto cloudbr0
>> >> iface cloudbr0 inet static
>> >> bridge_ports eth0
>> >> address 192.168.1.4
>> >> netmask 255.255.255.0
>> >> gateway 192.168.1.1
>> >>
>> >> And this is the output for 'ip link '
>> >>
>> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>> mode
>> >> DEFAULT
>> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
>> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
>> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>> >> state DOWN mode DEFAULT
>> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> >>
>> >> And 'ip address'
>> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> >> inet 127.0.0.1/8 scope host lo
>> >> inet6 ::1/128 scope host
>> >> valid_lft forever preferred_lft forever
>> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
>> >> master cloudbr0 state DOWN qlen 1000
>> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>> >> state DOWN
>> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
>> >>
>> >>
>> >>
>> >> Regards
>> >> Karan Pugla
>> >>
>> >>
>> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <ms...@gmail.com>
>> >> wrote:
>> >>
>> >> > Hi Karan,
>> >> >
>> >> > Try assigning a static address to the interface then bring it up
>> using
>> >> > ifup. This should in theory not close down the IP address once link
>> has
>> >> > been lost.
>> >> >
>> >> > Hope this helps,
>> >> > Marty
>> >> >
>> >> >
>> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <di...@gmail.com>
>> >> wrote:
>> >> >
>> >> > > Hi
>> >> > >
>> >> > > I'll be giving a short demo on CLOUDSTACK in my organization and
>> for
>> >> > this
>> >> > > I have a very basic setup of Cloudstack 4.1.1 where I am using
>> one
>> >> > laptop
>> >> > > as management server as well as agent . Also, I am using basic
>> >> > networking.
>> >> > > From logs I have observed that whenever my network cable is
>> >> unplugged, MS
>> >> > > doesn't start and throws following exception:
>> >> > >
>> >> > > 2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
>> >> > > (Timer-1:null) Start configuring cluster manager :
>> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
>> >> > > 2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
>> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
>> >> > > 2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
>> >> > > (Timer-1:null) Unhandled exception
>> >> > > javax.naming.ConfigurationException: cluster node IP should be
>> valid
>> >> > local
>> >> > > address where the server is running, please check your
>> configuration
>> >> > > at
>> >> > >
>> >> > >
>> >> >
>> >>
>> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
>> >> > > at
>> >> > >
>> >> > >
>> >> >
>> >>
>> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>> >> > > at
>> >> > >
>> >>
>> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
>> >> > > at java.util.TimerThread.mainLoop(Timer.java:555)
>> >> > > at java.util.TimerThread.run(Timer.java:505)
>> >> > >
>> >> > > Just for starting MS I have to attach my laptop to a network.
>> Please
>> >> > > suggest me a way where I can start MS without being connected to
>> any
>> >> > > network since I have a single host setup. I have tried bringing my
>> >> > > interface up using 'ip link set eth0 up' but eth0 status is always
>> >> DOWN
>> >> > > unless I plug it into a network.
>> >> > >
>> >> > >
>> >> > > Regards
>> >> > > Karan Pugla
>> >> > >
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Rafael Weingartner
>> >
>>
>>
>>
>> --
>> Rafael Weingartner
>>
>
>
Re: Management Server does not start when interface cable is unplugged.
Posted by "Karan ." <di...@gmail.com>.
192.168.1.4 is my CS server ip and yes I can ping it. Currently, I have
only one machine in my setup and I have assigned this ip to it and I am
running MS as well as agent over it.
I would like to know how I can run CLOUDSTACK in a single node setup
without being connected to any network and gateways.
On Mon, Sep 30, 2013 at 1:40 AM, Rafael Weingartner <
rafaelweingartner@gmail.com> wrote:
> better, what is the CS server ip address?
>
>
> 2013/9/29 Rafael Weingartner <ra...@gmail.com>
>
> > from the server that CS is running can you ping this address:
> 192.168.1.4?
> >
> >
> > 2013/9/29 Karan . <di...@gmail.com>
> >
> > Hi Marty,
> >>
> >> Interface already has static ip assigned to it. In fact, this is how
> >> cloudstack has configured my /etc/network/interfaces
> >>
> >> auto lo
> >> iface lo inet loopback
> >>
> >> auto eth0
> >> iface eth0 inet manual
> >>
> >> auto cloudbr0
> >> iface cloudbr0 inet static
> >> bridge_ports eth0
> >> address 192.168.1.4
> >> netmask 255.255.255.0
> >> gateway 192.168.1.1
> >>
> >> And this is the output for 'ip link '
> >>
> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
> >> DEFAULT
> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> >> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> >> state DOWN mode DEFAULT
> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >>
> >> And 'ip address'
> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >> inet 127.0.0.1/8 scope host lo
> >> inet6 ::1/128 scope host
> >> valid_lft forever preferred_lft forever
> >> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> >> master cloudbr0 state DOWN qlen 1000
> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> >> state DOWN
> >> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> >> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
> >>
> >>
> >>
> >> Regards
> >> Karan Pugla
> >>
> >>
> >> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <ms...@gmail.com>
> >> wrote:
> >>
> >> > Hi Karan,
> >> >
> >> > Try assigning a static address to the interface then bring it up using
> >> > ifup. This should in theory not close down the IP address once link
> has
> >> > been lost.
> >> >
> >> > Hope this helps,
> >> > Marty
> >> >
> >> >
> >> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <di...@gmail.com>
> >> wrote:
> >> >
> >> > > Hi
> >> > >
> >> > > I'll be giving a short demo on CLOUDSTACK in my organization and
> for
> >> > this
> >> > > I have a very basic setup of Cloudstack 4.1.1 where I am using one
> >> > laptop
> >> > > as management server as well as agent . Also, I am using basic
> >> > networking.
> >> > > From logs I have observed that whenever my network cable is
> >> unplugged, MS
> >> > > doesn't start and throws following exception:
> >> > >
> >> > > 2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
> >> > > (Timer-1:null) Start configuring cluster manager :
> >> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> >> > > 2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
> >> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> >> > > 2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
> >> > > (Timer-1:null) Unhandled exception
> >> > > javax.naming.ConfigurationException: cluster node IP should be valid
> >> > local
> >> > > address where the server is running, please check your configuration
> >> > > at
> >> > >
> >> > >
> >> >
> >>
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> >> > > at
> >> > >
> >> > >
> >> >
> >>
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> >> > > at
> >> > >
> >> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> >> > > at java.util.TimerThread.mainLoop(Timer.java:555)
> >> > > at java.util.TimerThread.run(Timer.java:505)
> >> > >
> >> > > Just for starting MS I have to attach my laptop to a network. Please
> >> > > suggest me a way where I can start MS without being connected to any
> >> > > network since I have a single host setup. I have tried bringing my
> >> > > interface up using 'ip link set eth0 up' but eth0 status is always
> >> DOWN
> >> > > unless I plug it into a network.
> >> > >
> >> > >
> >> > > Regards
> >> > > Karan Pugla
> >> > >
> >> >
> >>
> >
> >
> >
> > --
> > Rafael Weingartner
> >
>
>
>
> --
> Rafael Weingartner
>
Re: Management Server does not start when interface cable is unplugged.
Posted by Rafael Weingartner <ra...@gmail.com>.
Sorry, I haven't read the bottom of your email.
But, I believe that when you setup the cloudstack database with the command:
"cloudstack-setup-databases"
you could use th -i flag with a value like localhost or 127.0.0.1 then you
should not have problems.
Or if you do not wantto configure everything again, you can access the
database that CS has setup and then you could change the parameter called
host on table cloud.configuration to 127.0.0.1, then you should not have
problems.
Re: Management Server does not start when interface cable is unplugged.
Posted by Rafael Weingartner <ra...@gmail.com>.
better, what is the CS server ip address?
2013/9/29 Rafael Weingartner <ra...@gmail.com>
> from the server that CS is running can you ping this address: 192.168.1.4?
>
>
> 2013/9/29 Karan . <di...@gmail.com>
>
> Hi Marty,
>>
>> Interface already has static ip assigned to it. In fact, this is how
>> cloudstack has configured my /etc/network/interfaces
>>
>> auto lo
>> iface lo inet loopback
>>
>> auto eth0
>> iface eth0 inet manual
>>
>> auto cloudbr0
>> iface cloudbr0 inet static
>> bridge_ports eth0
>> address 192.168.1.4
>> netmask 255.255.255.0
>> gateway 192.168.1.1
>>
>> And this is the output for 'ip link '
>>
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
>> DEFAULT
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
>> master cloudbr0 state DOWN mode DEFAULT qlen 1000
>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>> state DOWN mode DEFAULT
>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>>
>> And 'ip address'
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 scope host lo
>> inet6 ::1/128 scope host
>> valid_lft forever preferred_lft forever
>> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
>> master cloudbr0 state DOWN qlen 1000
>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>> state DOWN
>> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
>>
>>
>>
>> Regards
>> Karan Pugla
>>
>>
>> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <ms...@gmail.com>
>> wrote:
>>
>> > Hi Karan,
>> >
>> > Try assigning a static address to the interface then bring it up using
>> > ifup. This should in theory not close down the IP address once link has
>> > been lost.
>> >
>> > Hope this helps,
>> > Marty
>> >
>> >
>> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <di...@gmail.com>
>> wrote:
>> >
>> > > Hi
>> > >
>> > > I'll be giving a short demo on CLOUDSTACK in my organization and for
>> > this
>> > > I have a very basic setup of Cloudstack 4.1.1 where I am using one
>> > laptop
>> > > as management server as well as agent . Also, I am using basic
>> > networking.
>> > > From logs I have observed that whenever my network cable is
>> unplugged, MS
>> > > doesn't start and throws following exception:
>> > >
>> > > 2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
>> > > (Timer-1:null) Start configuring cluster manager :
>> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
>> > > 2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
>> > > (Timer-1:null) Cluster node IP : 192.168.1.4
>> > > 2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
>> > > (Timer-1:null) Unhandled exception
>> > > javax.naming.ConfigurationException: cluster node IP should be valid
>> > local
>> > > address where the server is running, please check your configuration
>> > > at
>> > >
>> > >
>> >
>> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
>> > > at
>> > >
>> > >
>> >
>> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>> > > at
>> > >
>> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
>> > > at java.util.TimerThread.mainLoop(Timer.java:555)
>> > > at java.util.TimerThread.run(Timer.java:505)
>> > >
>> > > Just for starting MS I have to attach my laptop to a network. Please
>> > > suggest me a way where I can start MS without being connected to any
>> > > network since I have a single host setup. I have tried bringing my
>> > > interface up using 'ip link set eth0 up' but eth0 status is always
>> DOWN
>> > > unless I plug it into a network.
>> > >
>> > >
>> > > Regards
>> > > Karan Pugla
>> > >
>> >
>>
>
>
>
> --
> Rafael Weingartner
>
--
Rafael Weingartner
Re: Management Server does not start when interface cable is unplugged.
Posted by Rafael Weingartner <ra...@gmail.com>.
from the server that CS is running can you ping this address: 192.168.1.4?
2013/9/29 Karan . <di...@gmail.com>
> Hi Marty,
>
> Interface already has static ip assigned to it. In fact, this is how
> cloudstack has configured my /etc/network/interfaces
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet manual
>
> auto cloudbr0
> iface cloudbr0 inet static
> bridge_ports eth0
> address 192.168.1.4
> netmask 255.255.255.0
> gateway 192.168.1.1
>
> And this is the output for 'ip link '
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
> DEFAULT
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> master cloudbr0 state DOWN mode DEFAULT qlen 1000
> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> state DOWN mode DEFAULT
> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
>
> And 'ip address'
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> master cloudbr0 state DOWN qlen 1000
> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> 3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> state DOWN
> link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
>
>
>
> Regards
> Karan Pugla
>
>
> On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <ms...@gmail.com> wrote:
>
> > Hi Karan,
> >
> > Try assigning a static address to the interface then bring it up using
> > ifup. This should in theory not close down the IP address once link has
> > been lost.
> >
> > Hope this helps,
> > Marty
> >
> >
> > On Sun, Sep 29, 2013 at 7:41 PM, Karan . <di...@gmail.com> wrote:
> >
> > > Hi
> > >
> > > I'll be giving a short demo on CLOUDSTACK in my organization and for
> > this
> > > I have a very basic setup of Cloudstack 4.1.1 where I am using one
> > laptop
> > > as management server as well as agent . Also, I am using basic
> > networking.
> > > From logs I have observed that whenever my network cable is unplugged,
> MS
> > > doesn't start and throws following exception:
> > >
> > > 2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
> > > (Timer-1:null) Start configuring cluster manager :
> > > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> > > 2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
> > > (Timer-1:null) Cluster node IP : 192.168.1.4
> > > 2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
> > > (Timer-1:null) Unhandled exception
> > > javax.naming.ConfigurationException: cluster node IP should be valid
> > local
> > > address where the server is running, please check your configuration
> > > at
> > >
> > >
> >
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> > > at
> > >
> > >
> >
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> > > at
> > >
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > > at java.util.TimerThread.mainLoop(Timer.java:555)
> > > at java.util.TimerThread.run(Timer.java:505)
> > >
> > > Just for starting MS I have to attach my laptop to a network. Please
> > > suggest me a way where I can start MS without being connected to any
> > > network since I have a single host setup. I have tried bringing my
> > > interface up using 'ip link set eth0 up' but eth0 status is always DOWN
> > > unless I plug it into a network.
> > >
> > >
> > > Regards
> > > Karan Pugla
> > >
> >
>
--
Rafael Weingartner
Re: Management Server does not start when interface cable is unplugged.
Posted by "Karan ." <di...@gmail.com>.
Hi Marty,
Interface already has static ip assigned to it. In fact, this is how
cloudstack has configured my /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto cloudbr0
iface cloudbr0 inet static
bridge_ports eth0
address 192.168.1.4
netmask 255.255.255.0
gateway 192.168.1.1
And this is the output for 'ip link '
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
master cloudbr0 state DOWN mode DEFAULT qlen 1000
link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN mode DEFAULT
link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
And 'ip address'
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
master cloudbr0 state DOWN qlen 1000
link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
3: cloudbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN
link/ether 28:92:4a:1e:f1:37 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.4/24 brd 192.168.1.255 scope global cloudbr0
Regards
Karan Pugla
On Mon, Sep 30, 2013 at 1:23 AM, Marty Sweet <ms...@gmail.com> wrote:
> Hi Karan,
>
> Try assigning a static address to the interface then bring it up using
> ifup. This should in theory not close down the IP address once link has
> been lost.
>
> Hope this helps,
> Marty
>
>
> On Sun, Sep 29, 2013 at 7:41 PM, Karan . <di...@gmail.com> wrote:
>
> > Hi
> >
> > I'll be giving a short demo on CLOUDSTACK in my organization and for
> this
> > I have a very basic setup of Cloudstack 4.1.1 where I am using one
> laptop
> > as management server as well as agent . Also, I am using basic
> networking.
> > From logs I have observed that whenever my network cable is unplugged, MS
> > doesn't start and throws following exception:
> >
> > 2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
> > (Timer-1:null) Start configuring cluster manager :
> > ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> > 2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
> > (Timer-1:null) Cluster node IP : 192.168.1.4
> > 2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
> > (Timer-1:null) Unhandled exception
> > javax.naming.ConfigurationException: cluster node IP should be valid
> local
> > address where the server is running, please check your configuration
> > at
> >
> >
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> > at
> >
> >
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> > at
> > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> > at java.util.TimerThread.mainLoop(Timer.java:555)
> > at java.util.TimerThread.run(Timer.java:505)
> >
> > Just for starting MS I have to attach my laptop to a network. Please
> > suggest me a way where I can start MS without being connected to any
> > network since I have a single host setup. I have tried bringing my
> > interface up using 'ip link set eth0 up' but eth0 status is always DOWN
> > unless I plug it into a network.
> >
> >
> > Regards
> > Karan Pugla
> >
>
Re: Management Server does not start when interface cable is unplugged.
Posted by Marty Sweet <ms...@gmail.com>.
Hi Karan,
Try assigning a static address to the interface then bring it up using
ifup. This should in theory not close down the IP address once link has
been lost.
Hope this helps,
Marty
On Sun, Sep 29, 2013 at 7:41 PM, Karan . <di...@gmail.com> wrote:
> Hi
>
> I'll be giving a short demo on CLOUDSTACK in my organization and for this
> I have a very basic setup of Cloudstack 4.1.1 where I am using one laptop
> as management server as well as agent . Also, I am using basic networking.
> From logs I have observed that whenever my network cable is unplugged, MS
> doesn't start and throws following exception:
>
> 2013-09-29 23:09:09,693 INFO [cloud.cluster.ClusterManagerImpl]
> (Timer-1:null) Start configuring cluster manager :
> ClusterManagerImpl_EnhancerByCloudStack_d07fda90
> 2013-09-29 23:09:09,753 INFO [cloud.cluster.ClusterManagerImpl]
> (Timer-1:null) Cluster node IP : 192.168.1.4
> 2013-09-29 23:09:09,756 ERROR [utils.component.ComponentContext]
> (Timer-1:null) Unhandled exception
> javax.naming.ConfigurationException: cluster node IP should be valid local
> address where the server is running, please check your configuration
> at
>
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1319)
> at
>
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
> at
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
>
> Just for starting MS I have to attach my laptop to a network. Please
> suggest me a way where I can start MS without being connected to any
> network since I have a single host setup. I have tried bringing my
> interface up using 'ip link set eth0 up' but eth0 status is always DOWN
> unless I plug it into a network.
>
>
> Regards
> Karan Pugla
>