sdwdate sclockadj - bug report - SDWDATE_SUBSHELL_SCLOCKADJ_EXIT_CODE: 127

Development
1

Move to appropriate section if necessary. This notice came up in an alert window. I was not doing anything unusual before:

ERROR: ############################################ ## Error detected! Please
report this bug! # ## ## BASH_SOURCE: /usr/bin/sdwdate ## SDW_EXIT_ON_ERROR: 1

SDW_MODE: daemon ## SDWDATE_SUBSHELL_SCLOCKADJ_EXIT_CODE: 127 ##

exit_code: 0 ## error_cause: sdwdate_error_handler called with error_text:
subshell for sclockadj exited with non-zero exit code: 127
############################################

Edit by Patrick:
changed title

2

What Whonix version are you using?

Which Whonix repository are you using if any?

Any additional config such as AppArmor profiles?

3

Apologies, I’ve lost the password to the account I created to report the bug, thinking it’d be one-time-use.

To answer your questions, I’m using Whonix 9, stable repository, and no additional AppArmor profiles or nonstandard configurations. Hope this can be of some help.

4

Exit code 127 means that the binary could not be found. Same would happen if you run.

non-existent ; echo $?
-bash: non-existent: command not found
127

/usr/lib/sclockadj exists on your system?

Strange, because if it was a common issue, we’d heard from it multiple times now. Could be file system corruption.

Does the error persist after reboot?

/var/log/sdwdate.log could help.