Disk space vs stability

If you have root access to your Vera, you can login as “root”, and “df -h” to see the Vera disk space usage.

NOTE: This is a major deal when it comes to upgrades since the /overlay partition has to have enough disk space for the upgrade to succeed.

I decided to keep an eye on it, especially the Vera log directory /tmp/log/cmh since it takes a LOT of disk space and fills up quickly with a LOT of devices.

My first approach was to move the log files to a USB stick. It was still filling up regularly. Vera compresses the logs, keeps under the limit, but YOU see it as sluggishness and unreliability (my feelings on this).

I would simply DELETE the LuaUPnP.log file (the big offender) and *.gz files periodically taking my Vera /tmp/log/cmh partition to about 8% used (it was always 100% when I checked).

I decided to create a script to automate this.

cd /root
vi rm_logs.sh and press “i” to go into insert mode.

add the following three lines:

rm /tmp/log/cmh/LuaUPnP.log
rm /tmp/log/cmh/*.gz
reboot

save the file (esc :wq!)

chmod 777 rm_logs.sh

Next add the following line to cron:

crontab -e (go to the bottom, and press “i” to insert)

0 0 * * * /root/rm_logs.sh

save the crontab (esc :wq!)

NOTE: You will want to consider hard before doing this. If keeping the log files past 24hrs is important to you (or Vera support), do not try this!


Waiting on my Vera Plus in hopes of a faster controller with more disk/memory. We will see.

This is the problem i think have right now not enought space for upgrading.
How can you log as root?

@hmspain - If you leave your log settings at default(without Vera USB logging, Vera will rotate the logs every night. During this rotation, it will copy your day’s logs up to the Vera servers and then delete them form your local device. With default settings, you don’t have more than 24 hours worth of logs anyway. No scripts or modifications required.

@michelhamelin - http://wiki.micasaverde.com/index.php/Logon_Vera_SSH

rom is at 100% use is it why i cannot upgrade ?

Is it why?

@michelhemelin,

The vera file system is based on OpenWrt… Do some reading on openwrt.org first as it might help you put things into perspective…

Now, your vera overlay file system indeed is full (the rom mount itself should always be 100% full as it is read-only)… I suspect some old firmware files did not get deleted after upgrades… These are in the /etc/cmh-firmware folder and can be deleted safely… HOWEVER, if you do not know how to do this in a linux shell, I would advise AGAINST you doing it yourselves as you could brick your unit… rather engage vera support to resolve your upgrade issue.

Edit: my bad…’ I did not read the df -h output properly… Your vera actually has plenty of disk space… But my comment about reaching to Vera support team if you cannot upgrade still holds :slight_smile:

@LV999

About System Monitor when it show CPU usage 1.5, is it 1.5% or 150%
My guess was 150% but Tech support told me this only 1.5% are they wrong?

Well i’t pretty hard to get over 100%

I have never seen my Vera more that 15 percent. It’s usually a couple percent.
But I believe if you have cameras being display that are accessed via Vera … that the IO can add up quickly.

Also I think the nightly-heal might put a load on Vera … but I am not awake at 3:00 AM when it does it’s heal.

CPU is often often measured by something called load factor … which is an indication of the average number of runnable processes. (For a value more than 1, it indicates a job that has something to do is delayed!) A large load factor > 1 is not good for control devices like Vera.
It’s ok for a batch processing computer …