Mailing List Archive: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE

commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE

Oct 4, 2012, 8:19 AM

Post #1 of 8 (3123 views)

Hi,
FYI.
After upgrade to v0.26.0-2-ga49c750-dirty-20121004 BE hangs with
following error:

2012-10-04 08:58:02.329087 I Found 1 distinct programid authorities
2012-10-04 08:58:02.329338 I New static DB connectionSchedCon
2012-10-04 08:58:02.483552 I Listening on TCP 127.0.0.1:6544
2012-10-04 08:58:02.483596 I Listening on TCP 192.168.1.254:6544
2012-10-04 08:58:03.307553 I Main::Registering HttpStatus Extension
2012-10-04 08:58:03.309836 C Backend exiting, MainServer
initialization error.
2012-10-04 08:58:12.401313 I Running housekeeping thread

Reverting cb1e2844 seems to solve issue.

Some info:

[root@mythtv ~]# ifconfig
lan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
inet 192.168.1.254 netmask 255.255.255.0 broadcast 192.168.1.255
ether 6c:f0:49:b8:44:99 txqueuelen 1000 (Ethernet)
RX packets 963 bytes 579111 (565.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 875 bytes 94678 (92.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 51 base 0x8000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 0 (Local Loopback)
RX packets 538 bytes 48030 (46.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 538 bytes 48030 (46.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
inet 91.189.74.10 netmask 255.255.255.0 broadcast 91.189.74.255
ether 00:1b:21:d1:43:81 txqueuelen 1000 (Ethernet)
RX packets 2828 bytes 429977 (419.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1801 bytes 287955 (281.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xfdcc0000-fdce0000

DB settings are:
BackendServerIP: 192.18.1.254
BackendServerIP6: ::1

-br

Re: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE [ In reply to ]

raymond at wagnerrp

Oct 4, 2012, 8:39 AM

Post #2 of 8 (3078 views)

Permalink

On 10/4/2012 11:19, Warpme wrote:
> [root@mythtv ~]# ifconfig
> lan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
> inet 192.168.1.254 netmask 255.255.255.0 broadcast 192.168.1.255
> ether 6c:f0:49:b8:44:99 txqueuelen 1000 (Ethernet)
> RX packets 963 bytes 579111 (565.5 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 875 bytes 94678 (92.4 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device interrupt 51 base 0x8000
>
> DB settings are:
> BackendServerIP: 192.18.1.254
> BackendServerIP6: ::1

Your computer doesn't actually have a ::1 address because you have IPv6
completely disabled. Blank that setting.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-dev

Re: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE [ In reply to ]

warpme at o2

Oct 4, 2012, 10:26 AM

Post #3 of 8 (3071 views)

Permalink

On 10/4/12 5:39 PM, Raymond Wagner wrote:
> On 10/4/2012 11:19, Warpme wrote:
>> [root@mythtv ~]# ifconfig
>> lan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
>> inet 192.168.1.254 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> ether 6c:f0:49:b8:44:99 txqueuelen 1000 (Ethernet)
>> RX packets 963 bytes 579111 (565.5 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 875 bytes 94678 (92.4 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> device interrupt 51 base 0x8000
>>
>> DB settings are:
>> BackendServerIP: 192.18.1.254
>> BackendServerIP6: ::1
>
> Your computer doesn't actually have a ::1 address because you have
> IPv6 completely disabled. Blank that setting.
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-dev
>
Raymond,
Thx for replay.
I think it will be good to add log message that "Mainserver can't
continue due configured IP XX address is unavailable. Please make sure
Your config is OK and Your host has required IP interfaces and they are
correctly configured."

Lack of this message cost some of mine time (bisecting) which can be
greatly saved by this type of messaging in log.

-br

Re: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE [ In reply to ]

salstrom at gmail

Oct 4, 2012, 10:27 AM

Post #4 of 8 (3078 views)

Permalink

On Thu, Oct 4, 2012 at 8:19 AM, Warpme <warpme@o2.pl> wrote:
> Hi,
> FYI.
> After upgrade to v0.26.0-2-ga49c750-dirty-20121004 BE hangs with following
> error:
>
> 2012-10-04 08:58:02.329087 I Found 1 distinct programid authorities
> 2012-10-04 08:58:02.329338 I New static DB connectionSchedCon
> 2012-10-04 08:58:02.483552 I Listening on TCP 127.0.0.1:6544
> 2012-10-04 08:58:02.483596 I Listening on TCP 192.168.1.254:6544
> 2012-10-04 08:58:03.307553 I Main::Registering HttpStatus Extension
> 2012-10-04 08:58:03.309836 C Backend exiting, MainServer initialization
> error.
> 2012-10-04 08:58:12.401313 I Running housekeeping thread
>

This tripped me up on my upgrade last night as well. I ended up
reverting back to 0.25 and was going to tackle it this weekend.

Neil
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-dev

Re: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE [ In reply to ]

salstrom at gmail

Oct 4, 2012, 6:28 PM

Post #5 of 8 (3064 views)

Permalink

On Thu, Oct 4, 2012 at 8:39 AM, Raymond Wagner <raymond@wagnerrp.com> wrote:
> On 10/4/2012 11:19, Warpme wrote:
>>
>> [root@mythtv ~]# ifconfig
>> lan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
>> inet 192.168.1.254 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> ether 6c:f0:49:b8:44:99 txqueuelen 1000 (Ethernet)
>> RX packets 963 bytes 579111 (565.5 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 875 bytes 94678 (92.4 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> device interrupt 51 base 0x8000
>>
>> DB settings are:
>> BackendServerIP: 192.18.1.254
>> BackendServerIP6: ::1
>
>
> Your computer doesn't actually have a ::1 address because you have IPv6
> completely disabled. Blank that setting.
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-dev

I just tried again and in mythtv-setup the ::1 option was there but
greyed out so i could not blank it. Is there another way to do this?
As is I cannot upgrade to 0.26 because the MainServer has an
initialization error.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-dev

Re: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE [ In reply to ]

mythtv at interdog

Oct 6, 2012, 3:03 AM

Post #6 of 8 (3046 views)

Permalink

I have had the same issue when upgrading to 0.26.

My backend also doesn't have IPv6 enabled. The BackendServerIP6 entry is
greyed out in mythtv-setup, but shown as ::1 and was present in the
database. It looks to have been added recently, either as a result of the
0.25 or 0.26 upgrade.

I must agree the error message (or lack of is very confusing), no
indication of the problem, and the backend does not exit as the
housekeeping thread is still running.

The workaround, I can confirm, is going into mysql and removing the
BackendServerIP6 entry from the settings table, which then allow the
backend to start and function correctly.

Hope this helps someone.

Regards
Graham

On Thu, Oct 4, 2012 at 8:19 AM, Warpme <warpme [at] o2> wrote:
> Hi,
> FYI.
> After upgrade to v0.26.0-2-ga49c750-dirty-20121004 BE hangs with
following
> error:
>
> 2012-10-04 08:58:02.329087 I Found 1 distinct programid authorities
> 2012-10-04 08:58:02.329338 I New static DB connectionSchedCon
> 2012-10-04 08:58:02.483552 I Listening on TCP 127.0.0.1:6544
> 2012-10-04 08:58:02.483596 I Listening on TCP 192.168.1.254:6544
> 2012-10-04 08:58:03.307553 I Main::Registering HttpStatus Extension
> 2012-10-04 08:58:03.309836 C Backend exiting, MainServer initialization
> error.
> 2012-10-04 08:58:12.401313 I Running housekeeping thread
>

Re: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE [ In reply to ]

stuart at tase

Oct 6, 2012, 4:52 AM

Post #7 of 8 (3044 views)

Permalink

On Saturday 06 Oct 2012 11:03:20 Graham Chapman wrote:
> I have had the same issue when upgrading to 0.26.

I've pushed some fixes for these issues to fixes/0.26

> My backend also doesn't have IPv6 enabled. The BackendServerIP6 entry is
> greyed out in mythtv-setup, but shown as ::1 and was present in the
> database. It looks to have been added recently, either as a result of the
> 0.25 or 0.26 upgrade.

We now default to ::1 only if the address exists. If you have no IPv6 or not
that particular IPv6 address (localhost) then it's set to blank instead. This
fixes the catch22

> I must agree the error message (or lack of is very confusing), no
> indication of the problem, and the backend does not exit as the
> housekeeping thread is still running.

An error message is now shown and we will only exit if both IPv4 and IPv6
addresses are unavailable.

--
Stuart Morgan
MythTV
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-dev

Re: commit cb1e2844 (Cause backend to terminate if requested IP address is unavailable) hangs BE [ In reply to ]

salstrom at gmail

Oct 6, 2012, 8:51 AM

Post #8 of 8 (3040 views)

Permalink

On Oct 6, 2012 4:53 AM, "Stuart Morgan" <stuart@tase.co.uk> wrote:

> I've pushed some fixes for these issues to fixes/0.26
>
>
> We now default to ::1 only if the address exists. If you have no IPv6 or
not
> that particular IPv6 address (localhost) then it's set to blank instead.
This
> fixes the catch22
> An error message is now shown and we will only exit if both IPv4 and IPv6
> addresses are unavailable.
>
> --
> Stuart Morgan
> MythTV
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-dev

I have successfully upgraded my 0.25-fixes install to 0.26. Thank you for
the quick fix on this!

Neil

Mailing List Archive

Attached Files:

Attached Files: