No Matches Found!
Try with a different search term
Hello,
We have a question about some warnings in the logs of some devices, because we saw from our monitoring that these alarms are connected with some tries from the devices to connect to our AD server using kerberos authentication. The picture below shows the warning, but we receive alarms from devices as well, when the logs below are as follows - Device connected, and device disconnected. Can you help us with this issue?
What are the device firmware version and enrollment mode?
Have you made any changes to advanced configurations related to update schedule and connection mode?
It is abnormal to have connection test/retry done repeated in short intervals of the order of 20 seconds or less. Have you checked the stability of the wireless connection between the device and the server? There can be useful information about the cause that can be found in the device agent log file if the log level has already been set to verbose/informational.
.
Hello,
We partly figured out what is the problem, but we need some expertise for some of the things. We managed to see where the problem is, but we don't understand some things. I'll attach some parts of the log, so you can see and if you can, tell us what the actual problem is?
2023-04-06 15:05:12.192|DefaultDispatcher-worker-2|E|AP|[net.soti.comm.m] Socket write failed, disconnecting|h.a.x1: p2 was cancelled; job=p2{Cancelling}@4d0cffa
|
2023-04-06 15:05:12.192|DefaultDispatcher-worker-5|E|AP|[net.soti.comm.m] Unexpected exception|h.a.x1: p2 was cancelled; job=p2{Cancelling}@ad1c808
|
2023-04-06 15:05:12.193|DefaultDispatcher-worker-5|E|AP|[net.soti.comm.m] Exception while processing Message Queue|java.lang.InterruptedException: cancelled
at net.soti.comm.m.A(SourceFile:16)
at net.soti.comm.m$h.invokeSuspend(Unknown Source:11)
at g.x.j.a.a.resumeWith(SourceFile:4)
at h.a.e3.c0.H0(SourceFile:1)
at h.a.a.resumeWith(SourceFile:3)
at g.x.j.a.a.resumeWith(SourceFile:10)
at h.a.y0.run(SourceFile:21)
at h.a.e3.n.run(SourceFile:2)
at h.a.g3.k.run(SourceFile:1)
at h.a.g3.a.z(SourceFile:1)
at h.a.g3.a$c.d(SourceFile:4)
at h.a.g3.a$c.n(SourceFile:4)
at h.a.g3.a$c.run(SourceFile:1)
This is the reason for the question in first place. What this message means? And why after every single on of them, it tries to authenticate to our Active Directory server?
Hi Steeve,
Thanks for posting on SOTI Pulse and thanks Raymond for responding to the post.
I would suggest you open a case and we can look into it further, as there are many things that need to take into consideration while troubleshooting this issue, such as device is enrolled as Android Enterprise or classic, device agent version, MobiControl version, is the device has stable connectivity, advance configuration etc.
So, it would be better if we can troubleshoot this issue through Support Case.
Thank you.
Kind regards,
Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |
