Error message while starting : Failed to start Secure Distributed Web Date.

anon30480075 · January 4, 2018, 9:30pm

Hello Whonix Community,

I’m looking for some help and hope I’ll find some here. If not, please redirect me to the right place

While starting the Workstation AND the Gateway, I’me getting an error message. This doesn’t stop starting the machine correctly and the time are right on my desktops.

Please find a print screen of the message : https://imgur.com/d22QzoD

Thank you in advance for helping me to fix that issue even if it doesn’t affect the use of the system.

0brand · January 4, 2018, 11:22pm

Hi Cottonwoodhill

Even though Whonix is starting it is very important that sdwdate is functioning. Secure Distributed Network Time Synchronization; which sdwdate is responsible for-is crucial for security, privacy, and anonymity.

As the error message suggested you can run the following command to get the status of the service. In your konsole run:

sudo systemctl status sdwdate.service

If the sdwdate service is loaded but not running, you can use this command to start. In your konsole run:

sudo systemctl start sdwdate.service

If you are unable to start sdwdate please post output of the first command ( sudo systemctl status sdwdate.service )

anon30480075 · January 5, 2018, 3:02am

Hi 0brand and thank you very much for your reply.

If I type :

sudo systemctl status sdwdate.service

I get :

sdwdate.service - Secure Distribiuted Web Date
Loaded: loaded (/lib/systemd/system/sdwdate.service; enabled)
Active: failed (Result: start-limit) since jeu 2018-01-04 22:21:51 UTC; 4h 27min ago
Docs: TimeSync: Whonix ™ Time Synchronization Mechanism
Process: 8073 ExecStart=/usr/bin/sdwdate (code=exited, status=1/FAILURE)
Main PID: 8073 (code=exited, status=1/FAILURE)

jan 04 22:21:51 host systemd[1]: Unit sdwdate.service entered failed state.
jan 04 22:21:51 host systemd[1]: sdwdate.service holdoff time over, schedul…t.
jan 04 22:21:51 host systemd[1]: Stopping Secure Distribiuted Web Date…
jan 04 22:21:51 host systemd[1]: Starting Secure Distribiuted Web Date…
jan 04 22:21:51 host systemd[1]: sdwdate.service start request repeated too…t.
jan 04 22:21:51 host systemd[1]: Failed to start Secure Distribiuted Web Date.
jan 04 22:21:51 host systemd[1]: Unit sdwdate.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
user@host:~$ sudo systemctl start sdwdate.service
user@host:~$ sudo systemctl status sdwdate.service

sdwdate.service - Secure Distribiuted Web Date
Loaded: loaded (/lib/systemd/system/sdwdate.service; enabled)
Active: failed (Result: start-limit) since ven 2018-01-05 02:50:08 UTC; 8s ago
Docs: TimeSync: Whonix ™ Time Synchronization Mechanism
Process: 31560 ExecStart=/usr/bin/sdwdate (code=exited, status=1/FAILURE)
Main PID: 31560 (code=exited, status=1/FAILURE)

jan 05 02:50:08 host systemd[1]: Unit sdwdate.service entered failed state.
jan 05 02:50:08 host systemd[1]: sdwdate.service holdoff time over, schedul…t.
jan 05 02:50:08 host systemd[1]: Stopping Secure Distribiuted Web Date…
jan 05 02:50:08 host systemd[1]: Starting Secure Distribiuted Web Date…
jan 05 02:50:08 host systemd[1]: sdwdate.service start request repeated too…t.
jan 05 02:50:08 host systemd[1]: Failed to start Secure Distribiuted Web Date.
jan 05 02:50:08 host systemd[1]: Unit sdwdate.service entered failed state.

I can’t find what’s going wrong as I’m not famliliar with Linux at this date.

Could you please support me and help me to resolve this isusse ?

Thank you in advance.

0brand · January 5, 2018, 11:20am

Hi Cottonwoodhill

I should have also asked:

Is this a new Whonix installation? If so did you verify the images?
What hypervisor are you using?
Can you please provide the output of both:

cat /var/log/sdwdate.log
cat /var/log/kern.log | grep DENIED

anon30480075 · January 5, 2018, 5:06pm

Hi 0brand,

Thank you very much for your answer and for devoting time for me.

No this is not a new installation, about 6 months old but the message appeared from the begining on. I am just curious now and would like to resolve this error that I thought would desapear with some time/updates…
Whonix is running on VM VirtualBox

root@host:~# cat /var/log/sdwdate.log
2018-01-04 17:32:52,231 - sdwdate.log - INFO - sdwdate started. PID 635
2018-01-04 17:32:52,262 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 17:32:52,680 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 17:32:52 UTC 2018 (unixtime 1515087172.68)
2018-01-04 17:32:53,337 - sdwdate.log - INFO - sdwdate started. PID 782
2018-01-04 17:32:53,351 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 17:32:53,574 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 17:32:53 UTC 2018 (unixtime 1515087173.57)
2018-01-04 17:32:54,224 - sdwdate.log - INFO - sdwdate started. PID 804
2018-01-04 17:32:54,238 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 17:32:54,432 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 17:32:54 UTC 2018 (unixtime 1515087174.43)
2018-01-04 17:32:55,082 - sdwdate.log - INFO - sdwdate started. PID 827
2018-01-04 17:32:55,094 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 17:32:55,291 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 17:32:55 UTC 2018 (unixtime 1515087175.29)
2018-01-04 17:32:55,932 - sdwdate.log - INFO - sdwdate started. PID 849
2018-01-04 17:32:55,945 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 17:32:56,168 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 17:32:56 UTC 2018 (unixtime 1515087176.17)
2018-01-04 20:03:56,317 - sdwdate.log - INFO - sdwdate started. PID 639
2018-01-04 20:03:56,352 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:03:57,146 - sdwdate.log - WARNING - Prerequsite check:
Tor Bootstrap Result: Tor’s Control Port could not be reached.
Did you start Gateway beforehand?
Please run whonixcheck on Gateway.
2018-01-04 20:04:07,480 - sdwdate.log - WARNING - Prerequsite check:
Tor is not yet fully bootstrapped. 85 % done.
Tor reports: NOTICE BOOTSTRAP PROGRESS=85 TAG=handshake_or SUMMARY="Finishing handshake with first hop"
2018-01-04 20:04:27,909 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:04:27 UTC 2018 (unixtime 1515096267.91)
2018-01-04 20:04:28,443 - sdwdate.log - INFO - sdwdate started. PID 1095
2018-01-04 20:04:28,459 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:04:28,705 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:04:28 UTC 2018 (unixtime 1515096268.71)
2018-01-04 20:04:29,190 - sdwdate.log - INFO - sdwdate started. PID 1118
2018-01-04 20:04:29,206 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:04:29,442 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:04:29 UTC 2018 (unixtime 1515096269.44)
2018-01-04 20:04:29,937 - sdwdate.log - INFO - sdwdate started. PID 1140
2018-01-04 20:04:29,951 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:04:30,442 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:04:30 UTC 2018 (unixtime 1515096270.44)
2018-01-04 20:04:30,940 - sdwdate.log - INFO - sdwdate started. PID 1168
2018-01-04 20:04:30,952 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:04:31,168 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:04:31 UTC 2018 (unixtime 1515096271.17)
2018-01-04 20:04:31,714 - sdwdate.log - INFO - sdwdate started. PID 1194
2018-01-04 20:04:31,726 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:04:31,948 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:04:31 UTC 2018 (unixtime 1515096271.95)
2018-01-04 20:31:42,752 - sdwdate.log - INFO - sdwdate started. PID 640
2018-01-04 20:31:42,785 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:31:49,131 - sdwdate.log - WARNING - Prerequsite check:
Tor Bootstrap Result: Tor’s Control Port could not be reached.
Did you start Gateway beforehand?
Please run whonixcheck on Gateway.
2018-01-04 20:32:21,637 - sdwdate.log - WARNING - Prerequsite check:
Tor is not yet fully bootstrapped. 85 % done.
Tor reports: NOTICE BOOTSTRAP PROGRESS=85 TAG=handshake_or SUMMARY="Finishing handshake with first hop"
2018-01-04 20:32:41,948 - sdwdate.log - WARNING - Prerequsite check:
Tor is not yet fully bootstrapped. 90 % done.
Tor reports: NOTICE BOOTSTRAP PROGRESS=90 TAG=circuit_create SUMMARY="Establishing a Tor circuit"
2018-01-04 20:32:52,126 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:32:52 UTC 2018 (unixtime 1515097972.13)
2018-01-04 20:32:52,615 - sdwdate.log - INFO - sdwdate started. PID 3995
2018-01-04 20:32:52,651 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:32:52,869 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:32:52 UTC 2018 (unixtime 1515097972.87)
2018-01-04 20:32:53,352 - sdwdate.log - INFO - sdwdate started. PID 4017
2018-01-04 20:32:53,361 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:32:53,510 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:32:53 UTC 2018 (unixtime 1515097973.51)
2018-01-04 20:32:54,107 - sdwdate.log - INFO - sdwdate started. PID 4041
2018-01-04 20:32:54,117 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:32:54,284 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:32:54 UTC 2018 (unixtime 1515097974.28)
2018-01-04 20:32:54,852 - sdwdate.log - INFO - sdwdate started. PID 4063
2018-01-04 20:32:54,865 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:32:55,024 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:32:55 UTC 2018 (unixtime 1515097975.02)
2018-01-04 20:32:55,611 - sdwdate.log - INFO - sdwdate started. PID 4099
2018-01-04 20:32:55,619 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 20:32:55,766 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 20:32:55 UTC 2018 (unixtime 1515097975.77)
2018-01-04 22:11:36,116 - sdwdate.log - INFO - sdwdate started. PID 638
2018-01-04 22:11:36,157 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 22:11:38,393 - sdwdate.log - WARNING - Prerequsite check:
Tor Bootstrap Result: Tor’s Control Port could not be reached.
Did you start Gateway beforehand?
Please run whonixcheck on Gateway.
2018-01-04 22:11:48,654 - sdwdate.log - WARNING - Prerequsite check:
Tor is not yet fully bootstrapped. 85 % done.
Tor reports: NOTICE BOOTSTRAP PROGRESS=85 TAG=handshake_or SUMMARY="Finishing handshake with first hop"
2018-01-04 22:13:20,015 - sdwdate.log - WARNING - Prerequsite check:
Tor is not yet fully bootstrapped. 90 % done.
Tor reports: NOTICE BOOTSTRAP PROGRESS=90 TAG=circuit_create SUMMARY="Establishing a Tor circuit"
2018-01-04 22:13:30,159 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 22:13:30 UTC 2018 (unixtime 1515104010.16)
2018-01-04 22:13:30,626 - sdwdate.log - INFO - sdwdate started. PID 7516
2018-01-04 22:13:30,634 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 22:13:30,792 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 22:13:30 UTC 2018 (unixtime 1515104010.79)
2018-01-04 22:13:31,372 - sdwdate.log - INFO - sdwdate started. PID 7538
2018-01-04 22:13:31,382 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 22:13:31,564 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 22:13:31 UTC 2018 (unixtime 1515104011.56)
2018-01-04 22:13:32,131 - sdwdate.log - INFO - sdwdate started. PID 7561
2018-01-04 22:13:32,139 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 22:13:32,290 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 22:13:32 UTC 2018 (unixtime 1515104012.29)
2018-01-04 22:13:32,880 - sdwdate.log - INFO - sdwdate started. PID 7583
2018-01-04 22:13:32,890 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 22:13:33,041 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 22:13:33 UTC 2018 (unixtime 1515104013.04)
2018-01-04 22:13:33,619 - sdwdate.log - INFO - sdwdate started. PID 7605
2018-01-04 22:13:33,627 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-04 22:13:33,775 - sdwdate.log - INFO - Fetching remote times, start Thu Jan 04 22:13:33 UTC 2018 (unixtime 1515104013.78)
2018-01-05 16:46:26,544 - sdwdate.log - INFO - sdwdate started. PID 638
2018-01-05 16:46:26,585 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-05 16:46:27,134 - sdwdate.log - WARNING - Prerequsite check:
Tor Bootstrap Result: Tor’s Control Port could not be reached.
Did you start Gateway beforehand?
Please run whonixcheck on Gateway.
2018-01-05 16:46:37,458 - sdwdate.log - INFO - Fetching remote times, start Fri Jan 05 16:46:37 UTC 2018 (unixtime 1515170797.46)
2018-01-05 16:46:38,113 - sdwdate.log - INFO - sdwdate started. PID 915
2018-01-05 16:46:38,122 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-05 16:46:38,278 - sdwdate.log - INFO - Fetching remote times, start Fri Jan 05 16:46:38 UTC 2018 (unixtime 1515170798.28)
2018-01-05 16:46:38,763 - sdwdate.log - INFO - sdwdate started. PID 953
2018-01-05 16:46:38,775 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-05 16:46:38,922 - sdwdate.log - INFO - Fetching remote times, start Fri Jan 05 16:46:38 UTC 2018 (unixtime 1515170798.92)
2018-01-05 16:46:39,531 - sdwdate.log - INFO - sdwdate started. PID 1013
2018-01-05 16:46:39,541 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-05 16:46:39,699 - sdwdate.log - INFO - Fetching remote times, start Fri Jan 05 16:46:39 UTC 2018 (unixtime 1515170799.7)
2018-01-05 16:46:40,376 - sdwdate.log - INFO - sdwdate started. PID 1035
2018-01-05 16:46:40,386 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-05 16:46:40,529 - sdwdate.log - INFO - Fetching remote times, start Fri Jan 05 16:46:40 UTC 2018 (unixtime 1515170800.53)
2018-01-05 16:46:40,905 - sdwdate.log - INFO - sdwdate started. PID 1058
2018-01-05 16:46:40,915 - sdwdate.log - INFO - Tor socks host: 10.152.152.10 Tor socks port: 9108
2018-01-05 16:46:41,083 - sdwdate.log - INFO - Fetching remote times, start Fri Jan 05 16:46:41 UTC 2018 (unixtime 1515170801.08)

