What's new

Entware Okay to install entware update?

JTnola

Regular Contributor
IMG_5527.jpeg
 
It must have been a while since you checked for updates. How old is your router and firmware?
Generally, it‘s OK to update.
 
I had the exact same amount of updates this morning weirdly enough. Seems to be working fine since I updated all of it.

Not sure why the update server didn't seem to be getting notified before today.
 
It must have been a while since you checked for updates. How old is your router and firmware?
Generally, it‘s OK to update.
RT-AC86
14_2_2

I realize it’s EOL. I do however routinely check for and install script etc updates. Haven’t seen an entware update show in a while.

And thank you!
To clarify, I just meant: “Are there any known issues with this particular round of entware updates?”
 
That‘s why, I checked their website and to me there‘s no changelog published.

I ran the link you posted and a Change Log was listed with a Date of April 2, 2026. No details other than version number changes and the list was long this time.

The community is waiting for your approval and go ahead, once it reaches your server.
 
Proceed with some caution with syslog-ng. There's some welcome new stuff (and a lot of bug fixes) moving from 4.7 to 4.10-2. I don't think it will break anything, but it could overwrite .conf so make a copy first.

Among other things, it introduces logrotate functionality within syslog-ng.
 
The community is waiting for your approval and go ahead, once it reaches your server.
IMHO it's not the responsibility of @thelonelycoder to approve or disapprove the installation of Entware updates. You are suggesting he is somehow personally responsible for testing every third-party addon script or Entware package, on every router, every time there's an update. That's clearly not practical. If you're concerned about a specific addon script I suggest you check the dedicated developer's thread for reported issues.
 
IMHO it's not the responsibility of @thelonelycoder to approve or disapprove the installation of Entware updates. You are suggesting he is somehow personally responsible for testing every third-party addon script or Entware package, on every router, every time there's an update. That's clearly not practical. If you're concerned about a specific addon script I suggest you check the dedicated developer's thread for reported issues.

No, you have taken what I said out of context. His adoption to his server always lags behind the other 2 servers. This allows him to test on his own machines and see if it breaks any of his scripts and determine portability. This has been happening for years. I prefer the delay and caution and attention to detail. I am not saying it's his responsibility to the whole world, I don't know where you got that... it's not even logical.
 
Jump in, the water's fine.
 
Proceed with some caution with syslog-ng. There's some welcome new stuff (and a lot of bug fixes) moving from 4.7 to 4.10-2. I don't think it will break anything, but it could overwrite .conf so make a copy first.

Among other things, it introduces logrotate functionality within syslog-ng.
I did jump in and install the Entware updates, primarily for the long awaited unbound updates. The only warning during the install was:

Code:
Collected errors:
 * resolve_conffiles: Existing conffile /opt/etc/syslog-ng.conf is different from the conffile in the new package. The new conffile will be placed at /opt/etc/syslog-ng.conf-opkg.

Syslog is running fine, along with Scribe. I haven't noticed any functionality impairment to this point, though will need to compare and reconcile the config file to determine what changes exist before updating/replacing.
 
@penguin22 I never saw that, and my existing syslog-ng.conf retains it's customisations.
 
So far all looks good after the Entware update. Was surpised to see that just running Scribe and checking status
it does a sync and updated the version in syslog-ng.conf. Then restarts syslog-ng.
 
So far all looks good after the Entware update. Was surpised to see that just running Scribe and checking status
it does a sync and updated the version in syslog-ng.conf. Then restarts syslog-ng.
I found the same, having to check status in Scribe, which then updated and continued running.
 
I did an analysis of the Scribe modified syslog-ng.conf compared to the entware updated version and none of the changes in the entware update are relevant or needed. Updating entware, then performing a status check in Scribe to sync the changes is all that is needed.
 
I am having an issue syslog-ng on my mesh nodes only. Twice now I have found syslog-ng not running and had to start it
on all three mesh nodes.

This is what I am seeing in the messages file.

2026-04-07T11:03:04.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc stop_fw_check
2026-04-07T11:03:04.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
2026-04-07T11:03:05.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc start_fw_check
2026-04-07T11:03:05.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: start fw_check)
Apr 7 11:31:57 syslogd started: BusyBox v1.25.1
Apr 7 11:31:57 kernel: klogd started: BusyBox v1.25.1 (2025-11-15 00:39:15 UTC)
Apr 7 11:31:58 rc_service: cfg_client 9941:notify_rc start_fw_check
Apr 7 11:31:58 custom_script: Running /jffs/scripts/service-event (args: start fw_check)
Apr 7 11:54:08 hostapd: wl0.1: STA 64:52:99:5a:a3:86 WPA: group key handshake completed (RSN)
Apr 7 11:54:08 hostapd: wl0.1: STA 64:52:99:5a:a4:3a WPA: group key handshake completed (RSN)
Apr 7 11:54:08 hostapd: wl0.1: STA 9c:43:1e:48:09:67 WPA: group key handshake completed (RSN)
Apr 7 11:54:08 hostapd: wl0.1: STA 54:e0:19:3c:11:85 WPA: group key handshake completed (RSN)
Apr 7 11:56:59 rc_service: cfg_client 9941:notify_rc stop_fw_check
Apr 7 11:56:59 custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
Apr 7 11:57:00 rc_service: cfg_client 9941:notify_rc start_fw_check
Apr 7 11:57:00 custom_script: Running /jffs/scripts/service-event (args: start fw_check)
Apr 7 12:19:48 dropbear[28360]: Child connection from 10.215.101.87:57578
Apr 7 12:19:48 dropbear[28360]: Pubkey auth succeeded for 'agagne' with ssh-rsa key SHA256:keSmX5Qw3wtl/V5acJCVnPuQizXAoRWJuNk0TlLjw/o from 10.215.101.87:57578
Apr 7 12:19:53 scribe:kill_logger[28512]: optmsg=[/opt/var/log/messages]
Apr 7 12:19:53 scribe:kill_logger[28512]: syslog_loc=[/tmp/syslog.log]
Apr 7 12:19:53 scribe:kill_logger[28512]: script_conf=[/jffs/addons/scribe.d/config]
Apr 7 12:19:53 kernel: klogd: exiting
Apr 7 12:19:53 syslogd exiting
2026-04-07T12:20:05.000000-04:00 xt8-garage dropbear[28360]: Exit (agagne) from <10.215.101.87:57578>: Disconnect received
2026-04-07T12:26:23.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc stop_fw_check
2026-04-07T12:26:23.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
2026-04-07T12:26:25.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc start_fw_check
2026-04-07T12:26:25.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: start fw_check)
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top