How to eliminate FATAL error

yamakawa

Hi.

In order to monitor the status of Vertica, I am checking the FATAL message in vertica.log, and the following message is output approximately every 5 minutes.

---

2020-09-14 14:11:41.885 Init Session:0x7fec52ffd700 <LOG> @v_bhdb_node0001: 00000/2705: Connection received: host=192.168.183.61 port=42946 (connCnt 7)
2020-09-14 14:11:41.885 Init Session:0x7fec52ffd700 <FATAL> @v_bhdb_node0001: {SessionRun} 57V03/5785: Cluster Status Request by 192.168.183.61:42946
HINT: Cluster State: BHDB
UP: 3 of 3 (v_bhdb_node0001, v_bhdb_node0002, v_bhdb_node0003)
----
LOCATION: initSession, /data/qb_workspaces/jenkins2/ReleaseBuilds/Hammermill/REL-10_0_0-x_hammermill/build/vertica/Session/ClientSession.cpp:542
2020-09-14 14:11:42.746 Init Session:0x7fe928fff700 <LOG> @v_bhdb_node0001: 00000/2705: Connection received: host=192.168.183.61 port=42958 (connCnt 7)
2020-09-14 14:11:42.746 Init Session:0x7fe928fff700 <LOG> @v_bhdb_node0001: 00000/4540: Received SSL negotiation startup packet
2020-09-14 14:11:42.746 Init Session:0x7fe928fff700 <LOG> @v_bhdb_node0001: 00000/4691: Sending SSL negotiation response 'N'

2020-09-14 14:11:42.746 Init Session:0x7fe928fff700 <LOG> @v_bhdb_node0001: 08V01/4779: SSL negotiation failure

Why do I get this kind of message?
Please answer if you know the cause and solution.

Thanks.

Hibiki

This is the message that Vertica receives the 'clusterstatus' command from the client. As this is the product specification and is helpful to know Vertica receives this command from the unexcepted machines, we cannot make Vertica stop to generate this message. I think 192.168.183.61 machine is for MC. Please ignore this FATAL message on your monitoring tool.

yamakawa

@hibiki san
Thank you for answer.
We'll ignore this messages.