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

[YSQL] In case of port already taken connection manager will infinitely restart the process leading to exceed disk usage #25527

Open
1 task done
qvad opened this issue Jan 8, 2025 · 0 comments
Assignees
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug priority/medium Medium priority issue

Comments

@qvad
Copy link
Contributor

qvad commented Jan 8, 2025

Jira Link: DB-14783

Description

If port 5433 is already taken then tserver will spawn restart loop with log files spamming.

41985 2025-01-08 04:01:03.324 UTC info [none none] (init) odyssey (git: 2.17.3.0-b25_FINAL-13376-gf41f8cde88 release)
41985 2025-01-08 04:01:03.324 UTC info [none none] (init) 
41985 2025-01-08 04:01:03.324 UTC info [none none] (init) using configuration file '/home/yugabyte/data/yb-data/tserver/ysql_conn_mgr.conf'
41985 2025-01-08 04:01:03.324 UTC info [none none] (init) 
41985 2025-01-08 04:01:03.339 UTC error [none none] (system) failed to resolve :5433
41985 2025-01-08 04:01:03.339 UTC error [none none] (system) failed to bind any listen address
I0108 04:05:12.776304  1584 ysql_conn_mgr_wrapper.cc:194] Warmup of server connections is disabled in ysql connection manager
I0108 04:05:12.776315  1584 ysql_conn_mgr_wrapper.cc:198] Superuser connections will be made sticky in ysql connection manager
I0108 04:05:12.779645  1584 ysql_conn_mgr_conf.cc:116] Successfully created the configuration file for Ysql Connection Manager: /home/yugabyte/data/yb-data/tserver/ysql_conn_mgr.conf
I0108 04:05:12.779680  1584 ysql_conn_mgr_wrapper.cc:233] Using shared memory segment with key 13997for collecting Ysql Connection Manager stats
I0108 04:05:12.781006  1584 ysql_conn_mgr_wrapper.cc:242] Ysql Connection Manager process running as pid 102131
W0108 04:05:12.821514  1584 subprocess.cc:141] Ysql Connection Manager server returned with code 256, exited with status 1
I0108 04:05:12.821573  1584 process_wrapper.cc:99] Restarting Ysql Connection Managerprocess
I0108 04:05:12.821619  1584 ysql_conn_mgr_wrapper.cc:194] Warmup of server connections is disabled in ysql connection manager
I0108 04:05:12.821631  1584 ysql_conn_mgr_wrapper.cc:198] Superuser connections will be made sticky in ysql connection manager
I0108 04:05:12.822964  1584 ysql_conn_mgr_conf.cc:116] Successfully created the configuration file for Ysql Connection Manager: /home/yugabyte/data/yb-data/tserver/ysql_conn_mgr.conf
I0108 04:05:12.822997  1584 ysql_conn_mgr_wrapper.cc:233] Using shared memory segment with key 13997for collecting Ysql Connection Manager stats
I0108 04:05:12.834286  1584 ysql_conn_mgr_wrapper.cc:242] Ysql Connection Manager process running as pid 102140
W0108 04:05:12.861230  1584 subprocess.cc:141] Ysql Connection Manager server returned with code 256, exited with status 1
I0108 04:05:12.861284  1584 process_wrapper.cc:99] Restarting Ysql Connection Managerprocess
I0108 04:05:12.861326  1584 ysql_conn_mgr_wrapper.cc:194] Warmup of server connections is disabled in ysql connection manager
I0108 04:05:12.861337  1584 ysql_conn_mgr_wrapper.cc:198] Superuser connections will be made sticky in ysql connection manager
I0108 04:05:12.862869  1584 ysql_conn_mgr_conf.cc:116] Successfully created the configuration file for Ysql Connection Manager: /home/yugabyte/data/yb-data/tserver/ysql_conn_mgr.conf
I0108 04:05:12.862895  1584 ysql_conn_mgr_wrapper.cc:233] Using shared memory segment with key 13997for collecting Ysql Connection Manager stats
I0108 04:05:12.863922  1584 ysql_conn_mgr_wrapper.cc:242] Ysql Connection Manager process running as pid 102147
W0108 04:05:12.887552  1584 subprocess.cc:141] Ysql Connection Manager server returned with code 256, exited with status 1

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@qvad qvad added area/ysql Yugabyte SQL (YSQL) status/awaiting-triage Issue awaiting triage labels Jan 8, 2025
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue and removed status/awaiting-triage Issue awaiting triage labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

4 participants