My box is plugged to a TV, so I don't have a monitor to read exactly the message I have, (on My TV , it's blur). The message is something like GDM couldn't start. Unable to write in your home directory... (Press OK).
If I press OK , the login screen appears. I can't do anything else.
It's weird because it worked perfeclty yesterday. I shut it down, and the message appeared this morning when I started it up.

Version knoppmyth is R5A30.1

I looked at partitions in webmin and it says:

/dev/hda1 Linux mounted on / as ext3 0% free
/dev/hda2 Linux swap mounted a virtual memory
/dev/hda3 Linux Mounted on /cache as xfs 6% free
/dev/hda4 Linux mounted on /myth as xfs 73 % free



My problem may be the lack of space on "/". But I never save some files on this partition.

Does some one have any idea?

check your log files in /var/log

particularly mysql is bad a bout filling things up. This is definitely your problem search the forum for out of space or deleting logs.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Xsecret you are the best. It worked

I had this problem too so I changed the conf file so that mysql wouldn't keep logging every single database action (wtf why does it do that by default?). I guess that didn't fix it though, because a couple weeks later I'm back to not being able to log in again.

Edit: this time for me, it wasn't the mysql log, so I guess changing that line in the config file fixed that. It was the mythbackend.log file... hmm

Hi,

One thing that will cause error logs to grow big and fast is if you run out of cache space. Cache is used for watching live tv and will be going away if you uprade to the B.

Suggest you check mythv-setup (alt s) and set your cache size ~1gig, you can also change /cache/cache to be /myth/tv at the same. See if that is of any help.

Mike

Is the cache stored somewhere inside the myth directory and not the directory where I have recorded TV stored? That would totally explain it, because the recorded TV is a 250GB partition and the root partition is like 4GB.

Hi,
I don't recall exactly when mythtv removed the need for /cache but it was about the time A22 was released. When I saw the note in regards the live storage being in the /myth/tv directory is when I moved mine and never looked back.

Normally it is set up in the mythtv-setup to be /cache/cache but there was one error the crepted in and that was the default size was larger than the physical /cache partition. This would cause the live buffer to over fill if left in the "watch tv" mode for more than a few hours. This of course depended on the physical drive also. Mine were small drives so it happened sooner rather than later..

When the cache over filled then of course the system would report an error adding it to the log which is stored in the root partition, hence / =0 free space.

Here is what I ran to do clean up until I figured out the why... run as root.

Hope it helps you.
Mike

#!/bin/bash
#
echo "drive space starting....."
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
rm /cache/cache/*.nuv
echo " "
echo "drive space after clean-up....."
df -h
/usr/local/bin/reset-mythbackend
echo " "
/usr/local/bin/reset-mythbackend
echo " "
echo " The first time you select something it may display backend error,"
echo "click ok and then try again as it seems to be a message left over."
echo "Check your drive space storeage setup also"
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"