I installed R5A15 but ran into two problems. First, I couldn't get the remote to work. Secondly, /dev/hda1 fills up. Not being a Linux expert, I don't know what directory or file is filling it. But the log files in /var/log seem to be rather large for both kern.log and messages. The kern.log file is filled with messages that say something like:

ivtv: ENC IRQ OVERFLOW: #2001 Stealing a buffer, 2048 currently allocated

To me that looks bad.

I think I'm going to go back to an earlier version until R5 is more stable. Already lost all my programming since I foolishly failed to backup.

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien

I got the same errors...filled up my /var/log/messages and /var/log/kern.log files

i think my front end was left on the 'view recordings' screen, the one that plays the recording in a small window.

I cleaned up the log directory and rebooted. been fine since, we'll see

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

I saw this in R5A16. Large log files were: mysql.log, mythtv.log, kern.log, sys.log, messages.log, and a couple of others that I can't remember. I went spelunking to find the big log files, deleted them, rebooted and was fine for a few days, then it happened again, and I went through the "delete log files and reboot" routine, and have been ok for about a week. This has only happened on my backend (obviously), and when dev/hda1 filled up, mythbackend would not initiate and my frontends complained about it. That's how I discovered the prob.
I saw the same "ivtv: ENC IRQ OVERFLOW: #2001 Stealing a buffer, 2048 currently allocated" error messages.
It happens...

-B

Same thing happened to me. I set logrotate to rotate and compress them every night. No problem since.

-marc

infield, would you be kind enough to detail how to set logrotate and compress?

I had another problem with R5A16 as well. I couldn't get the remote control to work with it. The remote worked just fine with all the previous releases.

Right now I'm back on the previous release since I want a stable system, but I'd really like to upgrade to R5A16 if I can find a way to make the remote work and keep it from filling the disk. I really like the new features, the LxM, and the ability to tell Myth not to record reruns.

Oh, and just in case it will do any good, I'd like to suggest that KnoppMyth reserve a portion of the hard drive as a place to backup user data during upgrades. Then an upgrade could be done painlessly and completely automatically. All the information needed should be available in the backup section.

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien

I've read that, in the case of ivtv, setting any debug-related options to 0 can help.

-brendan

First off I'm no expert so follow my suggestions at your own risk. Also I'm not home so I can't check it against my sytem but . . .

The man page for logrotate has a pretty good summery


The logrotate config file looks somthing like this



- Find the logrotate config file on your system
- Add "compress" close to the top if it's not there already
- Make sure /var/log/messages and /var/log/kern.log have entires set to daily.

I think that's it. Good luck.

Thanks!

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien

Hi,
Don't know if this is simular to your trouble with a full drive, however here is what I discovered and what I did to cure the issue. Your mileage may vary. Don't reboot as you may have a difficult time with the full drive.

My first clue was when accessing the mythweb to check the recordings, there were several php errors. I ssh'd into the mythbox, ran df -h and sure enough all was full. I don't record much so I was a little surprised that my 16 gig drive was full:)

I made a little script that saves some repeated typing and if you follow all the steps, it should not be a re-occurring issue. You can do the steps manually one at a time also, Same results.

As root, I make a directory in /myth for my tools, (this may have wait until after the cleanup) as you won't loose them with up grades.

mkdir /myth/tools
chown mythtv:mythv /myth/tools
cd /myth/tools
nano cleanup-logs (create a file, copy and paste the following code)
#<code>
#!/bin/bash
#
df -h
echo " " > /var/log/messages
echo " " > /var/log/kern.log
echo " " > /var/log/syslog
echo " " > /var/log/mythtv/mythbackend.log
echo " " > /var/log/mythtv/mythbackend.log.1
df -h
/usr/local/bin/reset-mythbackend
echo "Check your drive space storeage setup"
echo "Pre fix the cause,"
echo "Menu = Home > Setup/Utilities > Setup > TV Settings > General >page3"
echo "set AutoExpire for about 4 gig or so and New Record for ~1400 meg."
echo "Don't know for sure but I think that these values will fly ok as"
echo "it works for me"
#<end code>
use control x to save it and then run sh cleanup-logs

