You might find that removing exim and installing dma fixes it. You’ll know when sudo aptitude update; sudo aptitude full-upgrade works and doesn’t error.
Even when trying with dma, it fails right when it hits Ntp pretty much giving the same error.
What’s the error? What if you just remove all the exim components and bsd-mailx?
I can’t get the Pi to boot anymore. I took the SD card out and put it in my PC and I can’t get it to read correctly. I think the SD might have crapped out on me.
Could be the original problem of all of this. I’ll grab a new card and do a clean install. I had some other weird issues so a clean start isn’t the worst of ideas!
Thanks for all of your help. I expect NTP to work after I reinstall haha.
I ordered a DS3231 RTC module (1 euro). Install it like this: https://translate.google.nl/translate?sl=nl&tl=en&js=y&prev=_t&hl=nl&ie=UTF-8&u=https%3A%2F%2Fraspberrytips.nl%2Fds3231-rtc-raspberry-pi%2F%23more-1631&edit-text=. Works like a charm.
I also have problem with time. “date” shows Thu 11 May 23:02:46 EEST 2017 but actual is 25th and time 21.22
Any ideas? I tried changing servers in ntp.conf but no success.
Unfortunately, I believe my problem was that my SD card was failing and lost some crucial files for NTP. The best advice I can give is below from Tinkerer. Try reinstalling NTP and if it fails, check the logs and see what is preventing it from installing. My card got bad enough to where it won’t boot anymore. So I’m on to a new card and fresh installs.
When the date is too far out, NTP won’t correct it automatically. That’s deliberate.
You need to set it roughly correctly, which you can do by:
sudo aptitude install ntpdate
sudo service ntp stop
sudo ntpdate -b pool.ntp.org
sudo service ntp start
The ntpdate command force steps the time to match that of the server found at pool.ntp.org.
2 Likes
check the timezone in the home assistant configuration file. Mine was set to central when I am in eastern
Thanks, that fixed it.
How can we do that with HassOS?
The log times are in UTC and my HassOS are in my local time zone.
Trying to sync them both together
1 Like
That’s just the way HassOS works I’m afraid, you can’t change it.
Apologies for reviving an old thread but how do I do this on Hass.io? My setup seems to have had a bit of a meltdown with the update to 202012 and it thinks it is September 2020 at the moment. I think that in turn is the root cause of other problems. Going in via SSL (using Putty) gets the response:
-bash: sudo: command not found
Sorted it. In case anyone else stumbles across this issue / thread like I did, I installed chrony from the community add on store and that then updated the system date / time settings.
1 Like
@Gronda, I’m trying to follow your steps but am a bit lost (sorry, very new to this). My system clock is also off by a variable amount each time I check so I installed the chrony add on but I am not sure how to update the system date and time settings after the install.
Hi @dawnchorus, I moved onto a HomeAssistant Blue a little while ago and no longer needed Chrony, I’m afraid. From memory just installing Chrony worked to update the time correctly every time I booted the Rpi. The problem I was having was the device losing three months so I was just looking for a way to get the date and time broadly right.
Very late here, troubleshooting as well, but when I run this I get an error saying the command doesn’t exist
Well, that was written back in 2017… 6 years ago. As was said two years later, with HAOS those commands don’t exist.
What you want to do is start a fresh thread and explain the problem you’re facing.
I did…. And got no replies… hence my search around as well.
1 Like