Re: [uWSGI] uwsgi python3.7, strange output

2019-06-17 Thread Tamer Higazi

Hi Damjan,

You were absolutely right:

ldd 
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/./libssl-8bb9b3dd.so.1.0.2o

    linux-vdso.so.1 (0x7ffe483ed000)
    libgssapi_krb5-174f8956.so.2.2 => not found
    libkrb5-fb0d2caa.so.3.3 => not found
    libcom_err-beb60336.so.2.1 => not found
    libk5crypto-622ef25b.so.3.1 => not found
    libcrypto-6448f03c.so.1.0.2o => not found
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9fc59db000)
    libz-a147dcb0.so.1.2.3 => not found
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9fc5813000)
    /lib64/ld-linux-x86-64.so.2 (0x7f9fc5c9b000)

removing in the requirement.txt psycopg2-binary and setting just 
psycopg2 after setting up a fresh environment solved my problem.



Thanks, Tamer


Am 17.06.19 um 23:35 schrieb Damjan Georgievski:



On Mon, 17 Jun 2019 at 23:27, Tamer Higazi <mailto:th9...@googlemail.com>> wrote:


Hi people,

I am not getting smart. Can somebody explain me this ?
Python 3.7 was compiled with this configure statement:

./configure  --enable-ipv6 --with-system-ffi --enable-shared

Any ideas what could there be wrong ?


best, Tamer


--


!!! uWSGI process 7604 got Segmentation Fault !!!
*** backtrace of 7604 ***
./uwsgi(uwsgi_backtrace+0x2a) [0x562ba9b9731a]
./uwsgi(uwsgi_segfault+0x23) [0x562ba9b976d3]
/lib/x86_64-linux-gnu/libc.so.6(+0x37840) [0x7f149fe2a840]

/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/./libssl-8bb9b3dd.so.1.0.2o(ssl3_cleanup_key_block+0xb)

[0x7f149b674cbb]



A wild guess would be that your psycopg2 (and its dependencies) is 
linked with a different openssl to what python3.7, uwsgi or some of 
the other python3.7 libraries are linked to.



--
damjan

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


[uWSGI] uwsgi python3.7, strange output

2019-06-17 Thread Tamer Higazi

Hi people,

I am not getting smart. Can somebody explain me this ?
Python 3.7 was compiled with this configure statement:

./configure  --enable-ipv6 --with-system-ffi --enable-shared

Any ideas what could there be wrong ?


best, Tamer


--


!!! uWSGI process 7604 got Segmentation Fault !!!
*** backtrace of 7604 ***
./uwsgi(uwsgi_backtrace+0x2a) [0x562ba9b9731a]
./uwsgi(uwsgi_segfault+0x23) [0x562ba9b976d3]
/lib/x86_64-linux-gnu/libc.so.6(+0x37840) [0x7f149fe2a840]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/./libssl-8bb9b3dd.so.1.0.2o(ssl3_cleanup_key_block+0xb) 
[0x7f149b674cbb]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/./libssl-8bb9b3dd.so.1.0.2o(ssl3_clear+0x16) 
[0x7f149b6725b6]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/./libssl-8bb9b3dd.so.1.0.2o(tls1_clear+0x9) 
[0x7f149b67e229]

/usr/lib/x86_64-linux-gnu/libssl.so.1.1(SSL_new+0x441) [0x7f14a0497811]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/libpq-239f9ac8.so.5.10(+0x23399) 
[0x7f149b90e399]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/libpq-239f9ac8.so.5.10(+0x24935) 
[0x7f149b90f935]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/libpq-239f9ac8.so.5.10(PQconnectPoll+0xb00) 
[0x7f149b8f9600]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/libpq-239f9ac8.so.5.10(+0xf099) 
[0x7f149b8fa099]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/.libs/libpq-239f9ac8.so.5.10(PQconnectdb+0x1f) 
[0x7f149b8fce5f]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/_psycopg.cpython-37m-x86_64-linux-gnu.so(+0x12631) 
[0x7f149bb4d631]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/_psycopg.cpython-37m-x86_64-linux-gnu.so(+0x133bf) 
[0x7f149bb4e3bf]

/usr/local/lib/libpython3.7m.so.1.0(+0xe9c12) [0x7f149da94c12]
/usr/local/lib/libpython3.7m.so.1.0(_PyObject_FastCallDict+0x8b) 
[0x7f149da3efab]

/usr/local/lib/libpython3.7m.so.1.0(+0x942db) [0x7f149da3f2db]
/usr/local/lib/libpython3.7m.so.1.0(_PyObject_CallFunction_SizeT+0x9e) 
[0x7f149da3fbce]
/storage/PyENV/saleorENV/lib/python3.7/site-packages/psycopg2/_psycopg.cpython-37m-x86_64-linux-gnu.so(+0xc1a8) 
[0x7f149bb471a8]

/usr/local/lib/libpython3.7m.so.1.0(PyCFunction_Call+0xf3) [0x7f149da40333]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x6fd0) 
[0x7f149da1a640]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x97e) 
[0x7f149db13a2e]
/usr/local/lib/libpython3.7m.so.1.0(_PyFunction_FastCallDict+0x1bb) 
[0x7f149da3e08b]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x364d) 
[0x7f149da16cbd]

/usr/local/lib/libpython3.7m.so.1.0(+0x674db) [0x7f149da124db]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x77f1) 
[0x7f149da1ae61]

/usr/local/lib/libpython3.7m.so.1.0(+0x674db) [0x7f149da124db]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x77f1) 
[0x7f149da1ae61]

/usr/local/lib/libpython3.7m.so.1.0(+0x674db) [0x7f149da124db]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x77f1) 
[0x7f149da1ae61]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x97e) 
[0x7f149db13a2e]
/usr/local/lib/libpython3.7m.so.1.0(_PyFunction_FastCallKeywords+0x93) 
[0x7f149da3e243]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x77f1) 
[0x7f149da1ae61]

/usr/local/lib/libpython3.7m.so.1.0(+0x674db) [0x7f149da124db]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x77f1) 
[0x7f149da1ae61]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x97e) 
[0x7f149db13a2e]
/usr/local/lib/libpython3.7m.so.1.0(_PyFunction_FastCallKeywords+0x93) 
[0x7f149da3e243]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x69cb) 
[0x7f149da1a03b]

/usr/local/lib/libpython3.7m.so.1.0(+0xa4310) [0x7f149da4f310]
/usr/local/lib/libpython3.7m.so.1.0(+0xb1126) [0x7f149da5c126]
/usr/local/lib/libpython3.7m.so.1.0(+0xb1591) [0x7f149da5c591]
/usr/local/lib/libpython3.7m.so.1.0(+0xe9c12) [0x7f149da94c12]
/usr/local/lib/libpython3.7m.so.1.0(_PyObject_FastCallKeywords+0xd3) 
[0x7f149da3e923]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x44ab) 
[0x7f149da17b1b]

/usr/local/lib/libpython3.7m.so.1.0(+0x674db) [0x7f149da124db]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x77f1) 
[0x7f149da1ae61]

/usr/local/lib/libpython3.7m.so.1.0(+0x674db) [0x7f149da124db]
/usr/local/lib/libpython3.7m.so.1.0(_PyFunction_FastCallDict+0x2d2) 
[0x7f149da3e1a2]
/usr/local/lib/libpython3.7m.so.1.0(_PyObject_FastCall_Prepend+0xe1) 
[0x7f149da3f171]

/usr/local/lib/libpython3.7m.so.1.0(+0xef129) [0x7f149da9a129]
/usr/local/lib/libpython3.7m.so.1.0(PyObject_GetItem+0x39) [0x7f149da28569]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x2ac6) 
[0x7f149da16136]
/usr/local/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x97e) 
[0x7f149db13a2e]

Re: [uWSGI] Help

2019-03-04 Thread Tamer Higazi

okay, I didn't see the AWS term. had tomatos on my eyes.
Sorry.

You have a dual core CPU (perhaps 32 bit even) and then with 4GB RAM.


Main problem!? Really!?

