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.

Sign up for GitHub

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

Jump to bottom

Had to stop portmaster because it blocked every connection from one day to the other #1328

Closed
NicolasGoeddel opened this issue Sep 23, 2023 · 14 comments
Closed

Had to stop portmaster because it blocked every connection from one day to the other #1328

NicolasGoeddel opened this issue Sep 23, 2023 · 14 comments
Labels
bug TYPE: a report on something that isn't working needs debug info ATTRIBUTE: this issue requires debug info to continue handling it stale ATTRIBUTE: this issue has not had recent activity

Comments

@NicolasGoeddel
Copy link

NicolasGoeddel commented Sep 23, 2023 •
edited
Loading

Pre-Submit Checklist:

What happened:
Today I started my computer from suspend and was not able to open any website. A dig google.de seemed to work but a curl timed out. In Firefox every tab I had open and tried to refresh ran into a timeout.
The UI of portmaster did not show anything weird but I decided to restart the service anyway with systemctl restart portmaster. The restart process never succeeded, so I tried systemctl stop portmaster in a different tab which worked after a while.
At the same time I did a journalctl -fu portmaster in a third tab and saw stuff like that:

nicolas@Rocky:~$ sudo journalctl -fu portmaster
[sudo] Passwort für nicolas: 
Sep 23 13:02:42 Rocky portmaster-start[623836]: 230923 13:02:42.816 on/nfq/nfq:212 ▶ WARN 099 nfqueue: no verdict set for packet pkt:7860 qid:17040 (192.168.178.25 -> 185.125.188.54) after 20.000860543s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.087 on/nfq/nfq:212 ▶ WARN 101 nfqueue: no verdict set for packet pkt:7862 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.000408251s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.087 on/nfq/nfq:212 ▶ WARN 103 nfqueue: no verdict set for packet pkt:7861 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.000456092s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.375 on/nfq/nfq:212 ▶ WARN 105 nfqueue: no verdict set for packet pkt:7864 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.000617775s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.375 on/nfq/nfq:212 ▶ WARN 107 nfqueue: no verdict set for packet pkt:7863 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.000668969s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.588 on/nfq/nfq:212 ▶ WARN 109 nfqueue: no verdict set for packet pkt:7866 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.001056938s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.588 on/nfq/nfq:212 ▶ WARN 111 nfqueue: no verdict set for packet pkt:7865 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.001110367s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.617 on/nfq/nfq:212 ▶ WARN 113 nfqueue: no verdict set for packet pkt:7867 qid:17040 (192.168.178.25 -> 8.8.4.4) after 20.00097697s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.617 on/nfq/nfq:212 ▶ WARN 115 nfqueue: no verdict set for packet pkt:7868 qid:17040 (192.168.178.25 -> 8.8.4.4) after 20.000956646s, dropping
Sep 23 13:02:43 Rocky portmaster-start[623836]: 230923 13:02:43.974 on/nfq/nfq:212 ▶ WARN 117 nfqueue: no verdict set for packet pkt:1351 qid:17160 (fe80::de15:c8ff:fef9:2120 -> 2a02:810b:4340:1710:c6df:1c5:1408:563a) after 20.000743351s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.075 on/nfq/nfq:212 ▶ WARN 119 nfqueue: no verdict set for packet pkt:7869 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000115477s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.075 on/nfq/nfq:212 ▶ WARN 121 nfqueue: no verdict set for packet pkt:7870 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000069592s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.095 on/nfq/nfq:212 ▶ WARN 123 nfqueue: no verdict set for packet pkt:1545 qid:17060 (2a02:810b:4340:1710:c6df:1c5:1408:563a -> 2a03:2880:f276:cd:face:b00c:0:167) after 20.000503377s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.161 on/nfq/nfq:212 ▶ WARN 125 nfqueue: no verdict set for packet pkt:7873 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000804254s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.161 on/nfq/nfq:212 ▶ WARN 127 nfqueue: no verdict set for packet pkt:7872 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000835542s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.161 on/nfq/nfq:212 ▶ WARN 129 nfqueue: no verdict set for packet pkt:7871 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000879473s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.351 on/nfq/nfq:212 ▶ WARN 131 nfqueue: no verdict set for packet pkt:7874 qid:17040 (192.168.178.25 -> 157.240.251.60) after 20.000519929s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.567 on/nfq/nfq:212 ▶ WARN 133 nfqueue: no verdict set for packet pkt:1546 qid:17060 (2a02:810b:4340:1710:c6df:1c5:1408:563a -> 2a00:1450:4001:810::2003) after 20.000192095s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.567 on/nfq/nfq:212 ▶ WARN 135 nfqueue: no verdict set for packet pkt:1547 qid:17060 (2a02:810b:4340:1710:c6df:1c5:1408:563a -> 2a00:1450:4001:810::2003) after 20.000168419s, dropping
Sep 23 13:02:44 Rocky portmaster-start[623836]: 230923 13:02:44.998 on/nfq/nfq:212 ▶ WARN 137 nfqueue: no verdict set for packet pkt:1352 qid:17160 (fe80::de15:c8ff:fef9:2120 -> 2a02:810b:4340:1710:c6df:1c5:1408:563a) after 20.000384159s, dropping
Sep 23 13:02:45 Rocky portmaster-start[623836]: 230923 13:02:45.119 on/nfq/nfq:212 ▶ WARN 139 nfqueue: no verdict set for packet pkt:7875 qid:17040 (192.168.178.25 -> 185.125.188.59) after 20.000327867s, dropping
Sep 23 13:02:46 Rocky portmaster-start[623836]: 230923 13:02:46.022 on/nfq/nfq:212 ▶ WARN 141 nfqueue: no verdict set for packet pkt:1353 qid:17160 (fe80::de15:c8ff:fef9:2120 -> 2a02:810b:4340:1710:c6df:1c5:1408:563a) after 20.000643901s, dropping
...

