log errors to syslog [$5] about znc HOT 9 OPEN

The complete lack of any logging in znc is pretty unusual. For example, if you clobber the perms on your ssl cert so that znc can't read it, it just sits there with its eyes crossed and there's no indication of what's wrong.

from znc.

Uhm, which errors are logged to *status?
AFAIK only failed rehashes are and logging just those to syslog feels wrong.

Which other error messages do you have in mind?

from znc.

If I edit znc.conf and then "/znc rehash", I get messages if the rehashing did not succeed. However, if I "kill -HUP ", I am not given any messages if the rehashing failed. I would like to be able to look in a log file (syslog or otherwise) on the machine to diagnose errors.

from znc.

So only rehash errors should go to syslog, no other kind of error? Why would anyone check the syslog for failed rehashes then?

from znc.

Honestly, I've used znc for quite a while and have only had errors that were my fault (bad configs, etc). It's quite reliable, so I don't even really know what errors could happen.

The kind of errors I'm talking about are the ones that prevent ZNC from running. Of course, I've seen transient IRC connectivity issues. I agree that those may not need to be in a syslog entry (although I don't think that's a problem if they are there).

My situation is that I (and my coworkers) maintain an instance of znc on an internal machine for users that aren't familiar with IRC. Generally, those of us that are familiar use screen+irssi or our own instance of ZNC on our own machine. When users are added or removed from the znc config, the processed is HUP'd, and we have to simple wait and see if the changes took. There is no feedback. Server locations or ports may have been entered incorrectly. Closing tags may be missing. The only way to know if there is an error is to wait and see what happens. And "wait-and-see" only works if the recent change involved something that can be seen. If it were something like buffer size changes, I would have to assume the changes took since there is no way for me to see any logs. In my opinion, a known, standard place like syslog (or something else in /var/log) would let me check for errors easily and monitor with alerts if something needs attention.

from znc.

So in other words, you already figured out yourself that it's a bad idea to edit the config by hand. However, you didn't yet figure out that it's better to edit the config via webadmin.

from znc.

Something like http://logging.apache.org/log4cxx/ may be used, and it supports more than just syslog... Though perhaps we'll need a license change for that (e.g. #218)

from znc.

Is this bug still open ?

from znc.

from znc.