Scribe scribe - syslog-ng and logrotate installer

[elorimer]

I believe it has to do with if something is being written to the hard drive

I think this is Broadcom's wireless service for automatic channel selection. If so that is really weird.

EDIT: @Butterfly Bones beat me to it.

 

[L&LD]

What happens when you eject the USB disk? In my case it ends all logging [syslog.log in the webgui stays totally blank after the "### Top of Log File ###" line].

Re-insert USB - does Syslog-ng start automatically? and if so - are you getting all logging activity which was not displayed while USB ejected back in Sylog.log [or in "messages" file? In my case- for e.g. there is no sign of the log entry confirming that the USB was safely ejected ... although it was.

Fully agree that when Scribe runs it is stable and doing a great job [see my specs in signature] - just gets a bit wobbly when stopped as described.

I have no reason to eject the USB drive so far.

I may give that a try when 384.12 goes final and I do an M&M Config on my network (lots of experimenting these last few weeks).

If I needed to disconnect the USB drive, I would pull the power plug from the router (and not from the AC wall socket) and remove it then (if I needed to do so to upgrade firmware, for example). Safely ejecting it is not the same thing, ime.

 

[Jumpstarter]

This is from if I power it off and manually turn it on.

 

[elorimer]

If I uninstall scribe, I dont have the issue at all. So I am thinking it has to do with issues cause at the moment it launches something causes acsd to go crazy and never settle down.

You aren't by any chance using the system() source we experimented with a few months ago? If on alpha2 acsd is spamming the log through its own logging maybe system() is picking it up from two places.

 

[Jumpstarter]

I just downloaded scribe 2 days ago and have been running it with 384.12 alpha 2 every since so idk.

 

[Jumpstarter]

It does not appear to be logging my ascd inside scribe though. I am seeing them in regular system log.

 

[Jumpstarter]

 

[Jumpstarter]

This is what I see in scribe debug

 

[cmkelley]

What happens when you eject the USB disk? In my case it ends all logging [syslog.log in the webgui stays totally blank after the "### Top of Log File ###" line].

Re-insert USB - does Syslog-ng start automatically? and if so - are you getting all logging activity which was not displayed while USB ejected back in Sylog.log [or in "messages" file? In my case- for e.g. there is no sign of the log entry confirming that the USB was safely ejected ... although it was.

Fully agree that when Scribe runs it is stable and doing a great job [see my specs in signature] - just gets a bit wobbly when stopped as described.

Yeah, that would expected behavior until I implement a stop function in scribe. Just never thought about people ejecting the USB. LOL

 

[Jumpstarter]

Yeah, that would expected behavior until I implement a stop function in scribe. Just never thought about people ejecting the USB. LOL

Shouldnt it stop on its own using entware stop services.

 

[Jumpstarter]

@cmkelley and everyone else, thank you for your advice it seems to have fixed the issue I can reboot with out the issue now.

 

[cmkelley]

I just downloaded scribe 2 days ago and have been running it with 384.12 alpha 2 every since so idk.

No, I discontinued that a long time ago. Well before v2.0

 

[cmkelley]

Shouldnt it stop on its own using entware stop services.

Well yeah, but it won't restart syslogd or klogd. I have to have a think about that.

 

[cmkelley]

@cmkelley and everyone else, thank you for your advice it seems to have fixed the issue I can reboot with out the issue now.

What ultimately fixed it? Last post I saw a power off / power on only "fixed" it until you re-booted?

 

[cmkelley]

It does not appear to be logging my ascd inside scribe though. I am seeing them in regular system log.

Not 100% sure what you mean by this ... there is no filter included to send ascd messages to their own log file, so they would go in main "messages" file. Or are none appearing when ascd is not running at ~100% CPU?

 

[Jumpstarter]

What ultimately fixed it? Last post I saw a power off / power on only "fixed" it until you re-booted?

A power off fixed it, probably cleared something that was causing reboot hang issues. Cpu is now to normal after loading everything on reboot. I am so glad I do not have to remove your awesome script.

 

[Jumpstarter]

Not 100% sure what you mean by this ... there is no filter included to send ascd messages to their own log file, so they would go in main "messages" file. Or are none appearing when ascd is not running at ~100% CPU?

I am not sure what caused it but it is 100 percent fixed.

 

[joe scian]

Can I suggest that you post here your /opt/etc/logrotate.conf file, and the files in your /opt/etc/logrotate.d directory? Or PM them to @cmkelley ? Particularly the A00global file.

I'm thinking there might be something in the call to killall that is messing this up.

ok will do tomorrow

 

[kernol]

I have no reason to eject the USB drive so far.

I may give that a try when 384.12 goes final and I do an M&M Config on my network (lots of experimenting these last few weeks).

If I needed to disconnect the USB drive, I would pull the power plug from the router (and not from the AC wall socket) and remove it then (if I needed to do so to upgrade firmware, for example). Safely ejecting it is not the same thing, ime.

Noted @L&LD ... however I have experienced corrupted USB flash drives after simply pulling the power plug - some recovered [disk-check] others didn't - so I'm a bit OCD about "Safely Eject" .

Besides ... in my code development days back in the 1970's I never regarded a project as "complete" until I had catered for "idiots" like me who may want to "quit" the process even if the going was good . Graceful closure without any data loss / corruption was the target - as it was when I raised the issues on Diversion which were fixed perfectly by the lonelycoder .

 

[Xentrk]

Just checking in to say scribe has really improved my log viewing of openvpn client events during the development of x3mRouting.

Just noticed that my system log file has no entries. ### Top of Log File ### is the only entry. I have 0 bytes in the log files after the midnight rollover on June 7:

This is the first time this has happened. I just upgraded from scribe v2.0_0 (master) to scribe GitHub version: v2.0_1 (master). Then, I bounced openvpn client. Still no entries. This is on 384.12_alpha2-g6a46c21cce.

Edit: A reboot fixed the issue. Seeing log entries again.