11:28 a.m.
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
Also in log:
2018-02-16T16:35:12Z DEBUG stderr=
2018-02-16T16:35:12Z DEBUG Loading StateFile from
'/var/lib/ipa/sysrestore/sysrestore.state'
2018-02-16T16:35:12Z DEBUG Saving StateFile to
'/var/lib/ipa/sysrestore/sysrestore.state'
2018-02-16T16:35:12Z DEBUG Starting external process
2018-02-16T16:35:12Z DEBUG args=/bin/systemctl disable krb5kdc.service
2018-02-16T16:35:12Z DEBUG Process finished, return code=0
2018-02-16T16:35:12Z DEBUG stdout=
2018-02-16T16:35:12Z DEBUG stderr=
2018-02-16T16:35:12Z DEBUG duration: 0 seconds
2018-02-16T16:35:12Z DEBUG Done configuring Kerberos KDC (krb5kdc).
2018-02-16T16:35:12Z DEBUG Loading StateFile from
'/var/lib/ipa/sysrestore/sysrestore.state'
2018-02-16T16:35:12Z DEBUG Loading Index file from
'/var/lib/ipa/sysrestore/sysrestore.index'
2018-02-16T16:35:12Z DEBUG Configuring kadmin
2018-02-16T16:35:12Z DEBUG [1/2]: starting kadmin
2018-02-16T16:35:12Z DEBUG Starting external process
2018-02-16T16:35:12Z DEBUG args=/bin/systemctl is-active kadmin.service
2018-02-16T16:35:12Z DEBUG Process finished, return code=3
2018-02-16T16:35:12Z DEBUG stdout=failed
In /var/log/pki/pki-tomcat/ca/debug
[16/Feb/2018:16:35:22][localhost-startStop-1]: LdapBoundConnFactory: init
Property internaldb.ldapconn.port missing value
...
[16/Feb/2018:16:36:20][http-bio-8443-exec-3]:
CertificateAuthority:initSigUnit: ca.signing.cert not found
Property ca.signing.cacertnickname missing value
...
[16/Feb/2018:16:36:20][http-bio-8443-exec-3]: CA signing unit inited
[16/Feb/2018:16:36:20][http-bio-8443-exec-3]: cachainNum= 0
Could not get or build CA chain. Error
java.security.cert.CertificateException: Certificate is not a PKCS #11
certificate
...
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]:
CertificateAuthority:initSigUnit: ca cert found
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: CertificateAuthority:
initSigUnit 1- setting mIssuerObj and mSubjectObj
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: ca.signing Signing Unit
nickname caSigningCert cert-pki-ca
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: Got token Internal Key
Storage Token by name
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: Found cert by nickname:
'caSigningCert cert-pki-ca' with serial number: 1
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: converted to x509CertImpl
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: Got private key from cert
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: Got public key from cert
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: got signing algorithm
RSASignatureWithSHA256Digest
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: CA signing unit inited
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: cachainNum= 0
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: in init - got CA chain from
JSS.
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: ca.ocsp_signing Signing Unit
nickname ocspSigningCert cert-pki-ca
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: Got token Internal Key
Storage Token by name
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: Unable to find certificate
ocspSigningCert cert-pki-ca
[16/Feb/2018:16:36:23][http-bio-8443-exec-3]: SigningUnit: Certificate
object not found
Regards,
Andrey
11:32 a.m.
[root@<hostname> ~]# systemctl status pki-tomcatd(a)pki-tomcat.service
● pki-tomcatd(a)pki-tomcat.service - PKI Tomcat Server pki-tomcat
Loaded: loaded (/lib/systemd/system/pki-tomcatd@.service; enabled;
vendor preset: disabled)
Active: active (running) since Fri 2018-02-16 16:36:28 UTC; 52min ago
Main PID: 108490 (java)
CGroup:
/system.slice/system-pki\x2dtomcatd.slice/pki-tomcatd(a)pki-tomcat.service
└─108490 /usr/lib/jvm/jre-1.8.0-openjdk/bin/java
-DRESTEASY_LIB=/usr/share/java/resteasy-base
-Djava.library.path=/usr/lib64/nuxwdog-jni -classpath
/usr/share/tomcat/bin/bootstrap.jar...
Feb 16 16:36:37 <hostname> server[108490]:
CMSEngine.initializePasswordStore() begins
Feb 16 16:36:37 <hostname> server[108490]:
CMSEngine.initializePasswordStore(): tag=internaldb
Feb 16 16:36:37 <hostname> server[108490]: testLDAPConnection connecting to
<hostname>:389
Feb 16 16:36:38 <hostname> server[108490]:
CMSEngine.initializePasswordStore(): tag=replicationdb
Feb 16 16:36:38 <hostname> server[108490]: testLDAPConnection connecting to
<hostname>:389
Feb 16 16:36:38 <hostname> server[108490]: testLDAPConnection: The
specified user cn=Replication Manager
masterAgreement1-<hostname>-pki-tomcat,cn=config does not exist
Feb 16 16:36:38 <hostname> server[108490]: CMSEngine: init(): password test
execution failed for replicationdbwith NO_SUCH_USER. This may not be a
latest instance. Ignoring ..
Feb 16 16:36:41 <hostname> server[108490]: CA is started.
Feb 16 16:36:41 <hostname> server[108490]: PKIListener:
org.apache.catalina.core.StandardServer[after_start]
Feb 16 16:36:41 <hostname> server[108490]: PKIListener: Subsystem CA is
running.
12:40 p.m.
hi,
On Fri, Feb 16, 2018 at 6:28 PM, Markovich via FreeIPA-users <
freeipa-users(a)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
does your freeipa server meet the minimu requirements? (
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...
).
If the disk is very slow this could be a problem as well.
1:32 p.m.
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(a)lists.fedorahosted.org>:
hi,
On Fri, Feb 16, 2018 at 6:28 PM, Markovich via FreeIPA-users <
freeipa-users(a)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/admi
> n/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
>
>
>
does your freeipa server meet the minimu requirements? (
https://access.redhat.com/documentation/en-us/red_hat_
enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_
guide/installing-ipa#server-hw-recomendations).
If the disk is very slow this could be a problem as well.
_______________________________________________
FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
6:23 a.m.
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(a)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(a)lists.fedorahosted.org>:
> hi,
>
>
> On Fri, Feb 16, 2018 at 6:28 PM, Markovich via FreeIPA-users <
> freeipa-users(a)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/admi
>> n/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
>>
>>
>>
> does your freeipa server meet the minimu requirements? (
> https://access.redhat.com/documentation/en-us/red_hat_enter
> prise_linux/7/html/linux_domain_identity_authentication_and_
> policy_guide/installing-ipa#server-hw-recomendations).
>
> If the disk is very slow this could be a problem as well.
>
>
>
> _______________________________________________
> FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
> To unsubscribe send an email to freeipa-users-leave(a)lists.fedo
> rahosted.org
>
>
7:19 a.m.
New subject: FreeIpa install failed on CA did not start in 300.0s
Markovich via FreeIPA-users wrote:
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.
What phantom process was that?
rob
Regards,
Andrey
2018-02-16 22:32 GMT+03:00 Markovich <amrivkin(a)gmail.com
<mailto: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(a)lists.fedorahosted.org
<mailto:freeipa-users@lists.fedorahosted.org>>:
hi,
On Fri, Feb 16, 2018 at 6:28 PM, Markovich via FreeIPA-users
<freeipa-users(a)lists.fedorahosted.org
<mailto: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; 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
does your freeipa server meet the minimu requirements?
(https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...
<https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...>).
If the disk is very slow this could be a problem as well.
_______________________________________________
FreeIPA-users mailing list --
freeipa-users(a)lists.fedorahosted.org
<mailto:freeipa-users@lists.fedorahosted.org>
To unsubscribe send an email to
freeipa-users-leave(a)lists.fedorahosted.org
<mailto:freeipa-users-leave@lists.fedorahosted.org>
_______________________________________________
FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
7:38 a.m.
Hi Rob,
It was Apache Spark (master).
This was a Hadoop edge node.
Regards,
Andrey
> 19 февр. 2018 г., в 15:19, Rob Crittenden <rcritten(a)redhat.com> написал(а):
>
> Markovich via FreeIPA-users wrote:
>> 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.
>
> What phantom process was that?
>
> rob
>
>>
>> Regards,
>> Andrey
>>
>> 2018-02-16 22:32 GMT+03:00 Markovich <amrivkin(a)gmail.com
>> <mailto: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(a)lists.fedorahosted.org
>> <mailto:freeipa-users@lists.fedorahosted.org>>:
>>
>> hi,
>>
>>
>> On Fri, Feb 16, 2018 at 6:28 PM, Markovich via FreeIPA-users
>> <freeipa-users(a)lists.fedorahosted.org
>> <mailto: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; 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
>>
>>
>>
>> does your freeipa server meet the minimu requirements?
>>
(https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...
>>
<https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...>).
>>
>> If the disk is very slow this could be a problem as well.
>>
>>
>>
>> _______________________________________________
>> FreeIPA-users mailing list --
>> freeipa-users(a)lists.fedorahosted.org
>> <mailto:freeipa-users@lists.fedorahosted.org>
>> To unsubscribe send an email to
>> freeipa-users-leave(a)lists.fedorahosted.org
>> <mailto:freeipa-users-leave@lists.fedorahosted.org>
>>
>>
>>
>>
>>
>> _______________________________________________
>> FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
>> To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
>>
>
7:50 a.m.
New subject: FreeIpa install failed on CA did not start in 300.0s
MyGmail wrote:
Hi Rob,
It was Apache Spark (master).
This was a Hadoop edge node.
Ok, I just wanted to confirm it wasn't something left by IPA in a blown
install. Thanks for checking.
I did a brief source scan and I don't think we check for availability
for 8080 (just 8443). I'll open a ticket.
rob
Regards,
Andrey
> 19 февр. 2018 г., в 15:19, Rob Crittenden <rcritten(a)redhat.com> написал(а):
>
> Markovich via FreeIPA-users wrote:
>> 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.
>
> What phantom process was that?
>
> rob
>
>>
>> Regards,
>> Andrey
>>
>> 2018-02-16 22:32 GMT+03:00 Markovich <amrivkin(a)gmail.com
>> <mailto: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(a)lists.fedorahosted.org
>> <mailto:freeipa-users@lists.fedorahosted.org>>:
>>
>> hi,
>>
>>
>> On Fri, Feb 16, 2018 at 6:28 PM, Markovich via FreeIPA-users
>> <freeipa-users(a)lists.fedorahosted.org
>> <mailto: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; 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
>>
>>
>>
>> does your freeipa server meet the minimu requirements?
>>
(https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...
>>
<https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...>).
>>
>> If the disk is very slow this could be a problem as well.
>>
>>
>>
>> _______________________________________________
>> FreeIPA-users mailing list --
>> freeipa-users(a)lists.fedorahosted.org
>> <mailto:freeipa-users@lists.fedorahosted.org>
>> To unsubscribe send an email to
>> freeipa-users-leave(a)lists.fedorahosted.org
>> <mailto:freeipa-users-leave@lists.fedorahosted.org>
>>
>>
>>
>>
>>
>> _______________________________________________
>> FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
>> To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
>>
>
2260
days inactive
2263
days old
freeipa-users@lists.fedorahosted.org
7 comments
4 participants
participants (4)
-
Markovich -
MyGmail
-
Natxo Asenjo -
Rob Crittenden