Errors & unsuccessful install following Installation tutorial with Debian, NGinx and gunicorn

[oijn]

bepasty team,

Thanks for your support. I have been trying to get bepasty installed and setup on a Debian 10.7 server - and to that end have tried to follow the Installation tutorial with Debian, NGinx and gunicorn from https://bepasty-server.readthedocs.io/en/latest/install-tutorial.html.

Seems simple enough - though I think that maybe the tutorial may been to be updated for the latest Debian 10?

When installing I encountered many errors regarding Python 2.7 and Python 3.5 - and pip install was not successful.

So I installed:
python3-dev python3-pip virtualenv python3-virtualenv
update-alternatives --install /usr/bin/python python /usr/bin/python3.7 2
update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
update-alternatives --config python

This then allowed pip3 install to succeed.

However, when I try
service nginx reload
service supervisor reload

I get the following errors:
2020-12-13 18:09:44,693 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2020-12-13 18:09:44,695 INFO Included extra file "/etc/supervisor/conf.d/bepasty.conf" during parsing
2020-12-13 18:09:44,696 INFO RPC interface 'supervisor' initialized
2020-12-13 18:09:44,698 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-12-13 18:09:44,698 INFO supervisord started with pid 390
2020-12-13 18:09:45,700 INFO spawned: 'bepasty' with pid 1144
2020-12-13 18:09:46,058 INFO exited: bepasty (exit status 1; not expected)
...
2020-12-13 18:09:49,577 INFO exited: bepasty (exit status 3; not expected)
2020-12-13 18:09:52,581 INFO spawned: 'bepasty' with pid 1167
2020-12-13 18:09:52,959 INFO exited: bepasty (exit status 1; not expected)
2020-12-13 18:09:53,960 INFO gave up: bepasty entered FATAL state, too many start retries too quickly

Does anyone have any suggestions please.

[ThomasWaldmann]

update-alternatives --install /usr/bin/python python /usr/bin/python3.7 2
update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
update-alternatives --config python

Not required, just have python3 and related installed and use python3.

You don't need 2.7 for bepasty-server.

No idea about the supervisor issues.

Maybe try to get it working with the flask internal server first, that might be easier to debug. See flask docs.

[oijn]

It would seem that python 2.7 is part of the Debian base install? I didn't install it specifically. But to remove the pip or pip3 errors I had to define which python to use.

Thx - I will read the flask docs and see what I can identify.

Much appreciated for your assistance.

[ThomasWaldmann]

python 2.7 is not relevant. you can have it or not, it does not matter.

if you have python3 and the related tools installed, you can just invoke python3, pip3, etc.

[oijn]

Thanks for your pointers - I was able to get bepasty up and running.

I have a cookbook - in addition to what is listed in the Installation tutorial with Debian, NGinx and gunicorn.
What I could do is write it up here later. Hopefully, it might help someone else.

[ThomasWaldmann]

If you can do a minimal PR for our docs, that changes whatever is definitely wrong or missing, without adding unneeded stuff, that would be great!

[oijn]

I haven't done a PR for a very long time and will have to relearn - sorry will look at that over the Dec break. Over the break will also install from a clean server and double-check the cookbook instructions.

In the mean time until I have a chance to do that - I've updated the file and uploaded here. (I had to change *.rst to *.txt because git issues forum doesn't accept uploading *.rst.

install-tutorial.txt

[ThomasWaldmann]

Reopen to improve docs later.

[oijn]

I have updated the tutorial and verified by installing from a new Debian 10 minimal server install twice.

I have also (tried) to create a new pull request and answered the comments.

[update] After logging in again this morning - seems the PRs I did yesterday were to my own cloned repo? Have created a PR via git web interface against bepasty docs direct.