Bug 445622
Summary: | lokkit hangs kickstart installs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jonathan Steffan <jonathansteffan> |
Component: | system-config-securitylevel | Assignee: | Thomas Woerner <twoerner> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.1 | CC: | pknirsch, vanmeeuwen+fedora |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-29 11:41:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jonathan Steffan
2008-05-08 02:06:07 UTC
s/disabled'/disabled'\)/ --port=22 is not valid, testing --port=22:tcp now. --port=22:tcp also hangs. The resulting command is (read: the command that is hanging): lokkit --quiet --nostart -f --enabled --port=22:tcp --port=22:tcp Manually running this command seems to succeed, however the anaconda started lokkit command still hangs. Could you please attach the output of attaching a strace on the hanging lokkit command? How might I get strace into the active install? It seems busybox doesn't have it. Should I just scp a compatible binary? Oh right, that is a busybox environment. I do not know if it possible to get the strace from an installed system working with it. So, Jeroen van Meeuwen has ran into this issue before. The issue is setting: --enableldapauth --ldapserver=ldap.domain.tld --ldapbasedn=dc=domain,dc=tld --enablecache where the ldap.domain.tld is MS AD. Fun. Lokkit now runs as expected. Well, I had a similar issue where /etc/nsswitch.conf has "hosts: files dns ldap", network didn't come up properly, querying files and dns for "ldap01.domain.tld" failed accordingly and it fell back to ldap (which then again wanted ldap01.domain.tld), which resulted in timeouts and eventually segfaulted. While the catch-22 I encountered was caused by the network not coming up properly (hence no bug was logged), obviously one would want to see this particular issue fixed, as it's occurring during the installation and a perfectly viable use-case. This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". This looks to have been fixed is the 5.3 nss as I've been unable to reproduce it. Closing as CURRENTRELEASE as per comment #11. Please feel free to reopen in case the problem reappears. Thanks & regards, Phil |