Stephan A. Rickauer wrote:
> Has anyone seen this before in /var/log/maillog?
> 
> Apr 20 08:37:51 srv1 sm-mta[10664]: n3K6bpjJ010664: SYSERR(root):
> gatherq: cannot open "/var/spool/mqueue": No such file or directory
> 
> Apr 20 08:38:52 srv1 sm-mta[15383]: filesys_update failed: No such file
> or directory, fs=., avail=-1, blocksize=3
> 
> Apr 20 08:39:52 srv1 sm-mta[15383]: filesys_update failed: No such file
> or directory, fs=., avail=-1, blocksize=3
> 
> # ls -ld /var/spool/mqueue
> drwx------  2 root  wheel  512 Apr 20 08:57 /var/spool/mqueue
> 
> # df /var
> Filesystem  512-blocks      Used     Avail Capacity  Mounted on
> /dev/sd0e     16518928    204412  15488572     1%    /var
> 
> # touch /var/spool/mqueue/test 
> # ls -l /var/spool/mqueue/test
> -rw-r--r--  1 root  wheel  0 Apr 20 09:02 /var/spool/mqueue/test
>  
> 
> A restart of sendmail fixes the problem. However, I find this pretty
> weired. The filesystem seems to be fine and sendmail did fine for
> months, too ... I just realized this problem when I started to miss the
> daily messages of this system.

did you, by any chance, install a new baseXX.tgz file on the system?

This is a common message if you unpack the file sets without first
stopping sendmail, then restarting it afterwards (or a reboot).

it is mentioned in the various upgradeXX.html documents, but if you
google for the whole message, you miss it because I was too clever
broke the line at the 80 char point, so it would be as you see on
your monitor.

> 
> 
> Here's the full dmesg:
> 
> OpenBSD 4.4-stable (GENERIC.MP) #4: Sun Nov 16 14:21:18 CET 2008

I'd be more convinced I was right if this date was more recent. :)

Nick.

Reply via email to