We're Moving!

The Vertica Forum is moving to a new OpenText Analytics Database (Vertica) Community.

Join us there to post discussion topics, learn about

product releases, share tips, access the blog, and much more.

Create My New Community Account Now


{SessionRun} 00000: missing error text — Vertica Forum

{SessionRun} 00000: missing error text

Hi,

I have a simple question about message" missing error text" in Vertica.log as below:

Vertica version :6.1.3
 
28393 2014-08-12 10:56:37.019 DistCall Dispatch:0x7f034f177640 [Txn] <INFO> Commit Complete: Txn: a000000043ad45 at epoch 0x4153b
28394 2014-08-12 10:56:38.402 Init Session:0x7f035800f7f0 <LOG> @v_eprodw1_node0003: 00000/2705: Connection received: host=10.92.160.8 port=11013 (connCnt 1)
28395 2014-08-12 10:56:38.403 Init Session:0x7f035800f7f0 <LOG> @v_eprodw1_node0003: {SessionRun} 00000: missing error text
28396 2014-08-12 10:56:40.103 Init Session:0x7f035800f180 <LOG> @v_eprodw1_node0003: 00000/2705: Connection received: host=10.92.160.9 port=14312 (connCnt 1)
28397 2014-08-12 10:56:40.104 Init Session:0x7f035800f180 <LOG> @v_eprodw1_node0003: {SessionRun} 00000: missing error text

What are the causes of this message? and what does this mean?

This message kept printed in Vertica.log for a couple of days then later 3rd node from three nodes cluster went down with network issue. 

2014-08-11 15:45:58.200 TM Mergeout(00):0x7f717801f570 [Util] <INFO> Task 'TM Mergeout(00)' enabled2014-08-11 15:45:59.512 Init Session:0x7f7164011e70 <LOG> @v_eprodw1_node0003: 00000/2705: Connection received: host=10.92.160.9 port=13532 (connCnt 5)
2014-08-11 15:45:59.513 Init Session:0x7f7164011e70 <LOG> @v_eprodw1_node0003: {SessionRun} 00000: missing error text
2014-08-11 15:46:03.009 Init Session:0x7f7164014510 <LOG> @v_eprodw1_node0003: 00000/2705: Connection received: host=10.92.160.8 port=10887 (connCnt 5)
2014-08-11 15:46:03.010 Init Session:0x7f7164014510 <LOG> @v_eprodw1_node0003: {SessionRun} 00000: missing error text
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> Saw membership message 8192 on V:EPRODW1
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> Saw transitional message; watch for lost daemons
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> Saw membership message 8192 on Vertica:all
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> Saw transitional message; watch for lost daemons
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> Saw membership message 8192 on Vertica:join
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> Saw transitional message; watch for lost daemons
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> Saw membership message 6144 on V:EPRODW1
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> NETWORK change with 1 VS sets
2014-08-11 15:46:20.324 Spread Client:0x7af0e10 [Comms] <INFO> DB Group changed

Please shed some lights on this issue.

Regards,

Moses


Comments

  • do you use load balancer like f5 ? I see the same in our vertica.log and it's related to the health checks from f5.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file