Gábor Farkas wrote: > ! someone also uses fastcgi :-) > This used to be the first thing in Google by "django fastcgi" :-). > we do not have this problem on our system (at least we think so :-) This is good to hear :-). I have the problem on my virtual hosting where don't actually know what exactly has happened. So may be this was me making something stupid in /etc/rc.d script to start this up. However I have it deployed on another server where things go less unpredictably so I'll watch it. > , and > unfortunately do not know the solution. the RoR world seems to simply > periodically probe the fastcgi processes (open a tcpip connection to him > and check if it responds), and kill&spawn it if it does not respond. > Is there any working script of this kind? Or is it some kind of thing that a decent admin can eat for breakfast every day? :-) > how do you monitor your fastcgi processes? i mean, how do you check if > they are running or not? Well... I don't :-) That time when I saw "Internal server error" I just checked ps -aux | grep fcgi and didn't find anything. So I'm interested in this as well :-)
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
