What's new

uiScribe uiScribe - Custom System Log page for "scribed" logs

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I wanted to note that uiScribe seems to cause the System Log page to freeze on my 87U with 13.1. This happened a while ago, and I uninstalled it; I forgot why I uninstalled it and reinstalled it. No errors in the log though. Uninstalled it and I'm back to normal. I assume it is working fine for others. I customized the logs displayed to delete the crash log and the wclevent log (not important for), and when I opened the syslog segment it froze.
I have the same lag and eventual freeze on my AC86U. The lag is immediate on installation, takes a few seconds for any mouse or keyboard input to respond. After a few hours it will freeze and I have to use the "service restart_httpd" in an SSH terminal to get webgui access.

I disable all but messages, skynet, and afpd (Apple Time Machine backup). Merlin 384.13.0

I removed uiScribe, and I'm back to Loggly to monitor.
This usually happens when the WebUI is trying to load very large log files. Check the file sizes of the relevant .log files in /opt/var/log

Anything over 1-2MB is going to cause httpd to struggle. I advise setting up smaller log minsizes/more frequent log rotation using Scribe/syslog-ng config files.
 
This usually happens when the WebUI is trying to load very large log files. Check the file sizes of the relevant .log files in /opt/var/log

Anything over 1-2MB is going to cause httpd to struggle. I advise setting up smaller log minsizes/more frequent log rotation using Scribe/syslog-ng config files.
I am impacted by this and have some large log files. Do you mind pointing me in the right direction to either make the log rotation more frequent or lower the log max size? I looked at the syslog-ng.conf and logrotate conf file but not exactly sure what I need to change. Thanks in advance.
 
I am impacted by this and have some large log files. Do you mind pointing me in the right direction to either make the log rotation more frequent or lower the log max size? I looked at the syslog-ng.conf and logrotate conf file but not exactly sure what I need to change. Thanks in advance.
elorimer pointed you to the scribe thread where we are discussing this, I just want to say if you have more questions on the logrotate.d filters ask in that thread. I have most of them and will be happy to post the ones that I know work.
 
elorimer pointed you to the scribe thread where we are discussing this, I just want to say if you have more questions on the logrotate.d filters ask in that thread. I have most of them and will be happy to post the ones that I know work.

Please share - I need to tweak mine ... :).

Back on topic - I have found a "treasure" in uiScribe that I never realised was THE answer for cutting out the clutter in the Webgui uiScribe page which I don't want to see every time I open it. In my case the incessant dcd crashes wrought by buggy Asus closed source code and the wlcevents that are now many times more prolific under latest Asus stock code included in 384.14-beta [also an Asus closed source bug - these events should ONLY appear in Debug logging mode].

Simply open uiScribe in amtm - select option 1 "Customise list of logs displayed ..." and when the list comes up - simply punch the numbered items on the list which you would prefer NOT to see. You can always toggle them back on again if and when you wish.

THANKS @Jack Yaz for such a useful feature :D {thumbs Up}
 
Please share - I need to tweak mine ... :).

Back on topic - I have found a "treasure" in uiScribe that I never realised was THE answer for cutting out the clutter in the Webgui uiScribe page which I don't want to see every time I open it. In my case the incessant dcd crashes wrought by buggy Asus closed source code and the wlcevents that are now many times more prolific under latest Asus stock code included in 384.14-beta [also an Asus closed source bug - these events should ONLY appear in Debug logging mode].

Simply open uiScribe in amtm - select option 1 "Customise list of logs displayed ..." and when the list comes up - simply punch the numbered items on the list which you would prefer NOT to see. You can always toggle them back on again if and when you wish.

THANKS @Jack Yaz for such a useful feature :D {thumbs Up}
With the new scribe 2.2.0 release and testing, I'm now using the same ones that cmkelley has included in the examples directory.
Code:
/opt/share/syslog-ng/examples/

Some were modified along the way with testings, as you know. I think the only new one is the "afpd" filter that scrapes Apple Time Machine messages to their own log file.
 
With the new scribe 2.2.0 release and testing, I'm now using the same ones that cmkelley has included in the examples directory.
Code:
/opt/share/syslog-ng/examples/

Some were modified along the way with testings, as you know. I think the only new one is the "afpd" filter that scrapes Apple Time Machine messages to their own log file.

Thanks - but I thought you had tweaks to the logrotate.d filters which members may benefit from.
 
I tried scribe and uiScribe, but it wasn't the script I was looking for.
How can I uninstall scribe?
(uiScribe offers an uninstaller)
 
I tried scribe and uiScribe, but it wasn't the script I was looking for.
How can I uninstall scribe?
(uiScribe offers an uninstaller)
In the scribe menu
Code:
 zs.   Remove scribe
 
You might try the syslog-ng rewrite rules. Don't know what might happen.

EDIT: I played around with it but the .ash codes don't work in the webgui.
 
Last edited:
Basic highlighting is possible, i.e. this bit:

upload_2020-3-13_10-4-21.png


actually syntax highlighting the log message would be quite difficult to achieve
 
could we have syntax-highlighting?
Basic highlighting is possible, i.e. this bit:

View attachment 21887

actually syntax highlighting the log message would be quite difficult to achieve
Please don't. One of things I loathe about certain linux distributions is that looking at the log files in less is almost impossible because of the embedded escape sequences for the colors.

EDIT: Let me re-phrase that. Please don't do in in the logfile itself. Whatever you do in uiScribe is up to you, just don't add escape sequences to the logfiles.
 
Last edited:
Please don't. One of things I loathe about certain linux distributions is that looking at the log files in less is almost impossible because of the embedded escape sequences for the colors.

EDIT: Let me re-phrase that. Please don't do in in the logfile itself. Whatever you do in uiScribe is up to you, just don't add escape sequences to the logfiles.
Wouldn't dream of it. Editing the logfiles themselves would play havoc with anyone forwarding them on to another log system, as well as viewing them in plain text viewers/editors!
 
I played with a few escape sequences and they didn't work for me in the webgui display. Curious is all and I don't mean to fool more with it.

But just to be clear, the way to forward logfiles on to another system, like loggly or its sister, is to have separate configuration files that come first, without the final flag. And syslog-ng allows you to rewrite them anyway you might please, or for that matter reorder them to appear in a SQL-like grouping. You don't edit the logfiles, you write them in a different format. So in theory you could insert the escape sequences if they were viewable in some other way. That is the way I rewrite the messages template.
 

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!
Top