Adguardhome ipk autostart not working after reboot

Installing and Using OpenWrt
21

You marked your own post as the solution.

I think @frollic gave you the solution.

22

Sorry I am new, not aware. But that the solution which @frollic suggested is working as of now.

23

So just unmark your post as the solution, and mark @frollic's post above where he gave you the S99 as the solution.

That way, it makes it easier for others who might have the same problem to go right to it.

Thanks.

24

Yes, its done. Thanks to both of you.

25

Bit late to this thread but is this something we should look to have changed in the main package? I have noticed that autostart from boot hasn't worked for me either before but the init.d script does work fine, so I figured it was some race condition with my own setup.

Should we potentially submit the start value change upstream?

26

Official AGH binary service install on OpenWrt uses:

START=95
STOP=01

Link: https://github.com/AdguardTeam/AdGuardHome/blob/e783564084c8396fa0f216103e339d9c6991981a/internal/home/service.go#L530

I had used the official binary service install for a couple of years and with that init.d setting and AGH started a boot 100% of the time.

1 Like
27

Thanks for this and for @frollic looking at the existing start/stop values and identifying the issue. I think it needs to be changed upstream to avoid the race condition that's being hit on startup.

I'll look to submit a PR with the init.d script values updated to avoid this.

1 Like
28

Pull request has been sent for this change to the master branch. At some point it should be cherry-picked down to 21.02.

Thanks to OP for raising this, @frollic for highlighting the fix and @WildByDesign for flagging the AdGuard Home procd init script values being used.

3 Likes
29

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.