/var/spool/mqueue low space

[j773303]

as title, what's the mean of the message? Due to the /var file system is full.

[T G Manikandan]

This is because your /var file system is full.

Just do a
#du -k /var|sort -nr

and check the directories using more space.

Do check the size of the log files


/var/adm/wtmp
btmp

/var/adm/syslog/syslog.log
mail.log

Thanks

[T G Manikandan]

Also check

/var/tmp--->
temporary files

#find /var/tmp -mtime +7 -exec rm {} \;

Also check the /var/preserve dir.

[j773303]

I want to know the meaning of
/var/spool/mqueue low space?
Is it about sendmail?

[T G Manikandan]

Yes it is related to sendmail.

Due to the less file system space on /var,
Either incoming/outgoing mails are throwing these messages.
You need to free some space on the file system.

Thanks

[V. V. Ravi Kumar_1 · Accepted solution]

hi,
this message is related to sendamail only. u only need to cleanup /var/ file system. u can delete all files in /var/preserve directory safely, which releases lot of space. Sendmail maintains its mail queue related files in /var/spool/mqueue.
u can also delete file in /var/tmp

Regards

[Lisa Sorbo]

wow. I just wanted to say thanks for all these threads on /var - mine was up to 96% full and causing problems -- I had SAM trim the logs and went down to 52%. Wow! Thanks again for all you people who contribute to these threads - those of us who search the logs on Saturday afternoons really appreciate it !

[Anand_20]

/var/spool/mqueue file system is full and this may result the system not functioning properly. The best way is to remove unwanted files from this file system or else if you are not sure which files to be removed, alternative is to create another file system (/var/spool/mqueue1); Check for free PE in vg00, and move the files to the new filesystem which are not frequently being used.
This increases the space in /var and messages are suppressed.

[Bill Hassell]

/var is the most critical filesystem in HP-UX. When it gets full, almost everything breaks. The name /var is not without meaning: it is quite variable, but mostly grows. SAM can be used as a one-time fixer for /var but in the long run, you need to look at two solutions:

1. cron jobs that scan logfiles for useful data, then compress or zero the logfiles and other cron jobs to get rid of truly temporary files (/var/tmp).

2. some /var directories may get VERY large as a normal activity and these may be more suited to staying on a separate disk. This increases the fault-tolerance of a large server. For example, the following directories may be candidates for their own volume:

/var/tmp
/var/adm
/var/adm/sw
/var/adm/crash
/var/spool
/var/mail