Search results

If I'm understanding your setup, it should work as described - assuming that the subnet mask (e.g. 255.255.255.0) defined for the subnet in question includes the range of IP addresses you're talking about. As an example, I have one router configuration where the first 29 IP addresses (i.e. *.2...

The above log entries were generated by the previously installed MerlinAU script (i.e. *before* the 1.5.9 version update). You will likely need to review and rework your syslog-ng configuration settings when filtering the slightly modified log entries starting from MerlinAU 1.5.9 version; then...

Ah, OK, my apologies. I should have made it clear in the release notes (as I did when the v3.2.9 BETA development version was issued) that you must run the following 2 commands even if the BETA version was never installed: /jffs/scripts/scribe stable /jffs/scripts/scribe forceupdate The reason...

Could you both post the "/opt/etc/syslog-ng.conf" file that was installed with the latest v3.2.9 production release update? The latest version of the configuration file has a "2026-Feb-01" date stamp at the top of its header, and the critical changes are in the "source src" statement (see the...

Release Notes for Scribe v3.2.9 production version now available [2026-Feb-07] 1) IMPROVED: Modified code to be able to filter the initial log messages generated during the reboot process when syslog-ng has not yet been started. 2) IMPROVED: Modified code regarding the UI messages to be clear...

@thelonelycoder, A cousin of mine was having some issues with Diversion after installing the latest 5.4.6 version about 3 weeks ago, so he asked me to take a look. After reviewing his setup and double-checking the 'dnsmasq.conf' file, I found out that when enabling dnsmasq logging, some dnsmasq...

I don't like changing the original timestamps of the log entries, especially in situations where I'm trying to troubleshoot/debug issues occurring during the reboot sequence. IMO, the "dawn-of-time" timestamps (before NTP is started) make it extremely fast and easy to find when/where any reboot...

Well, according to the original code written by @cmkelley, updates are not allowed when in that state. Frankly, I don't know the exact reason(s) for it. The original code has a very explicit check for syslog-ng running before any script update is allowed to start, so I can only assume @cmkelley...

Thank you for testing and providing feedback. Glad the latest code is working well for you. You can find the initial description of the 2 problems I was trying to address in post #141. Essentially, during the reboot process, there is a deluge of log messages that get generated while all the...

Ah, OK. Yes, that's definitely intentional and the original behavior set by @cmkelley. When syslog-ng is not running, the main menu options are trimmed down to only what's considered essential or useful at that point.

Release Notes for Scribe v3.2.9_26013023 BETA Development Version [2026-Jan-31] 1) IMPROVED: Modified code to be able to filter the initial log messages generated during the reboot process when syslog-ng has not yet been started. 2) IMPROVED: Modified code regarding the UI messages to make...

Based on the syslog-ng documentation that I've been reading over the past few weeks (which, admittedly, is a small fraction of what's available online), Scribe is only scratching the surface of the quite extensive functionality and options currently available on syslog-ng 4.7 version, so I don't...

Correct. You do need the "A01global" logrotate configuration file as the bare minimum. As mentioned in my previous post, I've been working on a solution to get the initial reboot log entries saved into their corresponding filtered log files as opposed to just storing them all into the messages...

Yes, that's correct. On the uiScribe WebUI page, it can take up to ~3 minutes to fully update the individual log files if you log into the router immediately after a reboot. The log entries are not lost. What's happening is that the initial reboot log messages (i.e. about ~3 minutes worth of...

IMO, it's the currently displayed UI messages that are inaccurate and can lead to some confusion because the syslog-ng configuration "version check" does a lot more than just checking the syslog-ng "@version" number. I'll take a look and modify the UI messages to be clear about the intended...

I don't understand what you're trying to say. If you can provide clear and readable screenshots to show what you're seeing, along with a clear description and relevant context, I can answer your question.

Release Notes for Scribe v3.2.8 production version now available [2026-Jan-26] 1) FIXED: Modified code to prevent grep errors that may be generated when running "Show scribe status" while syslog-ng has not yet been started. [Thanks to @scootertramp for reporting the problem - post #155]

WRT the YazDHCP webpage, the left-most column (i.e. "Client Name (MAC Address)" + icon) of the IP address assignment table is populated using a "clientList" array variable, which is created/generated by code from the "/www/client_function.js" file. This essentially means that YazDHCP has really...

Release Notes for Scribe v3.2.7 production version now available [2026-Jan-25] 1) FIXED: When the call to Scribe found in the '/jffs/scripts/unmount' script was made *after* the Entware services had been stopped, it failed to properly reset and put back the system log files so the built-in...

Release Notes for uiDivStats v4.0.14 production version now available [2026-Jan-19] 1) FIXED: Removed a remnant function call from JavaScript code (i.e. comma()) that was causing an error when calls to show tooltips were made. [Thanks to @EmeraldDeer for reporting the problem] 2) FIXED...