Share This:

Sometimes, a customer runs out of disk space on their ADDM appliance in /usr, and when that happens, the Services will not start.

 

First, check for "core" files in /usr/tideway/cores:

cd /usr/tideway/cores

ls -la

If there are core files, see this KA:  000028149 - ADDM: you have found one or more core files in /usr/tideway/cores. What should you do before deleting them?

 

If no core files proceed:

 

So, the question is: What files can you remove safely (as a temporary solution) from the ADDM appliance, so that you can get the Services to start??

 

Please be very careful with these commands.

 

Before removing files, it is a good idea to make sure all the services are stopped:
sudo /sbin/service tideway stop

 

You can delete your record and pool data:

 

cd /usr/tideway/var/record

rm -rf *

cd /usr/tideway/var/pool

rm -rf *

 

You can delete data that was gathered for support:

 

cd /usr/tideway/var/gather

rm *

 

You can delete all or some of your ADDM log files (but only those in /usr/tideway/log directory!):

 

cd /usr/tideway/log

rm *

 

You can also delete any core files from /usr/tideway/core, and if you take backups of ADDM, you can consider removing backups you no longer need.

 

Now, try starting the services:

sudo /sbin/service tideway start

 

FYI, how to find your top twenty largest directories and files in /usr/tideway:

du -h /usr/tideway | sort -n -r | head -n 20

 

The /usr partition has a fixed amount of space.  Even if you got a larger disk, ADDM still only uses a certain amount of space.

You should have your datastore on a separate disk.

 

See this related posting:  Trending in Support: ADDM out of disk space for datastore disk (or low on space)

 

 

See these related Knowledge Article(s):

 

000094102 - ADDM: The appliance has shut down because available disk space is low

 

000028149 - ADDM: you have found one or more core files in /usr/tideway/cores. What should you do before deleting them?

 

NOTE ABOUT DATASTORE TRANSACTION LOGS:

It is a possibility that datastore transaction logs could be filling up the /usr partition.  You should never delete datastore transaction logs.

Do this to check the size:

cd /usr/tideway/var/tideway.db/logs

du -sh

How much space are these transaction logs taking?  If they are taking less than 500 K, it probably is not the problem.

If they are the problem, you should open a Support ticket.

 

NOTE ABOUT PERSIST FILES:

It is a possibility that persist files could be filling up the /usr partition.  You should not delete persist files unless directed to by support.

Do this to check the size:

cd /usr/tideway/var/persist

du -sh

How much space are the persist files taking?  If they are taking more than a few gig, it could be the problem.

If they are the problem, you should open a Support ticket.