A little goblin disables my linux server during the night...freezes... help!

crazyswede · 07-15-2004, 03:49 AM

I have a box configured to be a sort of storage server and it is running SUSE 9 and running Samba on it. The most of the disks are in fat32 and it had been running for months without a restart

but then I added another hard disk and it is not the same anymore

It now freezes with the screen being black and moving the mouse or keyboard does not help. You can also not connect across the network. So the only way of starting it is to press the restart button on the case...

It only freezes during the night... when no one is in the office

The only thing that uses the computer during the night is a backup program which backs up files from the drives (windows xp backup utility).

I first thought it was not enough power, but it never crashes during the day when everyone is accesing it?

Here are some logs of events when it freezes.... (freezes at 1:21 this morning)

From message log:

Quote:

Jul 14 17:17:50 nasserver smbd[8503]: [2004/07/14 17:17:50, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 17:17:50 nasserver smbd[8503]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 17:42:09 nasserver -- MARK --
Jul 14 17:59:00 nasserver /USR/SBIN/CRON[8569]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 14 18:00:00 nasserver /USR/SBIN/CRON[8574]: (root) CMD ( /usr/lib/sa/sa2 -A #update reports every 6 hour)
Jul 14 18:22:09 nasserver -- MARK --
Jul 14 18:42:09 nasserver -- MARK --
Jul 14 18:55:24 nasserver smbd[7591]: [2004/07/14 18:55:24, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 18:55:24 nasserver smbd[7591]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 18:59:00 nasserver /USR/SBIN/CRON[8697]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 14 19:22:09 nasserver -- MARK --
Jul 14 19:42:09 nasserver -- MARK --
Jul 14 19:59:00 nasserver /USR/SBIN/CRON[8817]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 14 20:22:09 nasserver -- MARK --
Jul 14 20:42:09 nasserver -- MARK --
Jul 14 20:59:00 nasserver /USR/SBIN/CRON[8938]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 14 21:22:09 nasserver -- MARK --
Jul 14 21:42:09 nasserver -- MARK --
Jul 14 21:59:00 nasserver /USR/SBIN/CRON[9058]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 14 22:22:09 nasserver -- MARK --
Jul 14 22:42:09 nasserver -- MARK --
Jul 14 22:59:00 nasserver /USR/SBIN/CRON[9179]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 14 23:22:09 nasserver -- MARK --
Jul 14 23:34:22 nasserver smbd[7591]: [2004/07/14 23:34:22, 0] smbd/nttrans.c:reply_nttrans(2082)
Jul 14 23:34:23 nasserver smbd[7591]: reply_nttrans: Unknown request 7 in nttrans call
Jul 14 23:59:00 nasserver /USR/SBIN/CRON[9300]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 15 00:00:00 nasserver /USR/SBIN/CRON[9304]: (root) CMD ( /usr/lib/sa/sa2 -A #update reports every 6 hour)
Jul 15 00:22:09 nasserver -- MARK --
Jul 15 00:42:09 nasserver -- MARK --
Jul 15 00:59:00 nasserver /USR/SBIN/CRON[9426]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 15 01:00:00 nasserver /USR/SBIN/CRON[9431]: (root) CMD (/sbin/evlogmgr -c "severity=DEBUG")
Jul 15 01:21:44 nasserver smbd[7591]: [2004/07/15 01:21:44, 0] smbd/nttrans.c:reply_nttrans(2082)
Jul 15 01:21:45 nasserver smbd[7591]: reply_nttrans: Unknown request 7 in nttrans call

from warn log:

Quote:

Jul 14 09:51:03 nasserver smbd[7592]: [2004/07/14 09:51:03, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 09:51:03 nasserver smbd[7592]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 10:59:02 nasserver smbd[7716]: [2004/07/14 10:59:02, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 10:59:02 nasserver smbd[7716]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 16:48:54 nasserver smbd[8439]: [2004/07/14 16:48:54, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 16:48:55 nasserver smbd[8439]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 16:48:58 nasserver smbd[8440]: [2004/07/14 16:48:58, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 16:48:58 nasserver smbd[8440]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 17:17:50 nasserver smbd[8503]: [2004/07/14 17:17:50, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 17:17:50 nasserver smbd[8503]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 18:55:24 nasserver smbd[7591]: [2004/07/14 18:55:24, 0] smbd/password.c:domain_client_validate(1558)
Jul 14 18:55:24 nasserver smbd[7591]: domain_client_validate: could not fetch trust account password for domain OSIRIS
Jul 14 23:34:22 nasserver smbd[7591]: [2004/07/14 23:34:22, 0] smbd/nttrans.c:reply_nttrans(2082)
Jul 14 23:34:23 nasserver smbd[7591]: reply_nttrans: Unknown request 7 in nttrans call
Jul 15 01:21:44 nasserver smbd[7591]: [2004/07/15 01:21:44, 0] smbd/nttrans.c:reply_nttrans(2082)
Jul 15 01:21:45 nasserver smbd[7591]: reply_nttrans: Unknown request 7 in nttrans call

I don't know if these logs are of any help?

I would really be grateful for any help

crazyswede

dannybpng · 07-15-2004, 08:46 AM

1. does it work if you remove the "new" drive? Is it possible it is failing after running for a while? Does the drive work fine in another computer?
2. Is it possible that the new drive is spinning down at night and does not start up in time?
3. Are you mounting, backuing up, then unmounting the drive?

I had problems with an automount setup where Samba would not let go of the mount and leaves several processes running. I had to kill the processes manually as root.

Just some things to check.

Dan

crazyswede · 07-16-2004, 03:14 AM

Thankyou for your reply

1. does it work if you remove the "new" drive? Is it possible it is failing after running for a while? Does the drive work fine in another computer?

The drive has been fine for over a year in a windows machine. It was reformated before it was stuck in the linux computer. The computer has 3 other hard drives in it that seem happy. I might pull one of the other drives out first because the latest drive is the one used the most.

2. Is it possible that the new drive is spinning down at night and does not start up in time?

It might. but when I came into work today it was ok.

3. Are you mounting, backuing up, then unmounting the drive?

All drives are always mounted. This is my fstab file:

Quote:

/dev/hde3 / reiserfs defaults 1 1
/dev/hde1 /windows/C vfat users,gid=users,umask=0002,iocharset=iso8859-1,code=437 0 0
/dev/hde2 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbdevfs /proc/bus/usb usbdevfs noauto 0 0
/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
/dev/dvd /media/dvd auto ro,noauto,user,exec 0 0
/dev/dvdram /media/dvdram auto ro,noauto,user,exec 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
/dev/hda1 /fat32/general vfat auto,defaults,umask=000,gid=samba 0 0
/dev/hda5 /fat32/it vfat auto,defaults,umask=000,gid=samba 0 0
/dev/hda6 /fat32/pastcon vfat auto,defaults,umask=000,gid=samba 0 0
/dev/hdb1 /fat32/swathe vfat auto,defaults,umask=000,gid=samba 0 0
/dev/hdc1 /fat32/currentcon vfat auto,defaults,umask=000,gid=samba 0 0

scott_R · 07-16-2004, 04:07 AM

Look at all those smbd errors. Somewhere along the line, your permissions (XP or Linux) aren't set up correctly. The errors, unfortunately, probably don't really hint at your problem. Have you tried using a Linux backup program, to see if it's just a windows unoperability thing?

crazyswede · 07-26-2004, 04:06 AM

Some of the windows xp machines have problems logging on, which I am trying to sort out. But this problem has been arround for a long time before it was freezing so I think it is someting else.

Could it be the windows backup program... could file shaddowing be a problem??? It backups everyday, but does not crash everyday?

dannybpng · 07-27-2004, 07:22 AM

I did a search for one of the error messages in your log file and it brought up the source code for Samba that handles NT transactions. It looks like your XP box is sending a transaction code that is not recognized by Samba. I am assuming it should be 1-6 but it senda a 7, as printed in your log file. There are some hacks in the code because of Windows NT/XP problems that might create problems for you too.

What version of Samba are you running?
If it is not the newest you might consider upgrading.

Dan

crazyswede · 07-28-2004, 04:12 AM

Thanks for the info...

I am running Samba version 2.2

I tried to install version 3 but the install path in SUSE is different and I have not found the right one yet. I have just found SUSE rpm files for Samba 3.

ldapsmb-1.31-14.i586.rpm
libsmbclient3-3.0.5-1.i586.rpm
libsmbclient3-devel-3.0.5-1.i586.rpm
samba3-3.0.5-1.i586.rpm
samba3-client-3.0.5-1.i586.rpm
samba3-doc-3.0.5-1.i586.rpm
samba3-pdb-3.0.5-1.i586.rpm
samba3-python-3.0.5-1.i586.rpm
samba3-vscan-0.3.4-1.i586.rpm
samba3-winbind-3.0.5-1.i586.rpm

I now have to figure out what to do with them and which files to use and how ( I am new to linux

and learning as I go along)