Disk Enclosures
Showing results for 
Search instead for 
Did you mean: 

ARMServer logs

Eric Kaiser

ARMServer logs

under /var/opt/hparray/log I have a ton of logs going back quite some time. Is there a way to clean out some of these logs. They are not that huge but do take up some much needed space under /var. Any help would be most appreciated...
Alex Glennie
Honored Contributor

Re: ARMServer logs

Kill ARMServer (NOT kill -9, just kill)

cd /var/opt/hparray/log/

Delete the log files and the LOGCATLG


Restart ARMServer
Eric Kaiser

Re: ARMServer logs

Great, but 1 question. Kill rather than /sbin/init.d/hparray stop ????
Insu Kim
Honored Contributor

Re: ARMServer logs

Logs there accumulate continously because there is AutoRAID attached to the system.
Log file is created at a given interval and is also generated when something wrong happend in AutoRAID.
The maximum file size is fixed so the new log file will be created if log file exceeds file size limitation.
Without these files, we can't assure what components of AutoRAID are causing any problems.
Please keep track of these files if you need more space.
Be aware that you need to leave the most of the latest logs with the lastest timestamps for troubleshooting.
One more thing is if you stop "hparray deamon" in /sbin/init.d, These log files will not created any more until daemon is back online.

Never say "no" first.
Darrel Louis
Honored Contributor

Re: ARMServer logs


Below the procedure to cleanup the armserver log files:

1. Stop ARMServer daemon
/sbin/init.d/hparray stop

2. Backup /var/opt/hparray/log to tape or another filesystem

3. Remove everything in array log directory
cd /var/opt/hparray/log
pwd (to ensure we are in the log directory rm -i *)
Note: Always exercise caution when using a wildcard with rm. The -i option
will force you to confirm deletion of each file

4. Create empty catalog file in /var/opt/hparray/log

5. Restart the ARMServer daemon
/sbin/init.d/hparray start

The logs in /var/opt/hparray/log are viewed with /opt/hparray/bin/logprint. You can do 1 of 2 things:

1. View them to see if you have any errors and delete after you don't find any errors.


2. Leave a couple of weeks of logs and delete the rest.
New log file is created every time system is rebooted.

You can view the files with the logprint command, see "man logprint".

Good Luck