root@host:~# cat /var/log/kern.log | grep DENIED
root@host:~#

No return from the machine for the second command line.

I hope I have answered your requests and remain at your disposal for further investigation.

0brand · January 5, 2018, 5:24pm

Hi CottenWoodhill

Thanks for running those commands. I didn’t expect there to be any output with cat /var/log/kern.log but just wanted to be sure. Can you please run this command in Whonix-Gateway konsole and post output.

whonixcheck

anon30480075 · January 5, 2018, 5:31pm

Dear 0brand,

Please find below the result of the output you asked for and that I ran on the Gateway :

Welcome to Whonix!
https://www.whonix.org
The programs included with the Whonix GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Whonix GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law. Whonix is a derivative of Debian GNU/Linux.
Whonix is based on Tor. Whonix is produced independently from the
Tor (r) anonymity software and carries no guarantee from The Tor Project
about quality, suitability or anything else.
Whonix is experimental software by means of concept and design.
Do not rely on it for strong anonymity.
default user account: user
default root account: root
default passwords: changeme
Type: “whonix” for help.
user@host:~$ whonixcheck
[INFO] [whonixcheck] Connected to Tor.
[INFO] [whonixcheck] Whonix is produced independently of, with no guarantee from, The Tor Project. Whonix is experimental software. Do not rely on it for strong anonymity. https://www.whonix.org
[INFO] [whonixcheck] SocksPort Test: Testing Tor’s SocksPort…
[INFO] [whonixcheck] SocksPort Test Result: Connected to Tor. IP: 196.54.55.14
[INFO] [whonixcheck] Whonix News Download: Checking for Whonix news and updates…
[INFO] [whonixcheck] Whonix News Result:
â Up to date: whonix-gateway-packages-dependencies 3.4.2-1
[INFO] [whonixcheck] Debian Package Update Check: Checking for software updates via apt-get… ( Documentation: Operating System Software and Updates - Kicksecure )
[INFO] [whonixcheck] Debian Package Update Check Result: No updates found via apt-get.
[INFO] [whonixcheck] Whonix APT Repository: Enabled.
When the Whonix team releases JESSIE 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 whonix_repository

0brand · January 6, 2018, 12:35am

Hi Cottonwoodhill

Did you modify whonix in any way. For example customizing using the Advanced Security Guide or anything not in the Whonix Wiki?

EDIT: Are you only getting this error message at system boot? (i.e. before whonix is bootstrapped )

anon30480075 · January 6, 2018, 7:05am

Hi 0brand,

No I didn’t change anything in Whonix parameters neither customized something. I’m new in the Linux world and wouldn’t have the ability to do so…

If I only have this message as system boot :
I would answer yes. Could it appear elsewhere ?

Thank you for your reply.

Patrick · January 6, 2018, 2:11pm

sudo journalctl -u sdwdate -f

sudo tail -f /var/log/sdwdate.log

While running the above commands in two konsole tabs, do this in another konsole tab.

sudo systemctl restart sdwdate

Then check the output of these commands if there is any error message.

Otherwise try this please and see if there are any errors.

sudo -u sdwdate sdwdate

anon30480075 · January 6, 2018, 10:49pm

Hi Patrick and thank you for joining this thread.

On the first terminal :

Results of the first command line
user@host:~$ sudo journalctl -u sdwdate -f
[sudo] password for user:
– Logs begin at sam 2018-01-06 22:27:34 UTC. –
jan 06 22:30:18 host sdwdate[1621]: return self.language.get(key, None)
jan 06 22:30:18 host sdwdate[1621]: AttributeError: ‘str’ object has no attribute 'get’
jan 06 22:30:18 host systemd[1]: sdwdate.service: main process exited, code=exited, status=1/FAILURE
jan 06 22:30:18 host systemd[1]: Unit sdwdate.service entered failed state.
jan 06 22:30:19 host systemd[1]: sdwdate.service holdoff time over, scheduling restart.
jan 06 22:30:19 host systemd[1]: Stopping Secure Distribiuted Web Date…
jan 06 22:30:19 host systemd[1]: Starting Secure Distribiuted Web Date…
jan 06 22:30:19 host systemd[1]: sdwdate.service start request repeated too quickly, refusing to start.
jan 06 22:30:19 host systemd[1]: Failed to start Secure Distribiuted Web Date.
jan 06 22:30:19 host systemd[1]: Unit sdwdate.service entered failed state.
sudo journalctl -u sdwdate -f

