kazaka
Contributor
Contributor

"Terminating on fatal IPC exception" after 5.1U1 update

Jump to solution

Hi,

after update ESXi from 5.1.0-799733 to 5.1.0.update01-1065491 there are alot of IPC exceptions logged in /var/run/log/syslog.log !

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

2013-06-28T08:44:13Z lsassd[5317]: 0x49ee0b90:Terminating on fatal IPC exception

Does anybody know something about it?

Is it critical? Can be fixed?

Regards,

Dimitar Kazakov

0 Kudos
1 Solution

Accepted Solutions
a_nut_in
Expert
Expert

Hi Dimitar,

Are you using AD/LDAP authentication for the hosts? If so, remove from AD, reboot, re-add to domain  and check?

Regards

a

Do remember to mark my post as "helpful" or "correct" if I've helped resolve or answer your query!

View solution in original post

0 Kudos
6 Replies
a_nut_in
Expert
Expert

Hi Dimitar,

Are you using AD/LDAP authentication for the hosts? If so, remove from AD, reboot, re-add to domain  and check?

Regards

a

Do remember to mark my post as "helpful" or "correct" if I've helped resolve or answer your query!

View solution in original post

0 Kudos
a_nut_in
Expert
Expert

/* Abort on any other exception */

  LSA_LOG_ERROR("Terminating on fatal IPC exception");

  kill(getpid(), SIGTERM);

   break;

  }

http://likewise-open.sourcearchive.com/documentation/5.4.0.39949-3/lsass_2server_2lsassd_2listener_8...

Do remember to mark my post as "helpful" or "correct" if I've helped resolve or answer your query!
0 Kudos
kazaka
Contributor
Contributor


Yes, I'm using AD authentication for it. Will try remove from AD, reboot, re-add to domain  this weekend, and will post result

0 Kudos
kazaka
Contributor
Contributor

Leaving AD stopped IPC exceptions syslog messages imedatelly. Even didn't need to reboot ESXi. Just rejoin AD again, and everything is OK now. No more IPC exception messages in syslog.

Thanks!

0 Kudos
Iwan_Rahabok
Expert
Expert

Thank you. Solved my problem too! I'm using ESXi 5.5.

e1
0 Kudos
bstrang
Contributor
Contributor

Similar issue after upgrading our vSphere 5.0 hosts to 5.5.....here is the summary of our issue and resolution:

Subject:  problem with using AD credentials on ESXi hosts after upgrade to 5.5 Issue with vSphere Hosts joined to Active Directory:

vSphere 5.0 servers were joined to the domains.

Upgraded from vsphere 5.0 to 5.5 in place with update manager.

Started seeing errors in syslog: (and in turn overloading SIEM server with these errors)

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

2014-03-12T14:41:38Z lsassd[33863]: 0x2882db70:Terminating on fatal IPC exception

Removed ESXi Hosts from AD and rejoined domains.

Errors stopped, but found out unable to log into hosts with ad credentials.

From PowerCLI saw this status for DomainMembershipStatus: "OtherProblem"

Ran ESXTOP to find lsassd processes, and killed the Worlds for those processes

(there seems to be 2 of them for all of our hosts – could be due to the in place upgrade, and removing and rejoining to AD)

Created directory on ESXi Hosts for Likewise agents "mkdir /var/lock/subsys"

Restarted the Likewise agents "/etc/init.d/netlogond restart; /etc/init.d/lwiod restart; /etc/init.d/lsassd restart;"

After a few minutes DomainMembershipStatus changes to Ok and login works with AD credentials….

0 Kudos