Re: dirsrv-admin: Failed to install a local copy of 389-admin-1.1.jar or one of its supporting files

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

 



That's the correct error, but it looks like slapd is being run by the ldap user:

ldap      5370  0.0  0.7 2670848 27996 ?       Sl   12:14   0:05 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-ldap-xxxx -i /var/run/dirsrv/slapd-ldap-xxxx.pid -w /var/run/dirsrv/slapd-ldap-xxxx.startpid

Permissions of the /usr/share/dirsrv/html/java/ directory are as follows:
-rw-r--r-- 1 root root   35001 Aug  8  2011 389-admin-1.1.8_en.jar
-rw-r--r-- 1 root root  181013 Aug  8  2011 389-admin-1.1.8.jar
lrwxrwxrwx 1 root root      22 Aug  1 17:15 389-admin-1.1_en.jar -> 389-admin-1.1.8_en.jar
lrwxrwxrwx 1 root root      19 Aug  1 17:15 389-admin-1.1.jar -> 389-admin-1.1.8.jar
lrwxrwxrwx 1 root root      22 Aug  1 17:15 389-admin_en.jar -> 389-admin-1.1.8_en.jar
lrwxrwxrwx 1 root root      19 Aug  1 17:15 389-admin.jar -> 389-admin-1.1.8.jar
-rw-r--r-- 1 root root   71571 Jun 21  2011 389-ds-1.2.6_en.jar
-rw-r--r-- 1 root root 1469522 Jun 21  2011 389-ds-1.2.6.jar
lrwxrwxrwx 1 root root      19 Aug  1 17:15 389-ds-1.2_en.jar -> 389-ds-1.2.6_en.jar
lrwxrwxrwx 1 root root      16 Aug  1 17:15 389-ds-1.2.jar -> 389-ds-1.2.6.jar
lrwxrwxrwx 1 root root      19 Aug  1 17:15 389-ds_en.jar -> 389-ds-1.2.6_en.jar
lrwxrwxrwx 1 root root      16 Aug  1 17:15 389-ds.jar -> 389-ds-1.2.6.jar


On Thu, Aug 2, 2012 at 1:12 PM, Chun Tat David Chu <beyonddc.storage@xxxxxxxxx> wrote:
What error are you seeing?

If the error is "Failed to install a local copy of 389-admin-1.1.jar or one of its supporting files" then I have seen that before.

What user is running the slapd process?  If it is root then it is wrong and should be something else.

I had this problem previously and the reason was because the slapd process was running as a wrong user.

- dc

On Thu, Aug 2, 2012 at 2:46 PM, Arnold Werschky <ag+389@xxxxxxxxxxxx> wrote:
Finally got the 389 server running over SSL....but some things had to manually configured.

Now I'm able to connect over the 389-console, but when I click on the Administration Server I get this error.

Same error on the Directory Server.

The rpms for console and admin are installed.

I ran setup-ds-admin.pl -u as suggested in an earlier thread, and that didn't help.

Any ideas?

Thanks!

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users


--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[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