What it does is it erases the log contents and replaces one single space character. This will allow you to get back into mythweb and delete a couple of recordings to free up a little space to work.

Once you have done that step, doing the "Pre fix" step should stop it from happening again. Hope this is helpfull.

I am running R5A16 on an e-machine 1.3 ghz, 256 meg mem, pvr350, and was very easy to set up. I don't expect it will work well with dtv.
Mike

Standard shell idiom for truncating a file is actually:

The bare ">" is equivalent to "cat /dev/null >"

OBTW - You should really look at which logfiles are big first and kill the older compressed versions as well...

Hi,
Thanks for the feedback on the script. I am not a programmer, but did / still do a little in basic as needed:) I first learned basic on a PDP1170, long time ago.

Anyway, the echo " " > filename is not a null string (notice the space character). A null string I think would be echo "" > filename so what I am doing is simply reclaiming the 28% space of my root directory that was consumed with the error logs by reducing the log sizes to one character in length. The logs selected were determined by doing ls -al /var/log and ls -al /var/log/mythtv

After the logs are reduced to a beginning size, I have the script restart the backend. May not be needed all the time, but the restart was needed for my box because when the root got full, the backend stopped because it couldn't write any more errors. With the backend running, you can then fix things and delete a couple of unwanted recordings using the browser.

I try to put all tweaks into a script form so they are exactly repeatable as my goal is to be able to change a harddrive, install, or upgrade (same machine) and return to the same stable state each time. I'm not quite there yet.

Any help and guidence is always welcomed:)
Mike

I have experienced this problem of the log being full as well. After running this following script that was posted I could then log into mythtv account again and access the frontend to watch recordings and such. However now all my programming and scheduling information is gone and I can't get it back. I have gone through mythtv-setup and checked my settings and ran mythfilldatabase several times to no avail. Everytime i run mythfilldatabase it ends with saying Authorization Failure, any thoughts anywone?

_________________
Thervey

Sempron 2400+
512mb PC2700
Asus A7v8x-x
PVR-250
GeForce2 32mb
R5A16
Current Prognosis: Looking good! List of things left to get working is the remotet. Any suggestions?

Hi thervey,

You might try this to fire off the remote, it was posted on the forum or wiki some place. There may be some tweaks you have to do for mapping but this does bring the pvr350 remote to life with no change.

# /etc/init.d/lirc start && update-rc.d lirc defaults

I put this stuff in a script in my favorite /myth/tools just in case of an upgrade
nano fix-lirc
#<code>
#!/bin/sh
#
#I keep a copy of the working file just in case
#cp /myth/tools/lircrc /home/mythtv/.mythtv/lircrc
/etc/init.d/lirc start && update-rc.d lirc defaults
#<end code>

Hope it works for the 250 also
Mike

Ran the snippet of code you posted and you were right, it did bring the remote to life. How do you map the buttons on the remote? Currently all the buttons do anything but what they are labeled as. Thanks!

_________________
Thervey

Sempron 2400+
512mb PC2700
Asus A7v8x-x
PVR-250
GeForce2 32mb
R5A16
Current Prognosis: Looking good! List of things left to get working is the remotet. Any suggestions?

Hi thervey,

Glad that helped I have never changed any of my button map so you may have to learn on your own and the share with everyone. I have seen some posts in regards to mapping topics

nano /home/mythtv/.mythtv/lircrc
will show what is current for each label and allow you to edit them. Worse thing you could do is mess it up differently but you know how to fix that part now.

I don't know if you made a "tools" directory, but if you did then do a quick back up of the file before you start. I believe there is a tool with in KnoppMyth that you may also run to edit the buttons. Try a few searches with remote as a key to see if that gives you some better help.

Half the fun of KnoppMyth is the learning experience

Mike

as root,
#<code>
# mkdir /myth/tools
# chown mythtv:mythtv /myth/tools
# cp /home/mythtv/.mythtv/lircrc /myth/tools
# echo "now you have a back up copy"
#<end code>