Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 445102
Smarts: Broker crashes with "Remote API connection" errors found in the Broker log
Last update date:
3/22/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Smarts Broker crashes with errors similar to the following found in the Broker log: CI_FlowBufferedHead_U [Remote API connection] HEAD|BUFFERED Read buffer, 0 bytes available of 2145 4D536572 76657200 00000573 74617465 ^|744E616D 65537472 2E310D0A 436F6E74 Write buffer, 0 bytes written of 2048 [^02000000 03000000 0064796C 30393634 36617070 30316E74 2D747970 653A2061 ->CI_FlowTCP_U [] IN_FLOW|PHYSICAL *:v4:426 KS 01-Jul-2009 21:04:29 BST, KR 03-Jul-2009 15:36:18 BST Open fd=413, 127.0.0.1:426 -> 127.0.0.1:53047, tmo 10428 07:09:38 N/S 1/1 Crash file associated with Smarts Broker crash contains the following: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. The following message is seen when Smarts Broker attempts to accept an http request: <SYS>-EMFILE-Too many open files
Cause
This issue is caused by customized code in the environment (such as a Java API). The reason for the fatal exception and crash is that there are too many failed client connections, and these client connections are generated by the customized code. The errors in the above Symptom statements reflect that there are repeated attempts made to connect to the Smarts Broker, but all of these attempts fail because there are too many open files. This can be seen when the Smarts Broker attempts to accept an http request. The "<SYS>-EMFILE-Too many open files" message indicates that there are too many open files or file descriptors in the environment. Smarts has a maximum limit of 128 http accept errors, after which it will dump all the flow messages and throw a fatal exception. The maximum number of file descriptors is usually based on the OS and is generally 1024.
Resolution
Because this issue is caused by customized code in the environment, EMC Support for Smarts cannot resolve this issue. The errors will need to be addressed in the customized code to resolve this issue.
