Description of problem: The supplied avahi-daemon will drop advertised remote printers after their TTL ends (4500s). This means that the remote printer will not be usable any more. Pinpointed to the Mageia supplied avahi 0.6.31 by directly copying the avahi-daemon binary from a Fedora Core 22 installation (0.6.31-43) and replacing the current /usr/sbin/avahi-daemon (On the remote machine) with this. Then the entries are kept as expected. Restarting the advertising avahi-daemon will reload the ttl and get the printers back. Version-Release number of selected component (if applicable): avahi-0.6.31-16 How reproducible: Always Steps to Reproduce: 1. Set up remote printers for CUPS and make sure they are advertised by avahi 2. Run avahi-browse -vt _ipps._tcp to verify 3. Wait 4500 seconds (75 minutes) 4. Rerun avahi-browse -vt _ipps._tcp and the printers are gone Seems like either 1. We need the patches that Fedora applies or 2. There is a bug in the Mageia patches
Have to add to this that the "transplanted" avahi-daemon also failed in the same way after some time (did probably not wait long enough), so disregard that part of the report. The same binary does work in a Fedora setup, so there is still a difference somewhere. And the original problem persists. Will test a fresh Ubuntu tomorrow.
Assignee: bugsquad => shlomif
CC: (none) => doktor5000
Does this happen with an avahi-daemon built from source? It may be an upstream problem.
Haven't tried, and the Ubuntu behaviour does indicate upstream. On the other hand Fedora works quite fine... All the same avahi version.
Also the fact that moving the working avahi-daemon from a Fedora installation to Mageia makes it fail actually points to the environment (conifg? Systemd? Other helpers?) more that the daemon itself. Always hard to figure out the weird logic in Pottering generated programs, complicated design and poor documentation generally.... I would also like to point out that the printserver runs Fedora FC23 if it makes a difference.
Hi Dag Nygren, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
CC: (none) => marja11
Still a problem. Chaning version to Mageia 6,
Version: 5 => 6
(In reply to Dag Nygren from comment #6) > Still a problem. Chaning version to Mageia 6, Which is now no longer supported; sorry. Would you like to say whether the problem persists in Mageia 7?
CC: (none) => lewyssmithAssignee: shlomif => bugsquad
(In reply to Lewis Smith from comment #7) > (In reply to Dag Nygren from comment #6) > > Still a problem. Chaning version to Mageia 6, > Which is now no longer supported; sorry. > Would you like to say whether the problem persists in Mageia 7? No reply, so closing as OLD Dag, if this issue still exists in Mageia 7 or 8-cauldron, then please reopen this report and change "Version:" in the upper left of this report.
Resolution: (none) => OLDStatus: NEW => RESOLVED