# connections disparity?
Posted: Tue May 16, 2017 11:38 pm
This seems a bit odd, so I wanted to report it to see if this is a potential problem or not. It certainly caused me some grief till I figured out what was happening.
I have had intermittent issues with new connections failing for a long time, many months, and I finally tracked it down. Curiously, it seems a "reporting issue" or just my own misunderstanding.
I run several servers inside the network that offer cloud services outside. (i.e bitcoin, litecoin, StorJ). There are moments when things get overloaded in # connections, but not bandwidth. During these moments, if the total # conenctions exceeded the router setting for "max connections" new connections would fail intermittently. That seems normal. However I never noticed this until now becasue I was looking in the wrong place.
Status -> Connected Hosts -> Hosts with Active Connections
This location lists the # connections active for each host, including gargoyle itself. Yet in those moments of overload, the total number of connections here did not exceed the setting for max connections.
Status -> Overview -> Device -> Connections
This location lists the total connections active and the max setting. Here the # connections did reach the max setting when things quit working.
For instance, the hosts section would list about 2000 total connections but on the overview section it would show 4095. This was during a time when new connections failed. I increased the max connection setting to 8192 and the connections on the overview screen jumped up to about 6000 very quickly. The hosts section added up to about 4000.
After running a while, the # connection in both screens dropped, I believe becasue the application that was causing hte connections was doing frequent retires upon failing that led to the constantly climbing numbers. Once the max setting was increased, the active number rarely exceeds the 2000 now.
So, in summary, It seems that the total # connections on the hosts section does not account for everything. There were more connections in total on the overview section and it was failing from being overloaded.
Is this a problem or a misunderstanding on my part?
I have had intermittent issues with new connections failing for a long time, many months, and I finally tracked it down. Curiously, it seems a "reporting issue" or just my own misunderstanding.
I run several servers inside the network that offer cloud services outside. (i.e bitcoin, litecoin, StorJ). There are moments when things get overloaded in # connections, but not bandwidth. During these moments, if the total # conenctions exceeded the router setting for "max connections" new connections would fail intermittently. That seems normal. However I never noticed this until now becasue I was looking in the wrong place.
Status -> Connected Hosts -> Hosts with Active Connections
This location lists the # connections active for each host, including gargoyle itself. Yet in those moments of overload, the total number of connections here did not exceed the setting for max connections.
Status -> Overview -> Device -> Connections
This location lists the total connections active and the max setting. Here the # connections did reach the max setting when things quit working.
For instance, the hosts section would list about 2000 total connections but on the overview section it would show 4095. This was during a time when new connections failed. I increased the max connection setting to 8192 and the connections on the overview screen jumped up to about 6000 very quickly. The hosts section added up to about 4000.
After running a while, the # connection in both screens dropped, I believe becasue the application that was causing hte connections was doing frequent retires upon failing that led to the constantly climbing numbers. Once the max setting was increased, the active number rarely exceeds the 2000 now.
So, in summary, It seems that the total # connections on the hosts section does not account for everything. There were more connections in total on the overview section and it was failing from being overloaded.
Is this a problem or a misunderstanding on my part?