You are not logged in.
- Topics: Active | Unanswered
#1 2022-11-12 10:42:31
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,458
[SOLVED] Wrong process identified as listening on a port.
I think I never faced something like that.
The system says dolphin is listening on 11213, but I know it is not.
So I kill dolphin to see what happens, and system finally answers correctly.
(!)
What the heck is happening here?
koko@Gozer# netstat -anpt|grep 11213
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 xyz.xyz.zzz.163:11213 0.0.0.0:* LISTEN 75004/dolphin
tcp 0 0 xyz.xyz.xyz.210:11213 0.0.0.0:* LISTEN 75004/dolphin
tcp 0 0 100.74.10.196:11213 0.0.0.0:* LISTEN 75004/dolphin
tcp 0 0 127.0.0.1:11213 0.0.0.0:* LISTEN 75004/dolphin
tcp 0 0 192.168.117.20:11213 0.0.0.0:* LISTEN 75004/dolphin
tcp 0 0 xyz.xyz.xyz.200:11213 0.0.0.0:* LISTEN 75004/dolphin
tcp 0 0 192.168.11.1:11213 0.0.0.0:* LISTEN 75004/dolphin
tcp 0 0 xyz.xyz.zzz.163:11213 66.115.165.230:54054 ESTABLISHED 75004/dolphin
tcp 84 0 xyz.xyz.zzz.163:11213 87.249.132.181:53487 CLOSE_WAIT 75004/dolphin
tcp 0 0 xyz.xyz.zzz.163:11213 91.248.27.164:32090 ESTABLISHED 1482864/qbittorrent
tcp 84 0 xyz.xyz.zzz.163:11213 143.244.48.197:13920 CLOSE_WAIT 75004/dolphin
tcp 0 0 xyz.xyz.zzz.163:11213 154.6.93.3:33527 ESTABLISHED 1482864/qbittorrent
tcp6 0 0 ::1:11213 :::* LISTEN 75004/dolphin
tcp6 0 0 fe80::6600:6aff:f:11213 :::* LISTEN 75004/dolphin
tcp6 0 0 fe80::b283:feff:f:11213 :::* LISTEN 75004/dolphin
tcp6 0 0 fe80::e50c:aa6e:d:11213 :::* LISTEN 75004/dolphin
tcp6 0 0 fe80::222:b0ff:fe:11213 :::* LISTEN 75004/dolphin
tcp6 0 0 fe80::287:24ff:fe:11213 :::* LISTEN 75004/dolphin
tcp6 0 0 fe80::222:b0ff:fe:11213 :::* LISTEN 75004/dolphin
[11:37:17] cd ~
koko@Gozer# killall dolphin
[11:37:49] cd ~
koko@Gozer# netstat -anpt|grep 11213
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 xyz.xyz.zzz.163:11213 0.0.0.0:* LISTEN 1482864/qbittorrent
tcp 0 0 xyz.xyz.xyz.210:11213 0.0.0.0:* LISTEN 1482864/qbittorrent
tcp 0 0 100.74.10.196:11213 0.0.0.0:* LISTEN 1482864/qbittorrent
tcp 0 0 127.0.0.1:11213 0.0.0.0:* LISTEN 1482864/qbittorrent
tcp 0 0 192.168.117.20:11213 0.0.0.0:* LISTEN 1482864/qbittorrent
tcp 0 0 xyz.xyz.xyz.200:11213 0.0.0.0:* LISTEN 1482864/qbittorrent
tcp 0 0 192.168.11.1:11213 0.0.0.0:* LISTEN 1482864/qbittorrent
tcp 0 0 xyz.xyz.zzz.163:11213 66.115.165.230:54054 ESTABLISHED 1482864/qbittorrent
tcp 0 0 xyz.xyz.zzz.163:11213 91.248.27.164:32090 ESTABLISHED 1482864/qbittorrent
tcp 0 0 xyz.xyz.zzz.163:11213 154.6.93.3:33527 ESTABLISHED 1482864/qbittorrent
tcp6 0 0 ::1:11213 :::* LISTEN 1482864/qbittorrent
tcp6 0 0 fe80::6600:6aff:f:11213 :::* LISTEN 1482864/qbittorrent
tcp6 0 0 fe80::b283:feff:f:11213 :::* LISTEN 1482864/qbittorrent
tcp6 0 0 fe80::e50c:aa6e:d:11213 :::* LISTEN 1482864/qbittorrent
tcp6 0 0 fe80::222:b0ff:fe:11213 :::* LISTEN 1482864/qbittorrent
tcp6 0 0 fe80::287:24ff:fe:11213 :::* LISTEN 1482864/qbittorrent
tcp6 0 0 fe80::222:b0ff:fe:11213 :::* LISTEN 1482864/qbittorrent [
Last edited by kokoko3k (2022-11-12 13:15:57)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
#2 2022-11-12 11:23:15
- astralc
- Member
- Registered: 2022-09-17
- Posts: 127
Re: [SOLVED] Wrong process identified as listening on a port.
It is a bug in qbittorrent, I think, as I ecounter it (also with smplayer) - processes opened from qbittorrent 'use' the port.
searched in their issue - this bug: https://github.com/qbittorrent/qBittorrent/issues/10312
Last edited by astralc (2022-11-12 11:24:06)
Offline
#3 2022-11-12 13:15:20
- kokoko3k
- Member
- Registered: 2008-11-14
- Posts: 2,458
Re: [SOLVED] Wrong process identified as listening on a port.
Thay explain why sometimes when I restart it, it fails to listen to its ports.
Wow, one can never stop learning, thanks!
Last edited by kokoko3k (2022-11-12 13:15:29)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline