I had to reboot my KnoppMyth machine a couple days ago because it was being flakey and when it came back up it said:

I was able to login as root (I have it to login mythtv automatically) and check the disk space. It shows 100% usage on my / mount. I have plenty left on /myth. Obviously this is the problem. My questions are: 1. I would guess that the database got huge. Is there a way to shrink it? Furthermore, would it be possible to run the database on another machine that has more disk space? If so would anyone have any instructions on doing this? 2. Is there anything else that I could delete to make more room?

Any suggestions would be helpful.

--Phekno[/code]

It's the log rolling glitch in R5C7. A search for "mysql.log" should turn up the cleanup and the fix. Ah, here it is... http://mysettopbox.tv/phpBB2/viewtopic.php?t=9261&start=18

Thanks for the help. I had just realized the problem right before I saw your post. I deleted the .log file and everything's fine for now. I'm going to follow the instructions for your fix and hopefully won't have the problem in the future. So you don't possibly have a suggestion to run the mythconverg database on a different server. I have plenty of hardware sitting around that could be used for a separate DB server for Myth only, but I would need instructions to do it. I *may* be able to get it to work but if you have any suggestions that would be greatly appreciated.

--Phekno

OK. So now I've been trying to get the KnoppMyth MySQL database set up on a different machine. I ended up using a machine running Ubuntu 6.06. I installed MySQL and MythTV so I could run the database. When I installed MythTV it asked for the root password of the MySQL database so I assume it was running the DB table creation scripts. Anyway, I went through mythtv-setup and managed to get my channels setup and when I ran mythfilldatabase I got a bunch of errors like:

I assume this is becaue I'm running a newer version of MySQL than MythTV supports but I'm not sure. Has anyone tried this? Do you have any suggestions? What am I missing?

--Phekno

There's really no need to do this, and good reasons not to do it. Once the minor logging rollover glitch is fixed the DB is very well behaved, it's disk and CPU usage are both relatively trivial compared to the frontend or even the backend. Not having it on the same box breaks assumptions in the back/restore/upgrade world as well as a number of other operationa;l scripts. If the impulse to fiddle is irresitible, knock yourself out, but if you're doing this to make the system more stable, it is far more likely to have the opposite effect.

Thanks for the reply. I did fix the log rollover issue. I agree with you in regards to not messing with it. "If it ain't broke, don't fix it." Does the program guide (what I'm guessing takes up the most space) rollover? In other words, does it only store two weeks of data? I'm guessing this is the case but just wanted to make sure. Anyway, thanks for your help.

Yes, old guide data rolls off. I think it only keeps one day back.

Thank God for this forum! My heart always skips a beat when some inane error comes up. I would hate to lose six months of recordings...

Thanks to all who make this possible! Especially you Cesman!

_________________
LinHES 8.4.3 Backend on MSI Z97 PC Mate with Pentium CPU, 16 GB DDR3 RAM, Two HD Homeruns + One HD Homerun Prime, 20 TB of storage

im having the same problem - i think - my / mount is 100% and my /myth mount is only 11%. I am not home, so i use putty to do whatever i need via ssh. i tried deleting the mysql.log - no good. I tried deleting hibernate-script - no good. df -h still shows 100% usage after a reboot. The problem i get is when I try to access it via mythweb. I dont see anything in my recorded programs or stream tv menus, and when i go to tv listings i get the error :

Fatal Error at /usr/share/mythtv/mythweb/includes/db.php, line 360:
SQL Error: Error writing file '/var/log/mysql/mysql.log' (Errcode: 28 ) [#3]

HELP!?!?

thanks,
~Eric~

Run this command as root

It will list all the directories in order of tha amount of space they're using. Let us know what the top 10 or 20 are.

I'm having the same error, but I think my problem is that /myth is full. I tried logging in as root and running mythtv to delete a recording via the interface, but i couldn't see any recordings to delete.

This is happening in my test box which only has a 20 gig hard drive, and is recording using a haup 150. I suspect it records faster than it can delete old stuff, and thus it filled up. Now I can't get it unstuck.

This happened once in a previous test rig (with a 40 gig drive), and I just had to log in as root, run mythtv and delete an old recording to get it working again. Then I tweaked the minimum free-space setting and didn't have the problem again... ...until this new test rig

I tried to delete a recording via the file system shell, but I may have just made a mess. I'd like to learn how to fix this, but I'm not above wiping the whole thing and restarting from scratch

Hi,

You guys need to tell what version you are running.
R5C7 had a log roll over issue
R5B7 not sure it's problems however one can be sure there is something, even if small
R5A series had different issues
And the R4V ...

By not having a version value, and we are thinking down one path for version R5__ and mean while you have R5__ then ideas are useless to you.

There are hundreds (thousands?) of pieces to make KnoppMyth what it is today, but things are always changing and that is where a little gotcha that some times sneaks in.

Mike

I'm running R5B7 and had the afforementioned problem with logrotate.d failing. I have since cleared the logs and fixed the logrotate problem, but now I'm having a different problem that is possibly related. Ever since the root dir filled up on my backend my frontend fails to list all recorded shows. Instead it lists one show. Every episode I've recorded of that show, but just that show. Amazingly, that show is neither alphabetically nor cronologically the first. It boggles my mind. It's obviously connecting to the backend database, but not getting all the info? Any ideas? Any suggestions to which logs I should examine?
Sorry to hijack, but I think it's related.
-UNOmar