On Tuesday, 13 October 2020 2:38:40 AM AEDT Thomas Goirand wrote: > > # gnocchi-api > > 2020-10-12 12:17:56,769 [7662] INFO gnocchi.service: Gnocchi version > > 4.3.1 /usr/bin/uwsgi: option '--http' is ambiguous; possibilities: > > '--http-socket' '--http-socket-modifier1' '--http-socket-modifier2' > > '--http11-socket' '--https-socket' '--https-socket-modifier1' > > '--https-socket-modifier2' getopt_long() error > > > > Above is the result of running gnocchi-api at the command-line. I realise > > that this might not be the right way to run it, but I think it still > > shouldn't abort due to using parameters that don't match the version of > > uwsgi in Debian. > > > > It seems that instead of --http it should use --http-socket. Also after > > that is fixed there's the issue that it uses the --http-keepalive option > > which is not accepted by the uwsgi in Debian. > > The gnocchi-api binary isn't meant to be started standalone, but it
https://gnocchi.xyz/operating.html This page says it is. > should be used by uwsgi, as per what the startup scripts are doing. If > you do /etc/init.d/gnocchi-api show-args, it will show: > > /usr/bin/uwsgi_python37 \ > --https-socket > [::]:8041,/etc/gnocchi/ssl/public/HOSTNAME.crt,/etc/gnocchi/ssl/private/HOST > NAME.pem \ > --ini /etc/gnocchi/gnocchi-api-uwsgi.ini > > (that is, if you've put some SSL files in /etc/gnocchi/ssl, otherwise it > wont use SSL). > > Therefore, I wonder if this bug is still valid or not... Especially if > you consider that the service isn't even using the --http option (where > is this coming from then?). It's coming from /usr/lib/python3/dist-packages/gnocchi/cli/api.py and I've supplied a patch. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
