Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Stuart Henderson
On 2017-05-05, Paolo Aglialoro wrote: > Thank you everybody! > > It was just a stupid typo, yes sometimes it's so hard to see what's in > front of the screen > Now the router has correctly started logging in the file. > > I also noticed it's still logging in /var/log/messages, is this correct?

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
Thank you everybody! It was just a stupid typo, yes sometimes it's so hard to see what's in front of the screen Now the router has correctly started logging in the file. I also noticed it's still logging in /var/log/messages, is this correct? Thanks On Fri, May 5, 2017 at 4:38 PM, Peter Hess

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Peter Hessler
The file you were looking at was named c2821.log. This has a '2' in the name. c2851.log is the one you referenced in the config file. it has a '5' in the name. That is what Allan and I were refering to. If the below was exactly how you created the files, then please restart syslogd, to ensure

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
Sorry Peter, what do '2' or '5' stand for? And what does creating a file with '5' mean? This was my procedure: # cat "" > c2851.log # chown root:wheel c2851.log # chmod 644 c2851.log On Fri, May 5, 2017 at 3:46 PM, Peter Hessler wrote: > On 2017 May 05 (Fri) at 15:38:36 +0200 (+0200), Paolo A

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Peter Hessler
On 2017 May 05 (Fri) at 15:38:36 +0200 (+0200), Paolo Aglialoro wrote: :As written, mtime was due by me recreating the file trying to make things :work, not by syslog. :As of today, in fact, mtime is still unchanged, while output to :/var/log/messages still flowing from router. : : :On Fri, May 5,

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
As written, mtime was due by me recreating the file trying to make things work, not by syslog. As of today, in fact, mtime is still unchanged, while output to /var/log/messages still flowing from router. On Fri, May 5, 2017 at 2:27 PM, Allan Streib wrote: > > > -rw-r--r-- 1 root wheel - 1 Ma

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Allan Streib
> -rw-r--r-- 1 root wheel - 1 May 4 15:43 /var/log/c2821.log ^ [...] > local1.debug/var/log/c2851.log

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
Thanks for the answer Stuart! Yes, I had created the file 644 root:wheel as listed (mtime is of yesterday I as deleted and recreated it when fiddling before writing to list): $ l /var/log/c2821.log -rw-r--r-- 1 root wheel - 1 May 4 15:43 /var/log/c2821.log $ l /var/log/switch.log -rw-r--r--

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Stuart Henderson
On 2017-05-04, Paolo Aglialoro wrote: > Hi all, > > I have an internal LAN syslogd server (recently upgraded to 6.1) since a > couple of years. It was successfully logging an old 2611XM cisco router, > now logs a dell switch and the new 2851 cisco router which swapped the old > one. > > PROBLEM: w

Incorrect file destination when logging with syslogd

2017-05-04 Thread Paolo Aglialoro
Hi all, I have an internal LAN syslogd server (recently upgraded to 6.1) since a couple of years. It was successfully logging an old 2611XM cisco router, now logs a dell switch and the new 2851 cisco router which swapped the old one. PROBLEM: while the dell switch correctly logs in the designated