So, my OS terminal whenever I tries to update the whole OS, it always says RETCODE 126 for the update. Is there any ways to fix this? @Sven @deeplow
“whole OS” = Qubes OS or a template? If template, which?
If a command is found but is not executable, the return status is 126.
Exit Status (Bash Reference Manual)
the whole entire os cannot update due to 126 error, and I just don’t know what just happened
Again, please describe in detail what you are doing?
sudo qubesctl --show-output state.sls update.qubes-dom0
or
sudo qubes-dom0-update
What is the output besides return code 126?
I tried this command and also the other one, but both came out the exact code as 126. The succession rate is 75%, but the 25% has error 126. Anything done wrong here?
Also, I have downloaded one package and said that qubes.ReceiveUpdates and qfile-agent has failed and exit with the code of 126.
@HPOA909 you are not providing sufficient information to even diagnose your problem. Please familiarize yourself with how to copy and paste clipboard text from dom0, then make the issue happen and copy & paste the output here into a post.
qubes.log (3.2 KB)
Here are the results:
[Howard@dom0 ~]$ sudo qubesctl --show-output state.sls update.qubes-dom0
[WARNING ] /usr/lib/python3.8/site-packages/salt/utils/files.py:396: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
f_handle = open(*args, **kwargs) # pylint: disable=resource-leakage
[ERROR ] Command 'systemd-run' failed with return code: 126
[ERROR ] stderr: Running scope as unit: run-r57eb49c5db8c44bb88ee5fa0652b213c.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 126
[ERROR ] retcode: 126
[ERROR ] Problem encountered upgrading packages. Additional info follows:
result:
----------
pid:
37618
retcode:
126
stderr:
Running scope as unit: run-r57eb49c5db8c44bb88ee5fa0652b213c.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 126
stdout:
local:
----------
ID: /etc/yum.repos.d/qubes-dom0.repo
Function: file.replace
Result: True
Comment: No changes needed to be made
Started: 17:36:53.342556
Duration: 15.577 ms
Changes:
----------
ID: /etc/yum.repos.d/qubes-templates.repo
Function: file.replace
Result: True
Comment: No changes needed to be made
Started: 17:36:53.358322
Duration: 1.702 ms
Changes:
----------
ID: update
Function: cmd.run
Name: if qubes-dom0-update --quiet --assumeyes --clean --action=clean expire-cache >/dev/null 2>&1; then
echo "result=True comment='Cache cleaned'"
else
echo "result=False comment='Could not clean cache'"
fi
Result: True
Comment: Cache cleaned
Started: 17:36:53.360891
Duration: 5896.156 ms
Changes:
----------
ID: update
Function: pkg.uptodate
Result: False
Comment: Problem encountered upgrading packages. Additional info follows:
result:
----------
pid:
37618
retcode:
126
stderr:
Running scope as unit: run-r57eb49c5db8c44bb88ee5fa0652b213c.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 126
stdout:
Started: 17:37:00.552689
Duration: 140813.701 ms
Changes:
Summary for local
------------
Succeeded: 3
Failed: 1
------------
Total states run: 4
Total run time: 146.727 s
DOM0 configuration failed, not continuing
Thank you @HPOA909. For mailing list users, the contents follows. This is beyond my current knowledge but maybe someone like @unman will take a look:
[Howard@dom0 ~]$ sudo qubesctl --show-output state.sls update.qubes-dom0
[WARNING ] /usr/lib/python3.8/site-packages/salt/utils/files.py:396: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
f_handle = open(*args, **kwargs) # pylint: disable=resource-leakage
[ERROR ] Command 'systemd-run' failed with return code: 126
[ERROR ] stderr: Running scope as unit: run-r57eb49c5db8c44bb88ee5fa0652b213c.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 126
[ERROR ] retcode: 126
[ERROR ] Problem encountered upgrading packages. Additional info follows:
result:
----------
pid:
37618
retcode:
126
stderr:
Running scope as unit: run-r57eb49c5db8c44bb88ee5fa0652b213c.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 126
stdout:
local:
----------
ID: /etc/yum.repos.d/qubes-dom0.repo
Function: file.replace
Result: True
Comment: No changes needed to be made
Started: 17:36:53.342556
Duration: 15.577 ms
Changes:
----------
ID: /etc/yum.repos.d/qubes-templates.repo
Function: file.replace
Result: True
Comment: No changes needed to be made
Started: 17:36:53.358322
Duration: 1.702 ms
Changes:
----------
ID: update
Function: cmd.run
Name: if qubes-dom0-update --quiet --assumeyes --clean --action=clean expire-cache >/dev/null 2>&1; then
echo "result=True comment='Cache cleaned'"
else
echo "result=False comment='Could not clean cache'"
fi
Result: True
Comment: Cache cleaned
Started: 17:36:53.360891
Duration: 5896.156 ms
Changes:
----------
ID: update
Function: pkg.uptodate
Result: False
Comment: Problem encountered upgrading packages. Additional info follows:
result:
----------
pid:
37618
retcode:
126
stderr:
Running scope as unit: run-r57eb49c5db8c44bb88ee5fa0652b213c.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 126
stdout:
Started: 17:37:00.552689
Duration: 140813.701 ms
Changes:
Summary for local
------------
Succeeded: 3
Failed: 1
------------
Total states run: 4
Total run time: 146.727 s
DOM0 configuration failed, not continuing
Please don’t mention me (@deeplow) without reason.
sorry
1 Like
@HPOA909
What template are you using for sys-firewall?
If you run an update manually in dom0, with “sudo qubes-dom0-update”,
what is the result?
Fc 34
Notes: I just reinstall the whole thing to get away from this mess
If you get the same error, pick up this thread again.
1 Like
I have another error in these template qubes. This time was the worst time to have in at all time. Here is the command error:
user@debian-10:~$ sudo apt-get update
Err:1 Index of /debian buster InRelease
Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
Err:2 Index of /r4.1/vm/ buster InRelease
Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
Err:3 Index of /debian-security buster/updates InRelease
Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
Reading package lists… Done
W: Failed to fetch https://deb.debian.org/debian/dists/buster/InRelease Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
W: Failed to fetch https://deb.debian.org/debian-security/dists/buster/updates/InRelease Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
W: Failed to fetch https://deb.qubes-os.org/r4.1/vm/dists/buster/InRelease Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
W: Some index files failed to download. They have been ignored, or old ones used instead.
user@debian-10:~$ sudo apt update
Err:1 Index of /r4.1/vm/ buster InRelease
Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
Err:2 Index of /debian buster InRelease
Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
Err:3 Index of /debian-security buster/updates InRelease
Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
Reading package lists… Done
Building dependency tree
Reading state information… Done
All packages are up to date.
W: Failed to fetch https://deb.debian.org/debian/dists/buster/InRelease Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
W: Failed to fetch https://deb.debian.org/debian-security/dists/buster/updates/InRelease Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
W: Failed to fetch https://deb.qubes-os.org/r4.1/vm/dists/buster/InRelease Reading from proxy failed - read (104: Connection reset by peer) [IP: 127.0.0.1 8082]
W: Some index files failed to download. They have been ignored, or old ones used instead.
debain-10.template.log (2.3 KB)
@Sven @unman
Also, all qubes templates has the same error.
Notes: my dom0 update was fine, including get date, keyboard and mouse inputs, and qubes notification commands. it’s only affects all qubes templates. all of these things are shows error 56.
WARN: ALL CONNECTION TO PORT 8082 WERE CONNECTION REFUSED.
SOLUTION:
In order to fix all of those errors, simply by insert this one simple command in dom0 terminal:
sudo qubes-dom0-update --action=reinstall binutils
Additionally, in /etc/qubes-rpc/polic/qubes.ConnectTCP, only have/add:
$anyvm $anyvm allow
Notes: this will fix everything if you didn’t remove the whole bash utillity
EDIT: Required to update/upgrade to 4.1.1 or 4.2. Any 4.2 updates? @unman
Edit2: Found out it was qubes.ConnectTCP problem