I have a headless server running a scanner and a webcam.
Quite often (several times a day) it becomes unreachable (via http or telnet) and I have to do a forced poweroff.
I have found lots of pages on how to troubleshoot a crash when you know what is wrong, but none that really seem to start from a position of ignorance. Strange, because I thought that was what troubleshooting was all about. Can anyone offer any suggestions as to where I should be looking. I have tried looking in /var/log for a crash or dump file, but there is nothing there. I have installed some crash dump utilities and I believe I have set up the kernel to do an auto-reboot on a kernel panic, but none of this seems to be getting me anywhere.
On Thu, 24 Jul 2008 15:16:03 GMT
nalexmay <nalexmay@no-mx.forums.opensuse.org> wrote:
>
> I have a headless server running a scanner and a webcam.
> Quite often (several times a day) it becomes unreachable (via http or
> telnet) and I have to do a forced poweroff.
> I have found lots of pages on how to troubleshoot a crash when you
> know what is wrong, but none that really seem to start from a
> position of ignorance. Strange, because I thought that was what
> troubleshooting was all about. Can anyone offer any suggestions as to
> where I should be looking. I have tried looking in /var/log for a
> crash or dump file, but there is nothing there. I have installed some
> crash dump utilities and I believe I have set up the kernel to do an
> auto-reboot on a kernel panic, but none of this seems to be getting
> me anywhere.
>
>
Hi
Have you looked at the kernel and messages log.
If you on a windows machine have a look at installing kiwisyslog and
setup remote sys logging
Else login via ssh and tail the logs and run top to see what is
happening when the system stops. Maybe a process is just running and
chewing up cpu.
Hardware wise, power supply ok, disks ok (run smart), can you run
memtest at boot to check the memory.
Install hddtemp (pacman repos) and check out disk temperatures, setup
lm_sensors to check temperatures of cpu and power supply voltages.
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 4:33, 2 users, load average: 0.59, 0.46, 0.91
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
well, first you have to ask yourself: is it a hardware problem, a
security problem or a network problem…
HARDWARE:
have you ruled out: heat (clean out the dog and cat hair, etc), failing
power supply, run a memory checker? [and, how about the router? blow the
dust out of it too…]
SOFTWARE/SECURITY
are you SURE a root kit has not been installed? is the box exposed to
the net in any way? running tripwire or similar on that box? is it fully
patched and updated? is it a still supported version of SuSE, or?
NETWORK:
you said you can telnet in…if YOU can, can someone from outside? your
router have an airtight password? consider abandoning telnet and use the
much safer SSH…
there are lots of tools to diagnosis most any potential network
problem…i’m not qualified to help you, but you might try posting in
the network forum (where i’m not)…
good luck,
–
DenverD (Linux Counter 282315)
A Texan in Denmark
Thanks Malcolm and thanks DenverD.
I have plenty to get on with there, but here are a few comments on stuff that I had already looked at.
I tried looking for a kernel log, but didn’t find one.
I looked at messages, but couldn’t see anything that meant anything useful to me. It’s huge though so I could be missing something.
I keep the hardware pretty clean.
I ran a memory check (memtest86) and it found no errors.
I think the router is ok as it is the device that other computers on the network are using without any problem.
I don’t know what a root kit is, so I suppose I don’t know if one has been installed.
I do know that the server is more or less completely cut off from the internet. Telnet port is certainly closed.
I believe it is fully patched and updated.
Yast2 seems to be saying it is anyway.
I’ve set up a cron job which should tell me if the server is still running after it is inaccessable via the network which should narrow the problem down a bit.
I will report back when I have tried some more of this stuff.
In the meantime, thanks again for your help.
I’m not quite beat yet, but I’m getting close.
I installed kiwi on my linux box, but it didn’t help. I still can’t make head or tail of any of the log files.
I ran extensive tests on my hard drive and found no problems.
Temperatures look okay and I am still working on installing automated temerature monitoring.
So far I can’t get lm_sensors to make all.
Anything else I can try?
On Thu, 24 Jul 2008 21:06:03 GMT
nalexmay <nalexmay@no-mx.forums.opensuse.org> wrote:
>
> I’m not quite beat yet, but I’m getting close.
> I installed kiwi on my linux box, but it didn’t help. I still can’t
> make head or tail of any of the log files.
> I ran extensive tests on my hard drive and found no problems.
> Temperatures look okay and I am still working on installing automated
> temerature monitoring.
> So far I can’t get lm_sensors to make all.
> Anything else I can try?
>
Hi
lm_sensors should be there already? Try;
sensors-detect
you may also need to activate if it finds sensors to use;
chkconfig lm_sensors on
I would look at running top and/or vmstat 5 (print every 5 seconds)
just to see when what is happening.
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 10:40, 1 user, load average: 0.37, 0.20, 0.14
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
Yes, you’re right.
I looked on Yast for lm_sensors, didn’t find it and assumed I needed to install it!
Sensors-detect ran ok, but it said:
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
Chip drivers
modprobe w83627hf
sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
What am I supposed to do with that? Which file am I supposed to add that too?
Other than that, sensors-detect finished.
What now?
Sorry, I should also have said that I can run top and/or vmstat, but there is nothing in the response that means anything to me in terms of solving this issue. Can you explain what it is that I am looking for?
On Fri, 25 Jul 2008 06:06:03 GMT
nalexmay <nalexmay@no-mx.forums.opensuse.org> wrote:
>
> Yes, you’re right.
> I looked on Yast for lm_sensors, didn’t find it and assumed I needed
> to install it!
> Sensors-detect ran ok, but it said:
>
> To load everything that is needed, add this to some /etc/rc* file:
> #----cut here----
> # Chip drivers
> modprobe w83627hf
> # sleep 2 # optional
> /usr/bin/sensors -s # recommended
> #----cut here----
>
> What am I supposed to do with that? Which file am I supposed to add
> that too?
>
> Other than that, sensors-detect finished.
>
> What now?
>
>
Hi
As long as you accept the ‘yes’ to build the
config /etc/sysconfig/lm_sensors the init script should start
everything ok.
You can test by running the command;
/etc/init.d/lm_sensors start
If that goes ok, you can check with the command;
sensors
Check that it’s configured to start;
chkconfig lm_sensors
It should say on, if not just add on to the end of the above command
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 0:33, 2 users, load average: 0.30, 0.15, 0.23
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
On Fri, 25 Jul 2008 06:16:03 GMT
nalexmay <nalexmay@no-mx.forums.opensuse.org> wrote:
>
> Sorry, I should also have said that I can run top and/or vmstat, but
> there is nothing in the response that means anything to me in terms of
> solving this issue. Can you explain what it is that I am looking for?
>
>
Hi
Ok for the top command, keep an eye on the information in the top
section. It may be swap or cpu, especially if you see swap suddenly
start to be used up. Then look at the current running processors in the
list below.
Vmstat will do the same sort of thing, but has information on the io
for the disks, see man vmstat for more detail.
Now I don’t think I asked if your disk space is ok. What is the output
from;
df -k
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 0:51, 2 users, load average: 0.05, 0.15, 0.17
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
The top section of top looks like this:
top - 14:02:57 up 7:16, 1 user, load average: 0.53, 0.72, 0.44
Tasks: 83 total, 1 running, 82 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.3%us, 0.7%sy, 0.0%ni, 96.1%id, 0.7%wa, 0.0%hi, 1.3%si, 0.0%st
Mem: 189588k total, 159108k used, 30480k free, 6412k buffers
Swap: 514040k total, 12104k used, 501936k free, 82464k cached
vmstat says:
procs -----------memory---------- —swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
0 0 12060 30236 6600 82532 0 2 20 14 99 46 2 1 96 1
df -k produces:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 7605888 3251584 3967944 46% /
udev 94792 76 94716 1% /dev
/dev/sda3 11132200 178468 10388244 2% /home
The trouble is, I can’t sit here waiting for the next crash to see what these things do. Sometimes it is a matter of minutes, but sometimes it can take hours.
Surely I need to set things up to record a log of anything critical so that I can look at it after a crash and see what happened?
Have I done that?
On Fri, 25 Jul 2008 13:16:03 GMT
nalexmay <nalexmay@no-mx.forums.opensuse.org> wrote:
>
> The top section of top looks like this:
> top - 14:02:57 up 7:16, 1 user, load average: 0.53, 0.72, 0.44
> Tasks: 83 total, 1 running, 82 sleeping, 0 stopped, 0 zombie
> Cpu(s): 1.3%us, 0.7%sy, 0.0%ni, 96.1%id, 0.7%wa, 0.0%hi, 1.3%si,
> 0.0%st
> Mem: 189588k total, 159108k used, 30480k free, 6412k buffers
> Swap: 514040k total, 12104k used, 501936k free, 82464k cached
>
> vmstat says:
> procs -----------memory---------- —swap-- -----io---- -system–
> ----cpu----
> r b swpd free buff cache si so bi bo in cs us sy id wa
> 0 0 12060 30236 6600 82532 0 2 20 14 99 46 2 1 96 1
>
> df -k produces:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda2 7605888 3251584 3967944 46% /
> udev 94792 76 94716 1% /dev
> /dev/sda3 11132200 178468 10388244 2% /home
>
> The trouble is, I can’t sit here waiting for the next crash to see
> what these things do. Sometimes it is a matter of minutes, but
> sometimes it can take hours.
> Surely I need to set things up to record a log of anything critical so
> that I can look at it after a crash and see what happened?
> Have I done that?
>
>
Hi
So all the tempertures etc are ok? I would recommend leaving a ssh
session running with top, at least this may eliminate software or
memory (swap) issues.
If you start adding extra processors, extra looging etc it may mask the
actual issue.
You could try piping the output of sensors via a cron job to a file to
see the environment information.
Did you install hddtemp?
Is the external environment ok, surge suppressor for the machine,
cleaner not plugging in a vacum cleaner 
sometimes something
other than the machine can be the issue.
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 2:24, 2 users, load average: 1.41, 1.09, 0.63
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
Yes, I have hddtemp installed and it says that my hard drive is running at 38`C.
I have set up a cron job to log the temperature and also the output of sensors every 10 mins.
The power supply is not going to be affected by anything externally here as there isn’t anything on this ring, so that can’t be the issue.
Leaving an ssh session running is not really a good test as this is supposed to be an unattended headless server.
Surely we should be able to log anything we need?
Of course, the thing hasn’t crashed in ages now.
Maybe your help has done the trick already!
On Fri, 25 Jul 2008 15:16:03 GMT
nalexmay <nalexmay@no-mx.forums.opensuse.org> wrote:
>
> Yes, I have hddtemp installed and it says that my hard drive is
> running at 38`C.
> I have set up a cron job to log the temperature and also the output of
> sensors every 10 mins.
> The power supply is not going to be affected by anything externally
> here as there isn’t anything on this ring, so that can’t be the issue.
> Leaving an ssh session running is not really a good test as this is
> supposed to be an unattended headless server.
> Surely we should be able to log anything we need?
> Of course, the thing hasn’t crashed in ages now.
> Maybe your help has done the trick already!
>
>
Hi
Maybe it was just say hey, your ignoring me…
The question is what to monitor/log and how often. Maybe it’s getting
disk io problems when running a scan job?
Maybe running the command ps -ef will identify some processes you think
could be the cause.
Unattended still needs to be monitored, there are so many options on
how to do this, snmp, nagios etc
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 3:48, 2 users, load average: 0.09, 0.18, 0.56
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
I have just run a couple of scan jobs and all still seems to be running fine.
ps -ef produced the following:
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 06:46 ? 00:00:01 init [5]
root 2 0 0 06:46 ? 00:00:00 [kthreadd]
root 3 2 0 06:46 ? 00:00:00 [migration/0]
root 4 2 0 06:46 ? 00:00:00 [ksoftirqd/0]
root 5 2 0 06:46 ? 00:00:03 [events/0]
root 6 2 0 06:46 ? 00:00:00 [khelper]
root 25 2 0 06:46 ? 00:00:00 [kblockd/0]
root 26 2 0 06:46 ? 00:00:00 [kacpid]
root 27 2 0 06:46 ? 00:00:00 [kacpi_notify]
root 90 2 0 06:46 ? 00:00:00 [cqueue/0]
root 91 2 0 06:46 ? 00:00:00 [kseriod]
root 108 2 0 06:46 ? 00:00:00 [pdflush]
root 109 2 0 06:46 ? 00:00:01 [pdflush]
root 110 2 0 06:46 ? 00:00:00 [kswapd0]
root 111 2 0 06:46 ? 00:00:00 [aio/0]
root 337 2 0 06:46 ? 00:00:00 [kpsmoused]
root 342 2 0 06:46 ? 00:00:00 [kondemand/0]
root 382 2 0 06:46 ? 00:00:01 [ata/0]
root 383 2 0 06:46 ? 00:00:00 [ata_aux]
root 389 2 0 06:46 ? 00:00:00 [scsi_eh_0]
root 390 2 0 06:46 ? 00:00:02 [scsi_eh_1]
root 488 2 0 06:46 ? 00:00:00 [ksuspend_usbd]
root 489 2 0 06:46 ? 00:00:00 [khubd]
root 876 2 0 06:46 ? 00:00:02 [kjournald]
root 933 1 0 06:46 ? 00:00:00 /sbin/udevd --daemon
root 1553 2 0 06:46 ? 00:00:00 [kjournald]
root 1602 2 0 06:46 ? 00:00:00 [kauditd]
root 1835 1 0 06:46 ? 00:00:00 /sbin/resmgrd
100 1844 1 0 06:46 ? 00:00:00 /bin/dbus-daemon --system
root 1853 1 0 06:46 ? 00:00:01 /sbin/syslog-ng
root 1857 1 0 06:46 ? 00:00:00 /sbin/klogd -c 1 -x -x
root 1859 1 0 06:46 ? 00:00:00 /sbin/acpid
root 1893 1 0 06:46 ? 00:00:00 /usr/sbin/console-kit-daemon
101 1962 1 0 06:46 ? 00:00:02 /usr/sbin/hald --daemon=yes
root 1966 1962 0 06:46 ? 00:00:00 hald-runner
root 2004 1966 0 06:46 ? 00:00:00 hald-addon-input: Listening on /
101 2007 1966 0 06:46 ? 00:00:00 hald-addon-acpi: listening on ac
root 2027 1966 0 06:46 ? 00:00:03 hald-addon-storage: polling /dev
root 2035 1 0 06:46 ? 00:00:00 /opt/kde3/bin/kdm
root 2051 2035 0 06:46 tty7 00:00:13 /usr/bin/Xorg -br -nolisten tcp
root 2056 2035 0 06:46 ? 00:00:00 -:0
root 2335 2056 0 06:47 ? 00:00:30 /opt/kde3/bin/kdm_greet
root 2605 1 0 06:47 ? 00:00:00 /sbin/dhcpcd -C -D -K -N -t 9999
root 2770 1 0 06:47 ? 00:00:00 /sbin/auditd -s disable
root 2772 2770 0 06:47 ? 00:00:00 /sbin/audispd
avahi 2816 1 0 06:47 ? 00:00:00 avahi-daemon: running NEC.local
root 2825 1 0 06:47 ? 00:00:00 /usr/sbin/avahi-dnsconfd -D
root 2840 1 0 06:47 ? 00:00:00 /usr/sbin/hddtemp -d -f /etc/hdd
root 2896 1 1 06:47 ? 00:07:57 /usr/local/bin/motion
root 2912 1 0 06:47 ? 00:00:01 /usr/sbin/nscd
bin 2928 1 0 06:47 ? 00:00:00 /sbin/portmap
root 2944 1 0 06:47 ? 00:00:01 /usr/sbin/cupsd
root 2984 1 0 06:47 ? 00:00:00 /usr/sbin/powersaved -d -f /var/
root 3035 1 0 06:47 ? 00:00:00 /usr/sbin/xinetd
root 3038 1 0 06:47 ? 00:00:00 /usr/lib/postfix/master
postfix 3052 3038 0 06:47 ? 00:00:00 qmgr -l -t fifo -u
root 3069 1 0 06:47 ? 00:00:00 /usr/sbin/sshd -o PidFile=/var/r
root 3084 1 0 06:47 ? 00:00:02 /usr/sbin/httpd2-prefork -f /etc
root 3094 1 0 06:47 ? 00:00:00 /usr/sbin/cron
root 3112 1 0 06:47 tty1 00:00:00 /sbin/mingetty --noclear tty1
root 3113 1 0 06:47 tty2 00:00:00 /sbin/mingetty tty2
root 3114 1 0 06:47 tty3 00:00:00 /sbin/mingetty tty3
root 3115 1 0 06:47 tty4 00:00:00 /sbin/mingetty tty4
root 3116 1 0 06:47 tty5 00:00:00 /sbin/mingetty tty5
root 3118 1 0 06:47 tty6 00:00:00 /sbin/mingetty tty6
wwwrun 3125 3084 0 06:47 ? 00:00:13 /usr/sbin/httpd2-prefork -f /etc
wwwrun 3126 3084 0 06:47 ? 00:00:04 /usr/sbin/httpd2-prefork -f /etc
wwwrun 3127 3084 0 06:47 ? 00:00:12 /usr/sbin/httpd2-prefork -f /etc
root 3160 1 0 06:47 ? 00:00:00 /usr/sbin/smartd
wwwrun 5729 3084 0 12:10 ? 00:00:12 /usr/sbin/httpd2-prefork -f /etc
wwwrun 5730 3084 0 12:10 ? 00:00:03 /usr/sbin/httpd2-prefork -f /etc
wwwrun 5757 3084 0 12:13 ? 00:00:07 /usr/sbin/httpd2-prefork -f /etc
wwwrun 5758 3084 0 12:13 ? 00:00:15 /usr/sbin/httpd2-prefork -f /etc
wwwrun 8304 3084 0 14:27 ? 00:00:04 /usr/sbin/httpd2-prefork -f /etc
postfix 8758 3038 0 15:06 ? 00:00:00 pickup -l -t fifo -u
wwwrun 8994 3084 0 15:28 ? 00:00:00 /usr/sbin/httpd2-prefork -f /etc
wwwrun 20283 3084 0 16:28 ? 00:00:00 /usr/sbin/httpd2-prefork -f /etc
root 20517 3035 0 16:39 ? 00:00:00 in.telnetd: tablet.home
root 20518 20517 0 16:39 ? 00:00:00 login – alex
alex 20519 20518 1 16:39 pts/0 00:00:00 -bash
root 20540 20519 0 16:39 pts/0 00:00:00 su
root 20541 20540 0 16:39 pts/0 00:00:00 bash
root 20552 20541 0 16:39 pts/0 00:00:00 ps -ef
Does anything here look like a problem?
I don’t know anything about snmp or nagios or the like.
I had a quick look after googling them.
They look very clever, but I’m not sure why I need them.
I have 4 other server boxes. None of them crash on a regular basis.
In fact they almost never crash. And as far as I know, none of them have anything
like snmp or nagios, they are more or less default Suse installations.
Will either of these things help me troubleshoot the problem?
> The trouble is, I can’t sit here waiting for the next crash to see what
> these things do. Sometimes it is a matter of minutes, but sometimes it
> can take hours.
> Surely I need to set things up to record a log of anything critical so
> that I can look at it after a crash and see what happened?
> Have I done that?
man top tells how to have it make log…
something like
top -b -d 60 > ~/[you decide where to put it]/top-log.txt
would plop down a log file which will rather quickly get pretty big…
because it will take a snapshot every 60 seconds…you can change that
to more or less…depending on what you feel your needs are…
HOWEVER, since we don’t yet know that it is not a network or disk
problem i’d recommend you use atop instead of top.
atop is similar to top but also watches/records network and disk
‘busyness’…
use YaST to add atop to your system (it is not a default install)…
when you do it will automatically take a system snapshot every 10
minutes and drop it into a log file named /var/log/atop/atop_YYYYMMDD
(where YYYYMMDD are digits representing the current date).
lets say you suffer a crash or inability to contact the server, when you
are again able to get in you can view the latest file thusly:
atop -r /var/log/atop/atop_YYYYMMDD
and step though the every 10 minute snapshots with ‘t’ forward, or ‘T’
backwards (in time)…
if you feel every ten minutes is too often or not often enough you can
edit /etc/atop/atop.daily
the default line near the top of the file
INTERVAL=600
gives the every ten minute peek…perhaps you want it every one minute
or even more often…just be careful to not fill up your hard
drive…because that will crash the box also…
or, you can watch it update every ten seconds at the command line just
by typing and entering
atop
(and, use ‘q’ to kill it)
good luck…Have Fun.
–
DenverD (Linux Counter 282315)
A Texan in Denmark
atop sounds very good, but YaST says it can’t find it.
Do I need to add a special repository?
> atop sounds very good, but YaST says it can’t find it.
> Do I need to add a special repository?
hmmmmm…i have it here but don’t know were it comes from, i have these
repositories:
community repositories i have are:
- main repository (NON-OSS)
- main repository (OSS)
- Main update repository
- NVIDIA Repository
- Packman Repository
- openSUSE BuildService for
– Mozilla
– OpenOffice.org
software repositories i have:
- Main(non-oss) download.opensuse.org/distribution/10.3/repo/non-oss/
- Main (oss) download.opensuse.org/repositories/openSUSE:10.3/standard/
- NVIDIA download.nvidia.com/opensuse/10.3
- OO.o
download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_10.3/ - mozilla download.opensuse.org/repositories/mozilla/openSUSE_10.3/
- packman ftp.skynet.be/pub/packman/suse/10.3/ (/i686 /i586)
- updates download.opensuse.org/update/10.3/
or, you can go to the source
http://www.atcomputing.nl/Tools/atop/download-atop.html
click on the 1.23 version rpm, and when you have it downloaded just
right click on it and select Actions > Install with YaST, give your root
pass and you are done son.
–
DenverD (Linux Counter 282315)
A Texan in Denmark
On Fri, 25 Jul 2008 15:56:03 GMT
nalexmay <nalexmay@no-mx.forums.opensuse.org> wrote:
>
> I have just run a couple of scan jobs and all still seems to be
> running fine.
>
> ps -ef produced the following:
<snip>
> root 2051 2035 0 06:46 tty7 00:00:13 /usr/bin/Xorg -br
> -nolisten tcp
> root 2056 2035 0 06:46 ? 00:00:00 -:0
> root 2335 2056 0 06:47 ?
> 00:00:30 /opt/kde3/bin/kdm_greet root 2605 1 0
> root 2896 1 1 06:47 ? 00:07:57 /usr/local/bin/motion
> 00:00:00 /usr/lib/postfix/master postfix 3052 3038 0
> root 3118 1 0 06:47 tty6 00:00:00 /sbin/mingetty tty6
> wwwrun 3125 3084 0 06:47 ? 00:00:13
> root 20517 3035 0 16:39 ? 00:00:00 in.telnetd:
> Does anything here look like a problem?
Hi
Ok, any reason to run X and telnet? If you need remote GUI access, I
would look at freeNX or my preference is NX from nomachine.com
I also see you have apache running, is this an external website?
What about postfix, not hanging on something?
I assume motion is the web camera application?
Have you looked at the apache logs for any issues, apache status ok?
atop can be found at http://software.opensuse.org/search
Or if you add the repository;
http://download.opensuse.org/repositories/server:/monitoring/openSUSE_11.0/
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 5:18, 2 users, load average: 0.26, 0.13, 0.16
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
Thanks guys.
Just as I got your post I was waiting for the one click install from the search at software.opensuse.org to finish.
I still am!
I have X on all my machines (I think).
I think it was part of the default Suse installation.
I have to be in init 5 for the webcam to work.
I always have a telnet daemon running.
Where I am administering on the local network,
it is great to be able to telnet so easily from a Win box.
It doesn’t seem to cause a problem on other machines.
Yes, I have apache, but no, it’s not an external website.
The scanner software interface is webbased and it is also useful to be able to see the webcam picture directly.
I don’t really know why I have postfix. Could that cause a problem?
Motion is the webcam application, yes.
I did have a look at the apache logs, but I didn’t find anything enlightening.