subprocess behave diferent in the server than in the client.

dk

unread,

Mar 30, 2015, 6:53:59 PM3/30/15

to django...@googlegroups.com

hi, I have a button in my webpage that lunch a subprocess and check the ping of the computer and save the information in a text file. that's it, very basic stuff.

If I am doing my click in the server computer everything works,

the subprocess will ping the computer, make the file and save the information.

and go back the corresponding view.

but if I do it from a client computer, does all the script, return the view that needs to return, but it never lunched the subprocess =(. is like that line was commented or something doesn't even complain or spits errors =(

have any one got an issue like this?

Message has been deleted

aRkadeFR

unread,

Mar 31, 2015, 12:45:54 PM3/31/15

to django...@googlegroups.com

What is your production stack (nginx/uwsgi/permissions folder etc. etc.)?
Do you have any logger / stack trace to debug it?

Thanks

On 03/31/2015 05:12 PM, dk wrote:

playing a littlie bit more, I found out that does work if I am using the manage.py runserver.

but doesn't work using the production django =(.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/bb43b536-352e-4eb0-b32a-485860d19e13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.