How to define syslog messages encoding as "system" on Netbotz

[DCIM_Support]

I use the Rack Access Pod 170 with Netbotz Rack Monitor 570, and I defined syslog messages configuration to be sent to a local Kiwi Syslog server.

The received messages by the Kiwi Syslog server are not recognize correctly generating the next error messages (samples)

2016-10-26 14:59:21  Daemon.Debug  172.20.51.159 thttpd[2211]: spawned CGI process 5333 for file '/opt/netbotz/cbin/nph-nbVarQueryCGI'
2016-10-26 14:59:21  Daemon.Debug  172.20.51.159 thttpd[2141]: spawned CGI process 23364 for file '/opt/netbotz/cbin/nph-nbVarQueryCGI'

Quick review on the Internet (http://www.kiwisyslog.com/help/syslogv82/index.html?adv_fileencodingformat.htm) shows the source is most probably related to the encoding format defined at the Netbotz level (Rack Access Pod 170 and/orNetbotz Rack Monitor 570)

I am also using AP9361 devices (Netbotz Rack Access PX) since years pointing also to the same Kiwi Syslog Server without this issue. Hence, I discard the trouble is related to the Kiwi Syslog server.

Thus, how can I update the encondign configuration at the Rack Access Pod 170 and/orNetbotz Rack Monitor 570 level?
Thanks for help and support.

Hervé

(CID:109447362)

[DCIM_Support]

Hello Herve,

At the moment, the only way to view information about the Rack Access Pod 170 is in the Appliance Event Log in Advanced View.  There might be an option to send this information to a Syslog server in a future BotzWare release, but I cannot say for sure if or when this feature will be added.
The Log option in Advanced View is really only intended for diagnostics and troubleshooting of the appliance. 

Regards

John T

(CID:109447390)

[DCIM_Support]

Hello John,

Thanks for your comment. From the Advanced View, yes it is possible to define a syslog server IP address from the Configuration part and the Log sub-part. This is the current configuration and the communication with the Kiwi Syslog server was validated.

However, the issue stays at the sent syslog message format itself and - most probably - with the used encoding.

From the different component available at the Configuration part I didn't found where this encoding could be updated. Shall it comes from a specific command-line?

Best regards,

Hervé

(CID:109447479)

[DCIM_Support]

Herve, You cannot add to or change the list of Components, but you can change the Log Level for each Component. You could change them to a log level of 8 - Trace, which would provide more detailed information about a process or daemon. But again, this would only be useful to our developers for troubleshooting and diagnosis. Hope that helps. John T

(CID:109447480)

[DCIM_Support]

Hi John, From the Advanced View interface we lowered the Global Log Level to 5.-Warning and all the Components Log Levels setup to 9.-Use global level where - we expect - will use the default level (at 5.-Warning). Unfortunately, our Kiwi Syslog Server keeps receiving too many messages 😞 Thus, can you please explain us where we have to setup the right levels from the Advanced View interface? Regards

(CID:110004071)

[DCIM_Support]

Hi Herve, Apologies for the late response. I believe you wer also speaking with my colleague Eduard Everard about this. At the moment, it is not possible to have the rack access system information that you are looking for, available in Syslog, but the feature may be included in a future release of NetBotz firmware release. However, I cannot say if or when that might be. As I mentioned before, the only way to get this informaiton in the Advanced View Appliance Event Log. Regards

(CID:110005355)

[DCIM_Support]

hello, This is correct, I was and I remain also in touch with Eduard Everard (nice guy btw). I fully understand the feature I need is not (yet) available with those Netbotz devices and no scheduled date is defined so far for another release. hence, I have to wait 😞 that's life. Thanks for the provided information and support. Best regards from rainy and cold Luxembourg Hervé

(CID:110005415)

[DCIM_Support]

Hi Hervé - we use Kiwi Syslog a lot internally and it should work fine as a Syslog server for the NetBotz appliances. Can you provide a screenshot or the log dumps from Kiwi showing us the issue in real time? That way, then I can look at this more closely with one of my teammates who actively uses Kiwi Syslog.

Also, for reference, which version of BotzWare do you have on your 570? v4.5.2?

(CID:109447477)

[DCIM_Support]

Hello Angela, Thanks for your help. We are using Netbotz 570 under version 4.5.2 build 20160602_1247 Our target consists in not sending the entries similar to the next ones: 2016-10-26 14:59:21 Daemon.Debug 172.20.51.159 thttpd[2211]: spawned CGI process 5333 for file '/opt/netbotz/cbin/nph-nbVarQueryCGI' 2016-10-26 14:59:21 Daemon.Debug 172.20.51.159 thttpd[2141]: spawned CGI process 23364 for file '/opt/netbotz/cbin/nph-nbVarQueryCGI' We would like having only messages related to the door management like: 2016-11-02 15:00:43 Daemon.Notice 172.20.51.159 nbVarWriteCGI: Switch 'Front Lock - LUXDC-PX650' set to 'Unlocked' by user 'apc' From the Advanced View interface we lowered the Global Log Level to 5.-Warning and all the Components Log Levels setup to 9.-Use global level where - we expect - will use the default level (at 5.-Warning). Unfortunately, our Kiwi Syslog Server keeps receiving too many messages 😞 Thus, can you please explain us where we have to setup the right levels from the Advanced View interface? Regards,

(CID:110004070)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.