On a second terminal we get :

user@host:~$ sudo tail -f /var/log/sdwdate.log
[sudo] password for user:
2018-01-06 22:30:16,863 - sdwdate.log - INFO - Fetching remote times, start Sat Jan 06 22:30:16 UTC 2018 (unixtime 1515277816.86)
2018-01-06 22:30:17,472 - sdwdate.log - INFO - sdwdate started. PID 1576
2018-01-06 22:30:17,482 - sdwdate.log - INFO - Tor socks host: 127.0.0.1 Tor socks port: 9108
2018-01-06 22:30:17,618 - sdwdate.log - INFO - Fetching remote times, start Sat Jan 06 22:30:17 UTC 2018 (unixtime 1515277817.62)
2018-01-06 22:30:18,226 - sdwdate.log - INFO - sdwdate started. PID 1599
2018-01-06 22:30:18,235 - sdwdate.log - INFO - Tor socks host: 127.0.0.1 Tor socks port: 9108
2018-01-06 22:30:18,370 - sdwdate.log - INFO - Fetching remote times, start Sat Jan 06 22:30:18 UTC 2018 (unixtime 1515277818.37)
2018-01-06 22:30:18,738 - sdwdate.log - INFO - sdwdate started. PID 1621
2018-01-06 22:30:18,748 - sdwdate.log - INFO - Tor socks host: 127.0.0.1 Tor socks port: 9108
2018-01-06 22:30:18,883 - sdwdate.log - INFO - Fetching remote times, start Sat Jan 06 22:30:18 UTC 2018 (unixtime 1515277818.88)

no error with the third coomand line and the output is :

user@host:~$ sudo -u sdwdate sdwdate
[sudo] password for user:
sdwdate started. PID 6705
Tor socks host: 127.0.0.1 Tor socks port: 9108
Fetching remote times, start Sat Jan 06 22:40:50 UTC 2018 (unixtime 1515278450.88)
Traceback (most recent call last):
File “/usr/bin/sdwdate”, line 552, in
icon, status = sdwdate.sdwdate_loop()
File “/usr/bin/sdwdate”, line 323, in sdwdate_loop
time_sanity_check = self.time_sanity_check(current_unixtime)
File “/usr/bin/sdwdate”, line 170, in time_sanity_check
self.message = (self.(‘tsc_1’) + status + self.(‘tsc_2’) + time_one)
File “/usr/lib/python2.7/dist-packages/guimessages/translations.py”, line 34, in gettext
return self.language.get(key, None)
AttributeError: ‘str’ object has no attribute ‘get’

Thank you for your help as I’m totally lost here…

Patrick · January 7, 2018, 1:10pm

Is there any difference between your /usr/share/translations/sdwdate.yaml and sdwdate.yaml?

wget https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml

diff /usr/share/translations/sdwdate.yaml sdwdate.yaml

Can you make head or tail of this? @troubadour @iry

anon30480075 · January 7, 2018, 1:30pm

Hi Patrick,

I’m not sure I have understood what your request was, so I entered this command line :

wget https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml
diff /usr/share/translations/sdwdate.yaml sdwdate.yaml

