Gsad max login connection reached without reasons

Archive Greenbone Community Edition
1

Hi There,

I’m witnessing an issue with gsad 7.0.3 where the application stop accepting new connections and force logout of existing sessions. It happens very quickly when the user use the “Back” button in his browser while navigating in the applications. But without this, it happens also while it takes much more time before happening.

Right before this happens, I have the following in my logfile:

gsad main:WARNING:2019-03-21 15h44.28 CET:15405: MHD: Server reached connection limit (closing inbound connection)
gsad main:WARNING:2019-03-21 15h44.29 CET:15405: MHD: Server reached connection limit (closing inbound connection)
gsad main:WARNING:2019-03-21 15h44.29 CET:15405: MHD: Server reached connection limit (closing inbound connection)
gsad main:WARNING:2019-03-21 15h44.44 CET:15405: MHD: Error: received handshake message out of context
gsad main:WARNING:2019-03-21 15h44.44 CET:15405: MHD: Error: received handshake message out of context
gsad main:WARNING:2019-03-21 15h44.44 CET:15405: MHD: Error: received handshake message out of context

In a multi-user configuration setup, this is just unusable. Is it a bug or a configuration issue ? Anything to do avoid this ?

Note that in the case below, there was only 1 user logged on the application. So it’s not related to the number of users connected at the same time.

Thanks a lot

2

Closing as a duplicate of the following topic below which is showing up when searching for “Server reached connection limit” at https://community.greenbone.net/search.