No log in Orchestrator for a robot

robot
logs

#1

Hi,
We have 3 robots connected to the Orchestrator.
For 2 of them, logs are available and displayed in the Orchestrator, but for the last one, there is no log.
Do you have an idea of what can happened ?

It used to work a week ago.
I can see the log files on the robot (Execute / Open Logs) but nothing on the Orchestrator.

Thanks for your help…

Nicolas


#2

Can you compare the logging levels of the robots in the settings.


#3

Hi,
We have “Information” for both.


#4

Can you change it to Trace or Verbose and check. For me Information just gives me Execution Started and Execution ended (only 2)


#5

Done, but with no change.
We can’t retrieve the logs in the Orchestrator.


#6

Any idea ?


#7

Please try below steps on the server.

Step 1:
Open a File Explorer and go to %appdata%\uipath\logs. (if there is no folder, then ignore this step and go to step 2)
You may find a file there, without extension, called “offline”. It is created by a Windows library “Event Tracing for Windows” or ETW and sometimes gets corrupted.
This file may be hidden, so please open the “View” menu in file explorer and check the option “Hidden items”.
Delete this file and restart the UiPath Robot service.

Step 2:
stop the UiPath Robot service
Delete the folder “C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data folder” and restart the service.


Logs stopped in Orchestrator
No logs generated in Orchestrator
Orcherstrator Issue
Orchestrator Community Edition logs missing
#8

I see this %appdata%\uipath\uipath\log (no logs)

Please ignore


#9

If you have file ‘offline’ in that folder, remove it.
If not, go to step 2. That should solve the problem!


#10

Hello Kumar,
It works !!!
I’ve been checking for weeks to solve this issue.
Many thanks


#11

This also fixed our issue. Can you please fix this issue so others do not have to repeat these ridiculous and unnecessary steps? Thank you.


#12

Step 2 helped me to resolve the issue. It happens randomly once we see the below error in event viewer. May be this is the cause.Restart the service helps in some instance for the same error.

Communication Failure.
{“message”:“Error while closing the websocket: System.Net.WebSockets.WebSocketException (0x80004005): An internal WebSocket error occurred. Please see the innerException, if present, for more details. —> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host\r\n at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state)\r\n at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)\r\n — End of inner exception stack trace —\r\n at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)\r\n at System.Net.Security._SslStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)\r\n at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)\r\n at System.Net.Security._SslStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback asyncCallback, Object asyncState)\r\n at System.Net.TlsStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState)\r\n at System.Net.PooledStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)\r\n at System.IO.Stream.<>c.b__53_0(Stream stream, ReadWriteParameters args, AsyncCallback callback, Object state)\r\n at System.Threading.Tasks.TaskFactory1.FromAsyncTrim[TInstance,TArgs](TInstance thisRef, TArgs args, Func5 beginMethod, Func`3 endMethod)\r\n at System.IO.Stream.BeginEndWriteAsync(Byte[] buffer, Int32 offset, Int32 count)\r\n at System.IO.Stream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)\r\n at System.Net.DelegatedStream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)\r\n at System.Net.WebSockets.WebSocketConnectionStream.WebSocketConnection.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)\r\n at System.Net.DelegatedStream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)\r\n at System.Net.WebSockets.WebSocketConnectionStream.<>n__1(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)\r\n at System.Net.WebSockets.WebSocketConnectionStream.d__22.MoveNext()\r\n— End of stack trace from previous location where exception was thrown —\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Net.WebSockets.WebSocketBase.d__48.MoveNext()\r\n— End of stack trace from previous location where exception was thrown —\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n at System.Net.WebSockets.WebSocketBase.WebSocketOperation.d__19.MoveNext()\r\n— End of stack trace from previous location where exception was thrown —\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Net.WebSockets.WebSocketBase.d__51.MoveNext()\r\n at System.Net.WebSockets.WebSocketBase.ThrowIfConvertibleException(String methodName, Exception exception, CancellationToken cancellationToken, Boolean aborted)\r\n at System.Net.WebSockets.WebSocketBase.d__51.MoveNext()\r\n— End of stack trace from previous location where exception was thrown —\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.AspNet.SignalR.WebSockets.WebSocketHandler.<>c.<b__13_0>d.MoveNext()”,“level”:“Error”,“timeStamp”:“2017-10-27T15:28:27.0725288+05:30”}


#13

The issue has been fixed in our lasted release of the orchestrator, Request you all to please update the Orchestrator to the latest version for the permanent fix.


#14

Hey @Pawan.rathore

Just for reference - “latest release” - could you give a specific version?
There’s no mention of it in 2017.1.6547 (2017-12-05) release notes and that’s the latest that has any.


#15

@andrzej.kniola
Yes, the issue has been fixed in 2017.1.6547 (2017-12-05), Released notes will be updated.


#16

@ovi @Cosmin_Ion_Nicolae @badita

Could you please confirm why this is required? This only impacts logging to Orchestrator, not to elastic search. We need to know how to prevent this in the future? I guess we could add something in to clear out this folder on a regular basis.

RD


#17

Hi Richard,

The logging architecture has been changed in latest release(as per my knowledge there were many fixes on Logs in 17.1.6522). So it’s not just a fix for the issue in particular, but improvements for logs in general.

Yes, if it happens(hopefully not anymore) a batch file can be run to delete that folder.

I don’t have an exact answer to this but i can tell you how this folder gets populated. The Robot uses this folder(C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data) to store temporary log files when the connection with Orchestrator is lost. Once the connection is restored it pushes the log messages to Orchestrator. This is a proprietary folder of Windows which sometimes gets corrupted therefore the logs are not sent to Orchestrator.


#18

Thanks Ovi. Great explanation.


#19

And what about slighthly different situation. There are few robots connected to orchestrator. All logs are visible in orchestrator but all except one robot have daily log files in …/AppData/Local/Uipath/Logs. One of backoffice robots stopped creating log files and it used to made them. How to fix it? Purging execution_log_data and restarting uipath service didnt help.


#20

Hi Bartosz,

What about the “offline” file? Can you find it using the steps Sunil provided above?

Can you see those logs in Orchestrator?