I installed R5A26 today ( twice to verify problem.)

I can get everything to work out of the box with a Dell server, P3 512 megs ram, pci yamaha card, 2 pvr-150 cards. Everything works like it is supposed to on the local machine. I can even get my mediaMVP to work remotely with it, using mythtv protocol.

Here are the problems

any remote mythtvfrontend can not connect to it. This include the cd version off of the R5A26 cd.

THese are all v18.x clients that work fine with my older 0.18.1 server. These problems show up as soon as I have prepared the backend for remote frontends via the docs. If figured that it was a version mismatch but the install cd frontend also gets the same error.

I get some variation of the following error.

/Users/dhickman/Applications/MythFrontend.app/Contents/Resources
2005-11-21 00:00:43.506 New DB connection, total: 1
Total desktop width=2048, height=768, numscreens=2
2005-11-21 00:00:43.564 Using screen 0, 1024x768 at 0,0
2005-11-21 00:00:43.604 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2005-11-21 00:00:43.606 New DB connection, total: 2
2005-11-21 00:00:43.622 Told to create a NEW database schema, but the database
already has 69 tables.
If you are sure this is a good mythtv database, verify
that the settings table has the DBSchemaVer variable.

2005-11-21 00:00:43.623 Database Schema upgrade FAILED, unlocking.
2005-11-21 00:00:43.625 Couldn't upgrade database to new schema, exiting.


This is a fresh database, the only frontend to access it is the localhost to verify that both tuners are working.

any ideas?

Thanks

dhh

Hi dhickman,

It works fine for me, however you need to do a couple of settings to enable it. Check Xsecrets wiki for the two changes as I forget off the top of the head.

Mike

I too have a problem with the latest R5A26 and have tried a number of front end builds. I have completed the changes as suggested on other posts (MasterServerIP=NULL) and still have problems. I suspect it has to do with changes to the database schema and I am simply not matching up the right front end with the backend used in R5A26. My front ends do work correctly with R5A22 and R5A16. When reviewing the schema it looks like #1083 is listed in the settings table in R5A26 and never gets changed. Maybe a locking issue of some sort? I will keep digging to look at differences. A partial log is posted below (from the front end):


2005-11-20 14:00:09.459 Database Schema upgrade FAILED, unlocking.
2005-11-20 14:00:09.460 Couldn't upgrade database to new schema, exiting.
2005-11-20 14:11:54.754 Using runtime prefix = /Applications/MythFrontend.app/Contents/Resources
2005-11-20 14:11:54.757 New DB connection, total: 1
2005-11-20 14:11:54.773 Total desktop dim: 2960x1050, with 2 screen[s].
2005-11-20 14:11:54.781 Using screen 0, 1680x1050 at 0,0
2005-11-20 14:11:54.797 Current Schema Version:
2005-11-20 14:11:54.797 Newest Schema Version : 1101
2005-11-20 14:11:54.798 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2005-11-20 14:11:54.799 New DB connection, total: 2
2005-11-20 14:11:54.815 Told to create a NEW database schema, but the database
already has 68 tables.
If you are sure this is a good mythtv database, verify
that the settings table has the DBSchemaVer variable.

I have followed the instructions on the wiki to

comment out skip-networking and to put the real ips in the mythtv-setup.

At least I am not the only person with this problem.

BTW, I get basically the same error message from both my mac clients and the cd frontend. All of the clients can connect to my old backend.

At least dual pvr-150 is working

dhh

I upgraded from 16 to 26 and I am still using my same frontend clients/packages from the ubuntu repositories without problem (0.18.1-5). Since they work I haven't tried remote frontend from the CD. I'll try that when I get home tonight.
According to your errors it doesn't look like a mysql problem, rather a difference in the database, but I am not sure.

_________________
ASUS A7N266 Micro-ATX Motherboard
Athlon 2200 processor
512K Kingston PC2100 Memory
MicroAtx Case
2 PVR250's w/remote
eVGA e-GeForce mx4000 (64 Ram with Tv/Out (Svideo))
Lite-on DVD cd-rw combo
120 GB Western Digital

Hi,
There are a couple of places to make changes, my.cnf is one, X11 forwarding is another, mythtv-setup > general > replace 127.0.0.1 with ip-of-the-knoppmyth-box-that-you-are-using-as-the-backend. (both places) and there maybe one more. When done, reboot so everything is re-init. I don't recall details as I cheat and follow the flow in the wiki write-up. I find it much easier to remember where to go for the information than trying to remember the information.

To help ensure it will work for you, use the same cd that you installed with to run the remote frontend. Then it has to match. There are like two questions for the frontend, pick a language and replace the localhost with the ip of the backend.