He's on AWS of couse it's 64bits, 2 CPU cores is a LOT of power for more
than 20 users, I serve 50 concurent user on AWS with a SINGLE core,
and 1GB of RAM, that doesn't scratch 1% of CPU usage and it is writting to
Postgres DB all the time, surely I don't use python/flask but 4GB is more than
enough for that.


ahh. that is of course one other thing.

I apologize.


Now for the log error message that is a bit unclear what happens,
trying to mimic the problem with 'wrk' and perhaps a simple app
to reproduce would help better.


Install terminator, split the screen

one for:
tail -f /var/log/myapp.log

the other for:
top

to see how the performance and at the point of crash is written

I would advise that.


best, Tamer

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] Help

2019-03-02 Thread Tamer Higazi

Dear Leo,

The main problem is that the hardware already is with very poor specs.
You have a dual core CPU (perhaps 32 bit even) and then with 4GB RAM.

you want to provide services and even like to earn money with it, and 
start saving money on hardware.
Why this nonsense ? Nobody said that you have to buy HIGH-END Hardware, 
but get the requirements 1st before doing anything.


Have you turned on logging and see what had been written inside that 
causes the crash?

What is written in the logs ?
Have you opened a shell and executed "top" to see what ressources are 
consumed ?


Serving long term connections is also no problem.
I have deald with websockets connections with written Python Stack and 
nginx as backend without any problems at all.


And why using flask web framework doing rest calls ?
Take Twisted. for example, or something totally small: 
http://docs.python-eve.org/en/latest/



best, Tamer


PS: best is to answer to the list and not taking individual addresses in 
CC like everybody else.



On 02.03.19 14:40, Léo El Amri wrote:

On 02/03/2019 14:04, Tamer Higazi wrote:

2. And with your comment "So please help to scale the application for
concurrent users."

is very unpolite.

I think it was just badly written english. I don't think they meant to
be unpolite.

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] Help

2019-03-02 Thread Tamer Higazi

Dear Ashraf,

1. Get yourself propper hardware, that would solve perhaps by 80% your 
problems.


2. And with your comment "So please help to scale the application for 
concurrent users."


is very unpolite.

Nobody has to help you, and people in the open source world don't make 
support for commercial vendors unless they are PAID for it.
If you want to get it run NOW, then look for a company that workout your 
problems, and make a deal with them.


Otherwise, you are old enough to workout the know-how yourself.

Here is a good starting point:

http://nginx.org/en/docs/http/load_balancing.html
https://uwsgi-docs.readthedocs.io/en/latest/Broodlord.html
https://uwsgi-docs.readthedocs.io/en/latest/Fastrouter.html

If you have worked out yourself things, and don't get it run and ask 
"GENTLY" what you have done wrong, then you get help.



best, Tamer


On 01.03.19 07:27, Ashraf Mohamed wrote:

Hi ,

I have a flask application which is running in nginx server and i am 
unbale to serve the application for more then 20 users (concurrently) 
as its gets break.


*_Error:_*
app: 0|req: 1/35] x.x.x.x () {44 vars in 5149 bytes} [Thu Feb  7 
14:01:42 2019] GET /url/edit/7e08e5c4-11cf-485b-9b05-823fd4006a60 => 
generated 0 bytes in 69000 msecs (HTTP/2.0 200) 4 headers in 0 bytes 
(1 switches on core 0)

*
*
*_OS version:_*
ubuntu 16.04 (aws)

*_CPU:_*
2 Core with 4 GB RAM

*_WebServer:_*
nginx version: nginx/1.15.0

*_APP Architecture:_*
I have 2 application running on different servers app 1(using for 
frontend ) and app 2( using for REST API Calls) both are flask 
applications


*
*
*_app1 uWSGI config :_*
*
*
[uwsgi]
module = wsgi
master = true
processes = 3
socket = app.sock
chmod-socket = 777
vacuum = true
die-on-term = true
logto = test.log
buffer-size=7765535
worker-reload-mercy = 240
thunder-lock = true
async=10
ugreen
listen = 950
enable-threads= True

*_app 1 nginx config_*
*_
_*

