Could not parse handle.exe output warning

276 views
Skip to first unread message

Alexander Shevchenko

unread,
Sep 11, 2017, 8:23:43 AM9/11/17
to rabbitmq-users
Hi,

RabbitMQ 3.6.9 on Erlang 19.2 inside Windows Docker container on Windows Server 2016

I've got the warning in rab...@ofslog-staging.log file:

=WARNING REPORT==== 11-Sep-2017::05:56:39 ===
Could not parse handle.exe output: "\r\nNthandle v4.1 - Handle viewer\r\nCopyright (C) 1997-2016 Mark Russinovich\r\nSysinternals - www.sysinternals.com\r\n\r\nHandle type summary:\r\r\n  <Unknown type>  : 190\r\r\n  <Unknown type>  : 88\r\r\n  <Unknown type>  : 55\r\r\n  ALPC Port       : 1\r\r\n  Desktop         : 1\r\r\n  Directory       : 2\r\r\n  IoCompletion    : 4\r\r\n  IRTimer         : 6\r\r\n  Key             : 6\r\r\n  Process         : 4\r\r\n  Semaphore       : 2\r\r\n  Thread          : 76\r\r\n  TpWorkerFactory : 3\r\r\n  WaitCompletionPacket: 7\r\r\n  WindowStation   : 2\r\r\nTotal handles: 447\r\r\n"


The output from powershell window:
PS> handle.exe /accepteula -s -p 227552


Nthandle v4.1 - Handle viewer
Copyright (C) 1997-2016 Mark Russinovich
Sysinternals - www.sysinternals.com


Handle type summary:
 
<Unknown type>  : 55
  ALPC
Port       : 1
 
Desktop         : 1
 
Directory       : 2
 
Event           : 210
 
File            : 27
 
IoCompletion    : 4
 
IRTimer         : 6
 
Key             : 6
 
Process         : 3
 
Semaphore       : 2
 
Thread          : 96
 
TpWorkerFactory : 3
 
WaitCompletionPacket: 7
 
WindowStation   : 2
Total handles: 425

I've attached log files.
Also I don't understand EACCESS error in log file. Looks like it can't access handle.exe. But other time it can, as it sees output from handle.exe.

Thank you.
rabbit@ofslog-staging.log
rabbit@ofslog-staging-sasl.log

Michael Klishin

unread,
Sep 11, 2017, 1:06:29 PM9/11/17
to rabbitm...@googlegroups.com
EACCESS can be due to insufficient permissions but also access blocked for other reasons, such as (it's a guess, there is
no evidence of this in this case) concurrent access to a resource, antivirus software blocking operations and so on.

The consequence of that is that the node won't have any information about the number of file descriptors
it uses.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Luke Bakken

unread,
Sep 27, 2018, 7:35:41 PM9/27/18
to rabbitmq-users
Hello,

Note the <Unknown type> lines. The code that reads the output from handle.exe expects to find a line containing File, which isn't shown. It appears that running handle.exe on its own always works.

Thanks,
Luke
Reply all
Reply to author
Forward
0 new messages