Description of problem: When I tested FreeIPA in rawhide, the installation always crashed due to wrong symlink to jss4.jar: # ipa-server-install ... [32/35]: configuring Posix uid/gid generation [33/35]: enabling compatibility plugin [34/35]: tuning directory server [35/35]: configuring directory to start on boot Done configuring directory server (dirsrv). Configuring certificate server (pki-tomcatd): Estimated time 3 minutes 30 seconds [1/20]: creating certificate server user [2/20]: configuring certificate server instance ipa : CRITICAL failed to configure ca instance Command '/usr/sbin/pkispawn -s CA -f /tmp/tmp0tRjAA' returned non-zero exit status 1 Configuration of CA failed /var/log/ipaserver-install.log: ... 2013-03-08T15:05:02Z DEBUG Starting external process 2013-03-08T15:05:02Z DEBUG args=/usr/sbin/pkispawn -s CA -f /tmp/tmpEjwkVe 2013-03-08T15:05:03Z DEBUG Process finished, return code=1 2013-03-08T15:05:03Z DEBUG stdout= 2013-03-08T15:05:03Z DEBUG stderr=pkispawn : WARNING ....... Dangling symlink '/var/lib/pki/pki-tomcat/common/lib/jss4.jar'-->'/usr/lib64/java/jss4.jar' 2013-03-08T15:05:03Z CRITICAL failed to configure ca instance Command '/usr/sbin/pkispawn -s CA -f /tmp/tmpEjwkVe' returned non-zero exit status 1 2013-03-08T15:05:03Z INFO File "/usr/lib/python2.7/site-packages/ipaserver/install/installutils.py", line 612, in run_script return_value = main_function() File "/sbin/ipa-server-install", line 986, in main dm_password, subject_base=options.subject) File "/usr/lib/python2.7/site-packages/ipaserver/install/cainstance.py", line 617, in configure_instance self.start_creation(runtime=210) File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py", line 362, in start_creation method() File "/usr/lib/python2.7/site-packages/ipaserver/install/cainstance.py", line 735, in __spawn_instance raise RuntimeError('Configuration of CA failed') 2013-03-08T15:05:03Z INFO The ipa-server-install command failed, exception: RuntimeError: Configuration of CA failed It seems that the jar file is somewhere else: # rpm -ql jss /usr/lib/java/jss4.jar /usr/lib64/jss/jss4.jar /usr/lib64/jss/libjss4.so /usr/share/doc/jss-4.2.6 /usr/share/doc/jss-4.2.6/MPL-1.1.txt /usr/share/doc/jss-4.2.6/gpl.txt /usr/share/doc/jss-4.2.6/jss.html /usr/share/doc/jss-4.2.6/lgpl.txt Version-Release number of selected component (if applicable): pki-ca-10.0.1-2.fc19.noarch jss-4.2.6-29.fc19.x86_64 How reproducible: Steps to Reproduce: 1. Install freeipa-server (I may provide a custom build) 2. Run ipa-server-install 3. Actual results: Installation crashes due to problem above. Expected results: Installation succeeds. Additional info:
Created attachment 707215 [details] Fix for platform-dependent JNI jar files In Fedora 16, 17, and 18, JNI jar files were required to be located under architecture specific locations (e. g. - /usr/lib/java and /usr/lib64/java). These rules were re-defined in 'https://fedoraproject.org/wiki/Packaging:Java#Packaging_JAR_files_that_use_JNI', as the JNI packaging rules were changed in Fedora 19 (and RHEL 7) back to the JNI rules that existed for Fedora 15 (e. g. - all JNI jar files will be located under /usr/lib/java).
Checked patch into 'master': * b953c172bf274352c628ffef7d3ef0ef4c9ce59d I will now work on creating a patch for 'rawhide', and building an RPM that contains this in Koji.
Ok, thanks for quick update! I will test the new rpm when it is ready.
Created attachment 708665 [details] Additional fix for platform-dependent JNI jar files Additional code associated with the check-in in Comment #2 above.
Created attachment 708666 [details] Patch for Koji build of Fedora 19
Created attachment 708667 [details] Spec file for Koji build of Fedora 19
(In reply to comment #4) > Created attachment 708665 [details] > Additional fix for platform-dependent JNI jar files > > Additional code associated with the check-in in Comment #2 above. Checked patch into 'master': * a2e27c2169f507f428519067148ea360ca3d3059
(In reply to comment #5) > Created attachment 708666 [details] > Patch for Koji build of Fedora 19 (In reply to comment #6) > Created attachment 708667 [details] > Spec file for Koji build of Fedora 19 Built 'pki-core-10.0.1-2.1.fc19' in Koji.
I can confirm, that this build fixed the issue for me.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Hi, I think the patch is not working correctly on older Fedora versions on 32bit. After upgrading on F18 from 10.0.1-1 to 10.0.2-2 I see the same issue, because /etc/pki/pki.conf contains "JNI_JAR_DIR=/usr/lib64/java" an a 32bit platform.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.