qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service failed

[adrelanos]

Happened to me in whonix-ws-15. (whonixcheck --verbose reports such.)
After sudo systemctl restart qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service ok.
apt upgrading functional, though.

user@host:~$ sudo systemctl status qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service
● qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service - Forward connection to updates proxy over Qubes RPC (127.0.0.1:45358)
   Loaded: loaded (/lib/systemd/system/qubes-updates-proxy-forwarder@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-06-20 12:48:14 UTC; 5min ago
  Process: 2930 ExecStart=/usr/bin/qrexec-client-vm  qubes.UpdatesProxy (code=exited, status=1/FAILURE)
 Main PID: 2930 (code=exited, status=1/FAILURE)

Jun 20 12:48:05 host systemd[1]: Started Forward connection to updates proxy over Qubes RPC (127.0.0.1:45358).
Jun 20 12:48:14 host systemd[1]: qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service: Main process exited, code=exited, status=1/FAILURE
Jun 20 12:48:14 host systemd[1]: qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service: Failed with result 'exit-code'.

sudo journalctl -u qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service
-- Logs begin at Thu 2019-06-20 12:45:56 UTC, end at Thu 2019-06-20 12:56:09 UTC. --
Jun 20 12:48:05 host systemd[1]: Started Forward connection to updates proxy over Qubes RPC (127.0.0.1:45358).
Jun 20 12:48:14 host systemd[1]: qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service: Main process exited, code=exited, status=1/FAILURE
Jun 20 12:48:14 host systemd[1]: qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service: Failed with result 'exit-code'.

user@host:~$ sudo systemctl restart qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service

user@host:~$ sudo systemctl status qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service
● qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service - Forward connection to updates proxy over Qubes RPC (127.0.0.1:45358)
   Loaded: loaded (/lib/systemd/system/qubes-updates-proxy-forwarder@.service; static; vendor preset: enabled)
   Active: active (running) since Thu 2019-06-20 12:53:29 UTC; 1s ago
 Main PID: 12929 (qrexec-client-v)
    Tasks: 1 (limit: 4667)
   Memory: 412.0K
   CGroup: /system.slice/system-qubes\x2dupdates\x2dproxy\x2dforwarder.slice/qubes-updates-proxy-forwarder@3-127.0.0.1:8082-127.0.0.1:45358.service
           └─12929 /usr/bin/qrexec-client-vm qubes.UpdatesProxy

Jun 20 12:53:29 host systemd[1]: Started Forward connection to updates proxy over Qubes RPC (127.0.0.1:45358).

[adrelanos]

[user@dom0 ~]$ cat /etc/qubes-rpc/policy/qubes.UpdatesProxy
$type:TemplateVM $default allow,target=sys-whonix
$tag:whonix-updatevm $default allow,target=sys-whonix
$tag:whonix-updatevm $anyvm deny
## Note that policy parsing stops at the first match,
## so adding anything below "$anyvm $anyvm action" line will have no effect

## Please use a single # to start your custom comments

# Default rule for all TemplateVMs - direct the connection to sys-net
$type:TemplateVM $default allow,target=sys-net

$anyvm $anyvm deny

[user@dom0 ~]$ qvm-tags whonix-ws-15
created-by-dom0
whonix-updatevm

[0brand]

Same issue here. This has been affecting all of the Debian 9 TemplateVMs on multiple systems starting today. Fortunately no issues with Whonix. I'm able to resolve this same as Patrick by restarting qubes-updates-proxy-forwarder

user@debian-9: ~$ sudo journactl -xe 
Jun 21 22:34:48 debian-9 systemd[1]: Failed to start Forward connection to updates proxy over Qubes RPC.
-- Subject: Unit qubes-updates-proxy-forwarder@29-127.0.0.1:8082-127.0.0.1:45746.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit qubes-updates-proxy-forwarder@29-127.0.0.1:8082-127.0.0.1:45746.service has failed.
-- 
-- The result is failed.
Jun 21 22:34:48 debian-9 systemd[1]: qubes-updates-proxy-forwarder@29-127.0.0.1:8082-127.0.0.1:45746.service: Unit entered failed state.

[marmarek]

Check the other side of it - qubes-updates-proxy in sys-whonix. And also see in dom0's journalctl if the qubes.UpdatesProxy qrexec service is called.

[tasket]

Possibly related thread in qubes-users about fedora-30 updates:
https://groups.google.com/d/msgid/qubes-users/919df0ac-c1a5-4da7-912b-fcd55249873f%40googlegroups.com

[adrelanos]

I cannot reproduce this anymore. Therefore closing.

If anyone is experiencing it, please comment and/or reopen as well as try to provide debug output requested by @marmarek in his last comment #5112 (comment) and ask for further help if unclear how to provide so.