<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi, I gave it a try, but neither ~/.ipa/default.conf or /etc/ipa/default.conf did work. I also tried "to fool" the ipa-server-install script by pausing it and wait for the CA to start. After "un-pausing" the script the same error occurs: "CA did not start in 300.0s" I might try to hack the services.py script but anyone got another suggestion? Kind regards, Winfried <div class="moz-cite-prefix">Op 02-04-15 om 13:38 schreef Martin Basti: </div> <blockquote cite="mid:551D2A2D.1020901@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 02/04/15 12:53, Winfried de Heiden wrote: </div> <blockquote cite="mid:551D1F8E.2080707@dds.nl" type="cite"> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> Hi all, "Because I can try" I gave a shot on installing freeipa-server on a Raspberry Pi 2. I used Fedora 21 for this. Installing looks promising, but fails somewhere halfway: <blockquote> [8/27]: starting certificate server instance [error] RuntimeError: CA did not start in 300.0s CA did not start in 300.0s </blockquote> and the install log will tell: <blockquote>[root@ipa log]# tail /var/log/ipaserver-install.log File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py", line 279, in start self.service.start(instance_name, capture_output=capture_output, wait=wait) File "/usr/lib/python2.7/site-packages/ipaplatform/redhat/services.py", line 229, in start self.wait_until_running() File "/usr/lib/python2.7/site-packages/ipaplatform/redhat/services.py", line 223, in wait_until_running raise RuntimeError('CA did not start in %ss' % timeout) 2015-04-02T09:58:36Z DEBUG The ipa-server-install command failed, exception: RuntimeError: CA did not start in 300.0s </blockquote> I 'm wondering if this is a timing issue... Of course the Pi2 tends to be slow and no wonder starting things will takes "some time"... (Yep, I 'm trying to move tons of stones using only a 2CV car...) The catalina log (that's the CA (Tomcat) log right?) tells it needs some more time to start: <blockquote>[root@ipa pki-tomcat]# tail /var/log/pki/pki-tomcat/catalina.2015-04-02.log Apr 02, 2015 11:59:20 AM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deployment of configuration descriptor /etc/pki/pki-tomcat/Catalina/localhost/ROOT.xml has finished in 84,815 ms Apr 02, 2015 11:59:20 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-8080"] Apr 02, 2015 11:59:20 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-8443"] Apr 02, 2015 11:59:20 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["ajp-bio-127.0.0.1-8009"] Apr 02, 2015 11:59:20 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 355603 ms </blockquote> Anyone got an idea how to set the time out for the CA to start to 10 or 15 minuten? Any other sugestion what is causing this problem? (no, I am not upgrading from an older version, this is a fresh install) Kind regards, Winfried <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> Hello, you can try: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.redhat.com/archives/freeipa-users/2015-April/msg00076.html">https://www.redhat.com/archives/freeipa-users/2015-April/msg00076.html</a> <pre class="moz-signature" cols="72">-- Martin Basti</pre> </blockquote> </body> </html>