On 3/2/20 9:53 AM, Nelson Bartley wrote:
I have fedora 31 cloud server installed on a local virtualbox. I have installed 389-ds
and the 389-cockpit admin module.
Using dscreate I created a local instance, and have successfully modified it with
I have not been able to get the cockpit component to work. Logging in to cockpit, via the
root account or my sudo account works, as soon as I click 389ds admin the cockpit window
comes up with "oops" "cockpit as experienced an unexpected error".
The admin shows I have an instance, it allows me to send server commands which appear to
It does not let me create new instances
It does not show any details under any tab (just blank page).
I'm wondering where to start looking to diagnose the problem. Obviously the web site
message wasn't helpful, the inspection console is just complaining about css. The
system error logs don't show anything out of the ordinary...
What exact version of cockpit & cockpit-389-ds is installed?
The only troubleshooting tool is the web console log (press 12). You
should get an expandable error and stacktrace in the log when the
console crashes. I am currently using the latest cockpit UI on F31, and
it works fine for me. But there must be something in the console log -
every "oops" message will log some type of stack trace.
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
389 Directory Server Development Team