Opened 10 years ago
Closed 10 years ago
Last modified 10 years ago
#12494 closed Bug Report - General (fixed)
Protocol version 0.87
| Reported by: | Owned by: | gigem | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.28 |
| Component: | MythTV - General | Version: | Master Head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Just upgraded my install of MythTV 0.28 to 2:0.28.0~master.20150820.d03d51d-0ubuntu0mythbuntu3, then restarted my system. All I get now is the following from mythwelcome:
"The server uses network protocol version 87, but this client only understands version 87. Make sure you are running compatible versions of the backend and frontend."
mythwelcome.log is showing lines such as:
Aug 21 09:17:28 babylon mythwelcome: mythwelcome[7442]: I CoreContext mythcorecontext.cpp:436 (ConnectCommandSocket) MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.1.234:6543 (try 1 of 5) Aug 21 09:17:28 babylon mythwelcome: mythwelcome[7442]: C CoreContext mythcorecontext.cpp:1558 (CheckProtoVersion) MythCoreContext::CheckProtoVersion(): Protocol version or token mismatch (frontend=87/(ノಠ益ಠ)ノ彡┻━┻ (No entiendo!),backend=87/??)
mythbackend.log reports:
Aug 21 09:24:43 babylon mythbackend: mythbackend[4687]: C ProcessRequest mainserver.cpp:1572 (HandleVersion) MainServer: MainServer::HandleVersion - Client sent incorrect protocol token for protocol version. Refusing connection!
Any clues? Hints? Workarounds? Looks like scheduled recordings are failing, too.
Change History (9)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
For example, firefox renders these pages differently:
comment:3 by , 10 years ago
Same issue but using mythfrontend , on Ubuntu 15.04
Upgraded from
MythTV Version : v0.28-pre-2996-g171f5f7 MythTV Branch : master Network Protocol : 86 Library API : 0.28.20150620-1 QT Version : 5.4.1 Options compiled in: linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_sdl using_taglib using_v4l2 using_x11 using_xrandr using_xv using_profiletype using_bindings_perl using_bindings_python using_bindings_php using_freetype2 using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2
comment:4 by , 10 years ago
Upgraded from 2:0.28.0~master.20150805.dba6f3b-0ubuntu0mythbuntu3 to 2:0.28.0~master.20150820.d03d51d-0ubuntu0mythbuntu3
At least, that's what Synaptic is telling me are the two most recent available versions.
comment:5 by , 10 years ago
| Owner: | set to |
|---|---|
| Status: | new → accepted |
comment:7 by , 10 years ago
Replying to David Engel <dengel@…>:
It would probably be good to document that near the #define for future trolls (speaking for myself since I started that whole thing, or at least escalated it). I suppose it could be dynamically checked in MythSocket::Validate() and MythCoreContext::CheckProtoVersion() as well.
comment:8 by , 10 years ago
Replying to David Engel <dengel@…>:
I am experiencing the same issue since updating my ubuntu 14.04 installation using the repository http://ppa.launchpad.net/mythbuntu/0.28/ubuntu
So far this fix is not in the repository ... is there a way to apply manually, or a workaround I could try? Any idea when this will be fixed in the repository? Until then my pvr is borked.
I wonder if that non-ASCII token is being treated differently in different places. It isn't new here, just has the added comment. Might be useful to know the version you upgraded from.