Can not access time machine

[awente]

Hi,

I've installed Amahi Time Machine. The Amahi(TM) Icon appears in my finder. But when I try to acces it via time machine or finder i got an error. finder says "Error while connecting to server amahi. Chech Servicer or IP-Adress...."

afpd.log shows this:

Code: Select all

ul 13 16:46:49.249958 afpd[19662] {main.c:148} (N:AFPDaemon): AFP Server shutting down on SIGTERM Jul 13 16:46:51.265498 afpd[21788] {status.c:719} (I:AFPDaemon): "Amahi™"'s signature is 6283DD83B0B6C5F003A152A72878EB66 Jul 13 16:46:51.266060 afpd[21788] {dsi_tcp.c:410} (I:DSI): dsi_tcp: hostname 'kruft' resolves to loopback address Jul 13 16:46:51.266113 afpd[21788] {dsi_tcp.c:260} (I:DSI): dsi_tcp: '192.168.0.111:548' on interface 'eth0' will be used instead. Jul 13 16:46:51.266131 afpd[21788] {afp_config.c:372} (N:AFPDaemon): AFP/TCP started, advertising 192.168.0.111:548 (2.2.1) Jul 13 16:46:51.266148 afpd[21788] {auth.c:1151} (I:AFPDaemon): uam: uam not found (status=-1) Jul 13 16:46:51.503992 afpd[21788] {auth.c:132} (I:AFPDaemon): uam: "DHX2" available Jul 13 16:46:51.506755 afpd[21788] {afp_avahi.c:81} (I:AFPDaemon): Registering volume 'Time Machine' with UUID: 'D8370486-5154-F0AF-1420-8F407CDD2169' for TimeMachine Jul 13 16:46:51.506803 afpd[21788] {afp_avahi.c:116} (I:AFPDaemon): Registering server 'Amahi™' with Bonjour Jul 13 16:46:51.508040 afpd[21788] {afp_avahi.c:314} (I:AFPDaemon): Successfully started avahi loop. Jul 13 16:46:51.508080 afpd[21788] {cnid.c:53} (I:AFPDaemon): Registering CNID module [last] Jul 13 16:46:51.508098 afpd[21788] {cnid.c:53} (I:AFPDaemon): Registering CNID module [dbd] Jul 13 16:46:51.508113 afpd[21788] {cnid.c:53} (I:AFPDaemon): Registering CNID module [tdb] Jul 13 16:47:40.886808 afpd[21861] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.0.100:57435 Jul 13 16:47:40.887071 afpd[21788] {main.c:214} (I:AFPDaemon): child[21860]: exited 1 Jul 13 16:47:40.887669 afpd[21788] {main.c:216} (I:AFPDaemon): child[21861]: done Jul 13 16:48:04.689514 afpd[21919] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.0.100:57439 Jul 13 16:48:04.690158 afpd[21788] {main.c:214} (I:AFPDaemon): child[21918]: exited 1 Jul 13 16:48:04.690592 afpd[21788] {main.c:216} (I:AFPDaemon): child[21919]: done Jul 13 16:48:15.766902 afpd[21939] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.0.100:57440 Jul 13 16:48:15.767477 afpd[21939] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: andreas Jul 13 16:48:15.795920 afpd[21939] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success Jul 13 16:48:15.796692 afpd[21939] {fault.c:122} (S:Default): =============================================================== Jul 13 16:48:15.796705 afpd[21939] {fault.c:123} (S:Default): INTERNAL ERROR: Signal 11 in pid 21939 (2.2.1) Jul 13 16:48:15.796712 afpd[21939] {fault.c:124} (S:Default): =============================================================== Jul 13 16:48:15.796879 afpd[21939] {fault.c:96} (S:Default): BACKTRACE: 3 stack frames: Jul 13 16:48:15.796891 afpd[21939] {fault.c:102} (S:Default): #0 /usr/sbin/afpd(netatalk_panic+0x1c) [0x7f7f18691aec] Jul 13 16:48:15.796897 afpd[21939] {fault.c:102} (S:Default): #1 /usr/sbin/afpd(+0x50bec) [0x7f7f18691bec] Jul 13 16:48:15.796912 afpd[21939] {fault.c:102} (S:Default): #2 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f7f1764c4a0] Jul 13 16:48:15.863640 afpd[21788] {main.c:219} (I:AFPDaemon): child[21939]: killed by signal 6 Jul 13 16:48:40.648421 afpd[21975] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.0.100:57444 Jul 13 16:48:40.648708 afpd[21788] {main.c:214} (I:AFPDaemon): child[21974]: exited 1 Jul 13 16:48:40.649233 afpd[21788] {main.c:216} (I:AFPDaemon): child[21975]: done Jul 13 16:58:19.042767 afpd[23343] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.0.100:57512 Jul 13 16:58:19.043032 afpd[21788] {main.c:214} (I:AFPDaemon): child[23342]: exited 1 Jul 13 16:58:19.043610 afpd[21788] {main.c:216} (I:AFPDaemon): child[23343]: done Jul 13 16:58:25.708022 afpd[23348] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.0.100:57513 Jul 13 16:58:25.708594 afpd[23348] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: andreas Jul 13 16:58:25.737596 afpd[23348] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success Jul 13 16:58:25.738767 afpd[23348] {fault.c:122} (S:Default): =============================================================== Jul 13 16:58:25.738792 afpd[23348] {fault.c:123} (S:Default): INTERNAL ERROR: Signal 11 in pid 23348 (2.2.1) Jul 13 16:58:25.738803 afpd[23348] {fault.c:124} (S:Default): =============================================================== Jul 13 16:58:25.739003 afpd[23348] {fault.c:96} (S:Default): BACKTRACE: 3 stack frames: Jul 13 16:58:25.739023 afpd[23348] {fault.c:102} (S:Default): #0 /usr/sbin/afpd(netatalk_panic+0x1c) [0x7f7f18691aec] Jul 13 16:58:25.739034 afpd[23348] {fault.c:102} (S:Default): #1 /usr/sbin/afpd(+0x50bec) [0x7f7f18691bec] Jul 13 16:58:25.739043 afpd[23348] {fault.c:102} (S:Default): #2 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f7f1764c4a0] Jul 13 16:58:25.803167 afpd[21788] {main.c:219} (I:AFPDaemon): child[23348]: killed by signal 6

any suggestions?

[bigfoot65]

Check /var/log/amahi-app-installer.log for errors.

[cpg]

looks like your HDA is at address 192.168.0.111 ... which is configured as a fixed address.

this is in the range 100-254, which is the dynamic DHCP range, ... which means the DHCP server may have given that very address to some other machine in the network. if that is the case, things could get very confusing very fast.

the actual error appears to be while getting a session from 192.168.0.100 (the first machine with DHCP range). the assumption here is that your HDA gave that IP. If not, that could be the problem in your setup.

now -- the error is a segmentation fault in netatalk, however. i supposed it could be due to it getting confused due to networking conflicts, however, it could also be due to

- out of memory
- out of disk
- bad RAM
- some other transient issue

finally, you may want to check the app installer log that @bigfoot65 pointed to (not that I just corrected the path, since it had a typo). however, it does appear that the app installed ok, since it's running and seems to be configured. it does not hurt checking.

in any case, you may want to reinstall and get your HDA strictly below IP 100.