Today I have updated rubyenterpriseedition (20090610) and passenger (2.24)
After that most of my issues has gone :). There is no problem with wiki creation/update. > activemq is a separate daemon all together, there's no reason why > rails would send it a signal. Are you sure about this? I know that, but that was happening for sure. I have made this workaround script, to watch when activemq is down: r...@gitorious:~# cat /usr/local/sbin/activemq_up.sh #!/bin/bash export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/ bin UP=`ps ax | grep java.*activemq | grep -c -v grep` if [ "$UP" == "0" ]; then /etc/init.d/activemq start fi #EOF Today I have excluded this script from the crontab, and after that activemq was ok ?! In the meantime, I have updated few times gitorious installation from http://gitorious.org/gitorious/mainline gitorious-mainline Maybe that fixed activemq shutdown. I was also suspicious to general system causes, because the system is run in the openvz virtual session. 2GB RAM allocated to the vz session, I suppose quite enough for activemq and gitorious/rails. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Gitorious" 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/gitorious?hl=en -~----------~----~----~----~------~----~------~--~---
