Author |
Message |
tzoom84
|
Posted: Wed Jul 16, 2008 9:44 pm |
|
Joined: Sat May 26, 2007 9:51 pm
Posts: 130
|
Ok so this go-around I did my best to search the boards and the web before posting. For R5.5, I just recently set up mythwelcome as tjc recommended for ACPI in his R5.5 notes. But now I get this error dialog as soon as the system is booted up with mythwelcome.
Quote: The server uses network protocol version 40, but this client only understands 31. make sure you are running compatible version of the backend and frontend. This didn't pop up when I reverted back to booting with mythfrontend. Mythfrontend still works fine with the backend. I think the error pops up whenever mythwelcome pings the backend for current and next recordings. This being because mythwelcome always says "Retrieving Recording Status" and "Retrieving Scheduled Recordings". I saw response way back from tjc that said: Quote: The versions of MythTV on your front end and back end boxes must match. Yours do not. You need to upgrade one or downgrade the other . But mine are both hosted on the same machine. And mythfrontend still communicates. Do I have to change mythwelcome from version 31 to version 40 somehow?
Otherwise, minimal hits here or on google found. Anyone ever experience this error?
Last edited by tzoom84 on Fri Jul 25, 2008 4:14 pm, edited 1 time in total.
|
|
Top |
|
 |
alien
|
Posted: Thu Jul 17, 2008 1:56 am |
|
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location:
Germany
|
Hmmm.... I've never seen anything like this before. Have you installed any additional SW since the install?
Admittedly, I haven't had a chance to install the official 5.5 version yet. I'm still stuck on a test version about a month old, but mythwelcome works fine with it.
Has anyone one else run mythwelcome successfully in 5.5?
I hope to be able to upgrade in the next week or so.... I'll let you know what happens.
_________________ ASUS AT3N7A-I (Atom 330) TBS 8922 PCI (DVB-S2)
|
|
Top |
|
 |
mythedoff
|
Posted: Thu Jul 17, 2008 9:35 am |
|
Joined: Mon Jul 31, 2006 10:41 pm
Posts: 149
|
I've have experience with that error but not in mythwelcome as I have not used it. I got that message using mythtv player on my xp box. I had to change the 31 to 40 in the config.xml file of mythtv player.
Code: <CONFIG_LastUsedProtocolVersion>40</CONFIG_LastUsedProtocolVersion>
Perhaps there is something similar for mythwelcome.
|
|
Top |
|
 |
tzoom84
|
Posted: Fri Jul 18, 2008 3:54 pm |
|
Joined: Sat May 26, 2007 9:51 pm
Posts: 130
|
mythedoff wrote: I've have experience with that error but not in mythwelcome as I have not used it. I got that message using mythtv player on my xp box. I had to change the 31 to 40 in the config.xml file of mythtv player. Code: <CONFIG_LastUsedProtocolVersion>40</CONFIG_LastUsedProtocolVersion> Perhaps there is something similar for mythwelcome.
I couldn't find a settings file for mythwelcome, with that config field. So I decided to just remove mythwelcome for now and set up auto-shutdown/wakeup without it. Best of luck to whomever runs along this issue. I'll update if I find more information. Thanks!
|
|
Top |
|
 |
tjc
|
Posted: Fri Jul 18, 2008 7:53 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Did you use the one that comes installed out of the box in R5.5 or did you install it following some old directions? The supplied version got plenty of testing prior to the release so it should just work.
|
|
Top |
|
 |
tzoom84
|
Posted: Fri Jul 18, 2008 9:05 pm |
|
Joined: Sat May 26, 2007 9:51 pm
Posts: 130
|
It was with the new install. I hadn't used mythwelcome in the last releases, from what I recall. But that's ok, I'm fine with the standard idle screen.
|
|
Top |
|
 |
alien
|
Posted: Sun Jul 20, 2008 11:03 am |
|
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location:
Germany
|
I just upgraded to 5.5 and don't have this problem.
I looked through the sql dump and didn't see anything that overrides the version.
I can think of two possibilities:
1. There is a rogue version of mythwelcome on your system. "which mythwelcome" should answer "/usr/bin/mythwelcome". If it doesn't, then that is your problem.
2. There is a rogue sql entry in your system that is overriding the version. If you do a backup, then search the /myth/backup/mythconverg.sql.gz file (uncompress it first) to see if there is anything related to mythwelcome version in your dump.
Allen
_________________ ASUS AT3N7A-I (Atom 330) TBS 8922 PCI (DVB-S2)
|
|
Top |
|
 |
tjc
|
Posted: Sun Jul 20, 2008 11:37 am |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Also make sure that you get the same results for these two commands:
Code: root@black2:~# md5sum /usr/bin/mythwelcome fa97e3f7f3949536c1a4f58d151bf566 /usr/bin/mythwelcome root@black2:~# sha1sum /usr/bin/mythwelcome 17568936cec6e23145c29e12ede191a177e190a5 /usr/bin/mythwelcome
|
|
Top |
|
 |
tzoom84
|
Posted: Sun Jul 20, 2008 3:22 pm |
|
Joined: Sat May 26, 2007 9:51 pm
Posts: 130
|
Here is what I got for those commands:
Code: root@mythtv:/# md5sum /usr/bin/mythwelcome b681b367c4b969f59b0d908a4885eb24 /usr/bin/mythwelcome root@mythtv:/# sha1sum /usr/bin/mythwelcome 0b530ef872f80b79f89a9a1df7a97aa3b066feb6 /usr/bin/mythwelcome
Doesn't seem to match. Does that mean I should maybe reinstall mythwelcome?
|
|
Top |
|
 |
tjc
|
Posted: Sun Jul 20, 2008 5:00 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
I think the problem is that you already did, and replaced the good one with a old one.
You can get the good ones back from the CD. See the rescue cd directions http://www.knoppmythwiki.org/index.php? ... AsRescueCD and copy them from the CDs /usr/bin to the one on the mounted root HD partition.
|
|
Top |
|
 |
tzoom84
|
Posted: Sun Jul 20, 2008 5:32 pm |
|
Joined: Sat May 26, 2007 9:51 pm
Posts: 130
|
tjc wrote: I think the problem is that you already did, and replaced the good one with a old one.
Hmm, old version... Well heres a quick recap since my first R5.5 install mistake,
1. Restored (mondo-boot) from a recent backup (R5F27).
2. Reinstalled R5.5 using Auto-upgrade.
3. Noticed in install guide (4.3) that my ACPI needed updates.
4. Followed mythwelcome wiki
5. Discovered error message (keeps computer from shutting down)
6. Now just booting with mythfrontend.
I haven't done too much config since, aside from loading kde and updating acpi. ...To be honest, I'm not even sure how to reinstall mythwelcome, except perhaps pull from the 0.21 cvs.
I recall a message saying there is a log of the install, but don't remember the location. Would that log provide some further insight? Or is there anything during the installation process I could have done that could have kept R5.5 from installing the new mythwelcome?
Really I don't mind sticking without mythwelcome. At this stage, its mainly just curiosity. And since a google search didn't show too many hits on this error in general, I figured it would serve good for reference.
|
|
Top |
|
 |
alien
|
Posted: Tue Jul 22, 2008 3:22 am |
|
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location:
Germany
|
Did you maybe do an apt-get that pulled in a lot of dependencies (i.e. a very long "The following packages will be upgraded" list)?
If that happened and the list was big enough to include parts of myth, you are probably going to find other things broken. It might be better to do a backup and re-install 5.5.
Allen
_________________ ASUS AT3N7A-I (Atom 330) TBS 8922 PCI (DVB-S2)
|
|
Top |
|
 |
tzoom84
|
Posted: Wed Jul 23, 2008 5:33 pm |
|
Joined: Sat May 26, 2007 9:51 pm
Posts: 130
|
The only apt-get that had significant dependancies was for kde. Although, after the warnings in the R5.5 Hints thread, I took note to check if any of the packages seemed major. Most seemed to be strictly kde related (apps, etc). But I could have overlooked something.
First I'll try recompiling from SVN. If that fails, I'll just do a reinstall and see if or if not that KDE affects anything.
|
|
Top |
|
 |
tzoom84
|
Posted: Fri Jul 25, 2008 4:14 pm |
|
Joined: Sat May 26, 2007 9:51 pm
Posts: 130
|
UPDATE:
I was able to successful recompile, but things were still acting funny in the display updates and MythWelcome not setting WakeUp settings.
So I reinstalled, and it did the trick. Thanks! Looks like things were broken in an apt-get or me moving things around.
|
|
Top |
|
 |