System:
SuSE 9.2 x86-64 Pro
AMD Opteron Tyan s2875anrf w/ onboard NIC.
max open files still set at default 1024.
Yesterday the server wouldn't respond to ping or accept new connections for
about 25-30 minutes. The server was up and running but for some reason the
NIC decided it didn't want to communicate for a while then it came back. Our
server monitors reported the downtime.
Anyone know why this occurred?
Sorry for a repost. I didn't include some important parts for this
how-to.
First off get this package from LSI.
http://www.lsilogic.com/downloads/license.do?id=2000&did=7776&pid=2411
It is the driver package for SuSe 9.1. In that driver package is a
directory called Utilities/MegaMON. In MegaMON is a file named
lsi_v35.tgz. Do a tar -xzvf lsi_v35.tgz. This is the monitor app you
will need.
Then do a "./install -suse". This will install the binaries and install
the startup script of raidmon in /etc/init.d and set itself to start on
the runlevels 2,3,4,5. If the raidmon script does not get installed just
copy it to the /etc/init.d directory.
I have modified my raidmon file to include some other items. Below is
mine:
------------------------------------------------------------
#!/bin/sh
#
# chkconfig: 2345 20 80
# description: RAIDMon is a daemon that monitors the RAID subsystem
# And generates e-mail to root
# processname: MegaServ.
# source function library
. /lib/lsb/init-functions
case "$1" in
start)
megadevice="megadev0"
rm -f /dev/$megadevice 2>/dev/null
megamajor=`cat /proc/devices|gawk '/megadev/{print$1}' `
mknod /dev/$megadevice c $megamajor 0 2>/dev/null
# New check: 10-31-01: Does node exist
if [ ! -c /dev/$megadevice ]
then
echo "
Character Device Node /dev/$megadevice does not exist.
Raid Monitor could not be started
"
exit 1
fi
echo -n 'Starting RAID Monitor:'
startproc /usr/sbin/MegaCtrl -start > /dev/null
sleep 1 ; MegaCtrl -disMail
touch /var/lock/subsys/raidmon
MegaCtrl -enChkCon
# check consistency on a Saturday at 01:00 very 4 weeks
MegaCtrl -cons -h01 -w4 -d6
echo
;;
stop)
echo -n 'Stopping RAID Monitor:'
startproc /usr/sbin/MegaCtrl -stop
megadevice="megadev0"
rm -f /dev/$megadevice 2>/dev/null
rm -f /var/lock/subsys/raidmon 2>/dev/null
echo
;;
restart|reload)
$0 stop
$0 start
;;
*)
echo "RAID Monitor is not Started/Stopped"
echo "Usage: raidmon {start|stop|restart}"
exit 1
esac
exit 0
-----------------------------------------------------------------------
Then just start the raidmon. "/etc/init.d/raidmon start". The above
changes tell my system to do a consistency check once a month at 1:00am.
This makes sure my RAID5 is working like it should.
Also note there will be a log file of /var/log/megaserv.log.
Next create this file "/usr/local/sbin/check_raid.sh" for checking the
logfile
for errors:
--- START SCRIPT ---
#!/bin/sh
# Simple RAID check script. Relies on consistency check run
by /etc/init.d/raidmon at
# 01:00 every day.
# This is then run by roots crontab at 04:30 everyday.
HOST=`hostname`
MAILTO="<your email>"
if grep -iq fail /var/log/megaserv.log
then date | mail -s "$HOST has a RAID array problem" $MAILTO
fi
exit 0
--- END SCRIPT ---
Then setup a cron job to check the log file for errors every hour or
whatever time you want. I check every day at 4:30am. Some might want to
check more often.
As root do a "crontab -e". Then enter:
# Check for any reported RAID array errors
30 4 * * * /usr/local/sbin/check_raid.sh
I use this setup on about a dozen production machines. It works
perfectly. This will work on 32bit and 64bit machines.
Brad Dameron
Systems Administrator
SeaTab Software
www.seatab.com
Hello everyone:
Thanks for all the help. Problem solved. I used the
'chown -R' command and it worked. I've checked a number of different
files in different folders and had full access, etc., to all of them.
If there are some files with problems, I haven't found them yet. Again,
thanks for all the help. Much appreciated.
Cheers,
Mike
Hello everyone:
Under SuSE 9.1, the wallpapers were under . . .
/.kde/share/wallpapers. Under SuSE 9.3, this path / directory doesn't
seem to exist anymore. Does anyone know where the /wallpaper directory
is so I can add some of my favorites to it?
Cheers,
Mike
Hi everyone:
Some good news - I've been able to recover working files from
my old /mike directory. Seems I forgot to creat a 'mount' point for the
HD. I deserve one wack with a wet noodle. Mea Culpa.
Cheers,
Mike
Hello everyone:
Well, it doesn't rain but not pour. My great idea simply
didn't work. For whatever reason, I can't get to the 30GB HD where I
copied my original desktop. The only good news is that many of the
files are on floppies (remember them) and I am able to recover some, but
not all, of the working files. A pain to be sure. Thanks for all the
help but, without access to the other HD, my efforts are in vain.
Again, thanks for all the help.
Cheers (well, a slight frown ;-| )
Mike
Hi all,
I've followed the tip written by Stefan to avoid the "Aiee, trying to kill
interrupt handler" or somesuch fatal error message at reboot after install.
That is, when installing SuSE 9.3 I've chosen to remove the SMP kernel and
use the defult one. Now the machine (MSI K8N nforce4 SLI with X2 dual core)
boot fine after reboot and I need to replace the default kernel with the smp
flavour. Obviously, getting the kernel from the DV leads to the same fatal
error.
So how can one get a more recent X6_64 kernel for SuSE 9.3 ? Wkere's the
download site and what#s the replacement procedure ? Should I simply install
the eventual rpm file and ovrewrite the present kernel or should I delete the
kernel first ? Some one can share pointers to that effect ?
Thanks.
Hello everyone:
Well, seems there's trouble right here in River City :-( I
was planning to do a fresh install on my AMD 64 / SuSE 9.3 desktop
machine and decided to save my
'/home/mike' directory on a separate hard drive (which I did). I then
performed a basic install and then copied the 'saved' /home/mike
directory to replace the /home/mike directory created during the install.
Not sure what I did or didn't do but when I tried to open the
files or use the devices, I kept getting KDE error messages (will not
save configuration). I have now done anohter clean install but, if
possible, would like to use the 'saved' /home/mike directory. Not sure
if this is a permissions problem or what. The old directory is still on
the separate hard drive so I do have access to it.
During the last corrputed install, I was able to save
important working files to my laptop so all is not lost. It would be
nice if I could salvage my earlier settings, etc., as this would save me
a lot of grief.
Any ideas. I did offer Tux a sacrifice of dandylions and some
dead bugs - not sure if this will help ;-)
Cheers,
Mike
For people who had problems with the broken sound after the latest 9.3
update kernel.
Please test the kernel in ftp.suse.com:/pub/people/ak/test1/
and report success/failure to me. I'm only interested in sound
problems right now.
Thanks.
-Andi
Turns out it was a homemade patch cable that decided to start flaking out
all the sudden ... had to slap my network admin upside the head.
-----Original Message-----
From: Kevin Wilson
Sent: Tuesday, August 09, 2005 12:48 PM
To: Suse-Amd64 (E-mail)
Subject: [suse-amd64] Network interface timeout
System:
SuSE 9.2 x86-64 Pro
AMD Opteron Tyan s2875anrf w/ onboard NIC.
max open files still set at default 1024.
Yesterday the server wouldn't respond to ping or accept new connections for
about 25-30 minutes. The server was up and running but for some reason the
NIC decided it didn't want to communicate for a while then it came back. Our
server monitors reported the downtime.
Anyone know why this occurred?
--
Check the List-Unsubscribe header to unsubscribe
For additional commands, email: suse-amd64-help(a)suse.com
