Closing that outdated report as EOL has been reached long time ago
** Changed in: likewise-open5 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/510683
likewise-open (5.4.0.42111-2) lucid; urgency=low
* LP BUG #509934, #510683 - Don't fail to load the lsassd
ad-provider when we fail to add a domain to the trust list
* LP BUG #543730 - Add likewise-open5-gui transition package
* Fix the likewise-open-gui Gnome Administration menu item
Fixed (again) in 5.4.0.42111-2~ppa4~lucid
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
new version just installed broke what was working... back to having to
restart lsassd. Attached is info from apt-cache showpkg likewise-open
** Attachment added: Output of apt-cache showpkg likewise-open
http://launchpadlibrarian.net/43381491/apt-cache%20showpkg%20likewise-open.txt
--
Gahhsorry. the patch is there but got removed from the series file
somehow
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'll get a new upload to the PPA tomorrow.
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I added the ppa to my system, ran apt-get update apt-get upgrade and
the packages from there was installed. After rebooting I was able to
immediately login with my domain creds. Will this fix be in the regular
repo soon? Thanks for the help!
--
'lsassd' has to be restarted in order to login
Thanks Gene. I'll request start the upload request process today.
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks! Will you post back once it is all finished so that I know I can
remove the extra repo?
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I think that this is an issue with the lsassd active-directory-provider
failing to load due to trusted domain detection failures. Please test
the 5.4.0.42111-2~ppa~lucid packages at https://launchpad.net/~likewise-
open/+archive/likewise-open-ppa
Thanks.
** Changed in: likewise-open (Ubuntu)
I just installed Lucid amd64 beta from CD and ran all updates. I am
having the same issue where I have to restart lsassd to be able to log
in post reboot.
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are
Gerald, upstart scripts would certainly at least help isolate the issue.
And they'd remove another issue I have, with updates failing because
they can't stop daemons that aren't running.
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this
It appears that this bug and the password caching issue reported in LP BUG
#509934 are an issue
with the lsassd AD provider not loading in the abscence of a network
connection. For the record, I
repro no such failure which is odd given several confirming reports.
I've tried reproducing the
** Tags added: likewise lucid upstart
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
For your #5 above, this is what I have in a shell script to rectify your
situation:
(thanks with help from the Likewise forum people)
if [ -f /etc/likewise-open/lsassd.reg ] [ $(grep -c
'HomeDirTemplate=%H/%D/%U' /etc/likewise-open/lsassd.reg) -lt 3 ]; then
# Hardy sed -i 's,;umask =
Bryan, I'll try to get a repro. I've not seen the startup issue in my
testing as of yet (with the likewise-open_5.4.0.42111-1 deb)
** Changed in: likewise-open (Ubuntu)
Assignee: (unassigned) = Gerald Carter (coffeedude.jerry)
--
'lsassd' has to be restarted in order to login
Bryan, I'll agree that likewise needs upstart scripts. But I cannot
reproduce the failure you describe. I installed Lucid Neta 1 from CD
and then installed the likewise-open 5.4.0.42111-1 deb from main, joined
a domain, rebooted, and logged back in with no issues. Is this
environmental
Gerald, just thought of something and will test once I get in the
office. We are using CISCO switches that have portfast on them and so
do many production environments. This slows the time that the link will
become enabled with protocol up and intern slows the DHCP process. Have
you tested this
I would agree with you Pete, I work at Arizona State University and
there is a ton of Cisco stuff setup, so I think you are onto something.
:-)
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
You received this bug notification because you are a member of
I also setup an Ubuntu 9.10 server at my PT job and am having the same
exact problem, and we are running some Cisco stuff and Dell Powerconnect
3024's. I am using Server 2003 Enterprise and its' DHCP server.
--
'lsassd' has to be restarted in order to login
https://bugs.launchpad.net/bugs/510683
ok. I don't have any Cisco switches handy. Any suggestions on a way to
simulate the delayed DHCP server response? Or should I just bite the
bullet and do the upstart scripts and see if that resolves it for you?
--
'lsassd' has to be restarted in order to login
What DHCP server do you have? If you're trying to repro in a VM
environment, I'd install dhcpd on the host, configure it for that
interface (disabling dnsmasq) and try setting:
delay_reply_dhcpoffer 3000
--
'lsassd' has to be restarted in order to login
Ok so disabling portfast makes it work, so it looks like the only real
solution would be to write upstart scripts. Side note why doesn't
likewise handle the reconnect once networking is started?
What happens for laptop users when not connected to the dc? In karmic
this works fine using cached
Here we need PortFast enabled otherwise, I believe the machine does
not come up with an IP address,then we have to manually, `sudo dhclient` to fix
that problem.
(that was true with HardyHeron)
Putting that aside, I have noticed that logging in with an active directory
account after a reboot,
After installing likewise on a fresh install of 10.04 (Lucid) Beta 1
(AMD64), lsassd appears to be running but a 'sudo netstat -lnp | grep
lsassd' shows it is not bound to any inet ports. This also causes issues
with joining and leaving domains, and likely most likewise related
tasks. Restarting
likewise needs upstart scripts.
For a workaround that is less manual on each startup (and could break
other services with only sysinit scripts),
change:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem and net-device-up IFACE=eth0 #or whatever is your main
interface
in
When I reboot the my Ubuntu 9.10 system, the accounts imported from MS AD are
not available for logging in.
lsassd service reports that it's running, however.
If I restart the service, MS AD accounts start working again.
This seems to happen consistently with every reboot and crash.
--
'lsassd'
Number 4. is:
My simple command line to restart 'lsassd' (/usr/bin/service lsassd
restart ) no longer works in /etc/rc.local, not sure if a bunch of
upstart stuff has been implemented in this release, that could cause
that.
--
'lsassd' has to be restarted in order to login
28 matches
Mail list logo
