Difference between revisions of "Issues"
From FreeNAS using Active Directory Wiki
m (→9.2.1.5: directory services goes bye bye after a reboot?) |
m (→9.2.1.5: found problem, easy fix) |
||
| Line 4: | Line 4: | ||
** Solution: Patch to fix issue is provided in the bug report. After patch is applied, turn off the CIFS service, then turn on Directory Services (which will automatically turn on the CIFS service). | ** Solution: Patch to fix issue is provided in the bug report. After patch is applied, turn off the CIFS service, then turn on Directory Services (which will automatically turn on the CIFS service). | ||
* Other known issues here | * Other known issues here | ||
| − | ** After a reboot, Directory Services stops working - need confirmation | + | ** After a reboot, Directory Services stops working - need confirmation. Resolved: actual issue was time skew. Both the AD & FreeNAS virtual machines in the test environment were powered down for multiple hours. The AD VM synced the time like it should have, the FreeNAS VM had the correct minutes, but the hour showed 11AM instead of 9PM (-10 hours, as set by my time zone). |
| + | **'''<u>This is a NON-ISSUE unless you run a virtualized environment, and power down both the host system and the guests for long periods of time.</u>''' | ||
| + | *** Fix: Enter FreeNAS console, and enter the following command: '''service ntpd stop && ntpdate 10.10.10.3 && service ntpd start''' - then Directory Services will start properly. | ||
| + | *** Fix was found on the FreeNAS forum, from moderator "survive", taken from [http://forums.freenas.org/index.php?threads/clock-sync.8276/#post-34636 THIS post] | ||
| + | [[File:Fixing time skew.png]] | ||
Revision as of 08:15, 29 April 2014
9.2.1.5
- Bug #4878
- Issue: CIFS is started, and can't be turned off, and Directory Services can't be turned on.
- Solution: Patch to fix issue is provided in the bug report. After patch is applied, turn off the CIFS service, then turn on Directory Services (which will automatically turn on the CIFS service).
- Other known issues here
- After a reboot, Directory Services stops working - need confirmation. Resolved: actual issue was time skew. Both the AD & FreeNAS virtual machines in the test environment were powered down for multiple hours. The AD VM synced the time like it should have, the FreeNAS VM had the correct minutes, but the hour showed 11AM instead of 9PM (-10 hours, as set by my time zone).
- This is a NON-ISSUE unless you run a virtualized environment, and power down both the host system and the guests for long periods of time.
- Fix: Enter FreeNAS console, and enter the following command: service ntpd stop && ntpdate 10.10.10.3 && service ntpd start - then Directory Services will start properly.
- Fix was found on the FreeNAS forum, from moderator "survive", taken from THIS post
