package likewise-open 5.4.0.39949-3 failed to install/upgrade:

[David]

Binary package hint: likewise-open

Failed to install from an upgrade from Ubuntu 9.10

ProblemType: Package
Architecture: i386
Date: Thu Mar 4 09:08:53 2010
DistroRelease: Ubuntu 10.04
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: likewise-open 5.4.0.39949-3
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: likewise-open
Title: package likewise-open 5.4.0.39949-3 failed to install/upgrade:
Uname: Linux 2.6.31-19-generic i686

[Marc Galmard (mgalmard)]

Same error on Alpha 10.4 while uninstalling the likewise-open package.

[Scott Salley (ssalley)]

The tool to convert and preserve the configuration is crashing while processing the likewise-open5 configuration files.

Could someone attach the likewise-open5 configuration files? They are /etc/likewise-open5/*.conf before upgrading and /etc/likewise-open/5_0_upgrade/*.conf during the upgrade. [Note the path differences.]

[Gerald Carter (coffeedude.jerry)]

Scott Salley wrote:
> The tool to convert and preserve the configuration is crashing while
> processing the likewise-open5 configuration files.
>
> Could someone attach the likewise-open5 configuration files? They are
> /etc/likewise-open5/*.conf before upgrading and /etc/likewise-
> open/5_0_upgrade/*.conf during the upgrade. [Note the path differences.]
>

Scott, this should already be fixed. I have new packages
I'm working on.

[James Lancaster (james-lancaster)]

This is also affecting a new installation (no upgrading).

[Gerald Carter (coffeedude.jerry)]

This should be fixed in likewise-open_5.4.0.42111-1~ppa1~lucid from the likewise-open Developement PPA

[Paul Webster (pwebster)]

I got hung up when upgrading from 9.10 to 10.04. I was on my domain username when upgrading. Upgrade completed with a couple likewise errors. Now i can't authenticate with domain account (DOMAIN\username). Suggestions?

[Gerald Carter (coffeedude.jerry)]

Paul, without knowing what the upgrade errors where, I can't give much feedback. Also note that the original upgrade failure report was against the 5.4.0.39949-3 package during alpha2. At the least, I need to know what processes are running after the upgrade and what the upgrade error was.

[Paul Webster (pwebster)]

Thanks Jerry-
What info would be helpful?
I know that in my pre-upgrade state, I had changed the sudoers file so that my DOMAIN\username account was included as an admin in the sudoers file.

During the upgrade, it asked for the names of Kerberos servers on my domain. I am at home and not connected to my domain, so I left these blank. Even if I were at work and on the domain I have no idea what the kerberos servers would be. I'm on a completely windows-centric AD domain.

During the upgrade it also advised me that Winbind and Likewise were not compatible with each other and had to be disabled. Should I uninstall one or both of them?

Do I need to go in and change a config file of some sort?

Maybe it will just work if I return to my domain and login with my domain account. I will return tomorrow morning. I'd like to get it fixed before then but if I can't, I'll live. I think I can still get to my files in the /home folder for my domain user by using sudo and nautilus.

[Paul Webster (pwebster)]

Jerry-
A little more info. When I open the Likewise-Open GUI, it gives me the attached error message. I'll bet it is because I am not in the domain to contact the DNS server. I am at home, where I routinely work on this laptop (it goes to work and back every day). I only use the domain account, as it keeps file storage/organization simpler.

My intention in opening the Likewise Gui was just to see what domain it thought I was a member of.

See attached.

[Paul Webster (pwebster)]

Sorry-
I neglected to mention that I am running the AMD64 desktop edition.

[Paul Webster (pwebster)]

As a follow-up to this, I brought the machine in to work this morning, connected to wireless, on my local admin level account, opened the likewise gui and tried to "leave" the domain. Attached is a screenshot of the error I got. I was thinking that if I could leave then I could re-join and everything would be back to normal.

I am guessing that I have some essential files missing in the authentication process.

Thanks for your help.

[Paul Webster (pwebster)]

I figured out a way to work around my situation and it almost works now.
I did the following:
-While I was logged in as local admin on the machine and inside the domain, I used synaptic to remove Winbind
-I rebooted
-Then I used synaptic to completely remove likewise open
-Rebooted the machine
-Reinstalled likewise open and likewise open gui
-Re-Joined the domain
-Rebooted machine and checked my domain login credentials (they worked)

*Now, the only thing that appears to not be working is that I can't login with those same credentials when I am outside the network. I'll check the likewise admin manual to see if there is a new setting I need to change. I need to be able to login with network username and password all the time so that I don't have to user accounts and two home directories. Big pain.