How to diagnose SMB/CIFS drop outs from FreeNAS

[Eds89]

Hi,

I have a FreeNAS/ESXi AIO, and am having an issue with SMB access from a VM on the same ESXi host the FreeNAS VM is.

FreeNAS and my Windows Server 2016 VMs both run on the same host, and are connected to the same vSwitch with vmxnet3 vNICS.
I have an app running on 2016, that stores and reads data at length, on a share on the FreeNAS box.
I am finding that the app repeatedly reports it is unable to write to that location.

I originally thought it may be a networking issue, as I was seeing some NDIS NIC reset events in Windows, but tried with a E1000 adapter also, and from other VMs, all with the same results.
As such, I am now suspecting there may be an issue on the FreeNAS side of things.

Can anyone tell me if there are any service or CIFS logs of any kind that I can look at in FreeNAS to see if there may be an issue?

Cheers
Eds

 

[anodos]

Hi,

I have a FreeNAS/ESXi AIO, and am having an issue with SMB access from a VM on the same ESXi host the FreeNAS VM is.

FreeNAS and my Windows Server 2016 VMs both run on the same host, and are connected to the same vSwitch with vmxnet3 vNICS.
I have an app running on 2016, that stores and reads data at length, on a share on the FreeNAS box.
I am finding that the app repeatedly reports it is unable to write to that location.

I originally thought it may be a networking issue, as I was seeing some NDIS NIC reset events in Windows, but tried with a E1000 adapter also, and from other VMs, all with the same results.
As such, I am now suspecting there may be an issue on the FreeNAS side of things.

Can anyone tell me if there are any service or CIFS logs of any kind that I can look at in FreeNAS to see if there may be an issue?

Cheers
Eds

/var/log/messages
/var/log/samba4/log.smbd

 

[Eds89]

Thanks for this!!

So I just enabled AD monitoring to resolve another issue I had, which obviously stopped and started the AD service (And by the looks of it, CIFS):

Code:

Apr 19 14:56:46 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 19 14:56:49 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstop
Apr 19 14:56:49 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstop
Apr 19 14:56:50 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstop
Apr 19 14:56:53 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory forcestop
Apr 19 14:57:00 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstop &
Apr 19 14:57:06 Eds-FS ActiveDirectory: /usr/sbin/service samba_server forcestop
Apr 19 14:57:07 Eds-FS ActiveDirectory: /usr/sbin/service ix-pre-samba start
Apr 19 14:57:10 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit forcestop
Apr 19 14:57:10 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 19 14:57:20 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 19 14:57:21 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstart default EDS89.COM
Apr 19 14:57:22 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart
Apr 19 14:57:23 Eds-FS ActiveDirectory: /usr/sbin/service ix-ldap quietstart
Apr 19 14:57:23 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit quietstart
Apr 19 14:57:25 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit status
Apr 19 14:57:26 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 19 14:57:31 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory quietstart
Apr 19 14:57:34 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory status
Apr 19 14:57:36 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 19 14:57:39 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 19 14:57:44 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstart
Apr 19 14:57:46 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstart &

When looking further back at the messages log, I see there was a similar instance last night when I saw the app drop connectivity (which I don't recall was with me doing anything in terms of config), but there is a large gap of time in the logs:

Code:

Apr 18 18:50:28 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 18 18:50:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstop
Apr 18 18:50:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstop
Apr 18 18:50:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstop
Apr 18 18:50:33 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory forcestop
Apr 18 18:50:49 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstop &
Apr 18 18:50:55 Eds-FS ActiveDirectory: /usr/sbin/service samba_server forcestop
Apr 18 18:50:55 Eds-FS ActiveDirectory: /usr/sbin/service ix-pre-samba start
Apr 18 18:50:58 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit forcestop
Apr 18 18:50:58 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 18 19:47:28 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 18 19:47:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstart default EDS89.COM
Apr 18 19:47:31 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart
Apr 18 19:47:31 Eds-FS ActiveDirectory: /usr/sbin/service ix-ldap quietstart
Apr 18 19:47:32 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit quietstart
Apr 18 19:47:33 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit status
Apr 18 19:47:34 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 18 19:47:38 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory quietstart
Apr 18 19:47:41 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory status
Apr 18 19:47:43 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 18 19:47:45 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 18 19:47:50 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstart
Apr 18 19:47:52 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstart &

Any thoughts why there may have been an hour gap in the middle of this service start attempt? The DC would have been up at this point.

I am going to try and monitor to find the next occurrence that isn't caused by me changing anything, and see if I see the same.

Cheers
Eds

 

[Eds89]

Ok I don't suspect the above log entries are related, as my application has just reported an "unexpected network error, unable to read from disk" and saw none of the above entries.

It did seem to occur in line with this event in the log.smbd log though, although not sure it would have any relation to the problem and just a coincidence?

Code:

[2018/04/19 16:11:27.628849,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
[2018/04/19 16:11:27.628892,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded

I can't see anything in any of the other SAMBA 4 log files (perhaps I need to increase log level)?
Nothing in the messages log file from what I can see.

 

[Eds89]

Ok also unlikely to be this, as it has happened again;

• I can see nothing in the messages log file
• I can see nothing in the samba4 log files
• I can see no events within Windows
• I can see no events in the vmware log for either the freenas VM or the Windows VM
• I can so no events in the vmkernel logs for the vswitch they connect via

Anyone able to offer other suggestions of what I can do/where I can look to further diagnose?

 

[anodos]

Thanks for this!!

So I just enabled AD monitoring to resolve another issue I had, which obviously stopped and started the AD service (And by the looks of it, CIFS):

Code:

Apr 19 14:56:46 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 19 14:56:49 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstop
Apr 19 14:56:49 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstop
Apr 19 14:56:50 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstop
Apr 19 14:56:53 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory forcestop
Apr 19 14:57:00 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstop &
Apr 19 14:57:06 Eds-FS ActiveDirectory: /usr/sbin/service samba_server forcestop
Apr 19 14:57:07 Eds-FS ActiveDirectory: /usr/sbin/service ix-pre-samba start
Apr 19 14:57:10 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit forcestop
Apr 19 14:57:10 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 19 14:57:20 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 19 14:57:21 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstart default EDS89.COM
Apr 19 14:57:22 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart
Apr 19 14:57:23 Eds-FS ActiveDirectory: /usr/sbin/service ix-ldap quietstart
Apr 19 14:57:23 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit quietstart
Apr 19 14:57:25 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit status
Apr 19 14:57:26 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 19 14:57:31 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory quietstart
Apr 19 14:57:34 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory status
Apr 19 14:57:36 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 19 14:57:39 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 19 14:57:44 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstart
Apr 19 14:57:46 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstart &

When looking further back at the messages log, I see there was a similar instance last night when I saw the app drop connectivity (which I don't recall was with me doing anything in terms of config), but there is a large gap of time in the logs:

Code:

Apr 18 18:50:28 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 18 18:50:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstop
Apr 18 18:50:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstop
Apr 18 18:50:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstop
Apr 18 18:50:33 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory forcestop
Apr 18 18:50:49 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstop &
Apr 18 18:50:55 Eds-FS ActiveDirectory: /usr/sbin/service samba_server forcestop
Apr 18 18:50:55 Eds-FS ActiveDirectory: /usr/sbin/service ix-pre-samba start
Apr 18 18:50:58 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit forcestop
Apr 18 18:50:58 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 18 19:47:28 Eds-FS ActiveDirectory: /usr/sbin/service ix-hostname quietstart
Apr 18 19:47:30 Eds-FS ActiveDirectory: /usr/sbin/service ix-kerberos quietstart default EDS89.COM
Apr 18 19:47:31 Eds-FS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart
Apr 18 19:47:31 Eds-FS ActiveDirectory: /usr/sbin/service ix-ldap quietstart
Apr 18 19:47:32 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit quietstart
Apr 18 19:47:33 Eds-FS ActiveDirectory: /usr/sbin/service ix-kinit status
Apr 18 19:47:34 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 18 19:47:38 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory quietstart
Apr 18 19:47:41 Eds-FS ActiveDirectory: /usr/sbin/service ix-activedirectory status
Apr 18 19:47:43 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.stop cifs
Apr 18 19:47:45 Eds-FS ActiveDirectory: /usr/local/bin/python /usr/local/bin/midclt call notifier.start cifs
Apr 18 19:47:50 Eds-FS ActiveDirectory: /usr/sbin/service ix-pam quietstart
Apr 18 19:47:52 Eds-FS ActiveDirectory: /usr/sbin/service ix-cache quietstart &

Any thoughts why there may have been an hour gap in the middle of this service start attempt? The DC would have been up at this point.

I am going to try and monitor to find the next occurrence that isn't caused by me changing anything, and see if I see the same.

Cheers
Eds

You can get more information about what AD monitoring is doing by looking in /var/log/middlewared.log.

Try looking at your AD environment for errors. This python script might help. Copy it to your FreeNAS server and run from the CLI (python ad_verifier.py). It's very much a WIP.

https://github.com/anodos325/samba_scripts/blob/master/not_samba/ad_verifier.py

 

[Eds89]

I have looked at my domain controller and can't see anything especially alarming being reported.

I have now started a test in my app to save to an SMB shared on a physical box instead, and see if this suffers the same problem as my existing read/writes.
If not, it's something happening on the AIO box.
If it does, it's likely an issue within the Windows VM itself.

Thanks for this script.
Can you give a brief overview of what it does and if it needs any configuration for my specific domain etc.?

Cheers

 

[Eds89]

I have run yourscript, and it highlights two things;

• Time skew between DC and FreeNAS is 1min 22sec
• My virtual storage network IP is not resolvable in DNS

The skew, I have now set FreeNAS to use my DC as it's NTP server. Is there a way to force an NTP sync to get them back in line?

As for the storage network not being resolvable, this shouldn't matter as far as I am aware, as this is used purely by ESXi and FreeNAS, and is not externally accessible on the physical network, or even by any VM on ESXi.

Is it possible it's purely down to time skew? My app is now saving to a physical machine's SMB share with zero problems.

Cheers!

 

[Eds89]

I have corrected the 1 minute skew, but seems the issue still occurs.
Any other thoughts of what else I can look at?

Definitely something to do with either ESXi networking or FreeNAS SMB service as far as I can tell.

 

[Eds89]

I have some more logs which I hope may be helpful:

I found the app had failed in its read from this share again, so I connected to my FreeNAS box using the shared folders snap in in Windows MMC. I saw the connected time for the session from that server.
I worked back the time to determine when the connection dropped and reconnected, and found that timestamp in my smbd log:

Code:

[2018/04/26 09:42:20.976808,  2] ../source3/smbd/server.c:803(remove_child_pid)
  Could not find child 8713 -- ignoring
[2018/04/26 09:57:21.027449,  2] ../source3/smbd/server.c:803(remove_child_pid)
  Could not find child 19922 -- ignoring
[2018/04/26 10:12:21.086799,  2] ../source3/smbd/server.c:803(remove_child_pid)
  Could not find child 31882 -- ignoring
[2018/04/26 10:27:21.178655,  2] ../source3/smbd/server.c:803(remove_child_pid)
  Could not find child 42961 -- ignoring
[2018/04/26 10:36:34.373737,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Downloads]"
[2018/04/26 10:36:34.374211,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Films]"
[2018/04/26 10:36:34.374681,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Games]"
[2018/04/26 10:36:34.375142,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Music]"
[2018/04/26 10:36:34.375627,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Photos]"
[2018/04/26 10:36:34.376113,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Software]"
[2018/04/26 10:36:34.379076,  2] ../source3/smbd/service.c:1120(close_cnum)
  10.0.0.17 (ipv4:10.0.0.17:57390) closed connection to service Downloads
[2018/04/26 10:36:35.333463,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Downloads]"
[2018/04/26 10:36:35.333955,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Films]"
[2018/04/26 10:36:35.334407,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Games]"
[2018/04/26 10:36:35.334877,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Music]"
[2018/04/26 10:36:35.335337,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Photos]"
[2018/04/26 10:36:35.335796,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Software]"
[2018/04/26 10:36:35.363888,  2] ../source3/smbd/service.c:841(make_connection_snum)
  10.0.0.17 (ipv4:10.0.0.17:61331) connect to service Downloads initially as user EDS\eds (uid=21105, gid=20513) (pid 49467)
[2018/04/26 10:42:21.226643,  2] ../source3/smbd/server.c:803(remove_child_pid)
  Could not find child 54127 -- ignoring
[2018/04/26 10:57:21.285166,  2] ../source3/smbd/server.c:803(remove_child_pid)
  Could not find child 65337 -- ignoring

10:36 was around the time that MMC said the connection was started.
Do the "Processing section '[Downloads]'" messages have anything to do with the drop out? Or is that FreeNAS reporting that something is connecting to the share to query available shares?

Cheers
Eds

EDIT: Another ocurrence of the same from earlier in the day from a different VM:

Code:

[2018/04/26 02:27:19.102305,  2] ../source3/smbd/server.c:803(remove_child_pid)
  Could not find child 82181 -- ignoring
[2018/04/26 02:28:13.291181,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Downloads]"
[2018/04/26 02:28:13.291655,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Films]"
[2018/04/26 02:28:13.292116,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Games]"
[2018/04/26 02:28:13.292569,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Music]"
[2018/04/26 02:28:13.293025,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Photos]"
[2018/04/26 02:28:13.293479,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Software]"
[2018/04/26 02:28:13.296988,  2] ../source3/smbd/service.c:1120(close_cnum)
  10.0.0.18 (ipv4:10.0.0.18:60270) closed connection to service Films
[2018/04/26 02:28:13.352297,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Downloads]"
[2018/04/26 02:28:13.352800,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Films]"
[2018/04/26 02:28:13.353253,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Games]"
[2018/04/26 02:28:13.353718,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Music]"
[2018/04/26 02:28:13.354167,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Photos]"
[2018/04/26 02:28:13.354632,  2] ../source3/param/loadparm.c:2787(lp_do_section)
  Processing section "[Software]"
[2018/04/26 02:28:13.385787,  2] ../source3/smbd/service.c:841(make_connection_snum)
  10.0.0.18 (ipv4:10.0.0.18:56773) connect to service Films initially as user EDS\eds (uid=21105, gid=20513) (pid 82945)

 

[Eds89]

Anyone have any thoughts on what else I can look at, as I still face this issue :(

 

[wizwazwhyno]

Hello, Eds89. I had this same issue and I believe I've solved it. Here is what i did:

Under auxillary parameters at Services > Samba (config), added this directive:
smb2 leases = no

At Directory > Active Directory > Enable monitoring,
unchecked box

https://forums.freenas.org/index.ph...ad-on-freenas-11-0-rc3-1d8ee7925.54967/page-2

Hope this helps.

 

[Eds89]

Interesting!
Have you found that both changes need to be made, or if this is related specifically to one of the other?
Any clue on what the leases=no option does?

I do have Monitoring enabled on the AD options, because my domain controller is hosted on FreeNAS and is not available until FreeNAS has started. So for me, I would need to keep it ticked to avoid manual intervention on every FreeNAS boot.

Cheers

 

[Eds89]

I am retesting my issue here with the AD monitoring option etc. but also came across the release notes for the latest FreeNas release https://www.ixsystems.com/blog/library/freenas-11-1-u4/

It mentions some fixes for SMB shares becoming unavailable.
Will also be testing with this update as well to see if it helps.

 

[GertVanderstukken]

Hello,

I am on "FreeNAS-11.1-U5" and I have a simular situation.
I don't have AD monitoring on, but my SMB connections are broken after exactly 10 hours.

I guess it has to do with Kerberos tickets expiring (MaxServiceTicketAge), but I have to dig into it deeper to find out more.

I see this in my log.wb-DOMAIN:

[2018/07/01 14:43:45.464599, 1] ../source3/libads/ldap_utils.c:93(ads_do_search
_retry_internal)
Reducing LDAP page size from 1000 to 500 due to IO_TIMEOUT
[2018/07/01 17:32:40.408424, 1] ../source3/libads/ldap_utils.c:93(ads_do_search
_retry_internal)
Reducing LDAP page size from 500 to 250 due to IO_TIMEOUT
[2018/07/01 19:43:46.115188, 1] ../source3/libads/ldap_utils.c:93(ads_do_search
_retry_internal)
Reducing LDAP page size from 250 to 125 due to IO_TIMEOUT
[2018/07/01 22:56:24.545977, 0] ../source3/winbindd/winbindd.c:281(winbindd_sig
_term_handler)

Anybody experiencing this also?
I see this when performing a very long file copy (I am migrating towards freeNAS).
After "exactly" 10 hours I get: An unexpected network error occured...
I can then hit retry and it continues.

On my Domain Controller I see kerberos ticket requests at that time.

 

[Elliot Dierksen]

Is NTP working correctly? Anything kerberos related will get really annoyed if both systems are in fairly close synch on time.

 

[GertVanderstukken]

Yes, NTP is perfectly running fine.
No time difference.

I can reproduce and see the error everytime exactly after 10 hours (600 minutes).
I checked at least 5 times now (hoping it was OK after some changes were made).