For the sake of completeness I am gonna respond to this questions even though the issue is now solved.
> > Hmmm, maybe it is an Amazon issue. > It was in fact a Xen(Virtualization) issue, maybe other applications were having problems too, not only apache. > > Help me to understand the problem a bit better though. > > When you do run: > > /etc/init.d/apache2 start > > are you saying that that command itself hangs, or that any request > against Apache hangs, or the whole system hangs? > The command itself hangs. Apache just does not start ( Nothing written to the logs, any request says no server is listening), the system still works ( I can login to other ssh session while the command is hung up, and it responds to Ctr-C) > > How many Apache processes do you see running? How much memory are they > using? Do the Apache processes appear to be doing straight away and > are then replaced with new ones? Ie., a fork bomb due to startup > failure? > Didn't have chance to see this in detail (but there were two apache2 processes and one apachectl) > > How have you configured mod_wsgi, are you trying to use daemon mode? > Yes it was daemon mode. > > Graham > Again thanks for your support, mod_wsgi is great. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
