Rare System check error

anon289739801 · July 31, 2022, 1:59pm

I have searched the forums far and wide and i cant find this issue before so i would like to report as well as finding a solution for the problem. Here is the output ERROR:

############################################################################### 
## systemcheck script bug. 
## No panic. Nothing is broken. Just some rare condition has been hit. 
## Try again later. There is likely a solution for this problem. 
## Please see Whonix News, Whonix Blog and Whonix User Help Forum. 
## Please report this bug! 
## 
## who_ami: systemcheck 
## identifier: 
## IDENTIFIER: systemcheck 
## exit_code: 1 
## error_cause: error_handler signal ERR detected with BASH_COMMAND: $output_tool --identifier "$IDENTIFIER" --whoami "$who_ami" "${output_text[@]}" 
## 
## For debugging, run: 
## 
## bash -x systemcheck --verbose 
## 
## Clean the output and report to developers. 
#########################################################################

Thank you
Anon

anon289739801 · July 31, 2022, 3:13pm

Any help would or hints on articles or wiki pages would be appreciated thank you!

Patrick · July 31, 2022, 3:37pm

Exactly as in the error message.

Or…

systemcheck --debug

anon289739801 · July 31, 2022, 7:35pm

it seems the error only appears on gui version of sytstemcheck

anon289739801 · July 31, 2022, 9:18pm

it only shows up on the graphical version of system check not terminal is there a way to debug for the gui version?

Patrick · August 1, 2022, 7:09am

systemcheck --gui --debug

Or.

systemcheck --cli --gui --debug

anon289739801 · August 1, 2022, 6:11pm

what do i paste it is thousands of lines long

anon289739801 · August 1, 2022, 6:12pm

what do i paste it is thousands of lines long.

Patrick · August 2, 2022, 10:26am

The last few lines before the error would probably be sufficient.

Got this issue…?

github.com/QubesOS/qubes-issues

VM logs filled with "host kernel: xen:grant_table: g.e x still pending" messages

opened 10:40PM - 01 Jun 22 UTC

closed 02:23AM - 20 Jul 22 UTC

TNTBOMBOM

T: bug C: kernel r4.1-buster-cur-test r4.1-dom0-cur-test P: default r4.1-bullseye-cur-test diagnosed r4.1-centos-stream8-cur-test r4.1-fc34-cur-test r4.1-fc35-cur-test r4.1-bookworm-cur-test r4.1-fc36-cur-test

### Qubes OS release 4.1 ### Brief summary Usually i keep Qubes running… for several days and i turn it off on weekends, Im discovering that longer the VM running the more logs getting duplication messages. ### Steps to reproduce - Open any VM and keep it open for several days (preferable to keep an app opened as well like thunderbird or hexchat ..etc) - Open Terminal and write: `sudo journalctl -b ` - See the output ### Expected behavior No duplication to this level at least. ### Actual behavior E.g log: ``` May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x735 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x149 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1bb4 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x12e still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1980 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x17a1 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0xc1 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x18a8 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x18b3 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x14c still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1c21 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x198c still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0xdc still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x720 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x15d still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x189f still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x177e still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1d3c still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1881 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x732 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x207 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x17c7 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1cc1 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x121 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x174a still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1780 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x162 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x1833 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x19e3 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x18a0 still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x179d still pending May 31 15:41:09 host kernel: xen:grant_table: g.e. 0x730 still pending ``` Full log: [journalctl-b.txt](https://github.com/QubesOS/qubes-issues/files/8819146/journalctl-b.txt)

Long running VM? In this case…

Then probably just ignore this error until the next update of systemcheck.

(Not a systemcheck error. It’s a Qubes issue. But systemcheck cannot show the super long log yet. Only after update.)

Patrick · August 2, 2022, 10:27am

The last few hundrets of lines are probably sufficient. See also:
Pasting Logs for Support

(Whonix is based on Kicksecure.)