There is a memory minimum on the remote frontend but I don't know what it is. You should be ok if you have a swap partition available.

That is all I know gentlemen.
Mike

elgordo123 I noticed you said you upgraded - rather than a fresh install. dhickman was yours a new install or upgrade? I seem to remember another thread suggesting some different problems between upgrading and fresh installs since in one case you have an existing database. I have been running a few test boxes - the backend I was referring to above was a fresh auto install from 26 - is it possible this is the cause? Also - I have not built a front end from the 26 sources or run from cd as I am running an os x front end and have used binarys. Since I am running test boxes, I went back to another and did a fresh install of both 16 and 22, both work with my os x front ends. That suggests something different between the fresh install of 22 and 26. Could it have to do with ownership or permissions that might be part of the table build or setup scripts? I am just throwing out ideas - I will keep digging (and try to compare the 22 install I have with the 26).

Both times it was a fresh install.

I tried it with the osx frontend and the fronend from another install.


I also tried the frontend that was on the cd.

same errors.

dhh

Hi dhickman,

My backend just crashed and I'm about to re-install the whole stuff. Just wondering whether you have solved this problem...As I'm using different remote frontends frequently I have to make a choice between R5A16 and R5A26. Do you have any GU for mysqladmin installed on your masterbackend? Can you figure out which hosts are associated with the user mythtv in the (master-)backend's database mythconverge? (with other word from which hosts the user mythtv is allowed to log on)

Regards,

Fiete

Added 11/27: After fresh install of R5A26 and following the modification as advised in the wiki it is not possible to connect to the MythTV server as remote frontend. Same error log as dhickman.

F.

Having the same problem as hickman..

2005-11-28 13:29:10.194 New DB connection, total: 1
Total desktop width=1152, height=864, numscreens=1
2005-11-28 13:29:10.203 Using screen 0, 1152x864 at 0,0
2005-11-28 13:29:10.210 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2005-11-28 13:29:10.212 New DB connection, total: 2
2005-11-28 13:29:10.216 Told to create a NEW database schema, but the database
already has 68 tables.
If you are sure this is a good mythtv database, verify
that the settings table has the DBSchemaVer variable.

2005-11-28 13:29:10.217 Database Schema upgrade FAILED, unlocking.
2005-11-28 13:29:10.217 Couldn't upgrade database to new schema, exiting.

What version do you have working? I had r5a16 nad r5a22 working great.. But no luck with r5a26..


Snake

It was R5A26 for the master backend (clean install), with multiple remote frontends (those are and will stay R5A16 or MythTV 0.18.1 (non CVS) on a SuSE distro).

Now I have switched back to R5A16 for the master backend, remote frontends are doing well

Fiete

Hi all,

I think that I have found one possible work-around for the following problem, there are others around in the forum:
-Fresh install of R5A26 to work as server (and local frontend)
-Remote fontends (running from CD or installed functioning as remote backend) can not connect to masterbackend (=server)
-For error logs see posts in this thread
-static IP adres

Possible solution (please do this on the masterbackend / server):
On master backend / server run mysql as user mythtv and mysql-user root:

password for user root is not set at install time of KnoppMyth. This will push you into >mysql
Next issue a grant privilege command for user mythtv for the database mythconverg, when connecting from the remote frontend. The remote frontend is identified by its IP adres:

Please replace 'remote-IP-adres' by the real IP adres of the remote frontend
next flush privileges

Exit mysql


Next try to connect to the masterbackend / server from the remote frontend.


Hope that it works as this is done on a MythTV install on a SuSE distro, using the same CVS MythTV as KnoppMyth.

Hope that you can remotely enjoy R5A26!!! I have the strong feeling that this in a security issue of mysql and can not be resolved by any install script.

Still the basic problem is not resolved (I'm definitely not a MySQL guru!!). What to think about dynamic IP adres assignment? Running from the CD as frontend with DHCP?

Fiete

That didn't help either..

NEXT!

I'm in the same boat. RA16 works with my Mac OS X frontend, but a fresh install of RA26 does not. It does not appear to be a mysql permissions issue. I was able to use the mysql monitor from the frontend machine with no problem like so:

mysql -u mythtv -p -h mythtv mythconverg


Where mythtv is also the hostname of the backend as well as the mysql username.

Anybody had any new insites into this?

FWIW, I have been able to get the mythtv python scripts working on two xboxes both for recorded programs and livetv. Those scripts need remote mysql access, but use samba filesharing to play the video. So I suppose that's more evidence that it's not a mysql permissions problem.

Hi,
I don't know about insight, but in this thread (post of Will) a solution is described.
http://mysettopbox.tv/phpBB2/viewtopic.php?t=7066

Fiete