On 11/17/21 19:27, Marek Marczykowski-Górecki wrote:
Try `systemctl status qubes-updates-proxy` there.
user@sys-firewall ~]$ sudo systemctl status qubes-updates-proxy
○ qubes-updates-proxy.service - Qubes updates proxy (tinyproxy)
Loaded: loaded
(/usr/lib/systemd/system/qubes-updates-proxy.service; enabled; vendor
preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2021-11-17 18:49:19 GMT;
43min ago
└─
ConditionPathExists=|/var/run/qubes-service/qubes-updates-proxy was not met
Nov 17 18:49:19 sys-firewall systemd[1]: Condition check resulted in
Qubes updates proxy (tinyproxy) being skipped.
and the reason is:
-rw-r--r-- 1 root root 0 Nov 17 18:49
/var/run/qubes-service/qubes-udates-proxy
the folder name has a typo:
qubes-udates-proxy vs. qubes-updates-proxy
creating the correct directory fix the issue.
Now the question is who (or what process) creating that wrongly?
Regards:
--
Zrubi
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/7ab34c5c-bb13-381c-ce1f-22c7cc03050e%40zrubi.hu.
