I can not restart syslogd service in freenas 9.3 stable.

[Isaias]

When I try to restart the service, shows me the following error:
# service syslogd restart
Will not 'restart' syslogd because syslogd_enable is NO.

#cat /etc/defaults/rc.conf|grep syslogd_enable
syslogd_enable="YES" # Run syslog daemon (or NO).

The system dataset is configured correctly. (see attached file.)

Thanks!!

 

[hispeedzintarwebz]

I've having the exact same problem, even after reboot. The last message to write to the console in the webgui was:

Dec 16 00:00:00 rubbermaid newsyslog[19823]: logfile turned over due to size>100K

And I've gotten the same email last night at midnight and just now at midnight:

newsyslog: pid file doesn't exist: /var/run/syslog.pid

Not finding much with google. Reassuring this is also happening to someone else.

Edit: My system dataset (aside from pool name) matches the post above.

 

[hispeedzintarwebz]

Hey! Would you look at that!

I edited /etc/rc.conf and syslogd_enable was set to "NO" and I'm not sure what changed it. Messages immediately started popping up in the console after
service syslogd start

Not sure what turned it off. Does this help you?

Edit: I'm still not getting as much as I'm used to seeing (I think...although I haven't paid as much attention to the console as I did when I first set it up, since I've upgraded to 9.3. I made and destroyed a dataset called "test" and this is all that popped up:

Dec 17 00:29:22 rubbermaid notifier: Stopping collectd.
Dec 17 00:29:25 rubbermaid notifier: Waiting for PIDS: 2905.
Dec 17 00:29:25 rubbermaid notifier: Starting collectd.
Dec 17 00:29:46 rubbermaid notifier: Stopping collectd.
Dec 17 00:29:55 rubbermaid notifier: Waiting for PIDS: 11106.
Dec 17 00:29:55 rubbermaid notifier: Starting collectd.

I feel like there should be more. Could be wrong.

 

[Isaias]

Hi,

Mysteriously me the same thing happened to me. When I edited the "rc.conf" file syslogd_enable was like "NO". I've changed and re-run the service correctly.

Regards.

 

[dlavigne]

Were these fresh installs or upgrades? Might be worth reporting as a bug. If you do, post the issue number here.

 

[hispeedzintarwebz]

This was an upgrade. What really confused me though is that it seemed to start right at midnight, not immediately after the upgrade had run.

I'll have to figure out how to get the logs off the linux box easily so I can include that with a bug report.