likewise-open service does not start automatically

Bug #205111 reported by Chris Rowson
44
Affects Status Importance Assigned to Milestone
likewise-open (Ubuntu)
Fix Released
Medium
Thierry Carrez

Bug Description

Binary package hint: likewise-open

---UBUNTU RELEASE---

Ubuntu hardy (development branch)
Release: 8.04

---PACKAGE RELEASE---

likewise-open:
  Installed: 4.0.5-0ubuntu1
  Candidate: 4.0.5-0ubuntu1
  Version table:
 *** 4.0.5-0ubuntu1 0

---PROBLEM---

The problem manifests after installation as an error message complaining 'error' at each normal (local) login, and the inability to login using domain accounts.

Logging on as a local user and trying:

lwiinfo -n “DOMAIN\username”

generates the error ‘could not obtain winbind separator!’

---WORKAROUND---

Running the command 'sudo likewise-winbindd -start' seems to resolve the lwiinfo problem, and restarting xserver (ctrl,alt,backspace) allows domain logons to occur.

It looks like the likewise-open script is not set to start with the system. To fix the problem permanently, running sysv-rc-conf and turning the likewise-open service on for runlevels 2,3,4,5 (for example) seems to work.

Revision history for this message
Claus Frein (cfrein) wrote :

Same here. Did a "sudo update-rc.d likewise-open defaults" to create runlevel-links, which didn't exist before.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package likewise-open - 4.0.5-0ubuntu2

