Re: dirsrv hangs on starting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



pgb 205 wrote:
> we are running 
> FC26
> ds-389 1.3.6.6-2
> 
> This is actually when starting freeipa with ipact -d start
> I get
> ipactl -d status
> ipa: DEBUG: importing all plugin modules in ipaserver.plugins...
> ipa: DEBUG: importing plugin module ipaserver.plugins.aci
> ipa: DEBUG: importing plugin module ipaserver.plugins.automember
> ipa: DEBUG: importing plugin module ipaserver.plugins.automount
> ipa: DEBUG: importing plugin module ipaserver.plugins.baseldap
> ipa: DEBUG: ipaserver.plugins.baseldap is not a valid plugin module
> ipa: DEBUG: importing plugin module ipaserver.plugins.baseuser
> ipa: DEBUG: importing plugin module ipaserver.plugins.batch
> ipa: DEBUG: importing plugin module ipaserver.plugins.ca
> ipa: DEBUG: importing plugin module ipaserver.plugins.caacl
> ipa: DEBUG: importing plugin module ipaserver.plugins.cert
> ipa: DEBUG: importing plugin module ipaserver.plugins.certprofile
> ipa: DEBUG: importing plugin module ipaserver.plugins.config
> ipa: DEBUG: importing plugin module ipaserver.plugins.delegation
> ipa: DEBUG: importing plugin module ipaserver.plugins.dns
> ipa: DEBUG: importing plugin module ipaserver.plugins.dnsserver
> ipa: DEBUG: importing plugin module ipaserver.plugins.dogtag
> ipa: DEBUG: importing plugin module ipaserver.plugins.domainlevel
> ipa: DEBUG: importing plugin module ipaserver.plugins.group
> ipa: DEBUG: importing plugin module ipaserver.plugins.hbac
> ipa: DEBUG: ipaserver.plugins.hbac is not a valid plugin module
> ipa: DEBUG: importing plugin module ipaserver.plugins.hbacrule
> ipa: DEBUG: importing plugin module ipaserver.plugins.hbacsvc
> ipa: DEBUG: importing plugin module ipaserver.plugins.hbacsvcgroup
> ipa: DEBUG: importing plugin module ipaserver.plugins.hbactest
> ipa: DEBUG: importing plugin module ipaserver.plugins.host
> ipa: DEBUG: importing plugin module ipaserver.plugins.hostgroup
> ipa: DEBUG: importing plugin module ipaserver.plugins.idrange
> ipa: DEBUG: importing plugin module ipaserver.plugins.idviews
> ipa: DEBUG: importing plugin module ipaserver.plugins.local
> ipa: DEBUG: importing plugin module ipaserver.plugins.join
> ipa: DEBUG: importing plugin module ipaserver.plugins.krbtpolicy
> ipa: DEBUG: importing plugin module ipaserver.plugins.ldap2
> ipa: DEBUG: importing plugin module ipaserver.plugins.location
> ipa: DEBUG: importing plugin module ipaserver.plugins.migration
> ipa: DEBUG: importing plugin module ipaserver.plugins.misc
> ipa: DEBUG: importing plugin module ipaserver.plugins.netgroup
> ipa: DEBUG: importing plugin module ipaserver.plugins.otp
> ipa: DEBUG: ipaserver.plugins.otp is not a valid plugin module
> ipa: DEBUG: importing plugin module ipaserver.plugins.otpconfig
> ipa: DEBUG: importing plugin module ipaserver.plugins.otptoken
> ipa: DEBUG: importing plugin module ipaserver.plugins.passwd
> ipa: DEBUG: importing plugin module ipaserver.plugins.permission
> ipa: DEBUG: importing plugin module ipaserver.plugins.ping
> ipa: DEBUG: importing plugin module ipaserver.plugins.pkinit
> ipa: DEBUG: importing plugin module ipaserver.plugins.privilege
> ipa: DEBUG: importing plugin module ipaserver.plugins.pwpolicy
> ipa: DEBUG: Starting external process
> ipa: DEBUG: args=klist -V
> ipa: DEBUG: Process finished, return code=0
> ipa: DEBUG: stdout=Kerberos 5 version 1.15.1
> ipa: DEBUG: stderr=
> ipa: DEBUG: importing plugin module ipaserver.plugins.rabase
> ipa: DEBUG: ipaserver.plugins.rabase is not a valid plugin module
> ipa: DEBUG: importing plugin module ipaserver.plugins.radiusproxy
> ipa: DEBUG: importing plugin module ipaserver.plugins.realmdomains
> ipa: DEBUG: importing plugin module ipaserver.plugins.role
> ipa: DEBUG: importing plugin module ipaserver.plugins.schema
> ipa: DEBUG: importing plugin module ipaserver.plugins.selfservice
> ipa: DEBUG: importing plugin module ipaserver.plugins.selinuxusermap
> ipa: DEBUG: importing plugin module ipaserver.plugins.server
> ipa: DEBUG: importing plugin module ipaserver.plugins.serverrole
> ipa: DEBUG: importing plugin module ipaserver.plugins.serverroles
> ipa: DEBUG: importing plugin module ipaserver.plugins.service
> ipa: DEBUG: importing plugin module ipaserver.plugins.servicedelegation
> ipa: DEBUG: importing plugin module ipaserver.plugins.session
> ipa: DEBUG: importing plugin module ipaserver.plugins.stageuser
> ipa: DEBUG: importing plugin module ipaserver.plugins.sudo
> ipa: DEBUG: ipaserver.plugins.sudo is not a valid plugin module
> ipa: DEBUG: importing plugin module ipaserver.plugins.sudocmd
> ipa: DEBUG: importing plugin module ipaserver.plugins.sudocmdgroup
> ipa: DEBUG: importing plugin module ipaserver.plugins.sudorule
> ipa: DEBUG: importing plugin module ipaserver.plugins.topology
> ipa: DEBUG: importing plugin module ipaserver.plugins.trust
> ipa: DEBUG: importing plugin module ipaserver.plugins.user
> ipa: DEBUG: importing plugin module ipaserver.plugins.vault
> ipa: DEBUG: importing plugin module ipaserver.plugins.virtual
> ipa: DEBUG: ipaserver.plugins.virtual is not a valid plugin module
> ipa: DEBUG: importing plugin module ipaserver.plugins.xmlserver
> ipa: DEBUG: Starting external process
> ipa: DEBUG: args=/bin/systemctl is-active dirsrv@domain-local.service
> ipa: DEBUG: Process finished, return code=3
> ipa: DEBUG: stdout=activating
> ipa: DEBUG: stderr=
> ipa: DEBUG: Starting external process
> ipa: DEBUG: args=/bin/systemctl is-active dirsrv@domain-local.service
> ipa: DEBUG: Process finished, return code=3
> ipa: DEBUG: stdout=activating
> ipa: DEBUG: stderr=
> ipa: DEBUG: Starting external process
> ipa: DEBUG: args=/bin/systemctl is-active dirsrv@domain-local.service
> ipa: DEBUG: Process finished, return code=3
> ipa: DEBUG: stdout=activating
> ...
> 
> the last block keep repeating forever. 
> 
> My question is how do I increase debugging level to give me proper information.
> There are several troubleshooting levels here
> http://directory.fedoraproject.org/docs/389ds/FAQ/faq.html
> 
> but which one would be most appropriate in this situation?
> 
> Or something else I can/should take a look at?

For a hang you probably want to attach gdb and get a stack trace.

rob
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux