Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

Tru64 eventviewer fill up /tmop with vsummsxxxx file

Pieter 't Hart
Honored Contributor

Tru64 eventviewer fill up /tmop with vsummsxxxx file

System Alphaserver DS25 with Tru64 V5.1B PK4
when starting "sysman event_viewer" /tmp in the root filesystem rapidly fills with a vsumms_root_xxxx.tmpyyyy until filesystem full or killing the event_viewer.
see attached file for "ps -ef|grep evm output
files in /var/evm/evmlog directory are moved to a different location, binary eventlog is rotated (kill -USR1).
So there is not much data to extract.

What is evmget putting in this vsumms-file?
how can i prevent filling up the root filesystem.
Thanks for any tips.
3 REPLIES
Pieter 't Hart
Honored Contributor

Re: Tru64 eventviewer fill up /tmop with vsummsxxxx file

maybe i found a clu in the sys_check output
" Operational: Very large file /var/adm/cron/log ( 551040 KB ) was found. "

after moving this file to another location
event_viewer could be started again.

I'll check it doesn't come back.
Pieter 't Hart
Honored Contributor

Re: Tru64 eventviewer fill up /tmop with vsummsxxxx file

yes that was the culprit.
eventviewer can be normally started, without filling the filesystem.
Pieter 't Hart
Honored Contributor

Re: Tru64 eventviewer fill up /tmop with vsummsxxxx file

too large /var/adm/cron/log
info found in sys_check ouput