Zoneminder Ubuntu 8X and Update Manager

metallica1973 · 04-29-2010, 01:01 PM

I have a system that has very limited disk space on /var and everytime I attempt to do any updates to the system via update manager it was always error saying that there is not enough disk space. I wanted to know how I can change the download directory of the update manager to a partition with more space?

tommcd · 04-30-2010, 11:12 AM

Quote:

Originally Posted by metallica1973

I have a system that has very limited disk space on /var and everytime I attempt to do any updates to the system via update manager it was always error saying that there is not enough disk space.

How much stuff do you have in your /var/log/ directory?
I have noticed that, for whatever reason, Ubuntu seems to accumulate log files in /var/log/ a lot more than other distros that I use, like Slackware for example.
If you have a ton of log files in /var/log/, then just run from the terminal:

Code:

sudo rm /var/log/*

Note that you will get a bunch of errors saying that you can not remove the directories in /var/log/. This is ok; and it is what you want. You just want to remove the log files, and not the directories in /var/log/, like /var/log/apt/ for example.
I routinely run the above command in Ubuntu with no ill effects.
Also, how big is your root partition for Ubuntu? And do you have a separate home partition?
Hope this helps.

tredegar · 04-30-2010, 11:22 AM

You can clean out all the old (already applied) update packages with
sudo apt-get clean
Then you'll have space for the new ones.

tommcd · 04-30-2010, 11:26 AM

Quote:

Originally Posted by tredegar

You can clean out all the old (already applied) update packages with
sudo apt-get clean
Then you'll have space for the new ones.

OH Yeah!!
That is a good idea also!
Thanks for posting it Tredegar.
The OP mentioned /var, so I thought of cleaning out the log files in /var/log.

metallica1973 · 05-03-2010, 06:54 PM

I am using this system for a survellence system using zoneminder and did a

PHP Code:



 
sudo du -h /var|more 
 
5.8G    /var/lib/mysql/zm 
284K    /var/lib/mysql/mysql 
5.8G    /var/lib/mysql 
4.0K    /var/lib/update-manager 
8.0K    /var/lib/PolicyKit 
12K     /var/lib/binfmts 
20K     /var/lib/initramfs-tools 
24K     /var/lib/pam

PHP Code:



 
sudo df -h 
 
/dev/sda8             4.6G  546M  3.9G  13% / 
tmpfs                1007M     0 1007M   0% /lib/init/rw 
varrun               1007M  108K 1007M   1% /var/run 
varlock              1007M     0 1007M   0% /var/lock 
udev                 1007M  2.9M 1005M   1% /dev 
tmpfs                1007M     0 1007M   0% /dev/shm 
lrm                  1007M  2.2M 1005M   1% /lib/modules/2.6.27-17-generic/volatile 
/dev/sda1             137M   53M   78M  41% /boot 
/dev/sda10            203G   89G  104G  47% /home 
/dev/sda9             2.8G   69M  2.6G   3% /tmp 
/dev/sda6             6.9G  2.0G  4.6G  31% /usr 
/dev/sda7             6.9G  6.6G     0 100% /var

I made zoneminder use the /home directory for recording but I have to figure out why the /var/lib/mysql/zm is the way that it is. I think that I have accumilated garbage in there from before I made the change.

tommcd · 05-04-2010, 07:31 AM

So did you try cleaning out the /var/lib/mysql/zm directory?
I am not familiar with Zoneminder, so I can not say what you would happen if you empty that directory. Certainly, though, you don't need all that stuff in there. Clean it out as much as you can and you should be good.

metallica1973 · 05-04-2010, 07:46 AM

I have to see if ibdata and those log file can be iliminated.

PHP Code:



machine1@Security:~$ sudo ls -l /var/lib/mysql/ 
total 20532 
-rw-r--r-- 1 mysql root         0 2010-04-29 13:39 debian-5.0.flag 
-rw-rw---- 1 mysql mysql 10485760 2009-12-09 14:24 ibdata1 
-rw-rw---- 1 mysql mysql  5242880 2009-12-09 14:24 ib_logfile0 
-rw-rw---- 1 mysql mysql  5242880 2009-01-01 19:05 ib_logfile1 
drwxr-xr-x 2 mysql root      4096 2009-01-01 19:05 mysql 
-rw------- 1 mysql root         6 2009-01-01 19:05 mysql_upgrade_info 
drwx------ 2 mysql mysql     4096 2009-07-19 08:46 zm

metallica1973 · 05-04-2010, 07:47 AM

I have to see if ibdata and those log file can be iliminated. thanks by the way to all.

PHP Code:



machine1@Security:~$ sudo ls -l /var/lib/mysql/ 
total 20532 
-rw-r--r-- 1 mysql root         0 2010-04-29 13:39 debian-5.0.flag 
-rw-rw---- 1 mysql mysql 10485760 2009-12-09 14:24 ibdata1 
-rw-rw---- 1 mysql mysql  5242880 2009-12-09 14:24 ib_logfile0 
-rw-rw---- 1 mysql mysql  5242880 2009-01-01 19:05 ib_logfile1 
drwxr-xr-x 2 mysql root      4096 2009-01-01 19:05 mysql 
-rw------- 1 mysql root         6 2009-01-01 19:05 mysql_upgrade_info 
drwx------ 2 mysql mysql     4096 2009-07-19 08:46 zm

tommcd · 05-04-2010, 10:34 AM

Quote:

Originally Posted by metallica1973

I have to see if ibdata and those log file can be iliminated.

I would think that any log file could be eliminated. If there are any configuration files, or directories, in /var/lib/mysql/zm, then I would leave them alone. But any log file can certainly be eliminated.
Also, there may (hopefully) be some option in Zoneminder that can reduce the amount of log files that are created. If the Zoneminder folks have a wiki or some available documentation, then this would be a good place to start.

tredegar · 05-04-2010, 12:00 PM

Zoneminder is an application that monitors cameras for movement, and records video data or snapshots when it sees movement.
It uses mysql to keep track of the data it gathers. It's neat.

Depending on how you have it set up:
- How many cameras, what field(s) of view?
- What sensitivity to movement ? (Spiders in front of cameras [they like the IR LEDs] can be a problem).
- How much is recorded, at what resolution, for how long, after it is triggered?
Etc....
.......It can soon collect a huge amount of data.

If this is for a "surveillance system" as you say, then you are going to have to decide at what point (probably determined by how old the data is) you can start throwing data away because it is no longer useful or relevant.

Another approach might be to delete the oldest records when the database is nearly at the limit of the available storage.

Just how much data you need to keep depends on your idea of "surveillance".
Just how much data you can keep depends on how much storage space you can afford.