Error - pakfire: TIME ERROR: Unable to get the nettime, this may lead to the verification error

Community
1

Can anyone help me? I always start the upgrade with “packfire upgrade” or sometimes “packfire upgrade --force”. So far always without problems.

Now I get…

> Sep 11 11:49:53 ipfire01 pakfire: PAKFIRE INFO: IPFire Pakfire 2.29-x86_64 started!
> Sep 11 11:49:53 ipfire01 pakfire: CORE INFO: Checking for Core-Updates...
> Sep 11 11:49:53 ipfire01 pakfire: CORE INFO: core-list.db is 160 seconds old. - DEBUG: noforce
> Sep 11 11:49:53 ipfire01 pakfire: CORE UPGR: Upgrading from release 185 to 187
> Sep 11 11:49:53 ipfire01 pakfire: DOWNLOAD STARTED: paks/core-upgrade-2.29-186.ipfire
> Sep 11 11:49:53 ipfire01 pakfire: MIRROR INFO: 23 servers found in list
> Sep 11 11:49:53 ipfire01 pakfire: DOWNLOAD INFO: Host: ftp.fau.de (HTTPS) - File: ipfire/pakfire2/2.29-x86_64/paks/core-upgrade-2.29-186.ipfire
> Sep 11 11:49:54 ipfire01 pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.29-x86_64/paks/core-upgrade-2.29-186.ipfire has size of 81570759 bytes
> Sep 11 11:52:49 ipfire01 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
> Sep 11 11:52:49 ipfire01 pakfire: DOWNLOAD INFO: File received. Start checking signature...
> Sep 11 11:52:49 ipfire01 pakfire: DOWNLOAD ERROR: The downloaded file (ipfire/pakfire2/2.29-x86_64/paks/core-upgrade-2.29-186.ipfire) wasn't verified by IPFire.org. Sorry - Exiting...
> Sep 11 11:53:09 ipfire01 pakfire: TIME ERROR: Unable to get the nettime, this may lead to the verification error.
> Sep 11 11:53:09 ipfire01 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.

Please help!

2

Check if the DNS server page is showing “working” in green and if the status of each dns server specified is also “OK” in green.

Pakfire contacts the pool.ntp.org to get a time and then it checks that time and offset to the time value on your IPFire system. If it can’t get a response from that ntp pool then it gives the message that you have found.

pakfire functions.pl

2 Likes
3

problem with using pool.ntp.org is you are contacting a cluster that has a lot of servers from everywhere and that is why they split it up by continents and countries. So a real valid address is 0.europe.pool.ntp.org or 0.north-america.pool.ntp.org or 0.us.pool.ntp.org. I heard of people having issues before with pool.ntp.org and the solution is to use the closest branch of the cluster.

1 Like
4

We cannot assign a country or continent pool as it is in the code itself.

Also if you use pool.ntp.org you will get your time, in most cases from servers close by to your actual location.

pool.ntp.org is also a valid address.

The pool.ntp.org project even writes

In most cases it’s best to use pool.ntp.org to find an NTP server (or 0.pool.ntp.org, 1.pool.ntp.org, etc if you need multiple server names). The system will try finding the closest available servers for you.

1 Like
5

Problem with it is it works in theory. Because the closest server doesn’t always get picked. I have 0.us.pool.ntp.org and 1.us.pool.ntp.org as my entries and I don’t have issues. However, when I had pool.ntp.org configured, it gave me errors randomly in the system log.