CentOS - Dec 2017 - upgrading python

On Mon, Dec 11, 2017 at 5:43 PM, Clint Dilks <clintd at
scms.waikato.ac.nz> wrote:
> On Tue, Dec 12, 2017 at 11:31 AM, <m.roth at 5-cent.us> wrote:
>
>> Pete Biggs wrote:
>> > On Mon, 2017-12-11 at 15:44 -0600, Frank Cox wrote:
>> >> On Mon, 11 Dec 2017 16:32:06 -0500
>> >> Larry Martell wrote:
>> >>
>> >> > Can I make that the default python?
>> >>
>> >> ~/.bashrc
>> >>
>> > No. I'm not entirely sure that is a good idea! No, not all.
>> >
>> > 'scl enable python27 bash' creates a *new* shell with the
correct
>> > environment.  As each invocation of bash reads .bashrc, it will
also
>> > create another new shell which will then read .bashrc and create
>> > another shell ....
>> >
>> > Depending on the speed of your machine and disks and how much
memory
>> > you have, it will take a few seconds to a few minutes to grind
your
>> > machine to a halt.
>>
>> The simplest way is to . <path/to/python2.7/enable, and you're
good to go.
> I definitely wouldn't make it the default python, but I have made it
the
> default for a particular user as long as they are not root.
>
> In the past I have got python27-mod_wsgi and httpd24-httpd working together
> by doing things like httpd24-httpd by doing things like
>
>
> cat /opt/rh/httpd24/root/etc/sysconfig/httpd
>
> export PATH=/opt/rh/python27/root/usr/bin:$PATH
> export
>
LD_LIBRARY_PATH=/opt/rh/python27/root/usr/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
I am running nginx and uWSGI. I added this to /etc/systemd/system/uwsgi.service:

ExecStart=/usr/bin/scl enable python27 bash; /usr/bin/uwsgi --emperor
/etc/uwsgi/sites

But it did not start:

   Loaded: loaded (/etc/systemd/system/uwsgi.service; enabled; vendor
preset: disabled)
   Active: failed (Result: start-limit) since Mon 2017-12-11 17:20:36
EST; 6s ago
  Process: 24492 ExecStart=/usr/bin/scl enable python27 bash;
/usr/bin/uwsgi --emperor /etc/uwsgi/sites (code=exited,
status=1/FAILURE)

On 12/11/2017 2:50 PM, Larry Martell wrote:
> ExecStart=/usr/bin/scl enable python27 bash; /usr/bin/uwsgi --emperor
> /etc/uwsgi/sites
You probably want:

ExecStart=/usr/bin/scl enable python27 '/usr/bin/uwsgi --emperor
/etc/uwsgi/sites'

See:

https://linux.die.net/man/1/scl

On Mon, Dec 11, 2017 at 5:57 PM, Kenneth Porter <shiva at sewingwitch.com>
wrote:
> On 12/11/2017 2:50 PM, Larry Martell wrote:
>>
>> ExecStart=/usr/bin/scl enable python27 bash; /usr/bin/uwsgi --emperor
>> /etc/uwsgi/sites
>
>
> You probably want:
>
> ExecStart=/usr/bin/scl enable python27 '/usr/bin/uwsgi --emperor
> /etc/uwsgi/sites'
>
> See:
>
> https://linux.die.net/man/1/scl
With that change it starts, but still with 2.7.5:

*** Starting uWSGI 2.0.13.1 (64bit) on [Mon Dec 11 17:47:19 2017] ***
compiled with version: 4.8.5 20150623 (Red Hat 4.8.5-4) on 28 July 2016 12:32:18
os: Linux-3.10.0-327.36.3.el7.x86_64 #1 SMP Mon Oct 24 16:09:20 UTC 2016
nodename: padev
machine: x86_64
clock source: unix
detected number of CPU cores: 8
current working directory: /etc/uwsgi/sites
detected binary path: /usr/bin/uwsgi
chdir() to /usr/local/motor/motor
your processes number limit is 195775
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /usr/local/motor/motor.sock fd 3
Python version: 2.7.5 (default, Sep 15 2016, 22:37:39)  [GCC 4.8.5
20150623 (Red Hat 4.8.5-4)]
*** Python threads support is disabled. You can enable it with
--enable-threads ***
Python main interpreter initialized at 0x13a75e0
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 1115752 bytes (1089 KB) for 10 cores
*** Operational MODE: preforking ***
WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x13a75e0
pid: 25616 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 25616)
spawned uWSGI worker 1 (pid: 25693, cores: 1)
spawned uWSGI worker 2 (pid: 25694, cores: 1)
spawned uWSGI worker 3 (pid: 25695, cores: 1)
spawned uWSGI worker 4 (pid: 25696, cores: 1)
spawned uWSGI worker 5 (pid: 25697, cores: 1)
spawned uWSGI worker 6 (pid: 25699, cores: 1)
spawned uWSGI worker 7 (pid: 25700, cores: 1)
spawned uWSGI worker 8 (pid: 25701, cores: 1)
spawned uWSGI worker 9 (pid: 25702, cores: 1)
spawned uWSGI worker 10 (pid: 25703, cores: 1)