|
On 10/07/2016 01:46 PM, ghiureai wrote:
Hi LIst,
I am seeing a segmentation fault (Error updating console.conf: ) r
when trying to build 389-ds admin console ,
see details : running setup-ds-admin.pl , my OS and packages
installed
Any clues , much appreciate.
Thank you
>>> setup-ds-admin.pl -ddd
+++check_and_add_entry: Entry not found
cn=Commands,cn=admin-serv-xxx cn=389 Administration Server,
cn=Server Group, cn=..., ou=....., o=NetscapeRoot error No such
object
+Entry cn=Commands,cn=admin-servxxxxxxxx, cn=389 Administration
Server, cn=Server Group, xxxxxxxxxxxxx, o=NetscapeRoot is added
+++updateLocalConf: writing Commands.objectclass: top
+++updateLocalConf: writing Commands.objectclass: nsResourceRef
+++check_and_add_entry: Entry not found
cn=sync-task-sie-data,cn=Commands,cn=xxxxxxxxxxxx, cn=389
Administration Server, cn=Server Group, cn=xxxxxxxxxxx,
ou=xxxxxxxxxxx, o=NetscapeRoot error No such object
+++check_and_add_entry: attepting to modify the entry
cn=sync-task-sie-data,cn=Commands,cn=xxxxxxxxxxxx, cn=389
Administration Server, cn=Server Group, xxxxxxxxxxxxx,
o=NetscapeRoot that does not exist
+++updateLocalConf: writing
Commands.sync-task-sie-data.changetype: modify
+++updateLocalConf: writing Commands.sync-task-sie-data.replace:
nsHelpRef
+++updateLocalConf: writing Commands.sync-task-sie-data.nshelpref:
/usr/share/dirsrv/manual/help/sync-task-sie-data.html
+++check_and_add_entry: Entry not found
cn=sync-task-sie-data,cn=Commands,cn=xxxxxxxxxxxx cn=389
Administration Server, cn=Server Group, xxxxxxxxxxxxxxxx,
o=NetscapeRoot error No such object
+Entry
cn=sync-task-sie-data,cn=Commands,cn=admin-serv-xxxxxxxxxxxxxx,
cn=Server Group, xxxxxxxxxx, o=NetscapeRoot is added
+++updateLocalConf: writing
Commands.sync-task-sie-data.objectclass: top
+++updateLocalConf: writing
Commands.sync-task-sie-data.objectclass: nstask
+++updateLocalConf: writing Commands.sync-task-sie-data.nshelpref:
/usr/share/dirsrv/manual/help/sync-task-sie-data.html
+++updateLocalConf: writing Commands.sync-task-sie-data.nsexecref:
runtime
+++check_and_add_entry: Entry not found
cn=change-sie-password,cn=Commands,cn=admin-serv-xxxxxxxxxxxxxxx
ou=xxxxxxxxxx, o=NetscapeRoot error No such object
+Entry
cn=change-sie-password,cn=Commands,xxxxxxxxxxxxxxxxxxxxxxxxx
o=NetscapeRoot is added
+++updateLocalConf: writing
Commands.change-sie-password.objectclass: top
+++updateLocalConf: writing
Commands.change-sie-password.objectclass: nstask
+++updateLocalConf: writing
Commands.change-sie-password.nsexecref: runtime
Updating adm.conf with information from configuration directory
server . . .
Updating the configuration for the httpd engine . . .
+Running /usr/lib64/dirsrv/cgi-bin/config op=set
configuration.nsSuiteSpotUser="ldap-d"
configuration.nsServerAddress="0.0.0.0" ...sh: line 1: 28656
Segmentation fault /usr/lib64/dirsrv/cgi-bin/config op=set
configuration.nsSuiteSpotUser="ldap-ds"
configuration.nsServerAddress="0.0.0.0" 2>&1
Error updating console.conf:
Could not update the httpd engine configuration.
Failed to create and configure the admin server
************************************************
The combination looks a little odd to me...
Your OS is rhel-6.x based upon the extension .el6. But the version
of 389-ds-base is 1.3.4.4. How did your get the version for el6?
Supported 389-ds-base for rhel-6 is 1.2.11.15-##.
Our latest 389-ds-base for el6 is 389-ds-base-1.2.11.15-75.el6_8.
There is an upstream release 1.3.4.4, but it was one year ago and
just for Fedoras...
http://www.port389.org/docs/389ds/releases/release-notes.html
my OS:
Linux 2.6.32-431.el6.x86_64 #1 SMP Thu Nov 21 13:35:52 CST 2013
x86_64 x86_64 x86_64 GNU/Linux
************************************************
rpm -qa | grep 389-*
389-admin-console-1.1.10-000.noarch
389-console-1.1.9-000.noarch
389-admin-1.1.42-000.x86_64
389-ds-base-1.3.4.4-000.x86_64
389-adminutil-1.1.22-000.x86_64
389-ds-console-1.2.12-000.noarch
*******************************************************
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
|