---------------
likewise-open (4.0.5-0ubuntu2) hardy; urgency=low

  * Added manpages from upstream
   - debian/likewise-open.manpages
   - debian/likewise-open-gui.manpages
  * merged changes from Nicolas Valcárcel <email address hidden>
   - Added support for KDE desktop (LP: #196778)
   - Removed unnecesary quilt support on debian/rules
  * debian/likewise-giu.xpm: changed to likewise logo from samba
  * debian/likewise-open.init: greatly simplified init script (LP: #205111)
   - merged status patch from Dustin Kirkland <email address hidden>
  * debian/likewise-open-gui.desktop: changed category to System;Settings
    (LP: #211833)
  * debian/patches/fix_window_close: from Soren Hanson <email address hidden>
    -fixes gtk close bug (LP: #211844)

 -- Rick Clark <email address hidden> Mon, 07 Apr 2008 18:17:15 -0400

Changed in likewise-open:
status: New → Fix Released
Revision history for this message
erik (erik-niload) wrote :

After a fresh install of 8.04 release, using synaptic to install likewise-open 4.0.5-0ubuntu3, I also did not have the runlevel scripts and the service did not start. cfrein's fix worked for me. I can verify this on another lean install tomorrow.

erik (erik-niload)
Changed in likewise-open:
status: Fix Released → Confirmed
Changed in likewise-open:
importance: Undecided → Medium
status: Confirmed → Fix Released
Revision history for this message
Larry (larry-salibra) wrote :

This same problem happens to me on a fresh install of 8.04 release as well. It is misleading because domain login will work after joining the domain with the likewise open gui but then fails after system reboot. I assume this is because the gui starts winbindd but on reboot winbind does not start.

Revision history for this message
Skids (rpalmer-sominet) wrote :

"This bug was fixed in the package likewise-open - 4.0.5-0ubuntu2"

Obviously it wasn't because the problem is still there and using:

sudo update-rc.d likewise-open defaults

and

sudo /etc/init.d/likewise-open start

does not fix the problem. Likewise will work for that session but once a reboot is done you cannot login and get the phantom Error box.

Revision history for this message
Neil Mclean (nwmclean) wrote :

I found that I can execute:
sudo update-rc.d likewise-open defaults

and the appropriate links are placed:
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc2.d/S20likewise-open -> ../init.d/likewise-open
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc3.d/S20likewise-open -> ../init.d/likewise-open
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc4.d/S20likewise-open -> ../init.d/likewise-open
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc5.d/S20likewise-open -> ../init.d/likewise-open

and if I restart then likewise-winbindd will start at system start.

If I then log in as a user at GDM, and execute the GUI to connect to a domain, successful. Later disconnect from the domain. Then check - the above links have been removed. This will mean on the next restart likewise-winbindd will not auto start at system startup.

Something, some part of the process of connecting and disconnecting from a domain deletes the links needed for autostart with system.

Cheers

Revision history for this message
Neil Mclean (nwmclean) wrote :

The problem is not yet fixed.

Revision history for this message
Mark Duncan (eattheapple) wrote :

Changed to Incomplete because as others have pointed out, it is indeed not fixed. I am also experiencing this.

Changed in likewise-open:
status: Fix Released → Incomplete
Revision history for this message
Rick Clark (dendrobates) wrote :

The postinst looks correct and most people are not having this issue.

Please see:
/var/lib/dpkg/info/likewise-open.postinst

Please purge the likewise-open package with the following command:
sudo apt-get purge likewise-open

Then reinstall and paste the output. The only way this should be happening is if the postinst is not running.

Revision history for this message
Neil Mclean (nwmclean) wrote :

I purged and reinstalled likewise-open as per above note. Sorry I did not capture any output from that. Post install did run and as I posted above - the appropriate links are placed:
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc2.d/S20likewise-open -> ../init.d/likewise-open
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc3.d/S20likewise-open -> ../init.d/likewise-open
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc4.d/S20likewise-open -> ../init.d/likewise-open
lrwxrwxrwx 1 root root 23 2008-05-09 22:30 /etc/rc5.d/S20likewise-open -> ../init.d/likewise-open

This will result in likewise-winbindd starting at system startup. So installation is not a problem. It is after first trying the system, to log in and log out, of a domain that the startup links are subsequently removed.

So... as per my last note.... the above startup links are REMOVED after:
- successful install of likewise-open
- logging in a a local user
- running the likewise-open-gui to perform a successful connection to the domain
- using likewise-open-gui to disconnect from the domain

I also notice that at the time of a successful connect to a domain a lot of odd things happens at my gnome desktop:
- the desktop loses all icons and panels. just selected wallpaper is present
- after a moment the desktop icons all return but things like conky, nm-applet need to be manually restarted
- if pidgin is running but minimised to the notification area - after the desktop revives pidgin is no longer minimised and also a folder of my home directory opens on the desktop of its own accord.

(the above is also repeated when I use the gui to disconnect from the domain)

Adding some more - I notice that when I initiate a connection to a domain my syslog gets flooded with the following messages:
console-kit-daemon[5583]: WARNING: Could not acquire name; will retry.
console-kit-daemon[5583]: WARNING: Failed to acquire org.freeedsktop.ConsoleKit

The above messages begin with a connection to a domain initiated as above with the gui. They do NOT stop when I disconnect from the domain. After disconnecting from the domain I can use my desktop and applications but initiating a log-out of the desktop account, or attempting to shutdown the PC, will result in a hang.

I can CTRL-ALT-F1 to a command prompt and restart the gdm but my system is still not stable and I need to reboot.

Also look at this bug report:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/231180

Cheers

Revision history for this message
Neil Mclean (nwmclean) wrote :

- note all my above comments refer to this situation
a. boot up ubuntu 8.04
b. log in as a local user
c. at the desktop can see likewise-winbindd did start up at system start if I pull up a terminal and "sudo /etc/init.d/likewise-open status"
d. then use the likewise-open-gui to join my PC to a domain

Weird things happen on my desktop (see above). syslog (daemon log) is flooded with warnings (see above).
========

I did some further testing:
a. boot up ubuntu 8.04
b. log in as local user
c. at the desktop can see likewise-winbindd did start up at system start if I pull up a terminal and "sudo /etc/init.d/likewise-open status"
d. then open a terminal window and use the likewise-open-cli to join my PC to a domain

Same weird things happen on my desktop
========

Now maybe so far my problem is a user problem - not knowing how to use likewise-open properly. Because in all the above scenarios I had never been able to log in to the domain from the ubuntu gui (gdm) screen. Always failed. All I knew was that likewise-winbindd was running and thought that was all was needed.

I did some further reading and testing:
a. boot up ubuntu 8.04
b. at the gdm GUI login screen I CTRL-ALT-F1 to a cli session.
c. in that cli session I initiated a likewise-open-cli domain join. Enter user password - SUCCESS
d. then CTRL-ALT-F7 back to the gdm login screen and log in with <email address hidden> and get a successful domain user log on.

Here I notice:
- I have a new desktop as if a first time user. My "home" directory is /home/DOMAIN/user (not /home/user)
- Everything works nicely. I see all the domain servers and PC's in Places>Network
- No problem with the logfile getting flooded with warning messages.
- When I log out no hangs or problems.

Wooohoo!!! Sooooo Sweet! Very slick. Very nice.

So I am wondering now if the problems I have in the first scenario (logged in as local user - using likewise-open CLI or GUI commands to then join domain) - is because I am doing the wrong thing?

Should I be able to do this? Or am I using likewise-open incorrectly if I do that?

In summary:
Likewise-open only works properly for me when (as well as having likewise-winbindd daemon running) I first drop to a command prompt and join to the domain BEFORE I log in at the gdm GUI....

(and perhaps that is how its supposed to work??)

Revision history for this message
BrianDrab (briand-kaplantrucking) wrote :

Exactly the same issue here. Fresh install of Hardy on a Dell Laptop with Likewise installed. Great job on figuring out a workaround Neil!! I too wonder if we are doing something wrong.

Revision history for this message
BrianDrab (briand-kaplantrucking) wrote :
Revision history for this message
Neil Mclean (nwmclean) wrote :

Hi Brian,

Yes I was aware of the need to edit /etc/nsswitch.conf and have been using a corrected version of that file in all the examples above.

So there are two queries I have:
1. Do we really need (is this the correct and expected process) to:
- stop at the login screen,
- CTRL-ALT-F1 to a terminal,
- start likewise-winbindd (if it is not running),
- initiate a domain-join at the CLI
- CTRL-ALT-F7 back to the GDM login prompt
- log in using this format "username@domain"

2. If I create the links in /etc/rc2.d (and other runlevels) so that likewise-winbindd will autostart, these links get deleted every time I leave a domain. This results in likewise-winbindd not starting automatically next reboot.

Revision history for this message
Evan (ev) wrote :

Marking as confirmed not because I can reproduce the bug myself, but because multiple users have reported that the bug persists despite the fix in the archive and there doesn't appear to be a request for additional information to warrant an incomplete status.

Changed in likewise-open:
status: Incomplete → Confirmed
Revision history for this message
Andrew Keyes (akeyes) wrote :

Having the same problem, going to try the work around.

Revision history for this message
Rick Clark (dendrobates) wrote :

There were two problems that resulted in this happening, one was in the packaging the other was in the source.

The packaging issue was fixed. I am working on a patch to fix the other issue.

Revision history for this message
Thierry Carrez (ttx) wrote :

This has been fixed in latest upstream sources, so this bug should be fixed in intrepid whenever bug 244968 is.
Note sure how easy/disruptive it would be to backport though.

Thierry Carrez (ttx)
Changed in likewise-open:
assignee: nobody → tcarrez
status: Confirmed → In Progress
Revision history for this message
Neil Mclean (nwmclean) wrote :

In the top summary there is a workaround described. This part is not correct:
"It looks like the likewise-open script is not set to start with the system. To fix the problem permanently, running sysv-rc-conf and turning the likewise-open service on for runlevels 2,3,4,5 (for example) seems to work."

Seems no matter which method is used to turn the service on for various runlevels. When you "leave" a domain, the start scripts are removed. Service will not be started at next system startup.

Workaround.. either:
- remember to check if likewise service is running, and start it if needed, before attempting to join a domain or....
- create an entry in the ubuntu "sessions" application to start the service at each reboot and forget about run scripts.

Cheers

Revision history for this message
Thierry Carrez (ttx) wrote :

This bug was fixed in the package likewise-open - 4.1.0.2956-0ubuntu1

---------------
likewise-open (4.1.0.2956-0ubuntu1) intrepid; urgency=low

  * missing-likewise-logo.diff: removed
  * fixed copyright notice
  * updated Standards-Version to 3.8.0
  * removed path from command in prerm
  * removed stop in S runlevel

 -- Rick Clark <email address hidden> Wed, 27 Aug 2008 08:56:20 -0500

likewise-open (4.1.0.2956-0ubuntu1~ppa2) intrepid; urgency=low

  * Remove libwbclient.so.0, use libwbclient0 package instead (LP: #254434)
  * Remove library links under /usr/lib/likewise-open

 -- Thierry Carrez <email address hidden> Tue, 05 Aug 2008 15:34:18 +0200

likewise-open (4.1.0.2956-0ubuntu1~ppa1) intrepid; urgency=low

  * New upstream version. (LP: #244968)
  * Removed fix_window_close patch (was merged upstream)
  * Fixed dh_perl call so that it looks into /usr/lib/likewise-open
  * Removed perl dep from likewise-open-gui since it is now pulled from
    likewise-open perl-Depends
  * Removed superfluous /etc/defaults empty directory creation
  * More descriptive desktop entries (LP: #253032)
  * Changed desktop entry logo to domainjoin-logo.png for consistency
  * likewise-open.prerm: leave domain before uninstall (LP: #230466)
  * missing-likewise-logo.diff: fix missing logo regression in domainjoin-gui
  * no-template-modifications.diff: disable template homedir|shell
    modifications and respect whatever was put in lwiauthd.conf
  * Changed Maintainer to reflect main inclusion

 -- Thierry Carrez <email address hidden> Fri, 01 Aug 2008 15:55:43 +0200

Changed in likewise-open:
status: In Progress → Fix Released
Revision history for this message
GideonRomm (gideon) wrote :

I downloaded the source from intrepid and compiled on hardy. The resulting deb installs fine, when combined with installing intrepid's version of libpam-runtime.

So far, so good.

I am attaching the deb, in case anyone else wants to try them or needs them.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.