You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
I Shutdown Portmaster from the power icon in the bottom left, and then restarted the app. Next I clicked "START CORE SERVICE" when prompted, and entered my password. Then Portmaster said:
"The Portmaster Core Service is not running"
"Unable to find Portmaster Core Service. Please re-install the Portmaster."
I was like, what? I went and did other stuff, and when I came back Portmaster was running normally.
What did you expect to happen?:
That it would start normally, instead of showing a worrying message and then starting.
How did you reproduce it?:
Shutdown Portmaster,
Run Portmaster,
Click "START CORE SERVICE",
Enter your password,
See this message: "The Portmaster Core Service is not running"
"Unable to find Portmaster Core Service. Please re-install the Portmaster."
Within a few seconds to over a minute, Portmaster will load normally.
Debug Information:
NOTE: I was unable to find a "Copy Debug Information" button on the Settings page. ("Global Settings", accessed from the gear icon, right?)
Version 1.5.1
Portmaster
version 1.5.1
commit tags/v1.5.1-0-g7c3925db32e665a40ba46d888e5e9cacf872beea
built with go1.21.2 (gc) linux/amd64
using options
by user@docker
on 17.10.2023
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
Platform: debian buster/sid
System: debian linux (debian) buster/sid
Kernel: 5.10.0-23-amd64 x86_64
No Module ErrorUnexpected Logs
231110 15:00:38.840 v/location:303 ▶ WARN 004 netenv: failed to get IPv4 device location from traceroute: received final echo reply without time exceeded messages
231110 15:00:39.117 les/worker:109 ▶ ERRO 006 interception: service-worker ebpf bandwidth stats monitor failed (1): ebpf: failed to load ebpf object: field UdpRecvmsg: program udp_recvmsg: load program: invalid argument: BPF_STX uses reserved fields (1 line(s) omitted) - restarting in 2s
231110 15:00:41.270 les/worker:109 ▶ ERRO 008 interception: service-worker ebpf bandwidth stats monitor failed (2): ebpf: failed to load ebpf object: field UdpRecvmsg: program udp_recvmsg: load program: invalid argument: BPF_STX uses reserved fields (1 line(s) omitted) - restarting in 4s
231110 15:00:45.368 les/worker:109 ▶ ERRO 010 interception: service-worker ebpf bandwidth stats monitor failed (3): ebpf: failed to load ebpf object: field UdpRecvmsg: program udp_recvmsg: load program: invalid argument: BPF_STX uses reserved fields (1 line(s) omitted) - restarting in 6s
231110 15:00:51.484 les/worker:109 ▶ ERRO 012 interception: service-worker ebpf bandwidth stats monitor failed (4): ebpf: failed to load ebpf object: field UdpRecvmsg: program udp_recvmsg: load program: invalid argument: BPF_STX uses reserved fields (1 line(s) omitted) - restarting in 8s
231110 15:00:59.603 /interface:042 ▶ WARN 014 ebpf: failed to load ebpf object 5 times, giving up with error field UdpRecvmsg: program udp_recvmsg: load program: invalid argument: BPF_STX uses reserved fields (1 line(s) omitted)
231110 15:01:03.512 pat/notify:170 ▶ WARN 016 compat: detected secure dns bypass issue with /usr/share/code/code
231110 15:01:15.788 pat/notify:170 ▶ WARN 018 compat: detected secure dns bypass issue with /usr/share/code/code
231110 15:03:37.742 pat/notify:170 ▶ WARN 020 compat: detected secure dns bypass issue with /usr/share/code/code
231110 15:08:38.794 pat/notify:170 ▶ WARN 022 compat: detected secure dns bypass issue with /usr/share/code/code
231110 15:10:44.520 CURRENT TIME
Status: Trusted
ActiveSecurityLevel: Trusted
SelectedSecurityLevel: Off
ThreatMitigationLevel: Trusted
CaptivePortal:
OnlineStatus: Online
Depending on what Connections had been open it sometimes takes a while to restart Portmaster.
That it tells you that it could not find something while it is there is unfortunate and potentially something we will look at in the future. But since this does not break anything and is not easily reproducible (not on any of the machines in the office, again it depends on the network state as well) I will close this issue for now.
What happened:
I Shutdown Portmaster from the power icon in the bottom left, and then restarted the app. Next I clicked "START CORE SERVICE" when prompted, and entered my password. Then Portmaster said:
"The Portmaster Core Service is not running"
"Unable to find Portmaster Core Service. Please re-install the Portmaster."
I was like, what? I went and did other stuff, and when I came back Portmaster was running normally.
What did you expect to happen?:
That it would start normally, instead of showing a worrying message and then starting.
How did you reproduce it?:
"Unable to find Portmaster Core Service. Please re-install the Portmaster."
Debug Information:
NOTE: I was unable to find a "Copy Debug Information" button on the Settings page. ("Global Settings", accessed from the gear icon, right?)
Version 1.5.1
Platform: debian buster/sid
No Module Error
Unexpected Logs
Status: Trusted
SPN: disabled (module disabled)
Resolvers: 4/4
Config: 4
Updates: stable (13/27)
Compatibility: IPTables Chains (41)
Goroutine Stack
The text was updated successfully, but these errors were encountered: