Site Admin
  • Content count

  • Joined

  • Last visited

  • Days Won

  • Feedback


About refresh

  • Rank
  • Birthday 04/14/1972

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Location
    Brisbane, Australia

Recent Profile Visitors

3,559 profile views
  1. Bingo. Either follow the Water Hole forum at the top, or use the RSS button at the bottom. Follow will send an email notification, RSS will update an RSS reader app.
  2. We send over 60,000 email notices out from the FOH forums per month via Sparkpost. Of those 2,000 daily emails, about 9% bounce and 8% are rejected by the receiving mail hosts. Gmail is by far the largest recipient at 45%. In short, we're gold as far as the server sending emails and peeps getting them, but some don't get through due to being blocked or bounced at the recipient end. Please add to your email whitelist to improve delivery rates. Given the 24:24 threads are new every day (the old ones are deleted), it's impossible to subscribe to those specific threads ahead of time, so follow the Water Hole forum to receive email notices of new threads within it. That should do the job and I can see 217 members already do it. If you're still not getting them, poke around at the Gmail end, because we're definitely sending them An alternative to avoid the risk of missing an email is to subscribe to the RSS feed for the Water Hole, which updates whenever new threads are posted. That of course means using RSS software, but they can typically be configured to notify via email or desktop notification when a new post is received, depending on how frequently you set it to ping the RSS provider. If your RSS app doesn't support email notifications, use something like IFTTT and Pushover -
  3. Just checking in to see how the site has been performing. AFAIK, everything's been pretty good for the last couple of weeks since we ditched the Sitelock CDN, which was causing us more problems than it solved. The root of the server performance issue is not looking like it was traffic capacity when the 24:24 thread is posted, but a faulty MySQL configuration failing during the 24:24 upload. It also appears that MySQL wasn't setup to handle the number of threads we are tossing at it during the spike. Both issues combined to cause a nasty fubar 2-3 times a week. We tested a lot of stuff during this ordeal to pin down the source of the problem. My gut told me something was causing a memory leak (we ruled out pretty much everything else) and I'm confident I was close to the mark. We've got some server optimisations underway that should resolve this bottleneck and hopefully sort this out once and for all. Those changes may cause other unforeseen issues, so please let me know if you see anything odd going on in the coming days. There will likely be a short outage to reboot the server after MySQL is updated, but other than that it should be business as usual.
  4. Thanks gents. The Sitelock page is our content distribution network unable to serve the 24:24 thread due to the volume of members madly clicking refresh to get in before everyone else. The Sitelock page won't display for everyone and if you see it, it should clear within a few minutes of the 24:24 thread going live. Corylax and Akela3rd, hitting refresh should clear the Sitelock page, which may be stuck in your web browser cache. To force a page refresh, type Ctrl+F5 or hold Ctrl while left-clicking the refresh button. Until we get more resources to handle the madness, this will continue if everyone keeps clicking the crap out of the refresh button when the 24:24 thread goes live. It spikes the concurrent CPU threads by 500% and overwhelms 24 CPUs and 16 GB of RAM. We doubled server resources on Friday and it looks to have made no difference. We're reviewing a proposal from our webhost today regarding migrating to Amazon Web Services to handle the 24:24 traffic spike and will get this fixed asap! If there was a better way to post the 24:24 specials, we'd do it.
  5. That's our window of chaos. We're pretty confident we know what we need to do now and a solution is in the works. As a Kiwi supermodel once said, "It won't hippen overnight, but it will hippen." Please bear with us for the next week or two (at a guess) while we sort things out behind the scenes.
  6. Thanks for the update MrGlass, Rob reported the same thing this morning. I think we can rule out the upload, the 24:24 thread was pre-loaded an hour early, then the site crashed when it was set live. The click frenzy is still overwhelming 24 CPUs and 16 GB of RAM, so we have our work cut out trying to get enough resources to handle the spike. We're investigating Amazon Web Services to improve our capacity to ride it out. Thanks for your patience everyone, we'll get there in the end.
  7. That makes perfect sense, however 2-3 minutes before the thread goes live is also when it's uploading, which makes this difficult to pinpoint. Could be the chicken, could be the egg... I've been on FOH with over 500 other site visitors and mashed the refresh button while waiting for the 24:24 thread to appear without any problems. Then the next day, half that number are on the site doing exactly the same thing and we'll get issues. We've doubled our server resources today and will see how things pan out on Monday. If the issue continues, we'll look into further upgrades.
  8. This is a quick appeal to anyone who experiences the dreaded "500" error, or sees a Sitelock "can't access site" error page to post in this thread as soon as possible after it happens. We know the site outages occur when the 24:24 thread is posted. I've experienced the outage myself, but what I can't tell is if errors are happening on the site outside that short window of time when the 24:24 thread goes live. So it would help us to know if anyone has connection issues to the site at other times of the day. What we believe is happening is one of two things - 1. The site is choking on the 24:24 post upload. It's several megabytes in size and is well within server resource limits, but can be slow to upload and taking up to 5 minutes to complete. Sometimes it stalls mid-way and knocks out FOH website access for everyone at Club Czar and us all here at FOH, only for the thread to show up and the issue disappear a few minutes later. Other times it gets through with no problems at all. 2. When the 24:24 thread is posted, we get a traffic spike. Again, the peak is well within server resource limits, but there's a very definite spike as the thread is posted. If traffic was to blame, I'd expect a steady ramp-like build-up as people progressively logged onto the site over 10-15 minutes, which is what happens, rather than an immediate spike we can pinpoint down to the second. Regardless of the cause, the site issues appear to correlate with the upload and/or site stalling. What we don't know is if the upload is causing the site errors, or if it's the traffic spike causing the upload error, or a combination of both. The issue for us is consistency - we can have no problems with 500 users online concurrently one day, then the site will fall over with only 250 online the next. On both occasions, most site visitors are here for the 24:24 thread and I expect everyone's trying to get in to view the offer. If it was definitely due to a traffic spike, surely 500 users would cause us more problems on a busy day than 250 on a quiet day, but it's completely random whether we have a problem or not. Long story short - we know there's a problem when the 24:24 thread is posted. What we don't yet know for sure is why or what's causing it. If you could post in this thread if and when you have problems accessing the site rather than emailing Rob so I can see the timestamps, get a site notification and jump on to check it out myself, that would greatly help our cause.
  9. Done. Don't worry about that Like limit anymore
  10. I'll bump it to 50 PigFish. Honestly, I don't see it as being a problem on this site
  11. There's a little notice to the left of the "Like this button" with the names of members who like your post. It also shows up as a notification in the black menu bar at the top of the screen. Likes can be used to highlight popular posts, but beyond that, does little more than add a bit of friendliness and interaction to the forums. The pissing contest stuff comes wrapped in Reputation, which would appear below the avatar and post count to the left of posts, if we used it. We don't use rep to avoid the bullying that is frequently associated with elitist members intimidating rather than welcoming noobs..."behold my mighty rep count!!1!". Again, petty but true.
  12. No particular reason, it's just set to a limit of 20 by default by the software. I don't think it has much of an impact on server resources, but that might be a consideration. In a community like this, we could probably get away without limits. But members on forums tend to form cliques and they hand out rep and likes to bolster each other's street cred to become the dominant forum gang. I've been on forums where post to like ratio is a thing...petty, but true.
  13. So....leave Likes as is, or bump the limit? It won't affect those who don't use Likes, so I'm more interested in what those who do feel is an appropriate limit. A minor bump to 30 perhaps? Personally, I tend to use Like as an alternative to "+1" or "I agree" posts. I don't hand out Likes like candy, but want that ability on forums that don't have it.
  14. That's why we allow Likes but don't use a Reputation system. Rep ends up being a dick-waving contest whereas Like is a simple way to appreciate forum contributions. I think we can also implement Dislikes, but that ends up with hurt feelings and childish tantrums. It's better to keep things simple and give the odd deserving post a pat on the back, which is why limits are in place. If we need to raise it, we can do that, but open-slather for Likes becomes meaningless.
  15. The problem seems to be that the quality of content is way too high. We have two choices - 1. Write more crap posts 2. Lift the Like limit I can only control the latter, I'll leave the former in less capable hands. I'll bump the limit to 30, 40 or 50 if that'll tickle more pickles. Let me know your preference.

Community Software by Invision Power Services, Inc.