I got mythbackend running. I gambled that I had got all the SQL code right
and ran it manually. That got DBSchemaVer up to 1347, seems OK. then I ran
aetc/init.d/mythtv-backend restart. That upgræded DBSchemaVer to 1348 and
did a bunch of other stuff without any problems.
so far so good.
Then it died with:
2017-08-03 02:27:20.857412 I [27769/27769] CoreContext housekeeper.cpp:706 (Start) - Starting HouseKeeper.
2017-08-03 02:27:20.873567 I [27769/27769] CoreContext serverpool.cpp:422 (listen) - Listening on TCP 0.0.0.0:6544
2017-08-03 02:27:20.874681 I [27769/27769] CoreContext serverpool.cpp:422 (listen) - Listening on TCP [::]:6544
2017-08-03 02:27:20.874735 I [27769/27769] CoreContext serverpool.cpp:422 (listen) - Listening on TCP 0.0.0.0:6554
2017-08-03 02:27:20.874779 I [27769/27769] CoreContext serverpool.cpp:422 (listen) - Listening on TCP [::]:6554
2017-08-03 02:27:20.874858 E [27769/27769] CoreContext serverpool.cpp:437 (listen) - Failed listening on TCP 0.0.0.0:6549 - Error 10: Operation on socket is not supported
2017-08-03 02:27:20.874878 I [27769/27769] CoreContext serverpool.cpp:454 (listen) - No IPv4 support on this system. Disabling MythTV IPv4.
2017-08-03 02:27:20.874915 E [27769/27769] CoreContext serverpool.cpp:437 (listen) - Failed listening on TCP [::]:6549 - Error 10: Operation on socket is not supported
2017-08-03 02:27:20.874928 I [27769/27769] CoreContext serverpool.cpp:463 (listen) - No IPv6 support on this system. Disabling MythTV IPv6.
2017-08-03 02:27:20.874942 E [27769/27769] CoreContext mediaserver.cpp:111 (Init) - MediaServer: WebSocketServer Create Error
2017-08-03 02:27:20.889206 I [27769/27769] CoreContext main_helpers.cpp:687 (run_backend) - Main::Registering HttpStatus Extension
2017-08-03 02:27:20.890239 C [27769/27769] CoreContext main_helpers.cpp:700 (run_backend) - Backend exiting, MainServer initialization error.
It turns out that if the http_proxy environment variable is set, mythbackend
tries to listen on port 6549 using my local squid proxy. Which fails. Of
course.
this is insane.
and what's really bizarre is that mythbackend DOESN'T try to do that for ports
6544 or 6554. WTF? Why go out of your way to do the wrong thing for just one
of the three ports you're listening on?
I've been seeing errors like "Failed listening on TCP [::]:6549 - Error
10: Operation on socket is not supported" for years with myth but just ignored
them because they've been non-fatal up until now - myth devs do a lot of
strange things but myth mostly works OK. I gave up stressing about non-fatal
myth bugs years ago.
This has been reported in the myth bug tracker and ignored for at least 5
years. It seems the myth devs don't understand what the problem is.
https://code.mythtv.org/trac/ticket/10633#comment:12
Anyway, the solution is to edit /etc/default/mythtv-backend and add:
unset http_proxy
just to be sure, I also added:
unset https_proxy
mythbackend is now running.
craig
PS: I expect that this will prevent any data fetching scripts (e.g.
imdb) that mythbackend might use from using my proxy. annoying but not a
show-stopper. If I have to, I can transproxy it.
--
craig sanders <cas@???>
