Scribe Scribe v3.2.3 [2025-Aug-24] - Entware syslog-ng and logrotate installer for Asuswrt-Merlin

[John Fitzgerald]

I'm curious if it was intentional to list the OSR link to uiScribe and not scribe in the title?

View attachment 67567

I’ll bite.
It was intentional.
How would you like your efforts acknowledged?

I have no skin in the game here but if the question is meant to clear up a misunderstanding more easily then please let your feelings be known here.

I’m sure no offense was meant.

 

[dave14305]

I’ll bite.
It was intentional.
How would you like your efforts acknowledged?

I have no skin in the game here but if the question is meant to clear up a misunderstanding more easily then please let your feelings be known here.

I’m sure no offense was meant.

I think you’ve overlooked the obvious error that the scribe script header now incorrectly points to the uiScribe repository url. It has nothing to do with attribution or ownership. scribe and uiScribe are different repositories on github.

 

[Martinski]

I'm curious if it was intentional to list the OSR link to uiScribe and not scribe in the title?

View attachment 67567

Good eye!! That's indeed a mistake. It's fixed now. Thanks for catching it.

For clarity, the error was introduced when we migrated Scribe's original repository to the AMTM-OSR repo, so it's been there since our initial v3.2.2 release. It was simple human error - nothing else and nothing more.

 

[Martinski]

I had a minor glitch with the update on my GT-BE98 Pro. scribe lost track of the syslog.log location. Simple fix was to re-detect it within scribe utilities (su. followed by rd. in the scribe menu).

Hmmm... I wonder how Scribe loses track of the syslog.log location. In the script, there's code that figures out the location of the original syslog.log file and then stores that information in a config file. That location would (and should) not change on the same router running the same F/W, so it's a very odd scenario. Fortunately, @cmkelley had the foresight to have a mechanism in place to "re-detect" the location (via the utility menu options you described) when things go awry.

Can you elaborate on the outward signs you notice when the problem occurred?
Did you happen to see the wrong or missing entry from the "Show scribe status" menu option?

I'm just trying to get a better understanding of the problem.

Thanks.

 

[visortgw]

Hmmm... I wonder how Scribe loses track of the syslog.log location. In the script, there's code that figures out the location of the original syslog.log file and then stores that information in a config file. That location would (and should) not change on the same router running the same F/W, so it's a very odd scenario. Fortunately, @cmkelley had the foresight to have a mechanism in place to "re-detect" the location (via the utility menu options you described) when things go awry.

Can you elaborate on the outward signs you notice when the problem occurred?
Did you happen to see the wrong or missing entry from the "Show scribe status" menu option?

View attachment 67575

I'm just trying to get a better understanding of the problem.

Thanks.

Yes, the missing entry appears in the "Show scribe status" menu. I initially saw it during the update itself.

 

[cmkelley]

Good eye!! That's indeed a mistake. It's fixed now. Thanks for catching it.

View attachment 67573

For clarity, the error was introduced when we migrated Scribe's original repository to the AMTM-OSR repo, so it's been there since our initial v3.2.2 release. It was simple human error - nothing else and nothing more.

While I could have phrased my question better, it was an honest question. I was scratching my head thinking well maybe he wanted people to install uiScribe which would then install scribe? I'm the office pedant where I work, documents for release that come through me rarely escape unscathed.

Actually, I noticed it on 3.2.2 and meant to get around to submitting a pull request, but then I thought what if it's intentional?

 

[Milan]

Is there still issue with syslog-ng and adguard running on the same router that is causing issues during reboots?

 

[Martinski]

While I could have phrased my question better, it was an honest question. I was scratching my head thinking well maybe he wanted people to install uiScribe which would then install scribe?

Ah, no worries. There was nothing wrong with your question. It was simple, clear, and straightforward; there was no room for misinterpretation, IMO. Understandably, you were curious about the reason for having the wrong GitHub URL repo on the script header. Your intentions were obviously good, and as you said, "It was an honest question."

I'm the office pedant where I work, documents for release that come through me rarely escape unscathed.

LOL!! Yeah, I get it. At work, I also have had to write and review documentation (e.g. functional plus technical specs, READMEs, usability documentation, etc.), so I tend to be the pedant reviewer on my team.

Anyway, the bottom line is that, IMO, your question was phrased correctly, and I honestly don't see how it could have been taken the wrong way.

