Troubleshoot Tor Whonix

[qwev]

(I hope this is the appropriate place to post this, if not please redirect me)

I am running into issues using Tor in Qubes-Whonix regarding the speed/stability.
I can connect to Tor using the control panel, with no bridges / with obsf4. (couldn’t use snowflake and meek-azure)
Once connected to Tor, I open the Tor browser in the anon-whonix qube or through a dispvm.
Most of the time I can do some light browsing, but the websites return the content in ‘burst?’.
This means I’d open multiple websites, and they would all load for 15 seconds to a minute, and then all load up at the same time. Then I can continue browsing normally for around 30 seconds and then it’s like the connection drops and this cycle starts again.

A simpler explanation would be that the connection keeps dropping, then works for a couple seconds and drops again. (The status in the control panel doesn’t change, I also didn’t notice any error in the logs)

I can use Tor on Tails/Windows without issues.

Here’s what I tried:

1. Cloning sys-whonix and manual regeneration (steps found on wiki “Why is Tor Slow”)
2. Reinstalling Qubes

Please let me know if anybody has the same issue, or how I could troubleshoot the issue further. Thank you

[Patrick]

• Tor Log Analysis
• Tor Connectivity Troubleshooting
• Connectivity Troubleshooting

[qwev]

Thank you for the reply.

I reinstalled Qubes once more.
Tor was perfectly working, until I updated the templates and rebooted Qubes.

I tried running “sudo anon-log” in sys-whonix, but it’s asking me to run as root, how can I solve this? Thank you

[Patrick]

@qwev

I tried running “sudo anon-log” in sys-whonix, but it’s asking me to run as root, how can I solve this? Thank you

You can use this fix:

sudo str_replace '"$log3"' '"$log2"' /usr/bin/anon-log

(Or use the newer version from git. - anon-gw-anonymizer-config/usr/bin/anon-log at master · Whonix/anon-gw-anonymizer-config · GitHub)

(This will be fixed in a later update.)

[qwev]

That fixed it thank you.

Here are my logs, many things seem to be wrong. I’d appreciate it if you could take a look

I ran the logs commands while connected to Tor as per the control panel, I also could browse 3 urls (while still getting timeouts) before getting too many timeouts and giving up.

To keep in mind:
Time in BIOS is set to UTC
Tor was working normally after reinstall, until updating templates/rebooting
I can access the internet in other qubes without Tor

Thank you.
Logs:

Tor Log Analysis

1. sudo anon-log
   tor.service:

Starting tor.service - Anonymizing overlay network for TCP (multi-instance-master)…
Finished tor.service - Anonymizing overlay network for TCP (multi-instance-master).

tor@default.service:

