SomeWhereOverTheRainBow
Part of the Furniture
syslog-ng not working is a symptom of a much larger problem. The first problem to tackle is ensuring your clock is set correctly.
good ol'ntp
syslog-ng not working is a symptom of a much larger problem. The first problem to tackle is ensuring your clock is set correctly.
Meh, ntp is pretty reliable, if anything it's a great canary for other network problems. Now, granted I live in a very large metro area where there are plentiful servers with low ping latency. IMHO, running an ntp server on a machine without a battery-backed clock (or a means of getting time independent of the network) is madness.good ol'ntp
Just noticed my logs stopped updating, since 4-10, when I did the big messy Entware update. Guess I should have been subscribed to this thread, but came to the same solution purely by accident. Glad our scripters give us their robust work, thanks for saving my bacon again.Just use "scribe status" at the command line or the "s" option on the scribe menu
I think syslog-ng doesn't create the file until it has a message to send to the file.The result is that 'ioctl' log works the other 2 mentioned above do not show up in /opt/var/log/ and the web UI is empty for those.
That is my experience as well.I think syslog-ng doesn't create the file until it has a message to send to the file.
CorrectI think syslog-ng doesn't create the file until it has a message to send to the file.
Yes, my jffs log is usually empty as well. But I've had problems in the past with a certain file filling up the jffs (I can't remember which one it was, it's a firmware-created file and I've seen others occasionally have the same issue). So it's nice to check every now and then.I only get two jffs messages at boot time. Hardly worth the sifting. In the standard setup, most of the start up sequence doesn't go through syslog-ng in the first place and is appended directly to messages.
I have a crash log on my 86U, though.
Yes indeed. My 86U on .16 posts to the crash.log every 15 minutes or so.@Torson, an 86U with an empty crash log? What is this sorcery!!
# log dcd crash dump to /opt/var/log/crash.log only
destination d_crash {
file("/opt/var/log/crash.log");
};
filter f_crash {
message("dcd") or
message("v8A") or
message("pgd = ") or
message("\\[00000000\\]") or
message("task: ") or
message("PC is at") or
message("LR is at") or
message("pc :") or
message("sp :") or
message("x12:") or
message("x11:") or
message("x9 :") or
message("x7 :") or
message("x5 :") or
message("x3 :") or
message("x1 :");
};
log {
source(src);
filter(f_crash);
destination(d_crash);
flags(final);
};
#eof
If you want you can send me a debug file ("d" in "su" sub-menu, although you can use "d" from the main menu as well) via PM but I'm crazy overloaded right now (I'm an "essential" employee) so I can only give it a once-over.@cmkelley - that's what I'm trying to figure out - sorcery may indeed be the answer - we're living uncertain times . However, running TrendMicro software is far from that; quite predictable. Those crash entries were there since I started using the AC86U. After installing Scribe and copying the 'crash' files to the right places the entries are gone.
What I believe, is that they still exist somewhere, I just can't figure out where, since they're nowhere to be found.
If the messages are not going to a separate log, then they should end up in messages. Look in messages for the style, as the filter is case sensitive unless you include the flag "flags(ignore-case)"Should I change it to "nextdns" again?
If you're saying the filter file in /opt/etc/syslog-ng.d/ changed, scribe doesn't include any filters for nextdns, so something else changed your filter.Just noticted that my NextDNS log file is empty since April 12.
I think I had manually created a config file with "nextdns" as program string, but it got updated about a week ago to a new included config file with program string "NextDNS"?
Should I change it to "nextdns" again?
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!