On Tue, 05 Aug 2003 08:49, you wrote: > Hi all > > I setup my IPCop box over the weekend and all was going sweet until I > applied fix1 (I'm using IPCop 1.3) Kernel panic, rebooted and everything > seemed fine, until I realized I couldn't get into the web interface to > check what went wrong. Another kernel panic made me decide to start over, > but last night it did the exact same thing, kernel panic (sorry don't have > the exact error handy), To be effective in helping you we do need the exact messages.
> and now can't get into the web interface at all, > but I can still browse the web. > > How can I fix this? Log into the machine locally and check out the bootup messages in /var/log/messages and the output from the dmesg command. This is stored in the file /var/log/dmesg Check that the web server is actually working. ps auxw | grep httpd should give a few lines of o/p if the daemon is running vis:- [EMAIL PROTECTED]:~ # ps auxw | grep httpd root 225 0.0 2.1 5664 664 ? S Aug01 0:11 /usr/sbin/httpd -DSSL nobody 23304 0.0 2.2 5664 672 ? S 00:01 0:00 /usr/sbin/httpd -DSSL nobody 23305 0.0 2.3 5664 728 ? S 00:01 0:00 /usr/sbin/httpd -DSSL nobody 23306 0.0 2.2 5664 672 ? S 00:01 0:00 /usr/sbin/httpd -DSSL nobody 23307 0.0 2.2 5664 672 ? S 00:01 0:00 /usr/sbin/httpd -DSSL root 26189 0.0 1.9 2572 604 ttyp0 S 09:06 0:00 grep httpd If it's not running attempt to restart it with:- /usr/sbin/httpd -DSSL and tell us what happens. > What could be causing it? Probably hardware problems. Have you been able to run memtest86 on the machine? Remember that you access the internal Apache server on an IPCop using port 81, or 445 for the https protocol. -- Sincerely etc., Christopher Sawtell
