Public bug reported:
Hi,
I'm just trying to get pki-server and pki-ca running under 16.04. Seems
to run into a circular problem:
pki-tomcatd.service can't be run:
#systemctl status pki-tomcatd.service
● pki-tomcatd.service - LSB: Start pki-tomcatd at boot time
Loaded: loaded (/etc/init.d/pki-tomcatd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-01-17 14:35:41 UTC; 55min
ago
Docs: man:systemd-sysv-generator(8)
Process: 7862 ExecStart=/etc/init.d/pki-tomcatd start (code=exited, status=5)
Jan 17 14:35:41 catestub systemd[1]: Starting LSB: Start pki-tomcatd at boot
time...
Jan 17 14:35:41 catestub pki-tomcatd[7862]: ERROR: No 'tomcat' instances
installed!
Jan 17 14:35:41 catestub systemd[1]: pki-tomcatd.service: Control process
exited, code=exited status=5
Jan 17 14:35:41 catestub systemd[1]: Failed to start LSB: Start pki-tomcatd at
boot time.
Jan 17 14:35:41 catestub systemd[1]: pki-tomcatd.service: Unit entered failed
state.
Jan 17 14:35:41 catestub systemd[1]: pki-tomcatd.service: Failed with result
'exit-code'.
but pkispawn, which should setup instances, as it man page claims, fails at the
end of the process, and it says
[ ok ] Starting pki-tomcatd (via systemctl): pki-tomcatd.service.
pkispawn : ERROR ....... server failed to restart
>From /var/log/pki/pki-ca-spawn.20180117154016.log
2018-01-17 15:41:11 pkispawn : INFO ....... executing
'/etc/init.d/pki-tomcatd start pki-tomcat'
2018-01-17 15:41:30 pkispawn : DEBUG ........... No connection - server
may still be down
2018-01-17 15:41:30 pkispawn : DEBUG ........... No connection -
exception thrown: ('Connection aborted.', error(104, 'Connection reset by
peer'))
2018-01-17 15:41:31 pkispawn : DEBUG ........... No connection - server
may still be down
2018-01-17 15:41:31 pkispawn : DEBUG ........... No connection -
exception thrown: HTTPSConnectionPool(host='catestub.buero.danisch.de',
port=8443): Max retries exceeded with url: /ca/admin/ca/getStatus (Caused by
NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection
object at 0x7ff4bd858b50>: Failed to establish a new connection: [Errno 111]
Connection refused',))
2018-01-17 15:41:32 pkispawn : DEBUG ........... No connection - server
may still be down
I don't see what's actually wrong since I have no idea how this was
intended to work or be setup. The README is just useless.
It looks a little bit as if it had been made for 14.04 or debian from
2014, and never been touched or checked since.
** Affects: dogtag-pki (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to dogtag-pki in Ubuntu.
https://bugs.launchpad.net/bugs/1743808
Title:
incompatible to tomcat8?
Status in dogtag-pki package in Ubuntu:
New
Bug description:
Hi,
I'm just trying to get pki-server and pki-ca running under 16.04.
Seems to run into a circular problem:
pki-tomcatd.service can't be run:
#systemctl status pki-tomcatd.service
● pki-tomcatd.service - LSB: Start pki-tomcatd at boot time
Loaded: loaded (/etc/init.d/pki-tomcatd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-01-17 14:35:41 UTC;
55min ago
Docs: man:systemd-sysv-generator(8)
Process: 7862 ExecStart=/etc/init.d/pki-tomcatd start (code=exited,
status=5)
Jan 17 14:35:41 catestub systemd[1]: Starting LSB: Start pki-tomcatd at boot
time...
Jan 17 14:35:41 catestub pki-tomcatd[7862]: ERROR: No 'tomcat' instances
installed!
Jan 17 14:35:41 catestub systemd[1]: pki-tomcatd.service: Control process
exited, code=exited status=5
Jan 17 14:35:41 catestub systemd[1]: Failed to start LSB: Start pki-tomcatd
at boot time.
Jan 17 14:35:41 catestub systemd[1]: pki-tomcatd.service: Unit entered failed
state.
Jan 17 14:35:41 catestub systemd[1]: pki-tomcatd.service: Failed with result
'exit-code'.
but pkispawn, which should setup instances, as it man page claims, fails at
the end of the process, and it says
[ ok ] Starting pki-tomcatd (via systemctl): pki-tomcatd.service.
pkispawn : ERROR ....... server failed to restart
From /var/log/pki/pki-ca-spawn.20180117154016.log
2018-01-17 15:41:11 pkispawn : INFO ....... executing
'/etc/init.d/pki-tomcatd start pki-tomcat'
2018-01-17 15:41:30 pkispawn : DEBUG ........... No connection - server
may still be down
2018-01-17 15:41:30 pkispawn : DEBUG ........... No connection -
exception thrown: ('Connection aborted.', error(104, 'Connection reset by
peer'))
2018-01-17 15:41:31 pkispawn : DEBUG ........... No connection - server
may still be down
2018-01-17 15:41:31 pkispawn : DEBUG ........... No connection -
exception thrown: HTTPSConnectionPool(host='catestub.buero.danisch.de',
port=8443): Max retries exceeded with url: /ca/admin/ca/getStatus (Caused by
NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection
object at 0x7ff4bd858b50>: Failed to establish a new connection: [Errno 111]
Connection refused',))
2018-01-17 15:41:32 pkispawn : DEBUG ........... No connection - server
may still be down
I don't see what's actually wrong since I have no idea how this was
intended to work or be setup. The README is just useless.
It looks a little bit as if it had been made for 14.04 or debian from
2014, and never been touched or checked since.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1743808/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help : https://help.launchpad.net/ListHelp
