I was doing some checking around this morning trying to figure out why I had a bad recording. Turns out it was the station not me.

Anyway, in checking some of the logs I found that /var/log/mythtv/mythbackend.log was empty

When I do ls -al
It shows this


Now these are the last rollover and the one before it.
I tried killing mythbackend.log and expecting it to recreate but no dice.

I had installed babysit_backend a couple of weeks back it all seemed to work fine. I noticed that the babysit log was doing the same thing as fat as ownership as were many others.

I usually do not log in as root but rather ssh in as user mythtv and su to root.

Most recently I installed the rrdtools to monitor my mbe.
That also showed strange owner ship but I killed the most recent one and now it recreated and seems correct but is still not growing.


it won't until it needs to reset the backend. Those are rare...

I know if I check the Backend logs in Mythweb it shows me typical output I am used to seeing.

I am still pretty new to Linux any thoughts.
Should it have made a difference if I built the scripts above when I was on myKnoppix box, when I log in from that machine I have to SU my personal profile and then ssh as su into the Mythbox.

Might be rambling here, but trying to give you all the things I can remember I have done over the last 2 weeks.

Thanks for the help.
Andy
[/code]

_________________
KnoppMyth R5.5
MBE: AMD64 3400+, K8N Neo4 Plat., 1Gig, Asus Extreme N6200, 320G pata, 2x320Gsata, 750Gsata, PVR-150 Retail w/Blaster
SBE: AMD XP2000, GA 7ZMMH, 1 Gig, XFX 256M 6200, 20 Gig, PVR-150 Retail w/Blaster
SBE: AMD Dur1800, 512M, PVR500

The ownership still looks funny. Did you possibly start mythbackend as root at some point?

I recommend you stop the backend, fix the ownerships (chown mythtv:mythtv /var/log/mythtv/mythbackendlog*), then restart the backend with the correct userID. Either just reboot your box, or as root use the startup script in /etc/init.d/. I think there are also ALT keybindings for starting/stopping the backend, but have never used them.

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)

Alien, I like never use the /etc/init.d route to start or stop the backend. Can't remember for sure if I did. I'll keep looking at things>

Updated information>

Last evening after I wrote the post, I did some additonal digging around.

The only thing that came to mind was to rm the bad current file and recreate it as a standard user. My thinking that would start a new file with the appropriate permissions since they should be inherited from the acls' for the directory.

After I did this I used key bindings to stop and start the backend.

It appears this morning they are updating correctly.

When I get home this evennig, I'll post updated snaps of the directory/file ownerships.

Thanks!

Solved: The solution was to rm the files and then recreate them as the appropriate user. Probalby was an easier way to do this, but that worked for me. YMMV. it appears to be rolling those logs properly and updating as it goes along.

_________________
KnoppMyth R5.5
MBE: AMD64 3400+, K8N Neo4 Plat., 1Gig, Asus Extreme N6200, 320G pata, 2x320Gsata, 750Gsata, PVR-150 Retail w/Blaster
SBE: AMD XP2000, GA 7ZMMH, 1 Gig, XFX 256M 6200, 20 Gig, PVR-150 Retail w/Blaster
SBE: AMD Dur1800, 512M, PVR500

I downgraded this from Solved as it has resurfaced.
After I had manually created the files as the appropriate users it worked until today.
Logs roller over last night as they have been and all of a sudden I am not writing to babysit_backend.log and mythbackend.log again.

Permissions were like this.
This one seems to rollover once a week or so so it just happened.


This one rolls every morning.


Any thoughts of what I can look at that is causing the change in permissions it would seem it is something being executed in a log rollover sctipt.

I did add LVM to this box yesterday morning, actually finished at about noon on Feb 3.

Thanks for the help!

_________________
KnoppMyth R5.5
MBE: AMD64 3400+, K8N Neo4 Plat., 1Gig, Asus Extreme N6200, 320G pata, 2x320Gsata, 750Gsata, PVR-150 Retail w/Blaster
SBE: AMD XP2000, GA 7ZMMH, 1 Gig, XFX 256M 6200, 20 Gig, PVR-150 Retail w/Blaster
SBE: AMD Dur1800, 512M, PVR500

Check to see what user the backend is running as, it should be mythtv as shown here:

If the backend is getting naively restarted by root that would explain this. Also make sure that the ownership and permissions on /var/log/mythtv look like this:

Any script which are monitoring/restarting the backend should either be running as mythtv or be using /etc/init.d/mythtv-backend restart which will ensure that the daemon is started as the right user.

TJC, mine looks the same as yours for the most part.





I know I can manually create these as Mythtv user and they start working again seems to be until something rolls over the logfiles. Seems to be tied to the babysit_backend.log rollover.

I suspect that you're right...

I have tried a couple of changes to see if I can correct this issue.
I cannot see where it forces a rotation of the babysit log.
In looking at the babysit_backend tips to install it, seems the user was not su.
Might be my issue cuz I do most everythig remotely and need to su in to do that.

I looked ownership of babysit_backend.sh

ls -al babysit_backend.sh reveals:


I changed ownership and group to be mythtv:


I then went into the root crontab at /etc/crontab and tried changing the username to mythtv.
It showed it was executing, but a test by killing the backend would not set the backend.
When I look in the script some of the commands like to restart the backend start with sudo.

I changed it back to root in the crontab. Tests show it is working and restores the backend.

not sure it this is correct but it is working.

I'll need to keep an eye on it to see if it keeps working.

I'll post back when I have more info.

Ok new info
I made some changes to lircrc which required a restart. I performed that restart last evening at 21:45 hrs or there abouts.
When it restarted it caused the logs to revert ownership and they were not writing again.
Here is what they look like. The last time I did any restarts etc was Feb 5
essentially babysit_backend.log had only a couple fo entires in it but the system had been working fine.



Any thoughts on what I should look at?
I did notice it seems to have restarted the logs and changed their permissions. My log files roll over at 04:45 every morning so it follows that the permissions changed at 21:46 when the system came back up and these two logs have not written since then.

_________________
KnoppMyth R5.5
MBE: AMD64 3400+, K8N Neo4 Plat., 1Gig, Asus Extreme N6200, 320G pata, 2x320Gsata, 750Gsata, PVR-150 Retail w/Blaster
SBE: AMD XP2000, GA 7ZMMH, 1 Gig, XFX 256M 6200, 20 Gig, PVR-150 Retail w/Blaster
SBE: AMD Dur1800, 512M, PVR500