No. If you have an 87U and tried 12A2, that does affect the network map and you need to go back to A1.has anyone reported this effecting the network map?
No. If you have an 87U and tried 12A2, that does affect the network map and you need to go back to A1.has anyone reported this effecting the network map?
I think this is because syslog-ng can't run when the USB is ejected, and nothing has restarted syslogd. So no logging is going on.Why do I ask? - because, aside from testing issues, that same routine would be usefully auto-invoked when the USB is ejected. Right now when the USB is ejected ... "### Top of Log File ###" gets written to System Log [Webgui] and nothing appears after it - no matter how long you wait.
So much for that idea. I thought maybe it was re-starting syslogd or klogd somehow.cmkelly
OK - I restarted QOS by going to QOS page and hitting apply which calls firewall-start and nat-start and I lost /tmp/syslog.log. After doing a ps | grep log this is what i got
Code:joescian@RT-AC5300:/jffs/scripts# ps | grep log 3107 nobody 42320 D dnsmasq --log-async 3108 joescian 1332 S dnsmasq --log-async 8383 joescian 8452 S {syslog-ng} supervising syslog-ng 8384 joescian 15324 S syslog-ng
I think this is because syslog-ng can't run when the USB is ejected, and nothing has restarted syslogd. So no logging is going on.
I wonder whether ejecting the USB is better left to amtm, which might call a stop sequence in scribe--I forget how that discussion went. But you are suggesting that the scribe stop would restart syslogd, which would destroy the symlink and start up a new /tmp/syslog.log; then on scribe restart it would see the file, copy it to messages, reform the symlink, kill syslogd and start syslog-ng. I guess that could work ok.
No rush - FULLY enjoying what you have done so far - in a mind boggling field, where you have done a massive amount to simplify an impossible task for us non-coders {Thumbs-Up}Good idea. Hopefully can implement no later than this coming weekend, my weeknights are looking iffy for the rest of the week.
I did not catch the name of the software that you use to display the logs. Would you repeat that for me?Like this?
Yes, an online service. I use the free version since my total data is way below their threshold.I did not catch the name of the software that you use to display the logs. Would you repeat that for me?
Yes, an online service. I use the free version since my total data is way below their threshold.
https://www.loggly.com/
Thanks to both of you. That is a no-no for me sending the logs to a remote server.Its a loggly screen.
In this post @cmkelley y mentions that syslog-ng now supports collectd, though I have not looked at it. I think @elorimer has and can offer more info.Thanks to both of you. That is a no-no for me sending the logs to a remote server.
I was hoping this is a free and open source software that I could install on my local CentOS server.
Run syslog-ng on the CentOS server and send the router logs there.I was hoping this is a free and open source software that I could install on my local CentOS server.
For me it simplifies log viewing to monitor events. Because each service is sorted to a separate log, it makes trouble shooting much, much easier.I've read most of this thread's pages. I am struggling to figure out what value I can get for using syslog-ng to me personally. What's motivating you guys to deploy and use this? Laymen's terms would be super! TY
Everyone has different reasons. For me personally it's to de-clutter the dcd crash, wlceventd, and iptables entries from the main log. Others might be using their routers in an office environment and need to monitor the logs for security, and it helps to break them out.I've read most of this thread's pages. I am struggling to figure out what value I can get for using syslog-ng to me personally. What's motivating you guys to deploy and use this? Laymen's terms would be super! TY
So much for that idea. I thought maybe it was re-starting syslogd or klogd somehow.
Next thing to do is see if it's even sylsog related. Can you create a dummy file called '/opt/var/log/dummy', and then create a symlink 'ln -s /opt/var/log/dummy /tmp/dummy-link', and then do whatever it is that kills the symlink between /opt/var/log/messages and /tmp/syslog.log? If it kills the link between dummy and dummy-link. then it's a separate issue form syslog/syslog-ng.
...For me personally it's to de-clutter the dcd crash, wlceventd, and iptables entries from the main log. Others might be using their routers in an office environment and need to monitor the logs for security, and it helps to break them out.
When did you last look at /var/log on your *NIX box? I'm sure you'll find more than one log file there.Funny, I never got why the linux default practice of dumping all messages and events into a single main system log other than "well that's best practice..." when then the first thing developers do is sort/search/organize it using tools like this! LOL.
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!