Glad to hear it :) I don't use the ha-proxy myself atm. If you run into any other issues definitely let me know though. I'd be happy to help if I can.
On Friday, May 10, 2013 8:00:04 AM UTC-5, smoggy wrote: > > Ok, apparently the commenting of > > option httpchk GET / > like > # option httpchk GET / > > solved the issue, now the logs do not get clogged with useless data. > It was just the haproxy that failed to start. > > > On Friday, May 10, 2013 1:37:27 AM UTC+1, smoggy wrote: >> >> I've checked ./haproxy-1.4/conf/haproxy.cfg >> >> and I indeed had >> >> listen express 127.9.181.130:8080 >> option httpchk GET / >> >> i commented that in order to get only tcp based checks instead of http >> ones to keep the logs cleaner. After restarting the cartridge >> with "rhc cartridge reload haproxy-1.4 --namespace my_namespace --app >> my_app " the log file still shows a hit or health check every 3 seconds :/ . >> >> Andrew do your logs also show these events ? have you had any >> configuration changes to prevent this from happening ? >> >> >> On Thursday, May 9, 2013 9:06:13 PM UTC+1, Andrew Replogle wrote: >>> >>> If you're using haproxy are you sure it's not the heartbeat check? >>> >>> On Wednesday, May 8, 2013 5:10:51 AM UTC-5, smoggy wrote: >>>> >>>> Hi folks, >>>> >>>> So in openshift in a python 2.6 cartridge + haproxy i'm having lots of >>>> accesses from openshift ip itself, like one every 3 seconds. I do not have >>>> any cron jobs. Is there a way to figure where these access are coming from >>>> : wsgi, web2py, openshift ? >>>> >>>> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
