On Mon, Feb 1, 2010 at 2:10 PM, Rich Megginson <rmeggins at redhat.com> wrote: > Sean Carolan wrote: >>> That's right... it opens a console, and starts writing to console.log. >>> Do the thing that makes it hang, and then take a look at that log file. >>> >> >> Ok, I'm going to do a "yum update" first because this system was >> installed back when it was still called Fedora Directory Project. I >> figure I might as well get to the current version before bugging you >> guys further... >> > It shouldn't hang at any rate - before you upgrade, you might try > fedora-idm-console -D 9 -f console.log > then run the console and reproduce the problem >> -- >> 389 users mailing list >> 389-users at lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/389-users >> > > -- > 389 users mailing list > 389-users at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/389-users > Some parts of the tool contact the http part 80|8080 of the directory server. Some parts talk to the ldap component 389. You should verify your TCP connectivity to 389, that could look like a 'hang' to the end user app.
