On 03/17/2018 05:21 PM, Alexander Bokovoy via FreeIPA-users wrote:
On Sat, 17 Mar 2018, Kat via FreeIPA-users wrote:
> But why would it work perfectly with CentOS on VBox, but not Fedora?
>
> No changes - still VirtualBox, just CentOS vs Fedora.
>
Different software, including different (much older) kernel and glibc.
I'm not really interested in VirtualBox and though I'm feeling your
pain, all I can recommend is to use a better virtualization software.
>
> On 3/17/18 01:55, Alexander Bokovoy wrote:
>> On pe, 16 maalis 2018, Kat via FreeIPA-users wrote:
>>> Hi
>>>
>>> Any ideas - VirtualBox - Fedora 27 server 4 CPUs and 4G ram (started
>>> at 2+2) and it STILL dies at trying to restart the CA and fails
>>> after 300.0s
>>>
>>> I have systems smaller than this running FreeIPA, so I can't believe
>>> it is a resource? Maybe a Fedora thing? Is there some way to
>>> increase the timeout? It just seems crazy that I need to allocate so
Hi,
JFTR, the timeout used during installation can be tuned by creating
/etc/ipa/installer.conf with the desired value:
$ cat /etc/ipa/installer.conf
[global]
startup_timeout=600
Flo
>>> much of my machine - I remember on older versions I ran
it with 2
>>> CPUs on 1G.
>> If CA does not start after 300.0 chances are your VirtualBox setup does
>> not provide enough entropy to get randomness needed for generating
>> certificates and keys. No amount of memory and CPU would help with that.
>>
>> See, for example,
https://www.virtualbox.org/ticket/11297
>>
>> Unfortunately, virtualbox developers still did not add support for
>> virtio-rng unlike all others.
>>
>> You can use something like haveged to improve entropy provided to VMs.
>>
> _______________________________________________
> FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
> To unsubscribe send an email to
> freeipa-users-leave(a)lists.fedorahosted.org