OpenVZ Forum: Support » Services inside container very slow to start

Home » General » Support » Services inside container very slow to start

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Services inside container very slow to start [message #35620]

Wed, 08 April 2009 19:58

kiddbios
Messages: 6
Registered: March 2009

Junior Member

Anybody have any idea why services within a container would be very slow to autostart. When we start VZ the container comes up very quickly and allows us to go into it. However, the services take a long time to actually start loading. When we start the services individually they come right up, maybe 10-20 seconds. When the services auto-start from bringing up a container it takes them 5 minutes or more. There are 3 services in question: Httpd, MySQL and Asterisk.

[Updated on: Wed, 08 April 2009 20:00]

Report message to a moderator

Re: Services inside container very slow to start [message #35738 is a reply to message #35620]

Mon, 20 April 2009 06:52

bbhenry
Messages: 17
Registered: February 2009

Junior Member

I have the same issue.

I see you talked about http, mysql and Asterisk. Seems like we are trying to achieve similar tasks here. I have migrated a PBX in a flash to VE. And I found from /var/log/messages , once the xinetd started, it took another 3 minutes to finish all other service at boot. What's going on? I actually have 2 different HN, the one with ubuntu server has this problem . But the one with a CentOS HN don't have this issue, everything start right at the same minute.

Here is the log for the VE that runs on the Ubuntu(Debian) Hardware Node:

Apr 19 23:30:30 piaf xinetd[590]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
Apr 19 23:30:30 piaf xinetd[590]: Started working: 1 available service
Apr 19 23:33:49 piaf init: no more processes left in this runlevel

Here is the log for the VE that runs on the CentOS hardware Node:

Apr 19 23:20:36 piaf xinetd[3524]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
Apr 19 23:20:36 piaf xinetd[3524]: Started working: 1 available service
Apr 19 23:20:52 piaf init: no more processes left in this runlevel

Any other thing or service that could be causing the slow down? or is there something we need to change in xinetd's config file? By the way, the kernel version on Ubuntu is 2.6.24-23-openvz.

Report message to a moderator