And the list goes on.

And finally it stopped:

Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: State 'stop-sigterm' timed out. Killing.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 623836 (portmaster-star) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560142 (portmaster-core) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 623838 (portmaster-star) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 624485 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 624492 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560143 (portmaster-core) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560144 (portmaster-core) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560145 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560146 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560149 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560150 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560152 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560153 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560198 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560200 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560295 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560302 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3560303 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3562190 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3570397 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Killing process 3605660 (n/a) with signal SIGKILL.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Main process exited, code=killed, status=9/KILL
Sep 23 13:03:47 Rocky portmaster-start[3607185]: Error: 10 errors occurred:
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/iptables -t mangle -C OUTPUT -j PORTMASTER-INGEST-OUTPUT --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGEST-OUTPUT' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/iptables -t mangle -C INPUT -j PORTMASTER-INGEST-INPUT --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGEST-INPUT' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/iptables -t filter -C OUTPUT -j PORTMASTER-FILTER --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/iptables -t filter -C INPUT -j PORTMASTER-FILTER --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/iptables -t nat -C OUTPUT -j PORTMASTER-REDIRECT --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-REDIRECT' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/ip6tables -t mangle -C OUTPUT -j PORTMASTER-INGEST-OUTPUT --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGEST-OUTPUT' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/ip6tables -t mangle -C INPUT -j PORTMASTER-INGEST-INPUT --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGEST-INPUT' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/ip6tables -t filter -C OUTPUT -j PORTMASTER-FILTER --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/ip6tables -t filter -C INPUT -j PORTMASTER-FILTER --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
Sep 23 13:03:47 Rocky portmaster-start[3607185]:         * running [/usr/sbin/ip6tables -t nat -C OUTPUT -j PORTMASTER-REDIRECT --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-REDIRECT' does not exist
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Failed with result 'timeout'.
Sep 23 13:03:47 Rocky systemd[1]: Stopped Portmaster by Safing.
Sep 23 13:03:47 Rocky systemd[1]: portmaster.service: Consumed 2h 7min 23.745s CPU time.

What did you expect to happen?:
Well, it should just work as every day.

How did you reproduce it?:
I will try to reproduce it right after I have posted the first version of this bug report.
Edit:
I now have started it again and it seems to work like expected. So currently I am not able to reproduce it. But in case you want to have a look at the logs, I copied all the logs from /opt/portmaster/logs from before after I stopped portmaster. Before adding them to this ticket I have to look into them to remove private information if there is any.

Debug Information:
@NicolasGoeddel NicolasGoeddel added the bug TYPE: a report on something that isn't working label Sep 23, 2023
@Raphty Raphty added the needs debug info ATTRIBUTE: this issue requires debug info to continue handling it label Sep 25, 2023
@github-actions
Copy link

Hey @NicolasGoeddel, thank you for raising this issue with us.

After a first review we noticed that we will require the Debug Info for further investigation. However, you haven't supplied any Debug Info in your report.

Please collect Debug Info from Portmaster while the reported issue is present.

@Raphty
Copy link
Member

Raphty commented Sep 25, 2023

yes the debug info would be nice. thanks

@NicolasGoeddel
Copy link
Author

I am not sure if I should hope that it happens again. 😅 But when I does I surely will give you the debug info.

@NicolasGoeddel
Copy link
Author

Damn, I just had the same issue again but forgot to save the Debug Info again...

The journal today started like this:

Okt 18 09:56:14 Rocky portmaster-start[46243]: 231018 09:56:14.119 dbus_linux:065 ▶ WARN 001 failed to get nameserver: failed to access /:org.freedesktop.NetworkManager.Connection.Active.Ip4Config: Das Objekt e>
Okt 18 09:56:14 Rocky portmaster-start[46243]: 231018 09:56:14.119 dbus_linux:072 ▶ WARN 003 failed to get nameserver: failed to access /:org.freedesktop.NetworkManager.Connection.Active.Ip6Config: Das Objekt e>
Okt 18 09:56:41 Rocky portmaster-start[46243]: 231018 09:56:41.172 er/resolve:453 ▶ WARN 005 resolver: query to dns://1.1.1.1:53#system failed: read udp 192.168.178.25:11172->1.1.1.1:53: i/o timeout
Okt 18 09:56:41 Rocky portmaster-start[46243]: 231018 09:56:41.172 er/resolve:453 ▶ WARN 007 resolver: query to dns://1.1.1.1:53#system failed: read udp 192.168.178.25:58116->1.1.1.1:53: i/o timeout
Okt 18 09:56:41 Rocky portmaster-start[46243]: 231018 09:56:41.431 er/resolve:453 ▶ WARN 009 resolver: query to dns://1.1.1.1:53#system failed: read udp 192.168.178.25:30085->1.1.1.1:53: i/o timeout
Okt 18 09:56:41 Rocky portmaster-start[46243]: 231018 09:56:41.431 er/resolve:453 ▶ WARN 011 resolver: query to dns://1.1.1.1:53#system failed: read udp 192.168.178.25:23966->1.1.1.1:53: i/o timeout
Okt 18 09:56:53 Rocky portmaster-start[46243]: 231018 09:56:53.687 connection:506 ▶ WARN 013 network: failed to get process and profile of PID 83906: failed to get Path for p83906: readlink /proc/83906/exe: no >
Okt 18 09:56:53 Rocky portmaster-start[46243]: 231018 09:56:53.688 connection:506 ▶ WARN 015 network: failed to get process and profile of PID 83907: failed to get Path for p83907: readlink /proc/83907/exe: no >
Okt 18 09:57:12 Rocky portmaster-start[46243]: 231018 09:57:12.814 pat/notify:170 ▶ WARN 017 compat: detected secure dns bypass issue with /snap/code/143/usr/share/code/code
Okt 18 09:57:12 Rocky portmaster-start[46243]: 231018 09:57:12.814 pat/notify:170 ▶ WARN 019 [9x] compat: detected secure dns bypass issue with /snap/code/143/usr/share/code/code
Okt 18 09:57:33 Rocky portmaster-start[46243]: 231018 09:57:33.826 on/nfq/nfq:212 ▶ WARN 021 nfqueue: no verdict set for packet pkt:1556 qid:17040 (192.168.178.25 -> 8.8.4.4) after 20.000048901s, dropping
Okt 18 09:57:33 Rocky portmaster-start[46243]: 231018 09:57:33.826 on/nfq/nfq:212 ▶ WARN 023 nfqueue: no verdict set for packet pkt:1557 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.00005358s, dropping
....
<over 10000 lines of the same WARN and ERRO messages>
...
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: State 'stop-sigterm' timed out. Killing.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46243 (portmaster-star) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46437 (portmaster-core) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46248 (portmaster-star) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46449 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46450 (portmaster-core) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46452 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46454 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46455 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46456 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46457 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46458 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46460 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46463 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46464 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46534 (portmaster-core) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Killing process 46713 (n/a) with signal SIGKILL.
Okt 18 10:37:51 Rocky systemd[1]: portmaster.service: Main process exited, code=killed, status=9/KILL
Okt 18 10:37:52 Rocky portmaster-start[93638]: Error: 10 errors occurred:
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/iptables -t mangle -C OUTPUT -j PORTMASTER-INGEST-OUTPUT --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGEST>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/iptables -t mangle -C INPUT -j PORTMASTER-INGEST-INPUT --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGEST-I>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/iptables -t filter -C OUTPUT -j PORTMASTER-FILTER --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' does >
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/iptables -t filter -C INPUT -j PORTMASTER-FILTER --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' does n>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/iptables -t nat -C OUTPUT -j PORTMASTER-REDIRECT --wait]: exit status 2: iptables v1.8.7 (nf_tables): Chain 'PORTMASTER-REDIRECT' does>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/ip6tables -t mangle -C OUTPUT -j PORTMASTER-INGEST-OUTPUT --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGE>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/ip6tables -t mangle -C INPUT -j PORTMASTER-INGEST-INPUT --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-INGEST>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/ip6tables -t filter -C OUTPUT -j PORTMASTER-FILTER --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' doe>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/ip6tables -t filter -C INPUT -j PORTMASTER-FILTER --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-FILTER' does>
Okt 18 10:37:52 Rocky portmaster-start[93638]:         * running [/usr/sbin/ip6tables -t nat -C OUTPUT -j PORTMASTER-REDIRECT --wait]: exit status 2: ip6tables v1.8.7 (nf_tables): Chain 'PORTMASTER-REDIRECT' do>
Okt 18 10:37:52 Rocky systemd[1]: portmaster.service: Failed with result 'timeout'.
Okt 18 10:37:52 Rocky systemd[1]: Stopped Portmaster by Safing.
Okt 18 10:37:52 Rocky systemd[1]: portmaster.service: Consumed 4min 9.998s CPU time.

In the background I ran sudo systemctl stop portmaster again.
Next time I really try to get some DebugInfo.

@NicolasGoeddel
Copy link
Author

NicolasGoeddel commented Oct 19, 2023 •
edited
Loading

It is happening again right now out of nowhere.
Here's the Debug Info: portmaster-issue-1328-debug-info.txt

I am going to restart the service so I can work again.

@NicolasGoeddel
Copy link
Author

In case it helps you. These are the first few lines of journalctl -u portmaster --since today:

Okt 19 12:31:51 Rocky portmaster-start[94471]: 231019 12:31:51.505 pat/notify:170 ▶ WARN 113 [4x] compat: detected secure dns bypass issue with /opt/Signal/signal-desktop
Okt 19 12:31:51 Rocky portmaster-start[94471]: 231019 12:31:51.505 pat/notify:170 ▶ WARN 115 [10x] compat: detected secure dns bypass issue with /opt/Signal/signal-desktop
Okt 19 12:32:11 Rocky portmaster-start[94471]: 231019 12:32:11.510 on/nfq/nfq:212 ▶ WARN 117 nfqueue: no verdict set for packet pkt:11090 qid:17040 (192.168.178.25 -> 1.1.1.1) after 20.000966867s, dropping
Okt 19 12:32:12 Rocky portmaster-start[94471]: 231019 12:32:12.518 on/nfq/nfq:212 ▶ WARN 119 nfqueue: no verdict set for packet pkt:11100 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000616735s, dropping
Okt 19 12:32:12 Rocky portmaster-start[94471]: 231019 12:32:12.519 on/nfq/nfq:212 ▶ WARN 121 nfqueue: no verdict set for packet pkt:11103 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000554297s, dropping
Okt 19 12:32:12 Rocky portmaster-start[94471]: 231019 12:32:12.519 on/nfq/nfq:212 ▶ WARN 123 nfqueue: no verdict set for packet pkt:11102 qid:17040 (192.168.178.25 -> 8.8.8.8) after 20.000598716s, dropping
....

I am using my computer since Okt 19 10:01:01 and it worked as expected. It just changed with that line you see above.

@NicolasGoeddel
Copy link
Author

I just had the issue again. Here's the Debug Info: 2023-10-24_portmaster-issue-1328-debug-info.txt

@NicolasGoeddel
Copy link
Author

Had the issue again. Here's the Debug Info: 2023-11-06_portmaster-issue-1328-debug-info.txt

@github-actions GitHub Actions
Copy link

github-actions bot commented Jan 9, 2024

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Jan 9, 2024
@NicolasGoeddel
Copy link
Author

Since November the issue did not happen again. So maybe it already is solved. I am not sure.
But since I got no answers to my last comments yet I want it to stay open.

@Raphty
Copy link
Member

Raphty commented Jan 9, 2024

thanks for the update, I looked into the debug info, I guess they were always after the issue happened, and I could not find the issue in there.

@NicolasGoeddel
Copy link
Author

thanks for the update, I looked into the debug info, I guess they were always after the issue happened, and I could not find the issue in there.

I copied the debug info during the issue. After copying it I restarted the portmaster service to be able to post it here. 😉

@github-actions github-actions bot removed the stale ATTRIBUTE: this issue has not had recent activity label Jan 10, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Mar 13, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug TYPE: a report on something that isn't working needs debug info ATTRIBUTE: this issue requires debug info to continue handling it stale ATTRIBUTE: this issue has not had recent activity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NicolasGoeddel @Raphty