user  root;
worker_processes  5;
events {
    worker_connections  4000;
}
http {
    server {
       limit_req zone=mylimit burst=20 nodelay;
       limit_req_status 444;
        listen 80 backlog=1000;
         listen [::]:80;
        server_name domain name;
        location /static {
           alias /home/ubuntu/flaskapp/app/static;
        }
        location / {
            include uwsgi_params;
uwsgi_read_timeout 120;
client_max_body_size 1000M;
          uwsgi_pass unix:///home/ubuntu/flaskapp/app.sock;
       }

    }

}


*_app 2 uWsgi config:_*

[uwsgi]
module = wsgi
master = true
processes = 5
socket = app2.sock
chmod-socket = 777
vacuum = true
die-on-term = true
logto = sptms.log
async = 10
ugreen
worker-reload-mercy = 240
enable-threads = true
thunder-lock = true
listen=2000
buffer-size=65535
no-defer-accept=true
stats=stats.sock
memory-report = true

*_app 2 nginx config :_*
*_
_*
worker_processes  1;
events {
    worker_connections  1024;
}
http {
access_log /var/log/nginx/access.log;
proxy_connect_timeout 2000;
proxy_read_timeout 2000;
fastcgi_read_timeout 2000;
error_log /var/log/nginx/error.log info;
    include       mime.types;
    gzip on;
    server {
        listen 80 backlog=2048;
        server_name x.x.x.x;
        location / {
            include uwsgi_params;
            uwsgi_pass unix:///home/ubuntu/app/app2.sock;
#keepalive_timeout 155s;
        }
    }
}


So please help to scale the application for concurrent users.


Thanks
Ashraf

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] php plugin ends with sapi global error, no start (SOLVED)

2019-02-04 Thread Tamer Higazi

Dear Krzysztof,
You were absolutely right. The --dlopen flag did it for me.

However, it is for me still a riddle, why the result of "ldd 
php71_plugin.so" pointed to the wrong library.


As I accomplished that, everything worked fine for me.

Do you still want the result of the ldd command ?


best, Tamer

On 04.02.19 01:21, Krzysztof Warzecha wrote:

Steps to reproduce:
1 - download php and build it with: ./configure
--prefix=/usr/local/php71-emb --enable-mbstring --enable-embed
make, and make install.

Is there any reason why you are not using libphp7.1-embed from the
repositories? (I'm assuming you are running Debian)


2 - build the plugin: UWSGICONFIG_PHPDIR=/usr/local/php71-emb python
uwsgiconfig.py --plugin plugins/php default php71

FYI I'm using:

- name: "pushd php-plugins; ./configure && make; popd"
   command: >
 chdir=/home/uwsgi-build/src/
 creates=/home/uwsgi-build/src/{{ item.name }}_plugin.so
 env CC=clang
 UWSGICONFIG_PHPPATH=/usr/bin/{{ item.config }}
 python uwsgiconfig.py --plugin plugins/php core {{ item.name }}
   with_items:
   - { name: php72, config: php-config7.2 }
   - { name: php71, config: php-config7.1 }
   - { name: php70, config: php-config7.0 }
   - { name: php56, config: php-config5.6 }

Looking at plugins/php/uwsgiplugin.py it seems that your version is
doing basically the same thing.


Could you show us the output from "ldd php71_plugin.so"? It should
import sapi_globals from libphp7.so.

Is it possible that you don't have libphp7.so in your system, but
libphp7.1.so? Could you try to execute something like this?

./uwsgi --dlopen /usr/lib/libphp7.1.so --plugin php71 --master
--socket :3030 --processes 4


___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


[uWSGI] php plugin ends with sapi global error, no start

2019-02-03 Thread Tamer Higazi

Hi everybody,

I built the uWSGI php plugin, and I am not getting it to run.
I tried it with all latest versions of php 7.1, 7.2 and 7.3 and I get 
always the same errors displayed.


Anybody knows why and what is going wrong up here ?

If anybody can tell me what i did wrong, I would kindly thank you.


best, Tamer


--


Steps to reproduce:
1 - download php and build it with: ./configure 
--prefix=/usr/local/php71-emb --enable-mbstring --enable-embed

make, and make install.

2 - build the plugin: UWSGICONFIG_PHPDIR=/usr/local/php71-emb python 
uwsgiconfig.py --plugin plugins/php default php71


and make the simple test:

./uwsgi --plugin php71 --master --socket :3030 --processes 4


the outout:

!!! UNABLE to load uWSGI plugin: ./php71_plugin.so: undefined symbol: 
sapi_globals !!!
*** Starting uWSGI 2.1-dev-99c74add (64bit) on [Sun Feb  3 21:19:47 
2019] ***

compiled with version: 6.3.0 20170516 on 03 February 2019 20:04:55
os: Linux-4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
nodename: mx-in
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 6
current working directory: /usr/local/uwsgi-g
detected binary path: /usr/local/uwsgi-g/uwsgi
dropping root privileges as early as possible
your processes number limit is 63656
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 TCP address :3030 fd 3
dropping root privileges after socket binding
dropping root privileges after plugin initialization
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
your request buffer size is 4096 bytes
mapped 364800 bytes (356 KB) for 4 cores
*** Operational MODE: preforking ***
*** no app loaded. GAME OVER ***

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] problems building php plugin

2014-10-07 Thread Tamer Higazi
I got it solved!
inside plugins/php/uwsgiplugin.py

I set:

ld_run_path = None

to

ld_run_path = '/usr/local/php53-emb/lib'


and it worked!


Am 06.10.2014 um 22:56 schrieb Tamer Higazi:
 Hi people,
 I tried to build the php plugin on a different machine.
 Can somebody tell me how to build the plugin without problems ?!
 
 I have built php as embedded version and installed it on:
 /usr/local/php53-emb
 
 
 
 
 Output:
 
 tamer@tux /usr/local/src/uwsgi-2.0.7 $
 UWSGICONFIG_PHPPATH=/usr/local/php53-emb/bin/php-config python
 uwsgiconfig.py --plugin plugins/php
 using profile: buildconf/default.ini
 detected include path: ['/usr/include', '/usr/local/include']
 *** uWSGI building and linking plugin plugins/php ***
 [x86_64-pc-linux-gnu-gcc -pthread] ./php_plugin.so
 /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld:
 cannot find -lphp5
 collect2: Fehler: ld gab 1 als Ende-Status zurück
 *** unable to build php plugin ***
 
 
 
 for any hints, thank you!
 
 
 Tamer
 

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


[uWSGI] problems building php plugin

2014-10-06 Thread Tamer Higazi
Hi people,
I tried to build the php plugin on a different machine.
Can somebody tell me how to build the plugin without problems ?!

I have built php as embedded version and installed it on:
/usr/local/php53-emb




Output:

tamer@tux /usr/local/src/uwsgi-2.0.7 $
UWSGICONFIG_PHPPATH=/usr/local/php53-emb/bin/php-config python
uwsgiconfig.py --plugin plugins/php
using profile: buildconf/default.ini
detected include path: ['/usr/include', '/usr/local/include']
*** uWSGI building and linking plugin plugins/php ***
[x86_64-pc-linux-gnu-gcc -pthread] ./php_plugin.so
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lphp5
collect2: Fehler: ld gab 1 als Ende-Status zurück
*** unable to build php plugin ***



for any hints, thank you!


Tamer
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] problem running uwsgi with php5 in embedded mode!

2014-09-19 Thread Tamer Higazi
Hi Roberto!
I had taken a look in the Apache documentation, I don't know how to
accomplish that, any hint for me ?!

My VhostEntry in Apache:
VirtualHost shop.mystore.com:80
 ProxyPass / uwsgi://127.0.0.1:3030/
 ProxyPassReverse / uwsgi://127.0.0.1:3030/
/VirtualHost

I have setup apache, because it was easier for me as yet have no idea
about nginx


Thank you for your response.



Tamer


Am 19.09.2014 um 07:17 schrieb Roberto De Ioris:
 php modifier in your frontend proxy ?

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] problem running uwsgi with php5 in embedded mode!

2014-09-19 Thread Tamer Higazi
Hi Roberto!

I got it working... I am really happy.
now I have to figure out, how to set the mime-type as uwsgi gives
everything out as text/html.

uwsgi loads the mime file, but gives back everything to apache with
text/html. Any ideas ?!


LD_LIBRARY_PATH=/usr/local/php5-emb/lib ./uwsgi --plugin
0:plugins/php/php --php-ini /usr/local/php5-emb/lib/php.ini --php-index
index.php --php-docroot /var/www/prestashop --master --socket
127.0.0.1:3030 --processes 4 --chdir /var/www/prestashop --mime-file
/etc/mime.types


Thanks a lott!


Am 19.09.2014 um 14:23 schrieb Roberto De Ioris:
 
 Hi Roberto!
 I had taken a look in the Apache documentation, I don't know how to
 accomplish that, any hint for me ?!

 My VhostEntry in Apache:
 VirtualHost shop.mystore.com:80
  ProxyPass / uwsgi://127.0.0.1:3030/
  ProxyPassReverse / uwsgi://127.0.0.1:3030/
 /VirtualHost

 I have setup apache, because it was easier for me as yet have no idea
 about nginx


 Thank you for your response.


 
 Maybe it is easier to force it in uwsgi itself:
 
 --route-run setmodifier1:14
 
 (ensure internal routing is builtin)
 
 Otherwise you could load the php plugin as the default one prepending it
 with 0:
 
 --plugin 0:path_to_php_plugin
 
 

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] problem running uwsgi with php5 in embedded mode! (solved)

2014-09-19 Thread Tamer Higazi
Adding these 2 parameters solved everything for me:
--check-static /var/www/prestashop/ --static-skip-ext .php


The complete uwsgi parameter:

LD_LIBRARY_PATH=/usr/local/php5-emb/lib ./uwsgi --plugin plugins/php/php
--php-ini /usr/local/php5-emb/lib/php.ini --check-static
/var/www/prestashop/  --static-skip-ext .php --php-allowed-ext .php
--php-index index.php --php-docroot /var/www/prestashop --master
--socket 127.0.0.1:3030 --processes 4 --chdir /var/www/prestashop
--route-run setmodifier1:14



Thanks again, Tamer!


Am 19.09.2014 um 16:16 schrieb Roberto De Ioris:
 
 Hi Roberto!

 I got it working... I am really happy.
 now I have to figure out, how to set the mime-type as uwsgi gives
 everything out as text/html.

 uwsgi loads the mime file, but gives back everything to apache with
 text/html. Any ideas ?!


 LD_LIBRARY_PATH=/usr/local/php5-emb/lib ./uwsgi --plugin
 0:plugins/php/php --php-ini /usr/local/php5-emb/lib/php.ini --php-index
 index.php --php-docroot /var/www/prestashop --master --socket
 127.0.0.1:3030 --processes 4 --chdir /var/www/prestashop --mime-file
 /etc/mime.types


 
 It is because the php engine is serving your static files. Can't you map
 (in apache) only the requests ending with .php to uWSGI ?
 

___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


[uWSGI] problem running uwsgi with php5 in embedded mode!

2014-09-18 Thread Tamer Higazi
Hi people!

I followed the guide, and built the php5 version in embedded mode. Setup
on apache the proxy server and started uwsgi:

LD_LIBRARY_PATH=/usr/local/php5-emb/lib ./uwsgi --plugin plugins/php/php
--master --socket 127.0.0.1:3030 --processes 4 --php-allowed-ext .php
--php-allowed-ext .inc --php-ini /usr/local/php5-emb/lib/php.ini --chdir
/var/www/prestashop

When I open the browser, I get this error message on the shell:

--- no python application found, check your startup logs for errors ---
[pid: 24693|app: -1|req: -1/1] 85.212.100.237 () {60 vars in 1079 bytes}
[Thu Sep 18 19:46:55 2014] GET / = generated 21 bytes in 0 msecs
(HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0)

Can you tell me, what I did wrong ?!


Thanks, Tamer
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi