[apport] package netatalk failed to install/upgrade:

I would greatly appriciate if this bug were fixed (ie I think that the priority should be high).

Netatalk seems to be the only sane way to set up an Apple network.

I'll try reproduce bug.

Hi Ante, its a bad bug. I can't get out this package of Synaptic and for
this I can't install or update anything without getting this annoying
Error. Sometimes it stops installing because of the bug. I need Netatalk
to connect my I-Mac. It's the only thing that does this.

Theo

Ante Karamatić schrieb:
> I'll try reproduce bug.
>
> ** Changed in: netatalk (Ubuntu)
> Importance: Undecided => Medium
> Status: Confirmed => In Progress
>
>

Interesting. What kernel do you use? Cause, I can reproduce this on Gutsy, but not on Feisty.

For a quick fix, if you need only file sharing, setting ATALKD_RUN and PAPD_RUN in /etc/default/netatalk to 'no' should make it possible to finish configuring netatalk (run in terminal: dpkg --configure -a). You Mac should be able to see shares then.

Hi Ante, it's the latest Version 7.x of Ubuntu (It's Feisty I think and
Kernel: initrd.img-2.6.20-16-generic
?), I can't reach the Version direct, because I use an older Version of
Ubuntu (6.06) now, on which Netatalk run very good. I will try the fix,
but I'm not shure this will work with the apt-problem. (After all, I
need PAPD as I use the Linux-Machine as a Printserver too) .
Synaptic always tell me, whenever I try to install anything, that the
new removal-script don't work. Next step is, trying an older one, but
this won't work too. So it stops with this "Error". If it will help, I
try to get the whole Text of the message.

theo

Ante Karamatić schrieb:
> Interesting. What kernel do you use? Cause, I can reproduce this on
> Gutsy, but not on Feisty.
>
> For a quick fix, if you need only file sharing, setting ATALKD_RUN and
> PAPD_RUN in /etc/default/netatalk to 'no' should make it possible to
> finish configuring netatalk (run in terminal: dpkg --configure -a). You
> Mac should be able to see shares then.
>
>

czil wrote:

> Hi Ante, it's the latest Version 7.x of Ubuntu (It's Feisty I think and

Yes, it is... And it works on my feisty, hm...

> Kernel: initrd.img-2.6.20-16-generic

uname -r - command to get kernel version, so that would be
2.6.20-16-generic. Feisty I have has -server I'll try with -generic, but
I doubt it's kernel...

Solution I said will work, but it will only fix installation of
netatalk, not netatalk it self. netatalk doesn't start cause it can't
bind to interface for some strange reason...

Here is the strace:

...
socket(PF_APPLETALK, SOCK_DGRAM, 0) = 3
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
ioctl(4, SIOCGIFCONF, {64, {{"lo", {AF_INET, inet_addr("127.0.0.1")}},
{"eth1", {AF_INET, inet_addr("192.168.0.100")}}}}) = 0
close(4) = 0
ioctl(3, SIOCGIFFLAGS, {ifr_name="lo",
ifr_flags=IFF_UP|IFF_LOOPBACK|IFF_RUNNING}) = 0
ioctl(3, SIOCGIFFLAGS, {ifr_name="eth1",
ifr_flags=IFF_UP|IFF_BROADCAST|IFF_MULTICAST}) = 0
ioctl(3, SIOCGIFADDR, {ifr_name="eth1", ???}) = -1 EADDRNOTAVAIL (Cannot
assign requested address)
socket(PF_APPLETALK, SOCK_DGRAM, 0) = 4
ioctl(4, SIOCADDMULTI, 0xbff52398) = -1 EINVAL (Invalid argument)
close(4) = 0
write(2, "eth1: disabled.\n", 16eth1: disabled.
) = 16
close(3) = 0
write(2, "atalkd: zero interfaces, exiting"..., 34atalkd: zero
interfaces, exiting.
) = 34
exit_group(1) = ?

Could everybody with problem add output of 'ifconfig'?

Thanks

----- original Nachricht --------

Betreff: Re: [Bug 109917] Re: [apport] package netatalk failed to install/upgrade:
Gesendet: Fr, 03. Aug 2007
Von: Ante Karamatić<email address hidden>

> Could everybody with problem add output of 'ifconfig'?
>
> Thanks
>
> --
> [apport] package netatalk failed to install/upgrade:
> <a href='https://bugs.launchpad.net/bugs/109917' target='_blank'><u>https://bugs.launchpad.net/bugs/109917</u></a>
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--- original Nachricht Ende ----

Hi, here is my ifconfig:

earl@earl66:~$ 'ifconfig'
eth0 Protokoll:Ethernet Hardware Adresse 00:30:05:1C:C6:8C
          inet Adresse:192.168.1.13 Bcast:192.168.1.255 Maske:255.255.255.0
          inet6 Adresse: fe80::230:5ff:fe1c:c68c/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:31357 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31940 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:22092654 (21.0 MiB) TX bytes:5125231 (4.8 MiB)

eth1 Protokoll:Ethernet Hardware Adresse 00:00:E8:DC:62:31
          inet6 Adresse: fe80::200:e8ff:fedc:6231/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:6 dropped:0 overruns:0 carrier:12
          Kollisionen:102 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
          Interrupt:9 Basisadresse:0x3400

lo Protokoll:Lokale Schleife
          inet Adresse:127.0.0.1 Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:196 errors:0 dropped:0 overruns:0 frame:0
          TX packets:196 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:29072 (28.3 KiB) TX bytes:29072 (28.3 KiB)

vmnet1 Protokoll:Ethernet Hardware Adresse 00:50:56:C0:00:01
          inet Adresse:192.168.131.1 Bcast:192.168.131.255 Maske:255.255.255.0
          inet6 Adresse: fe80::250:56ff:fec0:1/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Protokoll:Ethernet Hardware Adresse 00:50:56:C0:00:08
          inet Adresse:192.168.25.1 Bcast:192.168.25.255 Maske:255.255.255.0
          inet6 Adresse: fe80::250:56ff:fec0:8/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

earl@earl66:~$

sorry, it's german. I try to get the log of synaptic...

@czil

You have misconfigured system. Your hostname is 'earl66', but you /etc/hosts doesn't contain information about it. It should have something like this:

127.0.0.1 localhost.localdomain localhost
127.0.1.1 earl66.localdomain earl66

When you fix your /etc/hosts, installing netatalk, if eth0 is wired network, will succeed.

So, czil, you don't suffer from netatalk bug, but misconfigured system.

@pirulo, Peter

Are you maybe trying to run netatalk over wireless network? Most of the wireless devices don't support Appletalk. Appletalk doesn't work on my Intel Pro Wireless 3945, but it does on wired network card - Intel Ethernet Express.

Hi,
do you think it fixes the problems with installation? I thought apt alway tells me about a mistake in the removal-script???
other installations worked before, only netatalk-package made problems. I try to add it in the "hosts", but how and where?

127.0.0.1 localhost
127.0.1.1 earl66.sepp

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

this is the file. can you help me?

thx theo
----- original Nachricht --------

Betreff: [Bug 109917] Re: [apport] package netatalk failed to install/upgrade:
Gesendet: Sa, 04. Aug 2007
Von: Ante Karamatić<email address hidden>

> @czil
>
> You have misconfigured system. Your hostname is 'earl66', but you
> /etc/hosts doesn't contain information about it. It should have
> something like this:
>
> 127.0.0.1 localhost.localdomain localhost
> 127.0.1.1 earl66.localdomain earl66
>
> When you fix your /etc/hosts, installing netatalk, if eth0 is wired
> network, will succeed.
>
> So, czil, you don't suffer from netatalk bug, but misconfigured system.
>
>
> @pirulo, Peter
>
> Are you maybe trying to run netatalk over wireless network? Most of the
> wireless devices don't support Appletalk. Appletalk doesn't work on my
> Intel Pro Wireless 3945, but it does on wired network card - Intel
> Ethernet Express.
>
> --
> [apport] package netatalk failed to install/upgrade:
> https://bugs.launchpad.net/bugs/109917
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--- original Nachricht Ende ----

Hi Ante, this works!

So I hope this will be the same I restartet the machine tomorrow ;-) Sometimes
At least, the annoying message is away. It is not running as it should now, therer wher no configfiles in the netatalkfolder but I took the ones from the old system. maybe I get it with printing
thank you very much for your help!

theo
----- original Nachricht --------

Betreff: [Bug 109917] Re: [apport] package netatalk failed to install/upgrade:
Gesendet: Sa, 04. Aug 2007
Von: Ante Karamatić<email address hidden>

> @czil
>
> You have misconfigured system. Your hostname is 'earl66', but you
> /etc/hosts doesn't contain information about it. It should have
> something like this:
>
> 127.0.0.1 localhost.localdomain localhost
> 127.0.1.1 earl66.localdomain earl66
>
> When you fix your /etc/hosts, installing netatalk, if eth0 is wired
> network, will succeed.
>
> So, czil, you don't suffer from netatalk bug, but misconfigured system.
>
>
> @pirulo, Peter
>
> Are you maybe trying to run netatalk over wireless network? Most of the
> wireless devices don't support Appletalk. Appletalk doesn't work on my
> Intel Pro Wireless 3945, but it does on wired network card - Intel
> Ethernet Express.
>
> --
> [apport] package netatalk failed to install/upgrade:
> https://bugs.launchpad.net/bugs/109917
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--- original Nachricht Ende ----

czil wrote:

> So I hope this will be the same I restartet the machine tomorrow ;-) Sometimes
> At least, the annoying message is away. It is not running as it should now, therer wher no configfiles in the netatalkfolder but I took the ones from the old system. maybe I get it with printing
> thank you very much for your help!

You could do that or 'apt-get --purge remove netatalk', 'apt-get install
netatalk'.

Hi Ante, thanks for help, everything works fine now. I think it was no
googd idea to change the system from 6.10 to 7.x. something is wrong
again with this ubuntu, but not with netatalk anymore. so it was good
work you have done. thx.

theo

Ante Karamatić schrieb:
> czil wrote:
>
>
>> So I hope this will be the same I restartet the machine tomorrow ;-) Sometimes
>> At least, the annoying message is away. It is not running as it should now, therer wher no configfiles in the netatalkfolder but I took the ones from the old system. maybe I get it with printing
>> thank you very much for your help!
>>
>
> You could do that or 'apt-get --purge remove netatalk', 'apt-get install
> netatalk'.
>
>

Hi! I have some great news (I think).
I am not sure what is the standard for choosing a host name, but Ubuntu let me pick:
foobar
I assumed that this is an acceptable host name. I know that on Mac OS X, it would look like this:
foobal.local

The problem is how hostname parses names from the /etc/hosts file.
In the configuration script for netatalk, this command is called:
hostname --short

In the man pages, it states that the --short option makes it return the host name in /etc/hosts, but cut after the first dot.
Obviously, since foobar has no dot, it returns an error.

I am not sure if this is a bug or not with hostname. Are you supposed to have a hostname with no dot? What is the significance of it?

Anyways, if it is acceptable to have a hostname with no dot, I was able to find a good workaround for the configuration script to allow both cases to work.

The line of code in one (or more) of the configuration files has this:
ATALK_NAME=`/bin/hostname --short`

This can be changed to:
ATALK_NAME=`/bin/hostname | /bin/grep -v "\." || /bin/hostname --short`

With the revised line it takes into account hostnames that come with or without dots and should solve the problem.

So now either hostname, netatalk, or some Ubuntu package which allows the user to pick a hostname needs to be fixed given the circumstances.

I'm not entirely sure how hostnames/domains work and if it varies from Linux to Mac OS X.

I hope this was helpful. Can anyone else add input? Should I or someone else try to make a patch?

I tried installing netatalk on a reasonably plain ubuntu gutsy version. It failed with:
Setting up netatalk (2.0.3-6ubuntu1) ...
Starting Netatalk services (this will take a while): eth0: disabled.
atalkd: zero interfaces, exiting.
invoke-rc.d: initscript netatalk, action "start" failed.
dpkg: error processing netatalk (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 netatalk
E: Sub-process /usr/bin/dpkg returned an error code (1)

I added my active interface to /etc/netatalk/atalk.conf and reran
sudo apt-get install netatalk
which then successfully ran. Maybe the package shoudl prompt for interface?

greetings
nicholas

Happens in Hardy too.

@Jeff - hostname returns hostname. hostname --short returns hostname without domain part (it doesn't parse /etc/hosts; it looks at /etc/hostname which has single line and returns everything before the first '.'.

@nicholas - your eth0 is wireless?

@yct - what does? As you can see, there are couple of different problems in this bug report.

@Ante - subject not adressed specifically defaults the topic/title of this page!:)
In other words - package netatalk fails to install on Hardy 8.04 32-bit.

Also, I've just tried it on Hardy 8.04.1 X86_64 generic and it installs fine!

@yct - as commented couple of times in this bug report, netatalk doesn't work if your only working interface is wireless. atalkd will quit with message 'zero interfaces'. You need to have ethernet connection to install (to be specific - start) netatalk. PPP and WiFi connection don't do appletalk.

If you would like to install netatalk without ethernet connection, set up an IP on a interface:

sudo ifconfig eth0 10.0.0.1 up

and then install netatalk.

I get a similar error with Ubuntu 8.04 i386 when installing netatalk with apt-get.
--
Unpacking netatalk (from .../netatalk_2.0.3-9_i386.deb) ...
Setting up netatalk (2.0.3-9) ...
Starting Netatalk services (this will take a while): nbp_rgstr: Connection timed out
Can't register Petra:Workstation@*
invoke-rc.d: initscript netatalk, action "start" failed.
dpkg: error processing netatalk (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 netatalk
E: Sub-process /usr/bin/dpkg returned an error code (1)
--

Of note is hat I have two physical ethernet cards and connections on eth0 and eth1. Shutting both cards with ifdown and then bringing one card up (eth0) permits installation without the error. My ifconfig (with both up) is as follows:

eth0 Link encap:Ethernet HWaddr DE:LE:TE:D.
          inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::20c:6eff:fe97:b78a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:174088 errors:0 dropped:0 overruns:0 frame:0
          TX packets:211563 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:109965451 (104.8 MB) TX bytes:207806773 (198.1 MB)
          Interrupt:16 Base address:0xa000

eth1 Link encap:Ethernet HWaddr DE:LE:TE:D.
          inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::21c:f0ff:fe0b:91d4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:24245 errors:0 dropped:0 overruns:0 frame:0
          TX packets:284 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8079180 (7.7 MB) TX bytes:46520 (45.4 KB)
          Interrupt:19 Base address:0xe000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:1494 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1494 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:78600 (76.7 KB) TX bytes:78600 (76.7 KB)

Apparently netatalk has trouble figuring out which eth to hook to when there is more than one choice. The online manual for netatalk (http://netatalk.sourceforge.net/2.0/htmldocs) helped me figure out that atalkd (part of netatalk) breaks with two ethernet connections unless you configure atalkd.conf properly. By eliminating one connection, I avoided the described nuance. Starting the second eth after installation doesn't cause an issue (other than it doesn't house a netatalk connection). It would be nice if the package installation indicated at least confusion about which port to select or no ports available. Even better would be to ask what to do as a previous poster indicated.

I got a similar problem when installing netatalk on a freshly installed intrepid system. I also have two eth cards.

root@hylton:~# aptitude
Selecting previously deselected package db4.6-util.
(Reading database ... 123130 files and directories currently installed.)
Unpacking db4.6-util (from .../db4.6-util_4.6.21-10_amd64.deb) ...
Selecting previously deselected package rc.
Unpacking rc (from .../archives/rc_1.7.1-3_amd64.deb) ...
Selecting previously deselected package netatalk.
Unpacking netatalk (from .../netatalk_2.0.3-11ubuntu1_amd64.deb) ...
Processing triggers for man-db ...
Setting up db4.6-util (4.6.21-10) ...
Setting up rc (1.7.1-3) ...

Setting up netatalk (2.0.3-11ubuntu1) ...
Starting Netatalk services (this will take a while): nbp_rgstr: Connection timed out
Can't register hylton:Workstation@*
invoke-rc.d: initscript netatalk, action "start" failed.
dpkg: error processing netatalk (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 netatalk
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up netatalk (2.0.3-11ubuntu1) ...
Starting Netatalk services (this will take a while): eth0: multicast may not work correctly.
atalkd is already running (pid = 17614), or the lock file is stale.
invoke-rc.d: initscript netatalk, action "start" failed.
dpkg: error processing netatalk (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 netatalk
Press return to continue.

root@hylton:~# hostname
hylton

root@hylton:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:85:1c:5a:e2
          inet addr:87.96.142.66 Bcast:87.96.142.127 Mask:255.255.255.192
          inet6 addr: fe80::221:85ff:fe1c:5ae2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:120632 errors:0 dropped:65958747755 overruns:0 frame:0
          TX packets:56312 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:133949125 (133.9 MB) TX bytes:5197199 (5.1 MB)
          Interrupt:251 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:1c:f0:5b:6a:d3
          inet addr:192.168.1.2 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: 2002:c0a8:102::1/64 Scope:Global
          inet6 addr: fe80::21c:f0ff:fe5b:6ad3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:41432 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51053 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4464835 (4.4 MB) TX bytes:27034855 (27.0 MB)
          Interrupt:22 Base address:0xec00

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:231561 errors:0 dropped:0 overruns:0 frame:0
          TX packets:231561 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:60563738 (60.5 MB) TX bytes:60563738...

I am running into the same problem, but I only have one connection at eth0 (in addition to lo and virbr0, which I tried disabling to no avail). Running Jaunty on 32 bits.

I was running into the same problem....I brought down virbr0, removed netatalk with synaptic and reinstalled it and it worked.