app/portmaster-app.zip failed with: could not get component: the requested file is not available locally

[zeronymous]

What happened:
After rebooting computer, Portmaster core is not running, and cannot start portmaster ui

What did you expect to happen?:
Expected Portmaster to start

How did you reproduce it?:
The start command in /opt/safing/portmaster/portmaster.desktop is /opt/safing/portmaster/portmaster-start app --data=/opt/safing/portmaster. Running this command manually produces the output:

[pmstart] 2024/01/20 04:08:08 app/portmaster-app.zip failed with: could not get component: the requested file is not available locally

Debug Information:
OS: Debian 12
The most recent lines in journalctl -u portmaster.service:

<INTERRUPT>
240119 18:57:44.575 e/run/main:085 ▸WARN236 main: program was interrupted, shutting down.
Stopping Portmaster.service - Portmaster by Safing...
240119 18:57:44.676 dules/stop:057 ▸WARN 238 modules: starting shutdown...
240119 18:57:49.598 ine-status:560 ▸WARN 240 netenv: dns query check failed: resolver is shutting down
240119 18:57:59.600 ine-status:560 ▸WARN 242 netenv: dns query check failed: resolver is shutting down
240119 18:57:09.601 ine-status:560 ▸WARN 244 netenv: dns query check failed: resolver is shutting down
240119 18:57:19.602 ine-status:560 ▸WARN 246 netenv: dns query check failed: resolver is shutting down
240119 18:57:29.604 ine-status:560 ▸WARN 248 netenv: dns query check failed: resolver is shutting down
240119 18:57:39.605 ine-status:560 ▸WARN 250 netenv: dns query check failed: resolver is shutting down
240119 18:58:44.677 es/modules:312 ▸WARN 252 captain: timed out while waiting for stopfn/workers/tasks to finish: stopFn=false workers=1 tasks=0, continuing shutdown...
240119 18:58:44.767 ◂EOF
[pmstart] 2024/01/20 04:16:58 core/portmaster-core exited without error

followed by many repeated instances of:

portmaster.service: Main process exited, code=exited, status=1/FAILURE
Error: 10 errors occurred:
    * running [/usr/bin/iptables -t mangle -C OUTPUT -j PORTMASTER_INGEST_OUTPUT --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER_INGEST_OUTPUT' does not exist
    * running [/usr/bin/iptables -t mangle -C INPUT -j PORTMASTER_INGEST_INPUT --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER_INGEST_INPUT' does not exist
    * running [/usr/bin/iptables -t filter -C OUTPUT -j PORTMASTER-FILTER --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
    * running [/usr/bin/iptables -t filter -C INPUT -j PORTMASTER-FILTER --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
    * running [/usr/bin/iptables -t nat -C OUTPUT -j PORTMASTER-REDIRECT --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER-REDIRECT' does not exist
    * running [/usr/bin/iptables -t mangle -C OUTPUT -j PORTMASTER-INGEST-OUTPUT --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER-INGEST-OUTPUT' does not exist
    * running [/usr/bin/iptables -t mangle -C INPUT -j PORTMASTER-INGEST-INPUT --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER-INGEST-INPUT' does not exist
    * running [/usr/bin/iptables -t filter -C OUTPUT -j PORTMASTER-FILTER --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
    * running [/usr/bin/iptables -t filter -C INPUT -j PORTMASTER-FILTER --wait]: exit status 2 : iptables v1.8.9 (nf_tables): Chain 'PORTMASTER-FILTER' does not exist
    * running [/usr/bin/iptables -t nat -C OUTPUT -j PORTMASTER-REDIRECT --wait]: exit status 2 : iptales v1.8.9 (nf_tables): Chain 'PORTMASTER-REDIRECT' does not exist
portmaster.service: Failed with result 'exit-code'.
portmaster.service: Scheduled restart job, restart counter is at 3.
Stopped portmaster.service - Portmaster by Safing.
Started portmaster.service - Portmaster by Safing.
[pmstart] 2024/01/20 04:11:18 core/portmaster-core failed with: could not get component: signature verification failed: failed to make request to "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": Get "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": dial tcp: lookup updates.safing.io on 127.0.0.1:53 read udp 127.0.0.1:39644->127.0.0.1:53: i/o timeout
[pmstart] 2024/01/20 04:12:40 core/portmaster-core failed with: could not get component: signature verification failed: failed to make request to "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": Get "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": dial tcp: lookup updates.safing.io on 127.0.0.1:53 read udp 127.0.0.1:46955->127.0.0.1:53: i/o timeout
[pmstart] 2024/01/20 04:12:44 updating registry index
[pmstart] 2024/01/20 04:14:04 core/portmaster-core failed with: could not get component: signature verification failed: failed to make request to "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": Get "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": dial tcp: lookup updates.safing.io on 127.0.0.1:53 read udp 127.0.0.1:56244->127.0.0.1:53: i/o timeout
[pmstart] 2024/01/20 04:14:10 updating registry index
[pmstart] 2024/01/20 04:15:30 core/portmaster-core failed with: could not get component: signature verification failed: failed to make request to "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": Get "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": dial tcp: lookup updates.safing.io on 127.0.0.1:53 read udp 127.0.0.1:43236->127.0.0.1:53: i/o timeout
[pmstart] 2024/01/20 04:15:38 updating registry index
[pmstart] 2024/01/20 04:16:58 core/portmaster-core failed with: could not get component: signature verification failed: failed to make request to "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": Get "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": dial tcp: lookup updates.safing.io on 127.0.0.1:53 read udp 127.0.0.1:56916->127.0.0.1:53: i/o timeout
[pmstart] 2024/01/20 04:16:58 encountered 5 consecutive errors, giving up ...
Error: could not get component: signature verification failed: failed to make request to "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": Get "https://updates.safing.io/linux_amd64/core/portmaster-core_v1-6-5.sig": dial tcp: lookup updates.safing.io on 127.0.0.1:53 read udp 127.0.0.1:56916->127.0.0.1:53: i/o timeout

sudo nft list chains | grep PORTMASTER produces no output

contents of /opt/safing/portmaster/updates/linux_amd64/core/:

portmaster-core_v1-4-11
portmaster-core_v1-4-11.sig
portmaster-core_v1-5-1
portmaster-core_v1-5-1.sig
portmaster-core_v1-6-2
portmaster-core_v1-6-2.sig

contents of /opt/safing/portmaster/updates/linux_amd64/app/:

portmaster-app_v0-2-5/
portmaster-app_v0-2-5.zip
portmaster-app_v0-2-5.zip.sig
portmaster-app_v0-2-6/
portmaster-app_v0-2-6.zip
portmaster-app_v0-2-6.zip.sig

opt/safing/portmaster/updates/stable.json contains (among others) the line:

"linux_amd64/core/portmaster-core":"1.6.5",

[github-actions]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[zeronymous]

I was able to resolve the issue by finding the components that were named in config.json but that weren't present in /opt/safing/portmaster/updates/ subfolders and downloading them plus their accompanying .sig files from updates.safing.io and putting them in their correct locations within /opt/safing/portmaster/updates.

I'm not sure why they were missing in the first place though... Is it possible Portmaster applied a partial update (maybe due to lost network or sudden computer shutdown)?

[Raphty]

thanks for the report

sadly figuring out why this happend in one case is always hard, if there would be more reports we could figure it out more easily but this seems like a single incident.

Sorry for your inconvenience and thanks for reporting the fix.