VMware vSphere

 View Only
  • 1.  Service lsassd crashing, after trying to join domain

    Posted Mar 29, 2017 03:24 PM

    Hi all,

    I am having an issue while trying to join ESXi 5.5 to a domain.

    I was getting a plain "Join domain failed." error, so I enabled debug logging following this article: Enabling logging for Likewise agents on ESXi/ESX (1026554) | VMware KB

    Trying to join the domain again, lsassd service crashes and I'm seeing these errors in the /var/log/lsassd.log file;

    ==> /var/log/lsassd.log <==

    20170329140256:DEBUG:[LsaChangePermissions() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:262] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170329140256:DEBUG:0xffdd1540:[FakeClientConnection() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/sighandler.c:277] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170329140256:DEBUG:[LsaRemoveFile() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:62] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170329140256:VERBOSE:0xffdd1540:[lsassd_main() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:161] Lsa main cleaning up

    20170329140256:DEBUG:[LsaChangePermissions() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:262] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170329140256:DEBUG:0xffdd1540:[FakeClientConnection() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/sighandler.c:277] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170329140256:DEBUG:[LsaRemoveFile() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:62] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170329140256:INFO:[IPC] Shutting down server

    20170329140256:INFO:[IPC] Server shut down

    20170329140256:INFO:0xffdd1540:[lsassd_main() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:174] LSA Service exiting...

    I read multiple articles on the forum and the internet about AD join errors and troubleshooting, but I couldn't a solution.

    Any help is much appreciated.

    Many thanks.



  • 2.  RE: Service lsassd crashing, after trying to join domain

    Posted Mar 30, 2017 08:32 AM

    Attaching the full logs after an unsuccessful join in case they help.

    lsassd.log:

    20170330081545:VERBOSE:0xffed5540:[lsassd_main() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:117] Logging started

    20170330081545:INFO:0xffed5540:[LsaSrvVerifyNetLogonStatus() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:310] LsaSrvVerifyNetLogonStatus call to LWNet API returned 136

    20170330081545:DEBUG:0xffed5540:[LsaSrvVerifyNetLogonStatus() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:311] Error code: 136 (symbol: ERROR_NOT_JOINED)

    20170330081545:INFO:0xffed5540:[LsaSrvStartupPreCheck() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:243] LSA Process start up check for NetLogon complete

    20170330081545:INFO:0xffed5540:[LsaSrvVerifyLwIoStatus() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:345] LsaSrvVerifyLwIoStatus call to LwIo API returned 0

    20170330081545:INFO:0xffed5540:[LsaSrvVerifyLwIoStatus() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:351] LsaSrvVerifyLwIoStatus call to LwIo API returned 0

    20170330081545:INFO:0xffed5540:[LsaSrvStartupPreCheck() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:268] LSA Process start up check for LwIo complete

    20170330081545:DEBUG:0xffed5540:[LsaSrvInitAuthProvider() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/api/auth_provider.c:178] Provider lsa-activedirectory-provider loaded from static list

    20170330081545:DEBUG:0xffed5540:[InitADCacheFunctionTable() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/auth-providers/ad-provider/provider-main.c:4672] Unknown cache backend. Switching to default

    20170330081545:DEBUG:0xffed5540:[LsaInitializeProvider_ad() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/auth-providers/ad-provider/provider-main.c:243] Error code: 16406 (symbol: (null))

    20170330081545:DEBUG:0xffed5540:[LsaSrvInitAuthProvider() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/api/auth_provider.c:246] Error code: 16406 (symbol: (null))

    20170330081545:ERROR:0xffed5540:[LsaSrvInitAuthProviders() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/api/auth_provider.c:294] Failed to load provider [<null>] at [/lib/liblsass_auth_provider_ad.so] [error code:16406]

    20170330081545:INFO:[IPC] Starting server

    20170330081545:INFO:[IPC] Listening on endpoint /etc/likewise/.lsasd

    20170330081545:INFO:[IPC] Server started

    20170330082429:WARNING:0xffed5540:[LsaSrvHandleSignals() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/sighandler.c:183] Received signal [15]

    20170330082429:DEBUG:[LsaChangePermissions() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:262] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170330082429:DEBUG:0xffed5540:[FakeClientConnection() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/sighandler.c:277] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170330082429:DEBUG:[LsaRemoveFile() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:62] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170330082429:VERBOSE:0xffed5540:[lsassd_main() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:161] Lsa main cleaning up

    20170330082429:DEBUG:[LsaChangePermissions() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:262] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170330082429:DEBUG:0xffed5540:[FakeClientConnection() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/sighandler.c:277] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170330082429:DEBUG:[LsaRemoveFile() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/common/utils/fileutils.c:62] Error code: 2 (symbol: ERROR_FILE_NOT_FOUND)

    20170330082429:INFO:[IPC] Shutting down server

    20170330082429:INFO:[IPC] Server shut down

    20170330082429:INFO:0xffed5540:[lsassd_main() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/lsass/server/lsassd/libmain.c:174] LSA Service exiting...

    netlogond.log:

    20170330082430:0xffb36b70:INFO:[LWNetSrvGetDCTime() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/netlogon/server/api/dcinfo.c:434] Determining the current time for domain 'example.com'

    20170330082430:0xffb36b70:INFO:[LWNetSrvGetDCName() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/netlogon/server/api/dcinfo.c:97] Looking for a DC in domain 'example.com', site '<null>' with flags 10

    20170330082552:0xffb58b70:DEBUG:[LWNetSrvGetCurrentDomain() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/netlogon/server/api/lwnet-pstore.c:83] Error at /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/netlogon/server/api/lwnet-pstore.c:83 [code: 136]

    20170330082613:0xffb69b70:DEBUG:[LWNetSrvGetCurrentDomain() /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/netlogon/server/api/lwnet-pstore.c:83] Error at /build/mts/release/bora-2956592/likewise/esxi-esxi/src/linux/netlogon/server/api/lwnet-pstore.c:83 [code: 136]

    lwiod.log:

    20170330082429:VERBOSE:[IPC] (assoc:0x1f002b48) Dropping: Connection closed by peer

    20170330082430:TRACE:[IPC] (assoc:0x1f002510) => SMB_GET_LOG_INFO: <pointer> -> <SMB_REQUEST>

    {

      .dwCurTime = 1490862270

    }

    20170330082430:TRACE:[IPC] (assoc:0x1f002510) <= SMB_GET_LOG_INFO_SUCCESS: <pointer> -> <LWIO_LOG_INFO>

    {

      .maxAllowedLogLevel = 6

      .logTarget = 2

      .pszPath = <pointer> -> "/var/log/lwiod.log"

    }