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

Could not start local server #23

Open
olm52 opened this issue May 16, 2022 · 2 comments
Open

Could not start local server #23

olm52 opened this issue May 16, 2022 · 2 comments

Comments

@olm52
Copy link

olm52 commented May 16, 2022

In my Archlinux system fully updated proxy was working fine until a few days ago.
Kernel 5.17.8-AMD
systemd version 250.5-1
Now in journalctl I have these repeated errors:


mag 16 07:29:52 archlinux systemd[1]: go-dispatch-proxy.service: Scheduled restart job, restart counter is at 158.
mag 16 07:29:52 archlinux systemd[1]: Stopped go-dispatch-proxy load balancing proxy.
mag 16 07:29:52 archlinux systemd[1]: Started go-dispatch-proxy load balancing proxy.
mag 16 07:29:52 archlinux go-dispatch-proxy[13750]: [INFO] Load balancer 1: 192.168.1.5, contention ratio: 1
mag 16 07:29:52 archlinux go-dispatch-proxy[13750]: [INFO] Load balancer 2: 192.168.1.6, contention ratio: 1
mag 16 07:29:52 archlinux go-dispatch-proxy[13750]: [FATAL] Could not start local server on  127.0.0.1:8080
mag 16 07:29:52 archlinux systemd[1]: go-dispatch-proxy.service: Main process exited, code=exited, status=1/FAILURE
mag 16 07:29:52 archlinux systemd[1]: go-dispatch-proxy.service: Failed with result 'exit-code'.

This is the systemd service:

[Unit]
Description=go-dispatch-proxy load balancing proxy

[Service]
Type=simple
EnvironmentFile=/etc/go-dispatch-proxy.conf
Restart=on-failure
RestartSec=5s
ExecStart=/usr/bin/go-dispatch-proxy $OPTIONS

[Install]
WantedBy=default.target

And the content of /etc/go-dispatch-proxy.conf

OPTIONS="192.168.1.5 192.168.1.6"

@olm52
Copy link
Author

olm52 commented May 16, 2022

Now testing with a different port with -lport 8081 ...

@olm52
Copy link
Author

olm52 commented May 16, 2022

The port 8080 was used by another service...
However, even with port 8081 the connection often hangs for some time.
I guess this is something about the last release of systemd network or last kernel 5.17.x

I am using SwitchyOmega extension on Chrome.
I still have many mag 16 10:17:46 archlinux systemd[1]: go-dispatch-proxy.service: Failed with result 'exit-code'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant