Something Not working correctly with hostname of router screwing up Time Machine

[ComputerSteve]

yes but what do I add to the file?

 

[ComputerSteve]

I have a services-start but all it has is #!/bin/sh inside it

 

[Jeffrey Young]

You can use the built in editor vi, or install nano from entware (if you have entware installed).

Personally, vi is a bear to use (30+ year old original editor), so I use nano. I also use WinSCP and log into the router that way so I can use notepad++ to edit scripts on the router.

 

[ComputerSteve]

You can use the built in editor vi, or install nano from entware (if you have entware installed).

Personally, vi is a bear to use (30+ year old original editor), so I use nano. I also use WinSCP and log into the router that way so I can use notepad++ to edit scripts on the router.

OK i have the file but all thats inside it is #!/bin/sh ... What would I have to add to make time machine delay start or restart at boot? Do you know?

 

[Jeffrey Young]

I have a services-start but all it has is #!/bin/sh inside it

perfect, then add something like ....

sleep 60   # sleep for 60 seconds
service restart_timemachine

also, make sure the script is executable (chmod +x services-start)

 

[Jeffrey Young]

Before you bother editing the script, perhaps reboot your router, log in via SSH and issue the service restart_timemachine first to make sure that actually works for you.

 

[ComputerSteve]

so how do you know the service start is working lol cause when I run service restart_timemachine it works but after I rebooted it doesn't look like it did anything

 

[ComputerSteve]

this is what my services-start looks like now --
#!/bin/sh
sleep 60 # sleep for 60 seconds
service restart_timemachine

 

[ComputerSteve]

@RMerlin this is my log file
Jan 19 15:19:10 avahi-daemon[6421]: Host name conflict, retrying with AC86U-DEN-431
Jan 19 15:19:11 avahi-daemon[6421]: Host name conflict, retrying with AC86U-DEN-432
Jan 19 15:19:12 avahi-daemon[6421]: Host name conflict, retrying with AC86U-DEN-433
Jan 19 15:19:33 avahi-daemon[6421]: Alias name "RT-AC86U" successfully established.
Jan 19 15:21:56 custom_script: Running /jffs/scripts/service-event (args: restart timemachine)
Jan 19 15:21:56 Timemachine: daemon is stopped
Jan 19 15:21:56 Timemachine: No disk to auto start TimeMachine
Jan 19 15:21:56 afpd[9651]: Couldn't open extension maping file /usr/etc/extmap.conf
Jan 19 15:21:56 afpd[9651]: Couldn't load extension -> type/creator mappings file "/usr/etc/extmap.conf"
Jan 19 15:21:56 afpd[9651]: Netatalk AFP/TCP listening on 192.168.1.1:548
Jan 19 15:21:56 cnid_metad[9655]: Couldn't open extension maping file /usr/etc/extmap.conf
Jan 19 15:21:56 cnid_metad[9655]: Couldn't load extension -> type/creator mappings file "/usr/etc/extmap.conf"
Jan 19 15:21:56 cnid_metad[9655]: CNID Server listening on localhost:4700
Jan 19 15:21:58 Timemachine: daemon is started
Jan 19 15:21:58 avahi-daemon[9660]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jan 19 15:21:59 avahi-daemon[9660]: Alias name "RT-AC86U" successfully established.

 

[Jeffrey Young]

Check to make sure the script is executable by entering chmod +x /jffs/services-start.

When you say that service restart_timemachine works before you reboot, do you mean the command gives you just an OK, or does the command actually resolve your issue? I am working just on the assumption that restarting the daemon is the same as enabling / disabling time machine. It may not be, and another approach is required - such using nvram and disabling time machine, followed by enabling it again.

 

[ComputerSteve]

your right I didn't do the chmod +x /jffs/services-start its working now. After reboot the name correctly fixes itself. I hope @RMerlin you can figure out maybe a way to fix this without this bad aid like service start thing lol. I appreciate all the work you do your firmware is great =)

 

[ComputerSteve]

Also thanks @Jeffrey Young =)

 

[RMerlin]

I applied the official upstream fix, we'll see how it works out since I can't test it.

avahi: cleanup: ensure entries are dead for at least 1s · RMerl/asuswrt-merlin.ng@17fa585

If a dead AvahiEntry cleanup is scheduled, and we try to schedule another one, defer the existing callback by 1s. Also remove other calls to avahi_cleanup_dead_entries. This is done to ensure that...

github.com

 

[ComputerSteve]

I applied the official upstream fix, we'll see how it works out since I can't test it.

avahi: cleanup: ensure entries are dead for at least 1s · RMerl/asuswrt-merlin.ng@17fa585

If a dead AvahiEntry cleanup is scheduled, and we try to schedule another one, defer the existing callback by 1s. Also remove other calls to avahi_cleanup_dead_entries. This is done to ensure that...

github.com

Thanks @RMerlin when you release a new test build for the RT-AC86U I will let you know if its working.

 

[ComputerSteve]

Check to make sure the script is executable by entering chmod +x /jffs/services-start.

When you say that service restart_timemachine works before you reboot, do you mean the command gives you just an OK, or does the command actually resolve your issue? I am working just on the assumption that restarting the daemon is the same as enabling / disabling time machine. It may not be, and another approach is required - such using nvram and disabling time machine, followed by enabling it again.

When this fix is applied how do I remove the services start thing? Do I just delete the file and recreate it or just remove what I have inside of it.

 

[Jeffrey Young]

If the code fix is the only thing in services_start, then just delete it.

If however, other addons have code in services_start, use the nano editor and delete the code you don't need, save the file.

 

[ComputerSteve]

I applied the official upstream fix, we'll see how it works out since I can't test it.

avahi: cleanup: ensure entries are dead for at least 1s · RMerl/asuswrt-merlin.ng@17fa585

If a dead AvahiEntry cleanup is scheduled, and we try to schedule another one, defer the existing callback by 1s. Also remove other calls to avahi_cleanup_dead_entries. This is done to ensure that...

github.com

Just so you know @RMerlin the problem is still happening on 386.5 beta 1 on my GT-AX11000. The only way I can fix this is to toggle time machine after a reboot / or running that services-start script thing. If I don't do that after reboot the time machine name changes by adding numbers to the end of it.

 

[RMerlin]

Just so you know @RMerlin the problem is still happening on 386.5 beta 1 on my GT-AX11000. The only way I can fix this is to toggle time machine after a reboot / or running that services-start script thing. If I don't do that after reboot the time machine name changes by adding numbers to the end of it.

Then you will have to wait for the Avahi devs to resolve the issue.

 

[ComputerSteve]

So I think I found maybe whats causing this issue that after reboot AVAHI doesn't set the hostname properly. It has something to do with Diversion @thelonelycoder and the Alternate blocking list (I have set to 192.168.1.4) & Exclude devices from ad-blocking (I have set to 192.168.1.3). I notice that this seems to happen Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.3. Shouldn't it be the router IP of 192.168.1.1 its joining not the exclude server IP.
Mar 2 23:59:12 avahi-daemon[5562]: Host name conflict, retrying with AX11000-DEN-419
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 192.168.1.3 on br0.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 192.168.1.4 on br0.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 192.168.1.1 on br0.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 127.0.1.1 on lo.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 192.168.1.3 on br0.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 192.168.1.4 on br0.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 127.0.1.1 on lo.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 127.0.0.1 on lo.
Mar 2 23:59:12 avahi-daemon[5562]: Host name conflict, retrying with AX11000-DEN-420
Mar 3 00:01:43 avahi-daemon[9459]: Registering new address record for 192.168.1.3 on br0.IPv4.
Mar 3 00:01:43 avahi-daemon[9459]: Registering new address record for 192.168.1.4 on br0.IPv4.
Mar 3 00:01:43 avahi-daemon[9459]: Registering new address record for 192.168.1.1 on br0.IPv4.

 

[ComputerSteve]

So I think I found maybe whats causing this issue that after reboot AVAHI doesn't set the hostname properly. It has something to do with Diversion @thelonelycoder and the Alternate blocking list (I have set to 192.168.1.4) & Exclude devices from ad-blocking (I have set to 192.168.1.3). I notice that this seems to happen Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.3. Shouldn't it be the router IP of 192.168.1.1 its joining not the exclude server IP.
Mar 2 23:59:12 avahi-daemon[5562]: Host name conflict, retrying with AX11000-DEN-419
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 192.168.1.3 on br0.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 192.168.1.4 on br0.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 192.168.1.1 on br0.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 127.0.1.1 on lo.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 192.168.1.3 on br0.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 192.168.1.4 on br0.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 127.0.1.1 on lo.
Mar 2 23:59:12 avahi-daemon[5562]: Withdrawing address record for 127.0.0.1 on lo.
Mar 2 23:59:12 avahi-daemon[5562]: Host name conflict, retrying with AX11000-DEN-420
Mar 3 00:01:43 avahi-daemon[9459]: Registering new address record for 192.168.1.3 on br0.IPv4.
Mar 3 00:01:43 avahi-daemon[9459]: Registering new address record for 192.168.1.4 on br0.IPv4.
Mar 3 00:01:43 avahi-daemon[9459]: Registering new address record for 192.168.1.1 on br0.IPv4.

Has there been any fix on this??? I still have to resolve this through SSH. I wish maybe @RMerlin could apply some type of fix to have this so the hostname doesn't constantly change. If I change a wifi setting it changes & other things cause it to change. I need to manually run service restart_timemachine