Having some wierd things happen with samba...

[Norman Weathers]

Yeah, I know, the subject is "real" descriptive...

Anyway.

A couple of times now, I have come in to my office in the morning to see
my Linux server
spewing SMB messages all over the console.  I was able to capture a
couple of them lately.
They are:

[root at lithe /root]# cd /[1999/08/17 08:11:08, 0]
lib/debug.c:check_log_size(285)  check_log_size: open of debug file
/var/log/samba/log.smb failed - using console.
[1999/08/17 08:11:08, 0] smbd/process.c:timeout_processing(868)
  Reloading services after SIGHUP

Now, I went and checked my error logs,  and  they have been rotating
correctly, and there is a
/var/log/samba/log.smb available, and it is not as full as my last two
logs that I keep for when
I do comparisons.  This is twice that is has done this.  The services
are still available and working,
they just spew error's like that to the console.

What I did last time was delete my logs, restart the services, and touch
log.smb and log.nmb, and
then it works for about a week or two.

Is this a problem with samba (I am using samba 2.0.5a) or is this more
than likely a log rotation
problem with Linux (RedHat 6.0).

Also, I have a question from one of my logs... Is this a very familiar
message?  I don't remember
seeing this one very often.

[1999/08/10 14:14:41, 0] smbd/oplock.c:process_local_message(528)
  process_local_message: unsolicited oplock break reply from pid 10520,
port 1613, dev =
305, inode = 641552
[1999/08/10 14:14:41, 0] smbd/oplock.c:process_local_message(513)
  process_local_message: Received unsolicited break reply - dumping
info.
[1999/08/10 14:14:41, 0] smbd/oplock.c:process_local_message(528)
  process_local_message: unsolicited oplock break reply from pid 10520,
port 1613, dev =
305, inode = 641552
[1999/08/10 14:14:41, 0] smbd/oplock.c:process_local_message(513)
  process_local_message: Received unsolicited break reply - dumping
info.
[1999/08/10 14:14:41, 0] smbd/oplock.c:process_local_message(528)
  process_local_message: unsolicited oplock break reply from pid 10520,
port 1613, dev =
305, inode = 641552

This fills my logs along with the previous error.

Any help would be appreciated.  If I need to send an error log at a
higher debug level,
I can do that...

Thanks,


-------------------------------------------------------------------
Norman Weathers
Technology Coordinator ETS
University of Arkansas, Fayetteville

phone: (501) 575-3553 or (501) 575-4344
email: nweathe at comp.uark.edu or norman at lithe.uark.edu

"It's not that I 'prefer' to do this without an NT server.... I
just 'prefer' to do it where it will work..."
-------------------------------------------------------------------