one minute mythweb works and I can log in fine.

http://server.domain/mythweb/tv

the next minute I get a 404... logged in and checked /var/www/mythweb and all I got was:

config images modules music_url skins video_img
data includes music php_sessions themes

so somehow some process just thought it would be a good day to delete /tv and the php files. now I'm stuck without a way to record new shows, since I have my mythbox headless in a closet. have never experienced this crap before. how could I restore mythweb to working order again? don't tell me a full re-install. don't tell me.......

everything else works, top:ed and checked. shows are recording as usual and my ipodfeed (myth2ipod) puts them there fine.

please help!


/A

Tried to download the mythplugins and cp * -R /var/www/mythweb so I could get back the mythweb.php file and the other stuff. but now when I try to visit the page, it gives me this error:

"Database Setup Error

The database environment variables are not correctly set in the
included .htaccess file. Please read through the comments included
in the file and set up the db_* environment variables correctly.

Some possible solutions are to make sure that mod_env is enabled
in httpd.conf, as well as having followed the instructions in the
README about the AllowOverride settings."

This is like a nightmare to me. Is there no chance of re-installing _only_ the mythweb package without having to wipe everything clean!?

Not sure what the answer is, but I think more info would be helpful, in particular (a) which version of KnoppMyth you were using, and (b) did you try to install anything (maybe via apt-get?) prior to MythWeb flaking out on you?

BTW, I have no "/tv" directory in /var/www/mythweb so I don't think that is part of the problem.

ok, I installed the knoppmyth version before the latest one. completely out of the box. never installed anything else besides the myth2ipod script, but that was 3 weeks ago. has been working fine until this morning.

tried to look around the forum for info on how to reinstall just mythweb, and found this thread:

http://mysettopbox.tv/phpBB2/viewtopic.php?p=63305

but when I tried to install those plugins with dpkg -i I got a dependency error. the rest of the errors following that you can find in that thread. I'm getting this sinking feeling right now.

ok, this is totally weird. it seems the mythplugins installed even though I got the dependency error. mythweb is up and running again.

I've now idea what went wrong, and will probably never know. but it's good to have the assurance that if one subsystem of knoppmyth craps out, you can probably get it back without having to reinstall everything from scratch (and that "probably" is one good reason I would never use linux in its current shape as my main OS, OSX is my man there...).

Hey, I think I know why you were getting that database error. I've got not the latest knoppmyth, but the one prior to that (pardon my lazyness). I've been installing an updated PHP5, but that required I also installed Apache2. This caused obvious problems, and thankfully I also have Webmin enabled (that's TRULY a lifesaver). I found out that with little modification, Apache2 won't run mythweb out of the box. It requires a mod_env module that Apache2 doesn't load on default (as far as I know). What I do now, is run Apache2 on port 80 for most things, and simply run the stock Apache on port 81. Then I modified the links in /var/www to support: http://mythtv:81/mythweb/mythweb.php

I hope this helps in some way. Remember, I'm no expert -- expecially with Debian! I'm a mandrake and SuSE GUI guy!

--Jeff

now I've got problem with mythweb (and others) again... but this time it seems to be the mysql server...

http://mysettopbox.tv/phpBB2/viewtopic. ... 3610#63610

I almost hate to suggest this but you may want to turn on "smart" monitoring on your disk and check it periodically. It almost sounds like your disk drive is flaking out.

Brand new seagate 120GB... shouldn't happen. But I'll do that anyhow.

So you think auto-upgrade is the only solution? (and how do you turn S.M.A.R.T. on? turns out smart is not a very determinate search-string.)

found this info on the mysql site:

Using /usr/sbin/mysqld --verbose allowed me to see that there was an unrecognized variable 'old_passwords=1', which I later found out was being set by Debian in /etc/mysql/my.cnf for some backward compatibility with *Debian* software. Removing this entry from the configuration file was all that was needed to get my server working again. This bug has been addressed by the Debian package maintainers: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321578

----------------

then I tried changing that and starting mysqld again, which gave me this in syslog:

"/usr/sbin/mysqld: unknown variable 'expire-logs-days=20'"

so I changed that too with "nano /etc/mysql/my.cnf"

changed old_passwords=1
to
#old_passwords=1


changed expire-logs-days=20
to
#expire-logs-days=20

and lo and behold, when trying /etc/init.d/mysql start it now starts!! must have made an involuntary upgrade (with apt-get perhaps?) of the mysql my.conf file!

now I've made a backup, let's restart and see if everything is back to normal.