It is back to normal. I had to force update a few amtm packages as Entware refreshed files in init.d folderHi,
I have just done an Entware upgrade and it appears that unbound 1.13 appears not be working with unbound_manager - it does not start. I was able to start it using unbound-control
which ones?It is back to normal. I had to force update a few amtm packages as Entware refreshed files in init.d folder
cd /opt/etc/init.d
ls -lt > beforeupgrade
opkg update
opkg upgrade
ls -lt > afterupgrade
doneOnly v1.12 was published, so you may want to update the thread title.
Great description - that's exactly bare minimum that I have done yesterdayI would recommend that you update (force) any addon that creates a startup file in /opt/etc/init.d.
In my case, this was:
scribe (S01syslog-ng)
ntpmerlin (S77ntpd - see note below if you are running chrony)
unbound-manager (S61unbound)
I would recommend that you check your /opt/etc/init.d directory before updating Entware.
Something like:
Code:cd /opt/etc/init.d ls -lt > beforeupgrade opkg update opkg upgrade ls -lt > afterupgrade
Then you can compare which files where changed and update the appropriate addon.
NOTE for ntpMerlin users that are using chrony. Entware will see you have had ntpd installed, then install the newer version and also add a startup to init.d (S77ntpd).
In this case, I would recommend removing the S77ntpd file in /opt/etc/init.d. There should already be an S77chronyd file in init.d
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!