Opened 7 years ago

Closed 7 years ago

#9840 closed Bug Report - General (Fixed)

IPv6 commit breaks communication between frontend and backend on same machine.

Reported by: Greg G. <spikeygg.mythbox@…> Owned by: Raymond Wagner
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I updated git to latest master head revision yesterday (6be90d3ca5fdf0fe66a8d6380887d70785d297e2, Jun 10) and my frontend cannot communicate with my backend (same machine). Using divide and conquer I determined the problem to be contained within 8bf5157fdb844dc72e65bfc419e343b6764b58ba. My machine has two NIC ports on it but I only use one of them. I have tried putting eth0 "down" using ifconfig and the problem persists.

As requested I will attach both the frontend and backend with -v socket,network,extra as well as the output of ifconfig -a and the output of "netstat -antu".

Please let me know if you need any further information. Thanks, -Greg

Attachments (4)

debug_mythbackend.log (4.4 KB) - added by Greg G. <spikeygg.mythbox@…> 7 years ago.
mythbackend logfile with specific switches.
debug_mythfrontend.log (33.6 KB) - added by Greg G. <spikeygg.mythbox@…> 7 years ago.
mythfrontend logfile with specific switches.
debug_netstat.log (5.9 KB) - added by Greg G. <spikeygg.mythbox@…> 7 years ago.
netstat output with specific switches.
debug_ifconfig.log (1.3 KB) - added by Greg G. <spikeygg.mythbox@…> 7 years ago.
ifconfig output with specific switch.

Download all attachments as: .zip

Change History (16)

Changed 7 years ago by Greg G. <spikeygg.mythbox@…>

Attachment: debug_mythbackend.log added

mythbackend logfile with specific switches.

Changed 7 years ago by Greg G. <spikeygg.mythbox@…>

Attachment: debug_mythfrontend.log added

mythfrontend logfile with specific switches.

Changed 7 years ago by Greg G. <spikeygg.mythbox@…>

Attachment: debug_netstat.log added

netstat output with specific switches.

Changed 7 years ago by Greg G. <spikeygg.mythbox@…>

Attachment: debug_ifconfig.log added

ifconfig output with specific switch.

comment:1 Changed 7 years ago by greg

Owner: set to greg
Status: newassigned

comment:2 Changed 7 years ago by greg

Are you seeing seeing this problem?

From the looks of those output myth is never actually binding at all but also not spitting out an error.

Can you confirm for me if this is still a problem with the latest trunk code?

What distro is running on that backend?

Thanks

comment:3 Changed 7 years ago by Greg G. <spikeygg@…>

Yes, I am still experiencing this issue. Just updated to: v0.25pre-3767-gff6487b git trunk/head/master and tried enabling ipv6. Mythfrontend still complains about not being able to access the backend. I've worked around this issue by using this switch I found while googling:

echo net.ipv6.conf.all.disable_ipv6=1 > /etc/sysctl.d/disableipv6.conf

It disables ipv6 on all interfaces but requires a reboot to toggle. So checking this out is... not ideal. I'm running AMD64 release of Debian -- currently on wheezy/sid [testing].

Please do let me know if you need any more debug info.

comment:4 Changed 7 years ago by beirdo

Please try this again with current code.

comment:5 Changed 7 years ago by beirdo

Status: assignedinfoneeded

comment:6 Changed 7 years ago by Greg G. <spikeygg@…>

I have tried this again with master git from last night (Jan 29): v0.25pre-4212-g094c2d0 (094c2d09f79246ee6703e0802e6c7118ebe7e64d)

Unfortunately, the problem persists.

comment:7 in reply to:  6 Changed 7 years ago by Bill Meek <keemllib@…>

Replying to Greg G. <spikeygg@…>: ...

Unfortunately, the problem persists.

Greg, if you type: sysctl -a 2>/dev/null | grep bindv6only, do you find it set to 1 ? If so, its likely set in some file under /etc/sysctl.d/ and I'd suggest retesting with it set to 0. And if successful, what distribution are you running?

comment:8 Changed 7 years ago by Greg G. <spikeygg@…>

Thanks Bill, I tested with both ipv4 and ipv6 enabled. First, I deleted the disableipv6.conf file in sysctl.d directory and rebooted. Upon reboot, I verified that I had IPv6 addresses bound to my ethernet adapters (as well as IPv4 addresses). When attempting to run myth, the frontend could not communicate with the backend. I reinstated the disabledipv6.conf file (using the method described eariler in the ticket), rebooted again and myth works fine. I've mentioned previously in this ticket that I am running AMD64 version of Debian.

comment:9 Changed 7 years ago by beirdo

What do you have for the settings:

  • MasterServerIP (will have a host setting of NULL)
  • BackendServerIP (for each backend)

Your issue seems to be indicative of an odd setup.

That said, there is planned code about to be committed that should make this all a moot point.

comment:10 Changed 7 years ago by Greg G. <spikeygg.mythbox@…>

beirdo, I'm not sure if this is what you are asking but when I run mythtv-setup on my main machine (frontend/backend combo) both "Local Backend" and "Master Backend" are set to 192.168.0.10. It is the only backend I have in my system. I don't feel that I have an "odd setup" but something must be off with my setup because it seems that more people should be experiencing this issue. If these aren't the values you were asking about please give me more detail where I can find them.

Thanks, -Greg

comment:11 Changed 7 years ago by Raymond Wagner

Owner: changed from greg to Raymond Wagner
Status: infoneededassigned

comment:12 Changed 7 years ago by Raymond Wagner

Resolution: Fixed
Status: assignedclosed

Alter various listen servers to bind to discrete addresses.

Fixes #9840

Branch: master
Changeset: 37385baff83eea77116d13e22be96b74cfde2cec

Note: See TracTickets for help on using tickets.