Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
root ~ timedatectl status
Local time: Tue 2019-07-30 11:49:09 CEST
Universal time: Tue 2019-07-30 09:49:09 UTC
RTC time: Tue 2019-07-30 09:49:10
Time zone: Europe/Brussels (CEST, +0200)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
root ~
Any idea how to get the same output from the date command in buster like in stretch ?
NOTE: dmesg / rsyslog etc.. all show the good output. Only on command line the `date` command give's the bad layout.
root ~ dpkg-reconfigure tzdata
Current default time zone: 'Europe/Brussels'
Local time is now: Tue Jul 30 15:21:44 CEST 2019.
Universal Time is now: Tue Jul 30 13:21:44 UTC 2019.
root ~ date
Tue 30 Jul 2019 03:22:21 PM CEST
root ~
stays the same.
Note the strange thing it is happened on the updated systems from stretch to buster and on a clean install.
As you notice there is no reason why it would not be correct. Everything is as it should be configured and the same as on stretch but in Buster is has strange results. Also as far as I can see in the log files is everything ok only the `date` command gives problems. But yeah some of my scripts depend on the correct date output format.
root / var log /upgrade/date
Tue 30 Jul 2019 03:49:35 PM CEST
root / var log /upgrade/date --version
date (GNU coreutils) 8.26
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David MacKenzie.
root / var log date --version
date (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David MacKenzie.
root / var log
I copied the date command from stretch on an shared NFS and then used this on buster. With the same result.
Thank you for your imput. But I am sure it is not related to the powerline configuration. In that case I should have the same problem in Stretch. My systems and configurations are kept inline using ansible so both stretch as buster have the same powerline configuration and I not use the Powerlevel9k theme .
May be a date string to export.
I cannot do more. Sorry.
Well I have for me the workaround. I use now an export to set this "LC_TIME=en_IE.UTF-8" when I login. But in the end it should get fixed at some other level. I am not even sure if I had this problem when I was running buster when it was still in testing phase.
I hope they fix it. But my work around helps me at least.
Sorry but behavior of Buster seems more logical.
Can only be fixed what is clearly identified as a "bug". Check buglist, who knows.
Or ... re-investigate your scripts.... (=> convert date to something more consistent like date +%Y%m%d-%H:%M )