[ovirt-users] Failed to start service 'ovirt-imageio-proxy' after engine-setup

Yedidyah Bar David didi at redhat.com
Wed Aug 24 20:15:43 UTC 2016


On Wed, Aug 24, 2016 at 9:57 PM, Ralf Schenk <rs at databay.de> wrote:

> Hello List,
>
> After upgrading ovirt-hosted-engine setup failed with "Failed to start
> service 'ovirt-imageio-proxy'".
>
> If try to start it manually via
> journalctl -xe shows following error:
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]:
> self._secure_server(config, server)
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]: File
> "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/server.py", line
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]:
> server_side=True)
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]: File
> "/usr/lib64/python2.7/ssl.py", line 913, in wrap_socket
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]:
> ciphers=ciphers)
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]: File
> "/usr/lib64/python2.7/ssl.py", line 526, in __init__
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]:
> self._context.load_cert_chain(certfile, keyfile)
> Aug 24 20:51:10 engine.mydomain.local ovirt-imageio-proxy[7635]: IOError:
> [Errno 2] No such file or directory
> Aug 24 20:51:10 engine.mydomain.local systemd[1]:
> ovirt-imageio-proxy.service: main process exited, code=exited,
> status=1/FAILURE
> Aug 24 20:51:10 engine.mydomain.local systemd[1]: Failed to start oVirt
> ImageIO Proxy.
>
> Config (/etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf) points to a
> non-existing cert
> /etc/pki/ovirt-engine/certs/imageio-proxy.cer
> and nonexisting key:
> /etc/pki/ovirt-engine/keys/imageio-proxy.key.nopass
>

Right, will be fixed in 4.0.3:

https://bugzilla.redhat.com/show_bug.cgi?id=1365451


>
> How to generate a correct cert and key for correct startup ?
>

There is no simple single one-liner to do that for now.

Search for "pki-enroll-pkcs12.sh" for examples if you really want to.

You can copy e.g. websocket-proxy key/cert.

You can use the 4.0 nightly repo - bugs in MODIFIED are already fixed there:

http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/

You can answer 'no' to 'configure image i/o proxy?', if you don't need it.
It's only needed for the new image uploader:

http://www.ovirt.org/develop/release-management/features/storage/image-upload/

Or you can wait for 4.0.3.

Best,


>
> Bye
> --
>
>
> *Ralf Schenk*
> fon +49 (0) 24 05 / 40 83 70
> fax +49 (0) 24 05 / 40 83 759
> mail *rs at databay.de* <rs at databay.de>
>
> *Databay AG*
> Jens-Otto-Krag-Straße 11
> D-52146 Würselen
> *www.databay.de* <http://www.databay.de>
>
> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
> Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm.
> Philipp Hermanns
> Aufsichtsratsvorsitzender: Klaus Scholzen (RA)
> ------------------------------
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Didi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160824/a2bcaaf3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo_databay_email.gif
Type: image/gif
Size: 1250 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160824/a2bcaaf3/attachment-0001.gif>


More information about the Users mailing list