Starting tor@default.service - Anonymizing overlay network for TCP…
Aug 24 14:25:29.468 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:25:29.469 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Configuration was valid
Aug 24 14:25:29.496 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:25:29.496 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Aug 24 14:25:29.500 [notice] Opening Control listener on 127.0.0.1:9052
Aug 24 14:25:29.500 [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Started tor@default.service - Anonymizing overlay network for TCP.
Stopping tor@default.service - Anonymizing overlay network for TCP…
tor@default.service: Deactivated successfully.
Stopped tor@default.service - Anonymizing overlay network for TCP.
Starting tor@default.service - Anonymizing overlay network for TCP…
Aug 24 14:26:08.123 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:26:08.123 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Configuration was valid
Aug 24 14:26:08.151 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:26:08.151 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Aug 24 14:26:08.155 [notice] Opening Control listener on 127.0.0.1:9052
Aug 24 14:26:08.155 [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Started tor@default.service - Anonymizing overlay network for TCP.
Stopping tor@default.service - Anonymizing overlay network for TCP…
tor@default.service: Deactivated successfully.
Stopped tor@default.service - Anonymizing overlay network for TCP.
tor@default.service: Consumed 1.126s CPU time.
Starting tor@default.service - Anonymizing overlay network for TCP…
Aug 24 14:28:07.388 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:28:07.388 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Configuration was valid
Aug 24 14:28:07.407 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:28:07.408 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Aug 24 14:28:07.412 [notice] Opening Control listener on 127.0.0.1:9052
Aug 24 14:28:07.412 [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Started tor@default.service - Anonymizing overlay network for TCP.
Stopping tor@default.service - Anonymizing overlay network for TCP…
tor@default.service: Deactivated successfully.
Stopped tor@default.service - Anonymizing overlay network for TCP.
Starting tor@default.service - Anonymizing overlay network for TCP…
Aug 24 14:29:03.475 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:29:03.475 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Configuration was valid
Aug 24 14:29:03.502 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:29:03.502 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Aug 24 14:29:03.507 [notice] Opening Control listener on 127.0.0.1:9052
Aug 24 14:29:03.507 [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Started tor@default.service - Anonymizing overlay network for TCP.
Stopping tor@default.service - Anonymizing overlay network for TCP…
tor@default.service: Deactivated successfully.
Stopped tor@default.service - Anonymizing overlay network for TCP.
tor@default.service: Consumed 21.746s CPU time.
Starting tor@default.service - Anonymizing overlay network for TCP…
Aug 24 14:40:41.680 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:40:41.680 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Configuration was valid
Aug 24 14:40:41.705 [notice] Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Aug 24 14:40:41.705 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Aug 24 14:40:41.708 [notice] Opening Control listener on 127.0.0.1:9052
Aug 24 14:40:41.708 [notice] Opened Control listener connection (ready) on 127.0.0.1:9052
Started tor@default.service - Anonymizing overlay network for TCP.

vanguards.service:

2. systemcheck --verbose --leak-tests

[INFO] [systemcheck] sys-whonix | Whonix-Gateway | whonix-gateway-17 TemplateBased ProxyVM | Sat Aug 24 02:54:11 PM UTC 2024
[INFO] [systemcheck] Environment variables test result: Ok.
[INFO] [systemcheck] Check sudo Result: OK
[INFO] [systemcheck] Whonix build version: 3:10.7-1
[INFO] [systemcheck] whonix-gateway-packages-dependencies-cli: 24.6-1
[INFO] [systemcheck] derivative_major_release_version /etc/whonix_version: 17
[INFO] [systemcheck] Whonix Support Status of this Major Version: Ok.
[INFO] [systemcheck] Spectre Meltdown Test: skipping since spectre_meltdown_check=false, ok.
[INFO] [systemcheck] Package Manager Consistency Check Result: Output of command dpkg --audit was empty, ok.
[INFO] [systemcheck] systemd journal check Result:
AppArmor:
########################################
AVC apparmor=“DENIED” operation=“open” class=“file” profile=“system_tor” name=“/sys/kernel/mm/transparent_hugepage/hpage_pmd_size” comm=“obfs4proxy” requested_mask=“r” denied_mask=“r”
########################################

secomp:
########################################

########################################

warnings:
########################################
Aug 24 14:25:29 host tinyproxy-wrapper[1189]: WARNING: obsolete config item on line 14
Aug 24 14:25:29 host tinyproxy-wrapper[1189]: WARNING: obsolete config item on line 15
Aug 24 14:25:29 host tinyproxy-wrapper[1189]: WARNING: obsolete config item on line 16
Aug 24 14:25:29 host tinyproxy-wrapper[1189]: WARNING: obsolete config item on line 17
Aug 24 14:25:32 host sdwdate-start-anondate-set-file-watcher[1304]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:32 host sdwdate-start-anondate-set-file-watcher[1304]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:25:32 host anondate[1417]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:32 host anondate[1417]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:25:32 host kernel: warn_alloc+0x165/0x1e0
Aug 24 14:25:36 host sdwdate-start-anondate-set-file-watcher[1430]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:36 host sdwdate-start-anondate-set-file-watcher[1430]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:25:39 host sdwdate-start-anondate-set-file-watcher[1822]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:39 host sdwdate-start-anondate-set-file-watcher[1822]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:25:43 host sdwdate-start-anondate-set-file-watcher[1947]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:43 host sdwdate-start-anondate-set-file-watcher[1947]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:25:47 host sdwdate-start-anondate-set-file-watcher[2073]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:47 host sdwdate-start-anondate-set-file-watcher[2073]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:25:53 host sdwdate-start-anondate-set-file-watcher[2198]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:53 host sdwdate-start-anondate-set-file-watcher[2198]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:25:59 host sdwdate-start-anondate-set-file-watcher[2324]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:25:59 host sdwdate-start-anondate-set-file-watcher[2324]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:26:07 host sdwdate-start-anondate-set-file-watcher[2551]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:26:07 host sdwdate-start-anondate-set-file-watcher[2551]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:26:13 host qubes.StartApp+xfce4-terminal-dom0[2774]: (xfce4-terminal:2778): dbind-WARNING **: 14:26:13.354: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Aug 24 14:26:15 host sdwdate-start-anondate-set-file-watcher[2894]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:26:15 host sdwdate-start-anondate-set-file-watcher[2894]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:26:25 host sdwdate-start-anondate-set-file-watcher[3048]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:26:25 host sdwdate-start-anondate-set-file-watcher[3048]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:26:35 host sdwdate-start-anondate-set-file-watcher[3187]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:26:35 host sdwdate-start-anondate-set-file-watcher[3187]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:26:46 host sdwdate-start-anondate-set-file-watcher[3329]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:26:46 host sdwdate-start-anondate-set-file-watcher[3329]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:26:56 host sdwdate-start-anondate-set-file-watcher[3467]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:26:56 host sdwdate-start-anondate-set-file-watcher[3467]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:27:07 host sdwdate-start-anondate-set-file-watcher[3642]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:27:07 host sdwdate-start-anondate-set-file-watcher[3642]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:27:18 host sdwdate-start-anondate-set-file-watcher[3797]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:27:18 host sdwdate-start-anondate-set-file-watcher[3797]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:27:28 host sdwdate-start-anondate-set-file-watcher[3933]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:27:28 host sdwdate-start-anondate-set-file-watcher[3933]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:27:39 host sdwdate-start-anondate-set-file-watcher[4082]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:27:39 host sdwdate-start-anondate-set-file-watcher[4082]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:27:49 host sdwdate-start-anondate-set-file-watcher[4307]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:27:49 host sdwdate-start-anondate-set-file-watcher[4307]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:00 host sdwdate-start-anondate-set-file-watcher[4444]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:00 host sdwdate-start-anondate-set-file-watcher[4444]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:10 host sdwdate-start-anondate-set-file-watcher[4647]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:10 host sdwdate-start-anondate-set-file-watcher[4647]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:11 host sdwdate-start-anondate-set-file-watcher[4772]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:11 host sdwdate-start-anondate-set-file-watcher[4772]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:14 host sdwdate-start-anondate-set-file-watcher[4897]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:14 host sdwdate-start-anondate-set-file-watcher[4897]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:17 host sdwdate-start-anondate-set-file-watcher[5024]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:17 host sdwdate-start-anondate-set-file-watcher[5024]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:22 host sdwdate-start-anondate-set-file-watcher[5158]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:22 host sdwdate-start-anondate-set-file-watcher[5158]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:27 host sdwdate-start-anondate-set-file-watcher[5285]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:27 host sdwdate-start-anondate-set-file-watcher[5285]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:34 host sdwdate-start-anondate-set-file-watcher[5419]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:34 host sdwdate-start-anondate-set-file-watcher[5419]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:41 host sdwdate-start-anondate-set-file-watcher[5549]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:41 host sdwdate-start-anondate-set-file-watcher[5549]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:50 host sdwdate-start-anondate-set-file-watcher[5682]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:50 host sdwdate-start-anondate-set-file-watcher[5682]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:28:59 host sdwdate-start-anondate-set-file-watcher[5818]: ______ WARNING: Tor bootstrap not done.
Aug 24 14:28:59 host sdwdate-start-anondate-set-file-watcher[5818]: ______ WARNING: local system time is NOT within Tor consensus time valid time range. (valid_after: ‘2024-08-23 19:00:00’ | middle_range: ‘2024-08-23 20:30:00’ | valid_until: ‘2024-08-23 22:00:00’)
Aug 24 14:51:06 host qubes.StartApp+xfce4-terminal-dom0[2774]: (xfce4-terminal:2778): Gtk-WARNING **: 14:51:06.440: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/check-symbolic.svg.
########################################

failed:
########################################
Aug 24 14:27:42 host kernel: tsc: Fast TSC calibration failed
Aug 24 14:27:42 host kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
Aug 24 14:27:42 host kernel: ACPI: _OSC evaluation for CPUs failed, trying _PDC
Aug 24 14:27:42 host swapon[520]: swapon: /dev/xvdc1: swapon failed: Device or resource busy
Aug 24 14:27:47 host xl[1026]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 24 14:27:47 host xl[1026]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 24 14:27:47 host xl[1026]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 24 14:25:32 host kernel: xen-balloon: vmemmap alloc failure: order:9, mode:0x4cc0(GFP_KERNEL|__GFP_RETRY_MAYFAIL), nodemask=(null),cpuset=/,mems_allowed=0
Aug 24 14:25:32 host loginctl[1471]: Could not attach device: Failed to open device ‘/sys/devices/platform/pcspkr/input/*’: No such device
Aug 24 14:25:34 host dbus-daemon[1621]: [session uid=1000 pid=1618] Activated service ‘org.freedesktop.systemd1’ failed: Process org.freedesktop.systemd1 exited with status 1
Aug 24 14:26:13 host systemctl[2754]: Failed to connect to bus: No medium found
Aug 24 14:26:13 host qubes.StartApp+xfce4-terminal-dom0[2774]: (xfce4-terminal:2778): Gdk-CRITICAL **: 14:26:13.326: gdk_atom_intern: assertion ‘atom_name != NULL’ failed
Aug 24 14:26:13 host qubes.StartApp+xfce4-terminal-dom0[2774]: (xfce4-terminal:2778): Gdk-CRITICAL **: 14:26:13.327: gdk_atom_intern: assertion ‘atom_name != NULL’ failed
Aug 24 14:26:13 host qubes.StartApp+xfce4-terminal-dom0[2774]: Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
Aug 24 14:30:31 host sdwdate[1243]: * stderr: connect error: SOCKSHTTPConnectionPool(host=‘mzi5yynpd6qqq3lnh7vnaojy36v3hcorytsut47zwkguhnorduyxwead.onion’, port=80): Max retries exceeded with url: / (Caused by NewConnectionError(‘: Failed to establish a new connection: 0x04: Host unreachable’))
Aug 24 14:30:31 host sdwdate[1243]: 2024-08-24 14:30:31 - sdwdate - INFO - failed_urls: 1 allowed_failures: 5
Aug 24 14:32:31 host sdwdate[1243]: 2024-08-24 14:32:31 - sdwdate - INFO - failed_urls: 2 allowed_failures: 5
Aug 24 14:33:28 host sdwdate[1243]: 2024-08-24 14:33:28 - sdwdate - INFO - failed_urls: 2 allowed_failures: 5
Aug 24 14:47:33 host root[7961]: /etc/xen/scripts/vif-route-qubes: ifdown vif8.0 failed
Aug 24 14:47:33 host root[7969]: /etc/xen/scripts/vif-route-qubes: ip route del 10.138.11.76 dev vif8.0 metric 32744 failed
Aug 24 14:47:33 host root[7974]: /etc/xen/scripts/vif-route-qubes: ip addr del 10.137.0.14/32 dev vif8.0 failed
Aug 24 14:51:59 host root[8260]: /etc/xen/scripts/vif-route-qubes: ifdown vif9.0 failed
Aug 24 14:51:59 host root[8269]: /etc/xen/scripts/vif-route-qubes: ip route del 10.138.31.240 dev vif9.0 metric 32743 failed
Aug 24 14:51:59 host root[8274]: /etc/xen/scripts/vif-route-qubes: ip addr del 10.137.0.14/32 dev vif9.0 failed
Aug 24 14:54:12 host sudo[9360]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/bin/systemctl --no-pager --no-block --no-legend --failed
########################################

errors:
########################################
Aug 24 14:27:42 host kernel: ACPI Error: No handler or method for GPE 00, disabling event (20230628/evgpe-839)
Aug 24 14:27:42 host kernel: ACPI Error: No handler or method for GPE 01, disabling event (20230628/evgpe-839)
Aug 24 14:27:42 host kernel: ACPI Error: No handler or method for GPE 03, disabling event (20230628/evgpe-839)
Aug 24 14:27:42 host kernel: ACPI Error: No handler or method for GPE 04, disabling event (20230628/evgpe-839)
Aug 24 14:27:42 host kernel: ACPI Error: No handler or method for GPE 05, disabling event (20230628/evgpe-839)
Aug 24 14:27:42 host kernel: ACPI Error: No handler or method for GPE 06, disabling event (20230628/evgpe-839)
Aug 24 14:27:42 host kernel: ACPI Error: No handler or method for GPE 07, disabling event (20230628/evgpe-839)
Aug 24 14:27:42 host kernel: hid_bpf: error while preloading HID BPF dispatcher: -22
Aug 24 14:27:42 host kernel: RAS: Correctable Errors collector initialized.
Aug 24 14:27:47 host xl[1026]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 24 14:27:47 host xl[1026]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 24 14:27:47 host xl[1026]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 24 14:25:29 host sdwdate-pre[1012]: + gcc /usr/src/sdwdate/sclockadj.c -o /usr/libexec/sdwdate/sclockadj -ldl -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=3 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now
Aug 24 14:26:13 host qubes.StartApp+xfce4-terminal-dom0[2774]: (xfce4-terminal:2778): dbind-WARNING **: 14:26:13.354: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Aug 24 14:30:31 host sdwdate[1243]: * stderr: connect error: SOCKSHTTPConnectionPool(host=‘mzi5yynpd6qqq3lnh7vnaojy36v3hcorytsut47zwkguhnorduyxwead.onion’, port=80): Max retries exceeded with url: / (Caused by NewConnectionError(‘: Failed to establish a new connection: 0x04: Host unreachable’))
Aug 24 14:30:31 host sdwdate[1243]: * remote_status: error
Aug 24 14:30:31 host sdwdate[1243]: [‘ok’, ‘ok’, ‘error’]
########################################

ordering cycle:
########################################

########################################

To see this for yourself…

1. Open a terminal. (dom0 → Start Menu → ServiceVM: sys-whonix → Terminal)
2. Run. sudo apparmor-info --boot
3. Run. sudo journalctl --boot | grep -i syscall=
4. Run. sudo journalctl --boot | grep -i warn
5. Run. sudo journalctl --boot | grep -i fail
6. Run. sudo journalctl --boot | grep -i error
7. Run. sudo journalctl --boot | grep -i “ordering cycle”

If you know what you are doing, feel free to disable this check.
Create a file /etc/systemcheck.d/50_user.conf and add:
systemcheck_skip_functions+=" check_journal "
[INFO] [systemcheck] check network interfaces Result: Ok.
[INFO] [systemcheck] Qubes qubes-db Test Result: Connection to local qubes-db daemon succeeded, ok.
[INFO] [systemcheck] Qubes Settings Test Result: Ok. (GATEWAY_IP: 127.0.0.1)
[INFO] [systemcheck] Qubes Settings Test Result: Ok, qubes_vm_type is ProxyVM.
[INFO] [systemcheck] Check Kernel Messages Test Result: Found nothing remarkable, ok.
[INFO] [systemcheck] Whonix firewall systemd unit check Result: Ok.
[INFO] [systemcheck] Check Package Manager Running Result: None running, ok.
[INFO] [systemcheck] Tor Check Result: “DisableNetwork 1” not active, ok.
[INFO] [systemcheck] Tor Config Check Result: Tor config ok.
[INFO] [systemcheck] Tor Running Check Result: Pid ‘7683’ running.
[INFO] [systemcheck] Control Port Filter Proxy Test Result: OK
[INFO] [systemcheck] check_anondate_do debugging information:

tor_consensus_status : verified
current_time_in_valid_range: true

current_time_torish : 2024-08-24 14:54:14
tor_consensus_valid_after : 2024-08-24 14:00:00
tor_consensus_valid_until : 2024-08-24 17:00:00
tor_consensus_middle_range : 2024-08-24 15:30:00

tor_cert_lifetime_output :
tor_cert_lifetime_valid : true
tor_cert_valid_after :

tor_consensus_user_permission : debian-tor
tor_consensus_group_permission: debian-tor
[INFO] [systemcheck] Tor SocksPort Reachability Test Result: Reachable. (curl exit code: 22 | curl status message: [22] - [HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f, --fail is used.])
[INFO] [systemcheck] Tor Connection Result: Ok.
tor_bootstrap_status: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY=“Done”
Tor Circuit: established
[INFO] [systemcheck] Time Synchronization Result: Ok.
Time synchronization status: success
sdwdate reports: Success.
whonix_firewall status: consecutive run after boot
onion-time-pre-script reports:
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time ‘Thu Jul 18 00:00:00 UTC 2024’ and expiration timestamp ‘Tue May 17 10:00:00 UTC 2033’, ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY=“Done”
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2024-08-24 14:00:00 and consensus/valid-until 2024-08-24 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code ‘0’ indicating ‘success’.
[INFO] [systemcheck] Connected to Tor.
[INFO] [systemcheck] Whonix Meta Packages Test Result: Meta package qubes-whonix-gateway installed, ok.
[INFO] [systemcheck] Whonix Unwanted Packages Test Result: None found.
[INFO] [systemcheck] Check Initializer Result: /var/lib/initializer-dist/status-files/first_run_initializer.fail does not exist, ok.
[INFO] [systemcheck] Check Virtualizer Result: Supported Virtualizer Qubes detected, continuing.
systemd-detect-virt result: qubes
[INFO] [systemcheck] PVClock Result: /sys/devices/system/clocksource/clocksource0/current_clocksource exist, is xen. This is non-ideal. A known issue. Contributions happily considered. Read more: Phabricator to Discourse Forums Migration - Phabricator Tickets - Whonix Forum
[INFO] [systemcheck] Check Timezone Result: /etc/timezone, Etc/UTC matches Etc/UTC, ok.
[INFO] [systemcheck] Check Timezone Result: /usr/share/zoneinfo/Etc/UTC matches /etc/localtime, ok.
[INFO] [systemcheck] IP Forwarding Result: /proc/sys/net/ipv4/ip_forward is 0, ok.
[INFO] [systemcheck] Check Logs Result: /home/user/.msgcollector/msgdispatcher-error.log does not exist, ok.
[INFO] [systemcheck] Check Logs Result: /run/systemcheck/.msgcollector/msgdispatcher-error.log does not exist, ok.
[INFO] [systemcheck] Check Logs Result: /var/lib/systemcheck/.msgcollector/msgdispatcher-error.log does not exist, ok.
[INFO] [systemcheck] Check Logs Result: /home/user/.cache/tb/torbrowser_updater_error.log does not exist, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname --fqdn” output is “host.localdomain”, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname” output is “host”, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname --ip-address” output is “127.0.0.1”, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname --ip-address” output is “localdomain”, ok.
[INFO] [systemcheck] Entropy Available Check Result: ok. /proc/sys/kernel/random/entropy_avail: 256
[INFO] [systemcheck] Check nonfree Result: Ok, no nonfree packages found. For more information, see:
Avoid Non-Freedom Software
[INFO] [systemcheck] Whonix APT Repository: Enabled.
When the Whonix team releases BOOKWORM updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please
read Placing Trust in Whonix to understand the risk.
If you want to change this, use:
sudo repository-dist
[INFO] [systemcheck] Qubes Updates Proxy Daemon Check Result: qubes-updates-proxy.service runing, ok.
[INFO] [systemcheck] Qubes UpdatesProxy Reachability Test: Trying to reach local Qubes UpdatesProxy… PROXY_SERVER: http://127.0.0.1:8082/
[INFO] [systemcheck] Qubes UpdatesProxy Reachability Result: Ok, torified update proxy reachable.
[INFO] [systemcheck] Qubes UpdatesProxy Connectivity Test: Trying to use Qubes update proxy… PROXY_SERVER: http://127.0.0.1:8082/
[INFO] [systemcheck] Qubes UpdatesProxy Connectivity Result: Unknown issue. (curl exit code: 56 | curl status message: [56] - [Failure in receiving network data.])
[INFO] [systemcheck] SocksPort IP Leak Test: Testing Tor’s SocksPort (SOCKS_PORT_SYSTEMCHECK: 9110)…
[INFO] [systemcheck] SocksPort IP Leak Test: Connected to Tor.
[INFO] [systemcheck] system default networking IP Leak Test: system default networking IP Leak Test…
[INFO] [systemcheck] system default networking IP Leak Test Test Result: Ok, Tor’s TransPort was not reachable.
This is expected on Whonix-Gateway’s default configuration.
(curl exit code: [6] - [Couldn’t resolve host. The given remote host was not resolved.])
[INFO] [systemcheck] Stream Isolation Test: Ok, skipped, because TransPort test failed! Can not test stream isolation. This is expected on Whonix-Gateway’s default configuration.
[INFO] [systemcheck] Debian Package Update Check: Checking for software updates via apt-get… ( Documentation: Operating System Software and Updates )
0% [Connecting to SOCKS5h proxy (socks5h://127.0.0.1:9050)] [Connecting to SOCKS5h proxy (socks5h://127.0.0.1:9050)] [Connecting to SOCKS5h proxy (socks5h://127.0.0.1:9050)] [Connecting to ^Ign:1 tor+https://deb.debian.org/debian bookworm InRelease
Ign:2 tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease
Ign:3 tor+https://deb.kicksecure.com bookworm InRelease
Ign:4 tor+https://deb.whonix.org bookworm InRelease
Ign:5 Index of /r4.2/vm/ bookworm InRelease
Ign:6 tor+https://deb.debian.org/debian bookworm-updates InRelease
Ign:3 tor+https://deb.kicksecure.com bookworm InRelease
Ign:4 tor+https://deb.whonix.org bookworm InRelease
Ign:2 tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease
Ign:5 Index of /r4.2/vm/ bookworm InRelease
Ign:7 tor+https://deb.debian.org/debian-security bookworm-security InRelease
Ign:4 tor+https://deb.whonix.org bookworm InRelease
Ign:5 Index of /r4.2/vm/ bookworm InRelease
Ign:2 tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease
Ign:3 tor+https://deb.kicksecure.com bookworm InRelease
Ign:8 tor+https://deb.debian.org/debian bookworm-backports InRelease
Err:2 tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease
SOCKS proxy socks5h://127.0.0.1:9050 could not connect to fasttrack.debian.net (0.0.0.0:0) due to: TTL expired (6) [IP: 127.0.0.1 9050]
Err:4 tor+https://deb.whonix.org bookworm InRelease
SOCKS proxy socks5h://127.0.0.1:9050 could not connect to deb.whonix.org (0.0.0.0:0) due to: TTL expired (6) [IP: 127.0.0.1 9050]
Err:5 Index of /r4.2/vm/ bookworm InRelease
Something wicked happened resolving ‘deb.qubes-os.org:https’ (-4 - Non-recoverable failure in name resolution)
Err:3 tor+https://deb.kicksecure.com bookworm InRelease
SOCKS proxy socks5h://127.0.0.1:9050 could not connect to deb.kicksecure.com (0.0.0.0:0) due to: TTL expired (6) [IP: 127.0.0.1 9050]
Ign:1 tor+https://deb.debian.org/debian bookworm InRelease
0% [Working][WARNING] [systemcheck] Debian Package Update Check Result: Could not check for software updates! (Timeout reached.) (apt-get code: 124)
Please manually check inside your ‘whonix-gateway-17’ TemplateVM.

1. Open a TemplateVM terminal. (dom0 → Start Menu → Template: whonix-gateway-17 → Terminal)
2. Update. upgrade-nonroot
3. Shutdown your TemplateVM. (dom0 → Qubes VM Manager → right click ‘whonix-gateway-17’ → Shutdown VM)
4. Shutdown and restart this TemplateBased ProxyVM. (dom0 → Qubes VM Manager → right click ‘sys-whonix’ → Shutdown VM)
   [INFO] [systemcheck] Warrant Canary Check: Debugging information:
   Canary Download Time : Sat Aug 24 14:36:29 UTC 2024
   Current Time : Sat Aug 24 15:06:12 UTC 2024
   Canary Signature Time : Thu Aug 15 18:07:39 UTC 2024
   Canary Expiration Time: Thu Sep 12 18:07:39 UTC 2024
   [INFO] [systemcheck] Warrant Canary Check: Ok.
   [INFO] [systemcheck] Please donate!
   See: Donating to Whonix

[Patrick]

qwev via Whonix Forum:

AVC apparmor=“DENIED” operation=“open” class=“file” profile=“system_tor”
name=“/sys/kernel/mm/transparent_hugepage/hpage_pmd_size”
comm=“obfs4proxy” requested_mask=“r” denied_mask=“r”

This could be an issue if using obfs4proxy.

Try Fix
Profiles. Follow
the principle, not the steps.

Aug 24 14:47:33 host root[7961]: /etc/xen/scripts/vif-route-qubes: ifdown vif8.0 failed
Aug 24 14:47:33 host root[7969]: /etc/xen/scripts/vif-route-qubes: ip route del 10.138.11.76 dev vif8.0 metric 32744 failed
Aug 24 14:47:33 host root[7974]: /etc/xen/scripts/vif-route-qubes: ip addr del 10.137.0.14/32 dev vif8.0 failed
Aug 24 14:51:59 host root[8260]: /etc/xen/scripts/vif-route-qubes: ifdown vif9.0 failed
Aug 24 14:51:59 host root[8269]: /etc/xen/scripts/vif-route-qubes: ip route del 10.138.31.240 dev vif9.0 metric 32743 failed
Aug 24 14:51:59 host root[8274]: /etc/xen/scripts/vif-route-qubes: ip addr del 10.137.0.14/32 dev vif9.0 failed

This could also be an issue. /etc/xen/scripts/vif-route-qubes is a
script by Qubes, not Whonix. Please check the Qubes issue tracker and
report to Qubes if no bug exists and share the report here.

[qwev]

After changing the bridge option to none and disabling ipv6 in sys-whonix, I got Tor “working” in anon-whonix but it’s still unusable, as my first post mentions it now does the same thing again of working for a couple seconds then being insanely slow and again.

I’m debating whether I should reinstall Qubes once more to get the full logs while Tor works well, then compare to the other logs from when it doesn’t work.
If you think that’d help please let me know which commands I should run to get the full logs needed.
Thank you.

new output from systemcheck ran in sys-whonix:
[INFO] [systemcheck] sys-whonix | Whonix-Gateway | whonix-gateway-17 TemplateBased ProxyVM | Sun Aug 25 07:34:39 PM UTC 2024
[INFO] [systemcheck] Environment variables test result: Ok.
[INFO] [systemcheck] Check sudo Result: OK
[INFO] [systemcheck] Whonix build version: 3:10.7-1
[INFO] [systemcheck] whonix-gateway-packages-dependencies-cli: 24.6-1
[INFO] [systemcheck] derivative_major_release_version /etc/whonix_version: 17
[INFO] [systemcheck] Whonix Support Status of this Major Version: Ok.
[INFO] [systemcheck] Spectre Meltdown Test: skipping since spectre_meltdown_check=false, ok.
[INFO] [systemcheck] Package Manager Consistency Check Result: Output of command dpkg --audit was empty, ok.
[INFO] [systemcheck] systemd journal check Result:
AppArmor:
########################################

########################################

secomp:
########################################

########################################

warnings:
########################################
Aug 25 18:42:02 host tinyproxy-wrapper[1199]: WARNING: obsolete config item on line 14
Aug 25 18:42:02 host tinyproxy-wrapper[1199]: WARNING: obsolete config item on line 15
Aug 25 18:42:02 host tinyproxy-wrapper[1199]: WARNING: obsolete config item on line 16
Aug 25 18:42:02 host tinyproxy-wrapper[1199]: WARNING: obsolete config item on line 17
Aug 25 18:42:04 host qubes.StartApp+xfce4-terminal-dom0[1623]: (xfce4-terminal:1634): dbind-WARNING **: 18:42:04.072: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Aug 25 18:42:05 host qubes.StartApp+xfce4-terminal-dom0[1623]: (xfce4-terminal:1634): Gdk-WARNING **: 18:42:05.400: …/…/…/gdk/x11/gdkproperty-x11.c:224 invalid X atom: 2452450306
########################################

failed:
########################################
Aug 25 18:41:53 host kernel: tsc: Fast TSC calibration failed
Aug 25 18:41:53 host kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
Aug 25 18:41:53 host kernel: ACPI: _OSC evaluation for CPUs failed, trying _PDC
Aug 25 18:41:53 host swapon[616]: swapon: /dev/xvdc1: swapon failed: Device or resource busy
Aug 25 18:41:57 host xl[1033]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 25 18:41:57 host xl[1033]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 25 18:41:57 host xl[1033]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 25 18:42:02 host loginctl[1325]: Could not attach device: Failed to open device ‘/sys/devices/platform/pcspkr/input/*’: No such device
Aug 25 18:42:03 host dbus-daemon[1453]: [session uid=1000 pid=1451] Activated service ‘org.freedesktop.systemd1’ failed: Process org.freedesktop.systemd1 exited with status 1
Aug 25 18:42:03 host systemctl[1575]: Failed to connect to bus: No medium found
Aug 25 18:42:04 host qubes.StartApp+xfce4-terminal-dom0[1623]: (xfce4-terminal:1634): Gdk-CRITICAL **: 18:42:04.058: gdk_atom_intern: assertion ‘atom_name != NULL’ failed
Aug 25 18:42:04 host qubes.StartApp+xfce4-terminal-dom0[1623]: Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
Aug 25 18:43:02 host sudo[4894]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/bin/systemctl --no-pager --no-block --no-legend --failed
Aug 25 18:44:18 host sdwdate[1485]: 2024-08-25 18:44:18 - sdwdate - INFO - failed_urls: 1 allowed_failures: 5
Aug 25 18:44:21 host sudo[10088]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/bin/systemctl --no-pager --no-block --no-legend --failed
Aug 25 18:45:00 host sdwdate[1485]: 2024-08-25 18:45:00 - sdwdate - INFO - failed_urls: 1 allowed_failures: 5
Aug 25 19:34:39 host sudo[17885]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/bin/systemctl --no-pager --no-block --no-legend --failed
########################################

errors:
########################################
Aug 25 18:41:53 host kernel: ACPI Error: No handler or method for GPE 00, disabling event (20230628/evgpe-839)
Aug 25 18:41:53 host kernel: ACPI Error: No handler or method for GPE 01, disabling event (20230628/evgpe-839)
Aug 25 18:41:53 host kernel: ACPI Error: No handler or method for GPE 03, disabling event (20230628/evgpe-839)
Aug 25 18:41:53 host kernel: ACPI Error: No handler or method for GPE 04, disabling event (20230628/evgpe-839)
Aug 25 18:41:53 host kernel: ACPI Error: No handler or method for GPE 05, disabling event (20230628/evgpe-839)
Aug 25 18:41:53 host kernel: ACPI Error: No handler or method for GPE 06, disabling event (20230628/evgpe-839)
Aug 25 18:41:53 host kernel: ACPI Error: No handler or method for GPE 07, disabling event (20230628/evgpe-839)
Aug 25 18:41:53 host kernel: hid_bpf: error while preloading HID BPF dispatcher: -22
Aug 25 18:41:53 host kernel: RAS: Correctable Errors collector initialized.
Aug 25 18:41:57 host xl[1033]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 25 18:41:57 host xl[1033]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 25 18:41:57 host xl[1033]: libxl: error: libxl_utils.c:815:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
Aug 25 18:42:01 host sdwdate-pre[1017]: + gcc /usr/src/sdwdate/sclockadj.c -o /usr/libexec/sdwdate/sclockadj -ldl -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=3 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now
Aug 25 18:42:04 host qubes.StartApp+xfce4-terminal-dom0[1623]: (xfce4-terminal:1634): dbind-WARNING **: 18:42:04.072: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
########################################

ordering cycle:
########################################

########################################

To see this for yourself…

1. Open a terminal. (dom0 → Start Menu → ServiceVM: sys-whonix → Terminal)
2. Run. sudo apparmor-info --boot
3. Run. sudo journalctl --boot | grep -i syscall=
4. Run. sudo journalctl --boot | grep -i warn
5. Run. sudo journalctl --boot | grep -i fail
6. Run. sudo journalctl --boot | grep -i error
7. Run. sudo journalctl --boot | grep -i “ordering cycle”

If you know what you are doing, feel free to disable this check.
Create a file /etc/systemcheck.d/50_user.conf and add:
systemcheck_skip_functions+=" check_journal "
[INFO] [systemcheck] check network interfaces Result: Ok.
[INFO] [systemcheck] Qubes qubes-db Test Result: Connection to local qubes-db daemon succeeded, ok.
[INFO] [systemcheck] Qubes Settings Test Result: Ok. (GATEWAY_IP: 127.0.0.1)
[INFO] [systemcheck] Qubes Settings Test Result: Ok, qubes_vm_type is ProxyVM.
[INFO] [systemcheck] Check Kernel Messages Test Result: Found nothing remarkable, ok.
[INFO] [systemcheck] Whonix firewall systemd unit check Result: Ok.
[INFO] [systemcheck] Check Package Manager Running Result: None running, ok.
[INFO] [systemcheck] Tor Check Result: “DisableNetwork 1” not active, ok.
[INFO] [systemcheck] Tor Config Check Result: Tor config ok.
[INFO] [systemcheck] Tor Running Check Result: Pid ‘1341’ running.
[INFO] [systemcheck] Control Port Filter Proxy Test Result: OK
[INFO] [systemcheck] check_anondate_do debugging information:

tor_consensus_status : verified
current_time_in_valid_range: true

current_time_torish : 2024-08-25 19:34:41
tor_consensus_valid_after : 2024-08-25 18:00:00
tor_consensus_valid_until : 2024-08-25 21:00:00
tor_consensus_middle_range : 2024-08-25 19:30:00

tor_cert_lifetime_output :
tor_cert_lifetime_valid : true
tor_cert_valid_after :

tor_consensus_user_permission : debian-tor
tor_consensus_group_permission: debian-tor
[INFO] [systemcheck] Tor SocksPort Reachability Test Result: Reachable. (curl exit code: 22 | curl status message: [22] - [HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f, --fail is used.])
[INFO] [systemcheck] Tor Connection Result: Ok.
tor_bootstrap_status: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY=“Done”
Tor Circuit: established
[INFO] [systemcheck] Time Synchronization Result: Ok.
Time synchronization status: success
sdwdate reports: Success.
whonix_firewall status: consecutive run after boot
onion-time-pre-script reports:
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time ‘Thu Jul 18 00:00:00 UTC 2024’ and expiration timestamp ‘Tue May 17 10:00:00 UTC 2033’, ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY=“Done”
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2024-08-25 18:00:00 and consensus/valid-until 2024-08-25 21:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code ‘0’ indicating ‘success’.
[INFO] [systemcheck] Connected to Tor.
[INFO] [systemcheck] Whonix Meta Packages Test Result: Meta package qubes-whonix-gateway installed, ok.
[INFO] [systemcheck] Whonix Unwanted Packages Test Result: None found.
[INFO] [systemcheck] Check Initializer Result: /var/lib/initializer-dist/status-files/first_run_initializer.fail does not exist, ok.
[INFO] [systemcheck] Check Virtualizer Result: Supported Virtualizer Qubes detected, continuing.
systemd-detect-virt result: qubes
[INFO] [systemcheck] PVClock Result: /sys/devices/system/clocksource/clocksource0/current_clocksource exist, is xen. This is non-ideal. A known issue. Contributions happily considered. Read more: Phabricator to Discourse Forums Migration - Phabricator Tickets - Whonix Forum
[INFO] [systemcheck] Check Timezone Result: /etc/timezone, Etc/UTC matches Etc/UTC, ok.
[INFO] [systemcheck] Check Timezone Result: /usr/share/zoneinfo/Etc/UTC matches /etc/localtime, ok.
[INFO] [systemcheck] IP Forwarding Result: /proc/sys/net/ipv4/ip_forward is 0, ok.
[INFO] [systemcheck] Check Logs Result: /home/user/.msgcollector/msgdispatcher-error.log does not exist, ok.
[INFO] [systemcheck] Check Logs Result: /run/systemcheck/.msgcollector/msgdispatcher-error.log does not exist, ok.
[INFO] [systemcheck] Check Logs Result: /var/lib/systemcheck/.msgcollector/msgdispatcher-error.log does not exist, ok.
[INFO] [systemcheck] Check Logs Result: /home/user/.cache/tb/torbrowser_updater_error.log does not exist, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname --fqdn” output is “host.localdomain”, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname” output is “host”, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname --ip-address” output is “127.0.0.1”, ok.
[INFO] [systemcheck] Check Hostname Result: “hostname --ip-address” output is “localdomain”, ok.
[INFO] [systemcheck] Entropy Available Check Result: ok. /proc/sys/kernel/random/entropy_avail: 256
[INFO] [systemcheck] Check nonfree Result: Ok, no nonfree packages found. For more information, see:
Avoid Non-Freedom Software
[INFO] [systemcheck] Whonix APT Repository: Enabled.
When the Whonix team releases BOOKWORM updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please
read Placing Trust in Whonix to understand the risk.
If you want to change this, use:
sudo repository-dist
[INFO] [systemcheck] Qubes Updates Proxy Daemon Check Result: qubes-updates-proxy.service runing, ok.
[INFO] [systemcheck] Qubes UpdatesProxy Reachability Test: Trying to reach local Qubes UpdatesProxy… PROXY_SERVER: http://127.0.0.1:8082/
[INFO] [systemcheck] Qubes UpdatesProxy Reachability Result: Ok, torified update proxy reachable.
[INFO] [systemcheck] Qubes UpdatesProxy Connectivity Test: Trying to use Qubes update proxy… PROXY_SERVER: http://127.0.0.1:8082/
[INFO] [systemcheck] Qubes UpdatesProxy Connectivity Result: Ok, functional.
[INFO] [systemcheck] SocksPort IP Leak Test: Testing Tor’s SocksPort (SOCKS_PORT_SYSTEMCHECK: 9110)…
[INFO] [systemcheck] SocksPort IP Leak Test: Connected to Tor.
[INFO] [systemcheck] system default networking IP Leak Test: system default networking IP Leak Test…
[INFO] [systemcheck] system default networking IP Leak Test Test Result: Ok, Tor’s TransPort was not reachable.
This is expected on Whonix-Gateway’s default configuration.
(curl exit code: [6] - [Couldn’t resolve host. The given remote host was not resolved.])
[INFO] [systemcheck] Stream Isolation Test: Ok, skipped, because TransPort test failed! Can not test stream isolation. This is expected on Whonix-Gateway’s default configuration.
[INFO] [systemcheck] Debian Package Update Check: Checking for software updates via apt-get… ( Documentation: Operating System Software and Updates )
Hit:1 tor+https://deb.whonix.org bookworm InRelease
Get:2 tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease [12.9 kB]
Hit:3 tor+https://deb.kicksecure.com bookworm InRelease
Hit:4 tor+https://deb.debian.org/debian bookworm InRelease
Hit:5 tor+https://deb.debian.org/debian bookworm-updates InRelease
Hit:6 tor+https://deb.debian.org/debian-security bookworm-security InRelease
Hit:7 tor+https://deb.debian.org/debian bookworm-backports InRelease
Hit:8 Index of /r4.2/vm/ bookworm InRelease
Fetched 12.9 kB in 1min 18s (164 B/s)
Reading package lists… Done
[INFO] [systemcheck] sudo apt-get dist-upgrade --simulate output:
Reading package lists…
Building dependency tree…
Reading state information…
Calculating upgrade…
The following packages were automatically installed and are no longer required:
hardened-malloc python3-daemon python3-lockfile
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[INFO] [systemcheck] Debian Package Update Check Result: No updates found via apt-get.
[INFO] [systemcheck] Warrant Canary Check: Debugging information:
Canary Download Time : Sun Aug 25 17:51:50 UTC 2024
Current Time : Sun Aug 25 19:36:27 UTC 2024
Canary Signature Time : Thu Aug 15 18:07:39 UTC 2024
Canary Expiration Time: Thu Sep 12 18:07:39 UTC 2024
[INFO] [systemcheck] Warrant Canary Check: Ok.
[INFO] [systemcheck] Please donate!
See: Donating to Whonix

[qwev]

small update
issue seem to disappear when not updating Whonix through the Qubes updator, currently using build version 3:10.7-1 and cli packages dependecies 24.4-1 with no issues.
(systemcheck --function show_versions --verbose)

[Patrick]

@qwev

I’m debating whether I should reinstall Qubes once more to get the full logs while Tor works well, then compare to the other logs from when it doesn’t work.
If you think that’d help please let me know which commands I should run to get the full logs needed.

No, this isn’t Microsoft Windows. Re-installation is rarely the best way to debug such issues.

Please take note of the introduction chapter on Connectivity Troubleshooting.

Also please refer to my prior reply, first block.

@Patrick

AVC apparmor=“DENIED” operation=“open” class=“file” profile=“system_tor”
name=“/sys/kernel/mm/transparent_hugepage/hpage_pmd_size”
comm=“obfs4proxy” requested_mask=“r” denied_mask=“r”

This could be an issue if using obfs4proxy.

Try Fix
Profiles . Follow
the principle, not the steps.

[qwev]

I’ve been trying to follow the steps from fix profiles but I’m not tech savvy, after running " sudo aa-logprof " i only get
“Reading log entries from /var/log/audit/audit.log.
Updating AppArmor profiles in /etc/apparmor.d.”
and nothing else.

Still, I did reinstall Qubes from scratch for some more testing.
The issue comes from the Qubes Updater, I updated the whonix templates from the terminal and Tor still worked perfectly.
Thought I could then use the Qubes Updater to update Fedora, but Tor stopped working and the apparmor error appeared. I can “use” Tor while not using obfs4, but it’s incredibly slow compared to before having the issue.

[Patrick]

@qwev

I’ve been trying to follow the steps from fix profiles but I’m not tech savvy, after running " sudo aa-logprof " i only get
“Reading log entries from /var/log/audit/audit.log.
Updating AppArmor profiles in /etc/apparmor.d.”
and nothing else.

After this you need to look which file was modified. Git will show you that. It’s included in the instructions.

This AppArmor issue has the potential to break obfsproxy which then has the potential to be the cause for this issue.