package likewise-open 5.4.0.42111-2ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Also affects x86_64. I think the following log line describes the problem:

Jul 27 14:06:57 lyled-desktop kernel: [18248.025734] lsassd[6511] general protection ip:7ff06b6142f8 sp:7fff0f7fd850 error:0 in liblwbase_nothr.so.0.0.0[7ff06b5bd000+7c000]

I also get that error on a fresh install of 5.4.0.42111-2ubuntu1.1, but after downgrading to 5.4.0.42111-2ubuntu1 it starts working again.

For now I have downgraded to 2ubuntu1 and forbidden 2ubuntu1.1

Same here, authenthication daemon dies in very ugly manner.

kernel: [ 1180.682202] lsassd[5046] general protection ip:7fba40c782f8 sp:7fffaae04ca0 error:0 in liblwbase_nothr.so.0.0.0[7fba40c21000+7c000]

Hello,

I have exactly the same problem after upgrading, on a AMD 64 computer. I've applied a recommended workaround found on #543963 bug report:
  $ killall lwsmd lwregd dcerpcd netlogond eventlogd lwiod lsassd

killall -9 if you have to. We're going to reset state anyways.

  $ /bin/rm -rf /var/lib/likewise-open
  $ mkdir -p /var/lib/likewise-open/{db,rpc,run}
  $ chmod 700 /var/lib/likewise-open/db

Now start lwsmd:
  $ /etc/init.d/lwsmd start

Import settings
  $ for file in /etc/likewise-open/*.reg; do lwregshell import $file; done

Reload lwsmd
   $ /etc/init.d/lwsmd reload

Start lsassd
  $ lwsm start lsass

After doing that, lsassd starts and I can re-join the domain. After rejoining (without rebooting) I can open a session using a domain user on a console environment. But... If I try to close the actual session (opened with a non-domain user) or if I try to reboot, lsass fails again... and domain authentication is not possible.
The general protection error appears again on logs.

New ideas?

this is giving me issues as well. i didn't even install it in the last 18 hours. i installed it a week ago (monday 2010/07/19). This morning I installed Skype via synaptic, and this error started coming up.

This is also 64bit (intel, though - not amd).

The errors (in "changes applied" dialogue of synaptic) start with this line:
Error: LW_ERROR_SERVICE_UNRESPONSIVE (41203)

Fix for pointer reference in cleanup code. Will be present in the ppa:likewise-open/ppa within 2 hours according to the build schedule.

Fix is in place. likewise-open-5.4.0.42111-2ubuntu1.2 published in ppa:likewise-open/ppa. Please confirm the upgrade fix and I will file an SRU request.

Hello everyone,

After updating to likewise-open-5.4.0.42111-2ubuntu1.2 the problem is solved, everything works fine!

Best regards

Hello!

I conform, this has fixed my issue, service is alive and allows me to logon.

Regards
Jakub

Hello,
Observed exactly the described bug here, x68_64 (10.04). After installing version from ppa:likewise-open/ppa everything was ok and corrected (domain login working properly).

Thanks Gerald

This issue is specific to version 5.4.0.42111-2ubuntu1.1

Version 5.4.0.42111-2ubuntu1 still lives in the main repository and seems to work just fine however probably not recommended as .1 was a security update. Downgrading worked for me.

Just got done installing version 5.4.0.42111-2ubuntu1.2 from the ppa and it's working great for me as well.

Thanks Gerald!

SRU request filed (subscribed ubuntu-sru) and pinged a few other ppl trying to push the update forward.

Am i the only one that is still experiencing the same errors, even with the package from the likewise PPA? I've also tried removing the package likewise-open and re-installing it instead of upgrading, but still the same result.

This bug was fixed in the package likewise-open - 5.4.0.42111-2ubuntu1.2

---------------
likewise-open (5.4.0.42111-2ubuntu1.2) lucid-security; urgency=low

  * Fix lsassd crash due to invalid hDirectory handle (LP: #610300).
 -- Gerald Carter <email address hidden> Tue, 27 Jul 2010 17:35:01 -0500

Denny, Can you provide me some more details? It is possible that you are not seeing this exact same bug and therefore the fix did n't help you. But the fix is definitely right for the original bug.

Gerald, sure, what kind of information do you need? I'll try and reinstall it tomorrow. What i do know is that i got the same error message: failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Denny, Please open a new bug specifically for your scenario since my guess is that it is slightly different even though has the same symptom. Please include a cut-n-paste of the error reported from "apt-get install likewise-open" and the output of "ps axf" after the "apt-get". Thanks

Hello Gerald, I'm pretty sure it was exactly the same, but here's something weird... I did a complete removal again in synaptic and then re-installed it just to reproduce the errors. Now however I saw lots of 'merging' messages concerning registry keys (HKEY_THIS_MACHINE) that I did not see the last time I installed. Now I did not get any error messages however, the installation was succesful. After the installation I performed domainjoin-cli again and successfully logged onto the domain.

I can confirm the issues Denny was seeing. Doing an apt-get install likewise-open pulled in version 5.4.0.42111-2ubuntu1.2 but I still had the following error:
Setting up likewise-open (5.4.0.42111-2ubuntu1.2) ...
Stopping service reverse dependency: npfs
Stopping service reverse dependency: rdr
Stopping service reverse dependency: lwio
Stopping service reverse dependency: netlogon
Stopping service: lwreg
 * Stopping Likewise Service Manager: lwsmd [ OK ]
 * Starting Likewise Service Manager: lwsmd [ OK ]
Starting service: lwreg
 * Reloading Likewise Service Manager configuration [ OK ]
Starting service dependency: netlogon
Starting service dependency: lwio
Starting service dependency: rdr
Starting service dependency: npfs
Starting service: lsass
dpkg: error processing likewise-open (--configure):
 subprocess installed post-installation script returned error exit status 1

Dmesg contained the following line:
[1383286.018978] lwiod[6433]: segfault at 434950 ip 00434950 sp b66705ec error 4 in liblwmsg_nothr.so.0.0.0 (deleted)[441000+11000]

I had the same results each time I tried apt-get remove ; apt-get install on likewise-open until running dpkg --purge likewise-open ; apt-get install likewise-open which rebuilt the registry entries and everything works now.

@Tobin: same thing happened to me again when I removed the PPA. Then the packagemanager thinks he has to upgrade likewise-open to the same version again (why? it's the same version...) and gives the same error messages again. Fixed when I did dpkg --purge likewise-open ; apt-get install likewise-open again.