NTPD errors in the log

« previous next »

Print

Pages: [1]

Author Topic: NTPD errors in the log (Read 2562 times)

elektroinside

Hero Member
Posts: 574
Karma: 51

NTPD errors in the log

« on: February 03, 2018, 12:33:32 am »

I have this error in the logs:

# ntpd[34637]: mlockall(): Cannot allocate memory

The sync is working though, the daemon is up and running.

Time is crucial for me. Should I be worried?

Logged

OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member

marjohn56

Hero Member
Posts: 1676
Karma: 170

Re: NTPD errors in the log

« Reply #1 on: February 03, 2018, 09:55:02 am »

there are a couple of threads on this on Github. It appears its something to do with HardenedBSD, it appears ntpd complains and carries on regardless. I see the same log entry but the daemon is still running.

Logged

OPNsense 21.7 - Qotom Q355G4 - ISP - Community Fibre 1Gbps.

Team Rebellion Member - If we've helped you remember to applaud

elektroinside

Hero Member
Posts: 574
Karma: 51

Re: NTPD errors in the log

« Reply #2 on: February 03, 2018, 11:41:14 am »

Thank you

Logged

OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member

franco

Administrator
Hero Member
Posts: 13929
Karma: 1208

Re: NTPD errors in the log

« Reply #3 on: February 03, 2018, 03:42:57 pm »

The explanation via Shawn:

https://github.com/opnsense/core/issues/1785#issuecomment-344954311

Cheers,
Franco

Logged

Print

Pages: [1]

« previous next »