Hi everybody, some days ago I installed Openvz on a Fedora Core 4 box. Also, i installed Suse 9.3 and copied the whole image into the private-server-area on the server. Yet, the server works, BUT: ALL services (including network and ssh - who needs em don´t BOOT automatic. While watching Yast, all init-scripts should boot while starting the server. What´s wrong :-< ? After doing a /etc/init.d/network start and a /etc/init.d/ssh start, server is reachable from outside well . Also, the server hangs off if you do a vzctl stop vpsnumber. Seems to be a big problem with the start/stop scripts. Any ideas? If we could fix this problem up, i could test it and then would give anyone the sources so that everybody could install 9.3 Suse on its own. Thanks, Regards, Ronny
(1) Stop can be easily fixed by commenting out this line in /etc/init.d/halt: test -n "$REDIRECT" && exec 0<> $REDIRECT 1>&0 2>&0 I.e. you should put # as a first character of this line, or just remove it from /etc/init.d/halt. (2) Can you check what /sbin/chkconfig --add sshd tells you?
Hi Kir, [root@localhost ~]# vzctl enter 110 entered into VPS 110 localhost:/ # /sbin/chkconfig --add sshd insserv: Service boot.localfs has to be enabled for service sshd insserv: exiting now! /sbin/insserv failed, exit code 1 sshd 0:off 1:off 2:off 3:on 4:off 5:on 6:off localhost:/ # ? Thanks Ronny
I re-installed my image, localhost:/ # /sbin/chkconfig --add sshd sshd 0:off 1:off 2:off 3:on 4:off 5:on 6:off localhost:/ # all fine here, but still no ssh / network working after vps start :-< Thanks Ronny
Is /sbin/chkconfig --add network tells it's OK (enabled)? If no, enable the boot stuff it needs, recursively If yes, check what your /var/log/messages (the one inside a VPS) has to say about networking and sshd.
Hi localhost:/ # /sbin/chkconfig --add network network 0:off 1:off 2:on 3:on 4:off 5:on 6:off localhost:/ # Is ok, too. I will check my logs now
Strange messages: Jan 16 17:24:19 localhost init: Switching to runlevel: 6 (only from reboot) :-< Only running things after reboot / start vps are: localhost:/var/log # ps ax PID TTY STAT TIME COMMAND 1 ? Ss 0:00 init 6811 ? Ss 0:00 vzctl: pts/0 7836 pts/0 Ss 0:00 bash --login -i 7899 pts/0 R+ 0:00 ps ax :-< ? Thanks Ronny
Seems all ok, but don´t work. Looks like Suse doesn´t get the "runlevel" ? localhost:/var/log # /sbin/chkconfig Makefile off SuSEfirewall2_init off SuSEfirewall2_setup off acpid off alsasound on atd off autoyast off boot.cleanup on boot.clock on boot.coldplug on boot.crypto on boot.device-mapper on boot.evms off boot.idedma on boot.ipconfig on boot.isapnp on boot.klog on boot.ldconfig on boot.loadmodules on boot.localfs on boot.localnet on boot.md on boot.proc on boot.restore_permissions on boot.rootfsck on boot.sched off boot.scpm on boot.scsidev off boot.shm on boot.swap on boot.sysctl on boot.udev on cron on dbus on earlykbd on earlysyslog on fbset on gpm off hal on hwscan on irq_balancer on joystick off kbd on mdadmd off netstat off network on nfs on nfsboot on nscd on openct off pcscd off portmap on postfix on powersaved on random on raw off resmgr on rpasswdd off rpmconfigcheck off slpd off sshd on syslog on systat off xdm on localhost:/var/log #
You can also debug startup scripts by putting something like this to /sbin/rc: exec 1>/tmp/init.out 2>&1
Hi Kir, under /sbin, there are only the following files starting with rc: lrwxrwxrwx 1 root root 31 Jan 16 17:13 rcSuSEfirewall2 -> /etc/init.d/SuSEfirewall2_setup lrwxrwxrwx 1 root root 25 Jan 16 17:13 rccoldplug -> /etc/init.d/boot.coldplug lrwxrwxrwx 1 root root 17 Jan 16 17:13 rcfbset -> /etc/init.d/fbset lrwxrwxrwx 1 root root 15 Jan 16 17:13 rckbd -> /etc/init.d/kbd lrwxrwxrwx 1 root root 19 Jan 16 17:13 rcnetwork -> /etc/init.d/network lrwxrwxrwx 1 root root 19 Jan 16 17:13 rcportmap -> /etc/init.d/portmap lrwxr-xr-x 1 root root 19 Jan 16 17:18 rcpostfix -> /etc/init.d/postfix lrwxrwxrwx 1 root root 18 Jan 16 17:13 rcsyslog -> /etc/init.d/syslog lrwxrwxrwx 1 root root 4 Jan 16 17:13 reboot -> halt ? Thanks Ronny
I found a rc script under /etc/rc.d/rc And added as first line this exec 1>/tmp/init.out 2>&1 Let´s try
stty: standard input: Inappropriate ioctl for device This error seems to happen, after it, init stops the scripts (?) (one and only entry) Maybe it depends on this piece of code of original Suse´s rc: snip set -- $(stty size < $REDIRECT) snap ?
It should be rather harmless per se; still, try to comment it out and continue debugging
I found some postings with Google about people having the same problem. http://list.linux-vserver.org/archive/vserver/msg01363.html I did it this way, and now it SEEMS to work. I will test again (with hard - reboot and so on). If it works, and all works fine, i will publish my Suse-9.3-Image soon for the public so everyone can use it. Thanks for your help, Kir Regards, Ronny