@scottgelb wrote:
You won't be able to recover what was lost (unless in a snapshot) but you can reset syslog and it will start collecting again..saves a reboot
priv set advanced ; syslog reset_syslog
Thank you for this command! It really helped me out.
Note to others:
I was on my console, and when I did it, it said "bad syslog.conf line "*.info"
So I looked at another filer syslog.conf I had that was working, copied it, wrote it, and then restarted the syslog again.
This time it worked.
filer_name*> syslog reset_syslog
filer_name*> Fri Apr 17 12:45:33 EDT [syslogd]: logerror syslogd: bad syslog.conf line "*.info"
Fri Apr 17 12:45:33 EDT [syslogd]: logerror syslogd: bad syslog.conf line "*.info"
Fri Apr 17 12:45:33 EDT [syslogd]: logerror syslogd: bad syslog.conf line "*.info"
filer_name*> rdfile /etc/messages
filer_name*> version
NetApp Release 8.2.3 7-Mode: Thu Jan 15 21:30:45 PST 2015
filer_name*> rdfile /etc/syslog.conf
*.info
*.info
*.info
filer_name*> wrfile /etc/syslog.conf
*.info /dev/console
*.info /etc/messages
read: error reading standard input: Interrupted system call
filer_name*> rdfile /etc/syslog.conf
*.info /dev/console
*.info /etc/messages
filer_name*> syslog reset_syslog
filer_name*> Fri Apr 17 13:00:00 EDT [filer_name:kern.uptime.filer:info]: 1:00pm up 32 days, 11:16
Hope this helps somebody.