unix error

[999said999]

Hi everyone,
I am new to hp-unix servers, and need help solving the following errors:

unexpected exit:
LANG=C LC-ALL=C /usr/sam/lbin/samx -c -n -p 5445 -s nia /usr/sam/lib/nia.ui exit with a non-zero exit status

vxfs: msg001: vx-nospace - dev/vg00/lvol8 file system full

NOQUEUE low on space (have 27 SMTP - DAEMON needs 101 in /var/spool/mqueue

thanks

[Dennis Handly]

>vxfs: msg001: vx-nospace - dev/vg00/lvol8 file system full

(The other two may be related.)

You have too much space used on lvol8. Do a bdf to see what filesystem is there and clean up files.

[S.N.S]

Hi,
(For the no space error)
The bdf on my server gives something like this:

bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 819200 347328 468800 43% /
/dev/vg00/lvol1 1835008 127224 1694536 7% /stand
/dev/vg00/lvol8 8912896 5146640 3738592 58% /var
/dev/vg00/lvol7 7733248 2665824 5027896 35% /usr
.. .. .. .. ..
.. .. .. .. ..


You would need to either free up the LV - lvol8 by deleting unwanted/backed up directories & files from the Mounted on directory
Or lvextend as per standard procedures.

HTH
SNS

[Rita C Workman]

If lvol8 on your server is /var, then one real quick way to get space back is to cleanup old committed patches.
I'm guessing you, or anyone else there, haven't done this in awhile.

Try running:

cleanup -c 1

Agree to commit the patches and see if that doesn't reduce /var for you.

Then take the other folks advise and look and see what logfiles you can cleanup or at least reduce the size.
Example of some patches on /var
/var/adm/syslog/syslog.log
/var/adm/syslog/mail.log
/var/adm/cron/log
/var/opt/omni (logilfes)
...and so on...and so on....

Regards,
Rita

[Rita C Workman]

oops, sorry typo:

Example of some patches on /var

should say

Example of some logfiles on /var

/rcw

[999said999]

thanks to all of you for your suggestions.
i will try them tommorrow and update you.

[doug hosking]

Also look in /var/adm/crash. You may find some very large files there. These are memory images from prior system crashes.
That's one of the first places I would look.

Getting back to the original questions, I would tend to focus on the "low on space" issue. I think it's likely that the sam issue is a secondary effect of that.

[SoorajCleris]

search in the forum with "/var full"

you will get more than 50 thread with solution

Regards,
Sooraj

[999said999]

the bdf shows that the /var is 100%
so cleanup -c 1 freed some space to 92% and I am able to work with the server.
I might need to free more space from other directories as well, but for the time being I am happy.
Thanks all

[rmueller58]

if it is /var/
I would look to see what is consuming the space, and truncate or trim logs.

it could be /ar/adm/sw/save items from depot updates, you may want to check with gurus about removing items in the save, generally these are for rolling back a depot update..

try this:

cd /var
du |sort -n

It will show what is consuming the space.

If your /var/spool/mail is large you may want to force deletions on mbox items.. Our users don't "use" this other then three system users, Even so if there are issues space constraints "root" mail mbox can get big along with any possible system user. (We have a database engine that has an account such as oracle or informix, where the mbox needs cleaned out..

su - username

mailx

you will see:
mailx Revision: 1.179.214.2 PHNE_34304 Date: 07/01/23 01:29:55 Type ? for help.
"/var/mail/root": 59 messages 59 new
>N 1 root Fri Apr 16 18:00 2020/71155 cron
N 2 root Fri Apr 16 22:05 681/7451 cron
N 3 root Sat Apr 17 05:06 414/17460 cron
N 4 root Sat Apr 17 05:39 19095/1489314 cron
N 5 root Sat Apr 17 05:55 35/823 cron
?

you can read by doing
?1
exit

or
you can DO A
?d *
exit