Project

General

Profile

Bug #2083

Timemachine fails to start after reboot and, probably, stops by itself after a couple of weeks

Added by bolar about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
App
Target version:
Start date:
07/12/2016
Due date:
% Done:

100%


Description

I have installed Amahi Time Machine, it has been working fine for a year(at least I hope so) :D. Some time ago i discovered that it didn't work. I found out that netatalk had stopped. I started Netatalk manually and everything is fine for a couple of weeks when it stops again.
If I reboot my HDA it does't start. I've been searching through some scripts but I can't find out how timemachine starts. I'm considering to try uninstall/install "timemachine" and hope it will work :D (Amahi TM doesn't show in the finder of my mac)

From the terminal line after reboot of HDA with status, start and status of netatalk:

[root@home ~]# systemctl status netatalk
● netatalk.service - File and Printer sharing for Macintosh clients
Loaded: loaded (/usr/lib/systemd/system/netatalk.service; disabled)
Active: inactive (dead)
[root@home ~]# systemctl start netatalk
[root@home ~]# systemctl status netatalk
● netatalk.service - File and Printer sharing for Macintosh clients
Loaded: loaded (/usr/lib/systemd/system/netatalk.service; disabled)
Active: active (exited) since Tue 2016-07-12 11:01:27 CEST; 3s ago
Process: 1555 ExecStart=/bin/sh -c exec /usr/libexec/netatalk/netatalk.sh (code=exited, status=0/SUCCESS)
Main PID: 1555 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/netatalk.service
├─1561 /usr/sbin/cnid_metad -l log_note
└─1564 /usr/sbin/afpd -U uams_dhx.so,uams_dhx2.so -g nobody -c 20 ...
[root@home ~]# 

http://paste.fedoraproject.org/390306/14683400

Any idea to solution?

boot.log.rtf (1.86 KB) bolar, 07/12/2016 09:21 AM

History

#1 Updated by cpg about 3 years ago

  • Description updated (diff)
  • Status changed from New to Assigned
  • Assignee set to cpg

This is strange. I have been thinking about this -- maybe hard drive issues? like storage issues or perhaps even hardware issues?

#2 Updated by cpg almost 3 years ago

By the way, I notice the service is disabled, somehow, which may be why it stops sometimes (e.g. on reboots or if it ever crashed). Amahi never disables a service without user intervention, however.

In any case, try this to re-enable the service:

systemctl enable netatalk

#3 Updated by cpg almost 3 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from cpg to bolar

If it works, please close this bug.

#4 Updated by bolar almost 3 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100

I belive it works! Service is enabled and reboot is performed, and service is running!

Thnx!!!

Also available in: Atom