Starting node takes 10 minutes... before boot

R

rethus

Active Member
Feb 13, 2010
49
0
26
If I reboot proxmox, all nodes come up really fast as it should.

But one Node need 10 Minutes before it begin to boot.

I start the VM 105 and open the VNC-Viewer on it. Screen keeps Black for 10 Minutes. After 10 Minutes I see the Boot-Process starting in VNC.

Why are there such a delay?

Proxmox: 3.4-15
Node 105: Openvz
Node OS: Debian Linux
 
I do a restart (of whole Master) via GUI.
There are no nfs-mounts on this node (105).
But anyway, the VNC-Screen keeps black for node 105 till 10 Minutes are reached. Only after this time, the boot-process start... so even if there would be a nfs-mount on node 105, the lag apper before this.

you know what I mean... it's hard to explain :)
 
Starting container ...
Container is mounted
Adding IP address(es): 112.12.23.345
Setting CPU units: 400000
Setting CPUs: 4
Container start in progress...​

Starts up in 30 - 50 Seconds
 
What is happening on the command line at that time? Please run ps auxf after the start and run it e.g. every 5 seconds and post all tree entried below your VMID in question. This should look like this:

Code: 
root      7847  0.0  0.0  38664  1416 ?        Ss   Jul30  15:17 [lxc monitor] /var/lib/lxc 1007
root      7925  0.0  0.0  15492   840 ?        Ss   Jul30   2:04  \_ init [2]
root      8855  0.0  0.0 258672  1404 ?        Ssl  Jul30   0:07      \_ /usr/sbin/rsyslogd
root      8929  0.0  0.0  25904  1560 ?        Ss   Jul30   0:18      \_ /usr/sbin/cron
root      9071  0.0  0.0  36168  2352 ?        Ss   Jul30   0:46      \_ /usr/lib/postfix/master
systemd+  9081  0.0  0.0  38280  2376 ?        S    Jul30   0:14      |   \_ qmgr -l -t unix -u
systemd+ 24356  0.0  0.0  38232  3360 ?        S    20:10   0:00      |   \_ pickup -l -t unix -u -c
root      9097  0.0  0.0  12664  1356 pts/0    Ss+  Jul30   0:00      \_ /sbin/getty --noclear 38400 tty1
root      9098  0.0  0.0  12664  1436 pts/1    Ss+  Jul30   0:00      \_ /sbin/getty --noclear 38400 tty2
root     29936  0.0  0.0  55184  1260 ?        Ss   Jul30   0:00      \_ /usr/sbin/sshd
root     19147  0.0  0.4 397872 25184 ?        Ss   Jul31   5:35      \_ /usr/sbin/apache2 -k start
www-data 24183  0.0  0.1 397904  9280 ?        S    07:29   0:00          \_ /usr/sbin/apache2 -k start
www-data 24184  0.0  0.1 397904  9280 ?        S    07:29   0:00          \_ /usr/sbin/apache2 -k start
www-data 24185  0.0  0.1 397904  9280 ?        S    07:29   0:00          \_ /usr/sbin/apache2 -k start
www-data 24186  0.0  0.1 397904  9280 ?        S    07:29   0:00          \_ /usr/sbin/apache2 -k start
www-data 24187  0.0  0.1 397904  9280 ?        S    07:29   0:00          \_ /usr/sbin/apache2 -k start

Most of the time it is some strange service taking ages due to some DNS or other network problems.
 
You must log in or register to reply here.
Top Bottom