P.S.
Apologies for the belated response. This week I was extremely busy with work as I had a major deliverable due Aug 29th, right before our 3-day weekend for the Labor Day holiday here in the US.

 

[Martinski]

Yes, the missing entry appears in the "Show scribe status" menu. I initially saw it during the update itself.

OK, thanks for the information. Do you happen to know if the issue can be reproduced consistently?

I reviewed the functions that figure out the original location of the syslog.log file, and there may be some rare situations where the variable holding the path could be erroneously reset to an empty string. The reason is that there was no error checking and handling at all. I have improved the functions to avoid such unusual scenarios. The modified code is currently found only in the 'develop' branch, if you want to give it a try.

/jffs/scripts/scribe develop

 

[visortgw]

OK, thanks for the information. Do you happen to know if the issue can be reproduced consistently?

I reviewed the functions that figure out the original location of the syslog.log file, and there may be some rare situations where the variable holding the path could be erroneously reset to an empty string. The reason is that there was no error checking and handling at all. I have improved the functions to avoid such unusual scenarios. The modified code is currently found only in the 'develop' branch, if you want to give it a try.

/jffs/scripts/scribe develop

I had it happen once before, and I fixed it the same way. I updated to develop branch with no error.

 

[Martinski]

I had it happen once before, and I fixed it the same way. I updated to develop branch with no error.

Good to know. Thanks for the info.

 

[Davidncali001]

I had it happen once before, and I fixed it the same way. I updated to develop branch with no error.

I installed the Developer version of Scribe over the regular Scribe to see if it would resolve the issue I’m having, but I still can’t get the Skynet GUI stats to display in the router interface.

I’ve uninstalled both Scribe and Skynet multiple times and removed all traces of them, but the Skynet GUI stats remain blank every time.

My setup:

• Firmware: Merlin 3006.102.5
• Add-ons: Diversion, Skynet, Scribe, UIScribe

 

[Ripshod]

I installed the Developer version of Scribe over the regular Scribe to see if it would resolve the issue I’m having, but I still can’t get the Skynet GUI stats to display in the router interface.

I’ve uninstalled both Scribe and Skynet multiple times and removed all traces of them, but the Skynet GUI stats remain blank every time.

My setup:

• Firmware: Merlin 3006.102.5
• Add-ons: Diversion, Skynet, Scribe, UIScribe

Scribe doesn't affect the Skynet GUI. Which version of skynet? Which blocklist? What does the Skynet log say on the System Log page?

 

[Davidncali001]

Scribe doesn't affect the Skynet GUI. Which version of skynet? Which blocklist? What does the Skynet log say on the System Log page?

oh i had no idea. my bad. I thought it had to do with scribe.

On the System Log page everything looks normal. No errors or anything like that. Skynet is in it's own tab.

Here is the info you asked about:

Skynet v7.6.5
default Skynet blocklist

 

[dave14305]

On the System Log page everything looks normal. No errors or anything like that. Skynet is in it's own tab.

Are there any files in this directory?

ls -l /www/user/skynet/

What happens if you hit the Update Stats button or run firewall debug genstats

 

[Davidncali001]

The attached image show whats in: /www/user/skynet/

When I hit the Update Stats button inside the routers GUI, it tells me to wait while it attempts to generate stats. When I run run firewall debug genstats, I get a message on the screen that says: Generating Stats.

 

[Davidncali001]

The attached image show whats in: /www/user/skynet/

When I hit the Update Stats button inside the routers GUI, it tells me to wait while it attempts to generate stats. When I run run firewall debug genstats, I get a message on the screen that says: Generating Stats.

So I just rechecked the Skynet stats page in the routers UI and now the Skynet stats are working. I think it was the firewall debug genstats command that fixed the problem. I was having this problem for a week or two now.

Anyway, thank you dave14305!

​

 

[Ripshod]

I just rechecked the Skynet stats page in the routers UI and now the Skynet stats are working

I believe the stats update happens every 12 hours (anyone?) so there won't be any stats shown for that first 12.

 

[Twiglets]

I believe the stats update happens every 12 hours (anyone?) so there won't be any stats shown for that first 12.

My entry from the crontab [or cru l] is :

28 */12 * * * sh /jffs/scripts/firewall debug genstats #Skynet_genstats#


You always get caught by the lag .... is it working or not ???!!!

I suppose you could run it manually if you wanted ... I usually just wait