Hi all!

Finnaly found out, what was wrong.

Some phantomy process was using port 8080. Killed it and every thing became fine. 

It's very strange that FreIpa not checked this port for avaliablity as 389 or 686.

Regards,
Andrey

2018-02-16 22:32 GMT+03:00 Markovich <amrivkin@gmail.com>:
Hi Natxo,

[root@ hostname> ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2        30G   14G   17G  45% /
devtmpfs        7.9G     0  7.9G   0% /dev
tmpfs           7.9G   16K  7.9G   1% /dev/shm
tmpfs           7.9G   25M  7.9G   1% /run
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda1       497M   79M  419M  16% /boot
tmpfs           1.6G     0  1.6G   0% /run/user/996
tmpfs           1.6G     0  1.6G   0% /run/user/1012
tmpfs           1.6G     0  1.6G   0% /run/user/1004
/dev/sdb1        32G  968M   29G   4% /mnt/resource
tmpfs           1.6G     0  1.6G   0% /run/user/0

We have enough disk space.

Also FreeIpa was installed before on this host. And worked fine. And now I've to reinstall it.

Regards,
Andrey


2018-02-16 21:40 GMT+03:00 Natxo Asenjo via FreeIPA-users <freeipa-users@lists.fedorahosted.org>:
hi,


On Fri, Feb 16, 2018 at 6:28 PM, Markovich via FreeIPA-users <freeipa-users@lists.fedorahosted.org> wrote:
Hi FreeIPA users,

Please help find wat's going wrong while reinstalling freeipa...


2018-02-16T16:41:30Z DEBUG response body '<html>\n<head>\n<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>\n<title>Error 405 HTTP method POST is not supported by this URL</title$
2018-02-16T16:41:30Z DEBUG The CA status is: check interrupted due to error: Retrieving CA status failed with status 405
2018-02-16T16:41:30Z DEBUG Waiting for CA to start...
2018-02-16T16:41:31Z DEBUG request POST http://<hostname>:8080/ca/admin/ca/getStatus
2018-02-16T16:41:31Z DEBUG request body ''
2018-02-16T16:41:31Z DEBUG response status 405
2018-02-16T16:41:31Z DEBUG response headers Date: Fri, 16 Feb 2018 16:41:31 GMT
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html;charset=iso-8859-1
Content-Length: 408
Server: Jetty(9.3.z-SNAPSHOT)


CA did not start in 300.0s
CRITICAL Failed to restart the Dogtag instance.See the installation log for details.
ERROR Unable to retrieve CA chain: Retrieving CA cert chain failed: list index out of range



If the disk is very slow this could be a problem as well.



_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org