Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Classical server has a maximum of 64 connections when using systemd init scripts (ubuntu >= 16.04) [CORE5503] #5772

Closed
firebird-automations opened this issue Mar 15, 2017 · 10 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @kattunga

When using classic server with new systemd scripts there is a limit of 64 concurrent connections.

This is because systemd.socket has a default of 64 connections when Accept is true.

https://www.freedesktop.org/software/systemd/man/systemd.socket.html#MaxConnections=

To fix the problem a value for MaxConnections should be specified in /lib/systemd/system/firebird-classic.socket

[Unit]
Description=Firebird Classic Activation Socket
Conflicts=firebird-superserver.service

[Socket]
ListenStream=3050
Accept=true
MaxConnections=1024

[Install]
WantedBy=sockets.target

Commits: c126cbd 114885e

@firebird-automations
Copy link
Collaborator Author

Modified by: @kattunga

description: When using classic server with new systemd scripts there is a limit of 64 concurrent connections.

This is because systemd.socket has a default of 64 connections when Accept is true.

https://www.freedesktop.org/software/systemd/man/systemd.socket.html#MaxConnections=

To fix the problem a higher should be specified in /lib/systemd/system/firebird-classic.socket

[Unit]
Description=Firebird Classic Activation Socket
Conflicts=firebird-superserver.service

[Socket]
ListenStream=3050
Accept=true
MaxConnections=1024

[Install]
WantedBy=sockets.target

=>

When using classic server with new systemd scripts there is a limit of 64 concurrent connections.

This is because systemd.socket has a default of 64 connections when Accept is true.

https://www.freedesktop.org/software/systemd/man/systemd.socket.html#MaxConnections=

To fix the problem a value for MaxConnections should be specified in /lib/systemd/system/firebird-classic.socket

[Unit]
Description=Firebird Classic Activation Socket
Conflicts=firebird-superserver.service

[Socket]
ListenStream=3050
Accept=true
MaxConnections=1024

[Install]
WantedBy=sockets.target

@firebird-automations
Copy link
Collaborator Author

Modified by: @kattunga

summary: Classical server has a maximum of 64 connections when using systemd scripts => Classical server has a maximum of 64 connections when using systemd init scripts (ubuntu >= 16.04)

@firebird-automations
Copy link
Collaborator Author

Commented by: @ibaseru

this is good info, useful for some FAQ, but this is definitely not a Firebird "bug".
Firebird does not (and should not) change system parameters by installer or itself.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

AFAIU, this is not about system parameters, but rather about parameters of the Firebird service. And they are created by the installer.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0.2 [ 10785 ]

Fix Version: 4.0 Alpha 1 [ 10731 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Cannot be tested

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @kattunga

Thank you Dmitry

@firebird-automations
Copy link
Collaborator Author

Commented by: @mariuz

Solved with this commit

114885e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment