I got a kick out of some of the git commit comments, like "reverse for a reason".Just minor stuff that's been accumulating
I got a kick out of some of the git commit comments, like "reverse for a reason".Just minor stuff that's been accumulating
Anyone feel like helping me filter "hostapd" and "cake-qos" messages please? I've been trying and uninstalling scribe to get things working again as I keep failing. I create empty logs and nothing gets filtered. I've looked at the examples but seriously I'm drawing blanks now. Please anyone?
It depends on how snarky I'm feeling at the moment - I actually just looked at the commit history, and I have zero idea anymore why I did that. There's a reason my nick on github is cynicastic. Cynical and Sarcastic. Honestly if I could change my nick here without losing my history, I would, but oh well.I got a kick out of some of the git commit comments, like "reverse for a reason".
I do, except it might have been better the first way:I actually just looked at the commit history, and I have zero idea anymore why I did that.
When using multiple filters one after the other, or connecting filters with the logical AND/OR operators, the order of filters has a significant impact on performance. We recommend to put those filters in front that are the most likely to match the incoming log messages (if known).
My hostapd scripts are below: I get this error when running logrotate.Give me a few and I can do Cake...I'll see if I can get it over before the next publish...
Or share what you built...might just need a tweak or two. One key thing with the config files for both logrotate and syslog-ng is perms....0600 - else if never reads the config.
==> /opt/tmp/logrotate.daily <==
error: hostpad:1 lines must begin with a keyword or a filename (possibly in double quotes)
error: hostpad:6, unexpected text after }
# put hostapd messages into /opt/var/log/hostapd.log
destination d_hostapd {
file("/opt/var/log/hostapd.log");
};
filter f_hostapd {
( program("hostapd") or
program("hostapd") ) and
( message("eth7") or
message("eth7") ) or
( program("syslog") and
message("hostapd") );
};
log {
source(src);
filter(f_hostapd);
destination(d_hostapd);
flags(final);
};
#eof
/opt/var/log/hostapd.log {
rotate 4
postrotate
/usr/bin/killall -HUP syslog-ng
endscript
}
My hostapd scripts are below: I get this error when running logrotate.
Code:==> /opt/tmp/logrotate.daily <== error: hostpad:1 lines must begin with a keyword or a filename (possibly in double quotes) error: hostpad:6, unexpected text after }
I created both files with notepad++ on my Ubuntu desktop. I don't think that's the problem but a simple dos2unix command would fix that.I created "hostapd" files in both syslog-ng.d and logrotate.d directories cutting and pasting your text, then I did from the scribe menu rl, rs, lr without issue (but I didn't have any messages in that log).
Perhaps the file is not in Unix format? That is a logrotate error, and I'm guessing there is a typo in the name of the config file?
Yup typo was it, now it runs without error. Anyone got clues on how to do Cake yet? Everything I try fails.I'm guessing there is a typo in the name of the config file?
Not in the efforts I tried...lolUsing "CakeQOS-Merlin" with a program filter doesn't work?
It looks like withe release of 1.0.0 the log spam has stopped or at least reduced.As an aside, I'm not really a fan of filtering everything out of messages, just the somewhat noisy loggers, like pixelserv, skynet and spdMerlin that obscure other useful messages.
logrotate -f logrotate.conf
It's not stupid because there is a hidden surprise. lr runs logrotate as currently configured with the files in /opt/etc/logrotate.d and /opt/etc/logrotate.conf. Because those are usually configured for daily rotation, that means you can rotate the logs in /opt/var/logs once. If you run it again, it will see that they have been rotate already and not rotate them again.
Logrotate leaves you with a current log, a plain text rotated log, and several compressed earlier rotated logs. You can just delete the rotated log and the compressed logs if you want.
If you want to "clean", that is edit, the current log, it is best to stop syslog-ng first. You might do that, for example, if you've gotten some runaway logging to pixelserv.log. Otherwise your editor and syslog-ng will both be operating on the same file and you will get an inode mismatch.
If you want to force a rotation of a logs, you need to manually run it:
That will force (-f) a rotation of the logs without regard to age (the daily part) or size.Code:logrotate -f logrotate.conf
Should be, although I don't know anything about syslog on a mesh node. Presumably you don't need scribe and syslog-ng on the mesh node, so you can uninstall uiScribe on the mesh node, if it is installed and then you should get the fields to send log messages to a remote server. Remote logging on Asus-AC88U with Merlin 384.16Can syslog on the mesh node be configured to forward to the main router, where syslog-ng is listening?
Delete the suricata log from /opt/var/log/ and then open uiScribe and use menu #1 to hide it from the uiScribe group of logs. Next time you reboot, uiScribe will not have anything about it.I removed Suricata and still have the suricata.log entry on the scribe syslog page. How do I get rid of it? It's the only lingering part left of manual uninstall.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!