This question was originally posted on DCIM Support by mike sutton on 2019-10-30
can someone please explain with this log from DCE
10/30/19 16:29:27.124 WARN - User [tc4z1Whipu] from IP address [192.168.16.102] is not authorized to post to [/botpost/surveillance]com.netbotz.server.servlets.botpost.BotPostBasicProcessingFilterEntryPoint)
This comment was originally posted on DCIM Support by Kyle Story on 2019-10-30
I searched for a few keywords of your issue and found this message.
As for the NetBotz based message [10.67.33.83] is not authorized to post to [/botpost/surveillance], are you having surveillance issues? Are you missing clips or images? If so what troubleshooting have you done? If not then again, looking at these logs, you will find events that may cause you concern but without an actual issue on the server you are searching for a non-existent issue.
We can not assist in troubleshooting an issue that does not exist and how would we know if our troubleshooting worked if there is no issue to start with? We couldn't tell if it got better or worse. I strongly suggest staying away from reading the event log if you have no issues.You'll be chasing non-existent issues forever as there are always messages that may look like they're causing an issue.
This comment was originally posted on DCIM Support by mike sutton on 2019-10-31
Thanks but that's not really an answer, choosing to ignore something doesn't make it go away. The concern I have is that the user (User [tc4z1Whipu]) is not even configured on the Bot
This comment was originally posted on DCIM Support by Kyle Story on 2019-10-31
I agree, Was just letting you know what was said on another post related to the same topic.
This answer was originally posted on DCIM Support by Jeff Shaw on 2019-11-05
This is specifically related to Netbotz appliances. If you've ever restored DCE from backup, perhaps changed logins or certs, this could occur. Also, if you have a Netbotz appliance on your network that was not previously configured to post to this server, this could occur.
Locate this netbotz appliance, login to it with Advanced View, remove the DCE's that it's posting to, and rediscover it in this DCE - You do not need to delete it in DCE first. This should resolve the issue.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!