search

pki-bot / pki-issues-final

0 stars 0 forks source link

Pkispawn CA: cant change the default parameter 'user' and 'group' from pkiuser #1017

Open pki-bot opened 3 years ago

pki-bot commented 3 years ago

This issue was migrated from Pagure Issue #1025. Originally filed by saipandi on 2014-05-30 16:26:08:

When the CA default configuration parameters, 'user' and 'group' are changed from pkiuser (default), the pkispawn command gives an error. It works fine if the parameters are set to default, i.e. pkiuser. The error was reproducible. Even after creating a system user with groupid and userid 17 as required the same error occured.

pki-bot commented 3 years ago

Comment from saipandi at 2014-05-30 16:29:54

Configuration file used for CA params

pki-bot commented 3 years ago

Comment from saipandi at 2014-05-30 16:32:31

the log file cud not be attached due to size restrictions so i m attaching the snippet of the log file in /var/log/pki pki-ca-spawn.log

2014-05-29 17:39:05 pkispawn : DEBUG ........... chmod 770 /root/.dogtag/pki-saili/ca/alias 2014-05-29 17:39:05 pkispawn : DEBUG ........... chown 0:0 /root/.dogtag/pki-saili/ca/alias 2014-05-29 17:39:05 pkispawn : INFO ....... executing 'certutil -N -d /root/.dogtag/pki-saili/ca/alias -f /root/.dogtag/pki-saili/ca/password.conf' 2014-05-29 17:39:05 pkispawn : INFO ....... executing 'systemctl daemon-reload' 2014-05-29 17:39:05 pkispawn : INFO ....... executing 'systemctl start pki-tomcatd@\u2026' 2014-05-29 17:39:05 pkispawn : ERROR ....... subprocess.CalledProcessError?: Command '['systemctl', 'start', 'pki-tomcatd@\u2026']' returned non-zero exit status 1! 2014-05-29 17:39:05 pkispawn : DEBUG ....... Error Type: CalledProcessError? 2014-05-29 17:39:05 pkispawn : DEBUG ....... Error Message: Command '['systemctl', 'start', 'pki-tomcatd@\u2026']' returned non-zero exit status 1 2014-05-29 17:39:05 pkispawn : DEBUG ....... File "/usr/sbin/pkispawn", line 463, in main

rv = instance.spawn(deployer)

File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/configuration.py", line 97, in spawn

    deployer.systemd.start()

File "/usr/lib/python2.7/site-packages/pki/server/deployment/pkihelper.py", line 3102, in start

    subprocess.check_call(command)

File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call

    raise CalledProcessError?(retcode, cmd)
pki-bot commented 3 years ago

Comment from saipandi at 2014-05-30 16:32:51

journal logs

May 29 17:39:05 ipaqa64vme.idm.lab.bos.redhat.com systemd[1]: Starting PKI Tomcat Server pki-saili... May 29 17:39:05 ipaqa64vme.idm.lab.bos.redhat.com systemd[26414]: Failed at step USER spawning /usr/bin/pkidaemon: No such process May 29 17:39:05 ipaqa64vme.idm.lab.bos.redhat.com systemd[1]: pki-tomcatd@\u2026: control process exited, code=exited status=217 May 29 17:39:05 ipaqa64vme.idm.lab.bos.redhat.com systemd[1]: Failed to start PKI Tomcat Server pki-saili. May 29 17:39:05 ipaqa64vme.idm.lab.bos.redhat.com systemd[1]: Unit pki-tomcatd@\u2026 entered failed state.

pki-bot commented 3 years ago

Comment from saipandi at 2017-02-27 13:58:44

Metadata Update from @saipandi: