UTMStack
UTMStack v10, local install issue #437
-
|
My local install now won't load the UTMStack web portal. I get a "502 Gateway Error" instead. I tried an updated installer, but got this in /var/log/utm-setup.log: Starting datasources_agent_manager ... error ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (27eb8c538e81a507359d5203241598cb09076c2a0ddaf8730637d82025f1e131): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (8b247f7a496e72fc2a1710ed4c980841368bf96c58c3d32ba9b10445505f895a): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (6f52a7284cfa1fcc15d36fff3ba1c12c6ebf68dc06c627151ba49c29a249f4b9): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (27eb8c538e81a507359d5203241598cb09076c2a0ddaf8730637d82025f1e131): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
Hello, this error is returned by Docker when a service tries to start using a port that is already in use by another service. Please try using the command: Then restart the server and run the installer again. |
Beta Was this translation helpful? Give feedback.
-
|
Same result: support@siem: UTMStack InstallerChecking system requirements |
Beta Was this translation helpful? Give feedback.
-
|
@MaterialStep4 can you please provide the logs after "backend start failure:" line?? |
Beta Was this translation helpful? Give feedback.
-
|
Tried again, with a reboot, then ran the installer. It still failed. |
Beta Was this translation helpful? Give feedback.
-
|
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (68994e992d8a812dafd2a8a7a54e18844dea6c0c97fcbdd6e66bc226c2543694): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
Encountered errors while bringing up the project.
Found multiple config files with supported names: docker-compose.yml, compose.yml
Using docker-compose.yml
The Docker Engine you're using is running in swarm mode.
Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.
To deploy your application across the swarm, use `docker stack deploy`.
Starting postgres ...
Starting node1 ...
openvas is up-to-date
wazuh is up-to-date
autoupdate is up-to-date
watchtower is up-to-date
datasources_transporter is up-to-date
datasources_probe_api is up-to-date
datasources_mutate is up-to-date
filebrowser is up-to-date
Starting datasources_agent_manager ...
logstash is up-to-date
Host is already in use by another container
Starting postgres ... error
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (877ea6e26d45289fb17252f942984a9dcc0463ab495f94bb163cb723e807c472): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
Host is already in use by another container
Starting node1 ... error
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (fac941b5340b4103347aeaf3907aef8f867a21374b80823ae98b97c04475848f): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
Host is already in use by another container
Starting datasources_agent_manager ... error
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (98ed6d801d9a549f6a2ea86bfd720a1c758148495fe510362c3b451089caf47c): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (877ea6e26d45289fb17252f942984a9dcc0463ab495f94bb163cb723e807c472): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (fac941b5340b4103347aeaf3907aef8f867a21374b80823ae98b97c04475848f): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (98ed6d801d9a549f6a2ea86bfd720a1c758148495fe510362c3b451089caf47c): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
Encountered errors while bringing up the project.
Found multiple config files with supported names: docker-compose.yml, compose.yml
Using docker-compose.yml
The Docker Engine you're using is running in swarm mode.
Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.
To deploy your application across the swarm, use `docker stack deploy`.
datasources_mutate is up-to-date
Starting postgres ...
Starting node1 ...
openvas is up-to-date
wazuh is up-to-date
autoupdate is up-to-date
watchtower is up-to-date
filebrowser is up-to-date
datasources_transporter is up-to-date
datasources_probe_api is up-to-date
logstash is up-to-date
Starting datasources_agent_manager ...
Host is already in use by another container
Starting node1 ... error
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (1da12a79b11ccb5a2f73ed17f208b1a6792d6c8bbb9fb859ea799a95dcc04aca): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
Host is already in use by another container
Starting postgres ... error
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (5399ee165cb82319fb2fd82fb17b5626b9e04efbf7e145d6ec1cf2ab29b70597): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
Host is already in use by another container
Starting datasources_agent_manager ... error
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (2981bb1cef10df0fc5d5f754f622ee04f837462753d4e96610ef59d23b264788): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (1da12a79b11ccb5a2f73ed17f208b1a6792d6c8bbb9fb859ea799a95dcc04aca): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (5399ee165cb82319fb2fd82fb17b5626b9e04efbf7e145d6ec1cf2ab29b70597): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (2981bb1cef10df0fc5d5f754f622ee04f837462753d4e96610ef59d23b264788): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
Encountered errors while bringing up the project.
Found multiple config files with supported names: docker-compose.yml, compose.yml
Using docker-compose.yml
The Docker Engine you're using is running in swarm mode.
Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.
To deploy your application across the swarm, use `docker stack deploy`.
Starting postgres ...
Starting node1 ...
openvas is up-to-date
wazuh is up-to-date
autoupdate is up-to-date
watchtower is up-to-date
filebrowser is up-to-date
datasources_transporter is up-to-date
datasources_probe_api is up-to-date
datasources_mutate is up-to-date
Starting datasources_agent_manager ...
logstash is up-to-date
Host is already in use by another container
Host is already in use by another container
Starting node1 ... error
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (2b2b6ea21ef88c56af332d0837e30cbaa8719a9d782a1b3dd4c187b86fc9860a): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
Starting postgres ... error
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (de43d31d431b8b51b9dbcbccbd0d97b9f197f3c074a860a76860d2f63861a30f): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
Host is already in use by another container
Starting datasources_agent_manager ... error
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (98f3903ff896f16c3299a47c987e7ef25f6f9c152624859af9fbad8340f5d928): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (2b2b6ea21ef88c56af332d0837e30cbaa8719a9d782a1b3dd4c187b86fc9860a): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (de43d31d431b8b51b9dbcbccbd0d97b9f197f3c074a860a76860d2f63861a30f): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (98f3903ff896f16c3299a47c987e7ef25f6f9c152624859af9fbad8340f5d928): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
Encountered errors while bringing up the project.
Found multiple config files with supported names: docker-compose.yml, compose.yml
Using docker-compose.yml
The Docker Engine you're using is running in swarm mode.
Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.
To deploy your application across the swarm, use `docker stack deploy`.
Starting postgres ...
Starting node1 ...
openvas is up-to-date
wazuh is up-to-date
autoupdate is up-to-date
watchtower is up-to-date
filebrowser is up-to-date
datasources_transporter is up-to-date
datasources_probe_api is up-to-date
datasources_mutate is up-to-date
Starting datasources_agent_manager ...
logstash is up-to-date
Host is already in use by another container
Starting postgres ... error
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (8b247f7a496e72fc2a1710ed4c980841368bf96c58c3d32ba9b10445505f895a): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
Host is already in use by another container
Starting node1 ... error
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (6f52a7284cfa1fcc15d36fff3ba1c12c6ebf68dc06c627151ba49c29a249f4b9): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
Host is already in use by another container
Starting datasources_agent_manager ... error
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (27eb8c538e81a507359d5203241598cb09076c2a0ddaf8730637d82025f1e131): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
ERROR: for postgres Cannot start service postgres: driver failed programming external connectivity on endpoint postgres (8b247f7a496e72fc2a1710ed4c980841368bf96c58c3d32ba9b10445505f895a): Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
ERROR: for node1 Cannot start service node1: driver failed programming external connectivity on endpoint node1 (6f52a7284cfa1fcc15d36fff3ba1c12c6ebf68dc06c627151ba49c29a249f4b9): Error starting userland proxy: listen tcp4 0.0.0.0:9200: bind: address already in use
ERROR: for datasources_agent_manager Cannot start service datasources_agent_manager: driver failed programming external connectivity on endpoint datasources_agent_manager (27eb8c538e81a507359d5203241598cb09076c2a0ddaf8730637d82025f1e131): Error starting userland proxy: listen tcp4 0.0.0.0:9000: bind: address already in use
Encountered errors while bringing up the project.
…_________________________________________________
Jeff Slauson – IT Consultant – Creative Software Services, Inc.
***@***.******@***.***> – C: 319.310.0256 – O: 319.362.7722 ex.114
From: JD ***@***.***>
Sent: Friday, February 9, 2024 4:42 AM
To: utmstack/UTMStack ***@***.***>
Cc: Jeff Slauson ***@***.***>; Mention ***@***.***>
Subject: Re: [utmstack/UTMStack] UTMStack v10, local install issue (Discussion #437)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@MaterialStep4<https://github.com/MaterialStep4> can you please provide the logs after "backend start failure:" line??
—
Reply to this email directly, view it on GitHub<#437 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AP666QOTU2E77AX6K5UPZC3YSX4QVAVCNFSM6AAAAABDANPMGWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMJXGQ3TS>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, @MaterialStep4, according to the logs that you provided, maybe you have installed UTMStack on a "non clean" system, we recommend you to install it from scratch on a new system according to our guides. Use the latest version. Also, check your network, some required ports needs to be open so UTMStack can work as expected. |
Beta Was this translation helpful? Give feedback.
-
|
I did a full format and reinstall of UTMStack, and the issue is resolved.
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Freddy R. Laffita Almaguer ***@***.***>
Sent: Monday, February 26, 2024 3:17:04 AM
To: utmstack/UTMStack ***@***.***>
Cc: MaterialStep4 ***@***.***>; Mention ***@***.***>
Subject: Re: [utmstack/UTMStack] UTMStack v10, local install issue (Discussion #437)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Hi, @MaterialStep4<https://github.com/MaterialStep4>, according to the logs that you provided, maybe you have installed UTMStack on a "non clean" system, we recommend you to install it from scratch on a new system according to our guides. Also, check your network, some required ports needs to be open so UTMStack can work as expected.
—
Reply to this email directly, view it on GitHub<#437 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AP666QLMJJ2SUTKJ3VG3D53YVRHJBAVCNFSM6AAAAABDANPMGWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKOBZHA3DQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hi, @MaterialStep4, according to the logs that you provided, maybe you have installed UTMStack on a "non clean" system, we recommend you to install it from scratch on a new system according to our guides. Use the latest version. Also, check your network, some required ports needs to be open so UTMStack can work as expected.