Hi,

I have been using knoppmyth for about a year now. I had some minor problems and every time I was able to fix them and continue to be happy user. I reinstalled every time new version was out, and everything was perfect.
But yesterday picture on one of my frontends froze so I went to my master backend to try end fix the problem. While trying to restart backend it froze too. Completely. I did a hard reset and all hell broke loose. I couldn't log in, and I've noticed error message during boot that mysql is not able to write to /var/lib/mysql because partition is full. I immediately remembered coming across posts here about some logs running wild. My backend is installed in a triple-boot with ubuntu and winxp (I hardly ever use them, but they are there).
I booted to ubuntu, mounted mythtv root partition and started poking around /var/log folder.
I think I was paying with interest for my year without problems because at the same time my ISP's link went down, and I couldn't consult wiki or forums for some advice. I was also struck with overwhelming stupidity combined with being very tired (it was around 2AM) and impatient so I thought what the hell I'll just delete everything in my /var/log dir and see what happens. Doing that I was able to get only 70MB of free space so I guess problem was not in logs.
I am not a newbie, but I am not a pro either. I know my way around, but I never had any serious problems with my linux machines before (that's why I switched all my machines to linux) and I know very little about logs - I am a user, not really an admin.
My question is - how much damage have I done in my moment of imapatient stupidity? What to do next? Can I patch things up? and where to look for the problem?
Now the worst part - I didn't run mythbackup for about a month.
Mea culpa, mea culpa, mea maxima culpa.

I don't think you should have any real problems, I think the logs should be recreated when necessary. Did you delete the directories inside /var/log as well?
What version of KnoppMyth are you using?
What is the size of your KM root partition?
Do you use Mythsteam?

Bruce S.

_________________
Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P
16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD,
SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080
Hauppauage Nova-T 500, Nova-T LinHes R8.6.1

Thanks Bruce,
I deleted everything including dirs.
I am using R5E50
My root partition is 6GB and I have separate partitions for /mythtv and recordings.
I don't use Mythstream.

Thanks for the info.
There might be some issues with the apps that write to subdirs.
Good, there was an issue with R5C7 not rotating log files.
Thats bigger than usual, so I can't see where you would run out of space.
In the earlier versions, the streamed files would be under the mythtv home directory, so would occupy space on the / partition, this has now been symlinked to a directory on the myth partition.

What I would suggest is having a look at /var/log and check if the subdirectories are recreated, if not you will need to recreate the following directories with the correct ownership and permissions. I would recommend halting the backend and apache to reduce any problems while the directories are absent.


Hope this helps.

Bruce S.

_________________
Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P
16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD,
SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080
Hauppauage Nova-T 500, Nova-T LinHes R8.6.1

Everything seems to work now. Thanks Bruce.
The only problem now is that mythbackup shows this at the end:



but I don't know is that related

What differences does it show right above that? This usually indicates that something is still diddling with the DB despite the backups efforts to stop all the things which could interfer. You're not using the frontend at the same time or running one of the babysitting scripts that restart the backend are you? There are also a couple "harmless" differences that can occur here, but it's hard to say without the messages.

Next time I tried to run mythbackup it couldn't complete because /myth ran out of free space. This time I was able to identify perpertrator. It was .xsession-errors which grew to 3GB. I deleted it and mythbackup finished without errors.
How can I prevent .xsession-errors from growing to big?