and the outuput is :

user@host:~$ wget https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml diff /usr/share/translations/sdwdate.yaml sdwdate.yaml
converted ‘https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml’ (ISO-8859-1) → ‘https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml’ (UTF-8)
–2018-01-07 13:10:22-- https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml
Résolution de raw.githubusercontent.com (raw.githubusercontent.com)… 151.101.0.133
Connexion à raw.githubusercontent.com (raw.githubusercontent.com)|151.101.0.133|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 1813 (1.8K) [text/plain]
Sauvegarde en : « sdwdate.yaml »
sdwdate.yaml 100%[=====================>] 1.77K --.-KB/s ds 0s
2018-01-07 13:10:33 (39.7 MB/s) – « sdwdate.yaml » sauvegardé [1813/1813]
converted ‘http://diff’ (ISO-8859-1) → ‘http://diff’ (UTF-8)
–2018-01-07 13:10:33-- http://diff/
Résolution de diff (diff)… échec : Échec non récupérable lors de la résolution du nom.
wget.anondist-orig : impossible de résoudre l’adresse de l’hôte « diff »
/usr/share/translations/sdwdate.yaml: Schéma manquant.
converted ‘http://sdwdate.yaml’ (ISO-8859-1) → ‘http://sdwdate.yaml’ (UTF-8)
–2018-01-07 13:10:46-- http://sdwdate.yaml/
Résolution de sdwdate.yaml (sdwdate.yaml)… échec : Échec non récupérable lors de la résolution du nom.
wget.anondist-orig : impossible de résoudre l’adresse de l’hôte « sdwdate.yaml »
Terminé – 2018-01-07 13:10:57 –
Temps total effectif : 35s
Téléchargés : 1 fichiers, 1.8K en 0s (39.7 MB/s)

Please let me apology if I understood wrong or confirm it the result is the one one you was waiting for.

Thank you.

Patrick · January 7, 2018, 2:14pm

It is two different commands. Not one command. Each line is a separate command.

anon30480075 · January 7, 2018, 2:24pm

Thank you for your precision.

Well, I get no output when I type the second command after the first one, is that normal ?

root@host:~# wget https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml
converted ‘https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml’ (ISO-8859-1) → ‘https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml’ (UTF-8)
–2018-01-07 14:14:07-- https://raw.githubusercontent.com/Whonix/sdwdate/Whonix13/usr/share/translations/sdwdate.yaml
Résolution de raw.githubusercontent.com (raw.githubusercontent.com)… 151.101.120.133
Connexion à raw.githubusercontent.com (raw.githubusercontent.com)|151.101.120.133|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 1813 (1.8K) [text/plain]
Sauvegarde en : « sdwdate.yaml.2 »
sdwdate.yaml.2 100%[===========================================================>] 1.77K --.-KB/s ds 0s
2018-01-07 14:14:09 (49.6 MB/s) – « sdwdate.yaml.2 » sauvegardé [1813/1813]
root@host:~# diff /usr/share/translations/sdwdate.yaml sdwdate.yaml

Does that mean there is no difference between both files ?

Patrick · January 7, 2018, 2:31pm

Yes, no output and exit code of 0 means no difference.

anon30480075 · January 7, 2018, 2:41pm

Ok Patrick, thank you for the confirmation. Any further suggestion to find out what could be the problem ?

troubadour · January 7, 2018, 7:24pm

Can you make head or tail of this? @troubadour @iry

I have had this error a couple of days ago. To check, you can run anon-connection-wizard as user. It seems guimessage returns the error whenever it’s called.

I had no time to look into it. Will try to do it.

anon30480075 · January 10, 2018, 5:46pm

Hi @troubadour,

Please correct me if I’m missunderstanding, should I wait until an update is released ?

For now, there is no way on my side I could correct the situation ?

Thank you for your support.

troubadour · January 10, 2018, 9:28pm

Not necessarily. I guess you are using Whonix 13.
Could you post the content of the file translations.py. It is probably in /usr/share/pyshared/guimessages/ folder.

@Patrick
As at the moment I have no Whonix 13 available. I cannot not know if the issue corrected in ⚓ T625 python-guimessages guimessage.py breaks on default locales settings LANG=POSIX LANG=C was installed in Whonix 13.

In the meantime, a very similar error (when running a setup script as user) in guimessage.py instead of translations.py is fixed.