afpd fails to start: "Failed to create entry group: Not permitted"

Bug #841772 reported by Rachel Greenham on 2011-09-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
netatalk (Ubuntu)
Undecided
Unassigned

Bug Description

After upgrade to oneiric beta, netatalk failed to start properly. First thing I did was inadvisably tell apport to not report the bug in future for this version. But I do have the files left over in /var/crash from before I did that. Which I'll upload shortly...

Next thing I did was purge it and its immediate dependencies from the system, then reinstall, but it still won't start. But this means the .crash files pre-date the reinstall. It was, at least, the same version of the software. If there's a proper way to un-ignore crashes for this software version I'll be glad to do it and re-run...

This gets logged in /var/log/syslog:

Sep 5 13:07:25 twilight afpd[4297]: AFP/TCP started, advertising 192.168.0.100:548 (2.2-beta4)
Sep 5 13:07:26 twilight afpd[4297]: Failed to create entry group: Not permitted

In Natty I had been using my own afpd.service file to advertise afpd, and I still have disable-user-service-publishing set to yes in avahi-daemon.conf (because of wanting to advertise screen sharing in a sensible way) so I kind of suspect the error message relates to that (and may well have been there in natty too) rather than having anything to do with afpd dying. But it is the only thing I can find being logged at the time of its demise, so mentioning it.

ps shows the afpd process as not running immediately afterwards.

root@twilight:/etc/avahi/services# lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10
root@twilight:/etc/avahi/services# apt-cache policy netatalk
netatalk:
  Installed: 2.2~beta4-1
  Candidate: 2.2~beta4-1
  Version table:
 *** 2.2~beta4-1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: netatalk 2.2~beta4-1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Sep 5 13:10:16 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: netatalk
UpgradeStatus: Upgraded to oneiric on 2011-09-05 (0 days ago)
mtime.conffile..etc.netatalk.AppleVolumes.default: 2011-09-05T12:55:00.243172

btw, restoring AppleVolumes.default to its oneiric-default state doesn't help.

In fact the bug does seem to relate to user service publishing. I re-enabled that in avahi-daemon.conf and restarted netatalk and it immediately sprang back into life.

A little further digging and I found the -nozeroconf option for afpd, so used that, and am now happy. :-)

I only need to turn afpd's own zeroconf registration because of the annoying and useless "<user>'s remote desktop on <hostname>' advertising for unity/gnome desktop sharing, which can only be prevented by not *enabling* desktop sharing or disabling user service publishing in avahi.

I know this isn't the netatalk team's fault that the desktop sharing team refuse to consider changing this or at least making it configurable (it's a saga that's been running a while I fear).

Perhaps I might suggest that if -nozeroconf isn't defined but it fails to register the service, it doesn't just die mysteriously, or if it does, it gives a more useful error in the process? :-)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers