About 30% of my connections are less than 30 seconds. The majority of those are exactly 30 seconds. Is there an explanation to this? I’m just curious and not concerned. Inactivity timeout at 30 seconds maybe?
Not much can be done in 30 seconds. I guess fetching one web page could fit into that time… or a telegram message.
What OS are you on? Do you mean the standalone snowflake proxy? More info pls…
The latest Snowflake standalone proxy compiled using the GO method running on Ubuntu 22.04.4 LTS [5.15.0-102-generic|libc 2.35]
The stats are from the analysis of the verbose logging file.
By the way, how do you know how long the connections are?
Yes, there is an inactivity timeout.
I kinda figured the 30 seconds were that. I see it in the logs but there are lots of 10’s, 20’s, 40’s, and 50’s and was just wondering or even what is preventing activity from happening. Maybe some setting.
Closed connection due to inactivity
I will check my code to see if I can work that message into it’s thinking.
edited later:
I found no way to reliable associate a Closed connection due to inactivity to a particular session. It may be a 30 second timeout but it can apply to a session which was opened more than 30 seconds ago according to my logs.
I analyze the verbose logs using a series of awk and sort.
I get something like this: (I deliberately hid some info on those 2 lines)
Time: 000h 56m 36s open 2024/09/20 12:27:57 xx.xxx.xxx.xxx xxxxxxxxxxxxxxxx-xxxxxxxxxxxx close 2024/09/20 13:24:33
Time: 000h 21m 13s open 2024/09/20 12:40:36 xx.xxx.xxx.xxx xxxxxxxxxxxxxxxx-xxxxxxxxxxxx close 2024/09/20 13:01:49
edited later:
Let me correct this a bit.
The 2 awk scripts do work in Linux but you need a way to include all the logs in the extract process and I found this easier in Windows. Processing only 1 or 2 logs is really meaningless.
I’m sure some smart Linux guy could convert my .bat file to some script in Linux.
Am willing to share but no warranty.