[27-JUN-2013] [UPDATED] Sorry for another long-ish downtime

BLF Site-related Issues
41

Was the site down again? I couldn’t get on for a while…somewhere around 8:30-10 CDT?

42

Yes, sorry. I appreciate everyone’s patience.

43

Just got some more 502 Bad gateway messages 5 minutes before this post.

44

for the last hour or so BLF has not worked, and has been down many times in the last day :frowning:
i know your doing your best SB

45

Thanks everyone for hanging in all day. I’m going to call it good for now. I think I got it this time. :party:

46

Thank you for all your efforts, this is a great forum. I really miss it when it’s down! :slight_smile:

47

Don't you love computers SB? Lol. I don't miss the days when I did this kind of stuff..

Just in case you're curious - I just got .. this..

    • 0 ms "Content is going to be viewed" has been invoked.
    • 11.118 ms Executing the rule "subscription_user_node_return" on rule set "Content is going to be viewed"
    • 11.292 ms Condition "Check truth: Only act on page views, not teasers" evaluated to TRUE.
    • 11.381 ms Action execution: "Execute custom PHP code"
    • 41.953 ms Loaded variable "acting user"
    • 42.043 ms Evaluation of "Content is going to be viewed" has been finished.
    • 0 ms "After saving a new comment" has been invoked.
    • 0.082 ms Executing the rule "boost_new_comment" on rule set "After saving a new comment"
    • 0.25 ms Action execution: "Execute custom PHP code"
    • 0.344 ms Loaded variable "commented content"
    • 238.771 ms Executing the rule "subscription_comment_autosubscribe" on rule set "After saving a new comment"
    • 239.486 ms Loaded variable "created comment author"
    • 242.383 ms Condition "Textual comparison" evaluated to FALSE.
    • 242.488 ms Action execution: "Flag commented content, under "subscription_subscribed""
    • 312.98 ms Executing the rule "subscription_new_comment" on rule set "After saving a new comment"
    • 328.725 ms Action execution: "rendered_view_subscribed_flag"
    • 448.997 ms Successfully added the new variable "rendered_view_subscribed_flag"
    • 449.153 ms Action execution: "Execute custom PHP code"
    • 621.075 ms Evaluation of "After saving a new comment" has been finished.
    • 0 ms "Content is going to be viewed" has been invoked.
    • 0.515 ms Executing the rule "subscription_user_node_return" on rule set "Content is going to be viewed"
    • 0.724 ms Condition "Check truth: Only act on page views, not teasers" evaluated to TRUE.
    • 0.832 ms Action execution: "Execute custom PHP code"
    • 5.294 ms Loaded variable "acting user"
    • 5.39 ms Evaluation of "Content is going to be viewed" has been finished


Truthfully, those are some pretty god-awful numbers... Something is amiss.. Hundreds of milliseconds in computer time is an ETERNITY.


PPtk

48

:wink: Thanks! I temporarily enabled some debug code to try to debug a different issue. Personally, I don’t believe those millisecond numbers. :slight_smile:

49

Backend is mysql, right? If so, just enable logging (log= line in mysql.conf if memory serves) and then 'tail -f .logfile.'

You can quickly see if those mS numbers are real or not.. Unfortunately, my suspicion is that they are..

PPtk

50

This is pretty cool too.. I'm considering trying it out on our X-Ray image storage server since that Database grows by about 25GB per hour. I'd like a real-time health view.

http://www.graphdat.com/