Error with listener 7080


New Member
I encountered this issue for the second time. Unfortunately I was not able to check what occupied port before server was rebooted.

Basically port 7080 gets occupied and this results in not loading any vhost. SSH working, all thing, but nothing loads. Logs shows this:
2020-09-24 03:56:31.827112 [ERROR] HttpListener::start(): Can't listen at address adminListener: Address already in use!
2020-09-24 03:56:31.827769 [ERROR] HttpServer::addListener(adminListener) failed to create new listener
2020-09-24 03:56:31.827784 [ERROR] [config:admin:listener:adminListener] failed to start listener on address *:7080!
2020-09-24 03:56:31.827793 [ERROR] [config:admin:listener] No listener is available for admin virtual host!
2020-09-24 03:56:31.827825 [ERROR] Fatal error in configuration, exit!
Strange is that it is doing on one particular server. Other with same config are fine. I found out that at the same time there is certbot working. Could it be issue? Any idea how to prevent it?
2020-09-24 03:56:31, new private key to /etc/letsencrypt/archive/
2020-09-24 03:56:31, certificate to /etc/letsencrypt/archive/
2020-09-24 03:56:31, chain to /etc/letsencrypt/archive/
2020-09-24 03:56:31, full chain to /etc/letsencrypt/archive/
2020-09-24 03:56:31, new config /etc/letsencrypt/renewal/
2020-09-24 03:56:31,460:INFO:certbot.hooks:Running deploy-hook command: /usr/local/lsws/bin/lswsctrl restart
2020-09-24 03:56:34,531:INFO:certbot.hooks:Output from lswsctrl:
[OK] litespeed: pid=9703.
[OK] litespeed: pid=9729.



Let's encrypt probably not the issue. Better get the result next time with the following command so you can see which process occupied the admin port,
netstat -antupl | grep 7080


New Member
Hi, it happened again! I checked port before reboot (solved it as before) but nothing. Empty output and you can see it without grep:

netstat -antupl
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0    *               LISTEN      1633/master
tcp        0      0*               LISTEN      7029/sshd: root@pts
tcp        0      0   *               LISTEN      1159/sshd
tcp        0      0*               LISTEN      1445/mysqld
tcp        0      0*               LISTEN      1232/redis-server 1
tcp        0      0 *               LISTEN      834/systemd-resolve
tcp        0      0 78.47.XX.XXX:666        8.40.30.XX:58234        ESTABLISHED 7174/sshd: root@not
tcp        0    272 78.47.XX.XXX:666        8.40.30.XX:58206        ESTABLISHED 7029/sshd: root@pts
tcp6       0      0 :::25                   :::*                    LISTEN      1633/master
tcp6       0      0 ::1:6010                :::*                    LISTEN      7029/sshd: root@pts
tcp6       0      0 :::666                  :::*                    LISTEN      1159/sshd
tcp6       0      0 ::1:6379                :::*                    LISTEN      1232/redis-server 1
udp        0      0    *                           865/dhclient
udp        0      0 *                           834/systemd-resolve
Any other idea? OLS was meanwhile upgraded to 1.6.15. And it has to be something weird because as I mentioned it's just one server with no extra configuration.