On Thu, Jan 15, 2004 at 12:38:58AM +0000, James Turck wrote: > I have just cross installed an old redhat server I have at a colo with > debian using debootstrap etc. but keeping the old kernel. > > All went well and things looked good until I rebooted and couldn't get into > contact with the server.
<snip> > Jan 15 00:13:37 p15112151 syslogd 1.4.1#10: restart. <snip> > Jan 15 00:13:38 p15112151 /usr/sbin/cron[205]: (CRON) INFO (pidfile fd = 3) > Jan 15 00:13:38 p15112151 /usr/sbin/cron[206]: (CRON) STARTUP (fork ok) > Jan 15 00:13:39 p15112151 /usr/sbin/cron[206]: (CRON) INFO (Running @reboot > jobs) Hi, James! cron(8) is one of the last things init(8) spawns in Debian: $ ls /etc/rc2.d | grep ^S | awk '/cron/,0' S89anacron S89atd S89cron S91apache S99fetchmail S99rmnologin -- and those other don't leave a mark in /var/log/syslog; not at my system. So probably the system /is/ up'n'running. > then nothing...and I can't even ping it from the network. Firewall misconfiguration? Missing network support in the kernel/modules -- misconfigured /etc/modules.conf? Add some debugging /etc/init.d script, that would test the network connection--i.e. try to ping/listen on ports, writing in some log at the same time. HTH Jan. -- Jan Minar "Please don't CC me, I'm subscribed." x 9
pgp00000.pgp
Description: PGP signature
