Its a proud day for us here at FlockMod!
We have acquired and moved to http://flockmod.com/ as of today!
Its been a long road from our simple beginnings…
Here’s a picture of v7 from a couple years back, the earliest version I could find out there still.
Hope you guys enjoy the updates!
Sorry about any downtime the domain switch may have caused.
If you are still having issues accessing the app, you may need to close all flockmod related tabs and clear out your cache.
We had some major issues occur for a few minutes during the transfer that your  browser may have cached.
Luckily, switching domains is not an everyday thing 😛
We shouldn’t have that sort of issue happen again any time soon.
Happy new years everyone!
Flockmod 11.09 is out and we have some new tricks for our moderators!
If you are a mod with user events on in the config, you will now see the reverse dns of users shortly after they connect.
This should help with identifying users switching ip’s or using proxies.
We are also releasing our new tool, codenamed ‘modhax’.
This tool allows moderators to specify a trigger zone, and any users attempting to draw in it will have the specified action applied to them.
This tool will prevent users from developing scripts or tricks to draw faster then the moderators can watch, as it will check in the program to see who did it.
More detail on how to use modhax is available HERE
Enjoy guys,
FDT
11.08A Is out!
Its a hotfix for a few issues.
We have fixed a glitch that allowed misformatted gimp brushes to lag users for long periods of time.
We also fixed issues with the gimp brush allowing users to grey out the board.
The color wheel issue with alpha preview has also been fixed in this release (Sorry we didnt get to it earlier, it turns out it wasnt what we originally thought).
Enjoy!
–FDT
Flockmod 11.08 is out!
Its mostly bug fixes, but boy were they some big bugs!
Classic rooms are now working again
The eraser works normally on size 0 again
And the color wheel no longer glitches up when you switch to black/white.This fix did not work as planned, the glitch may be caused by our production process.
A hotfix will be attempted later on in the day to try to remedy this.Hope you guys enjoy!
–FDT
Good news and bad news.
First off, the bad news.
The server our gallery was on experienced a fairly serious hard drive failure, along with issues rebuilding the raid array.
Fsck was not bringing back our data, and we had to go into full file recovery mode as we had not gotten to the point of making a backup on that server.
We were unable to recover image data to a workable degree.
Much of the image data we did recover, showed signs of the corruption.
Now that the bad news is out of the way.
We did manage to recover the integration code that allows our gallery to integrate with our user accounts and flockmod itself.
This allowed us to restart the gallery on a new server.
We now have backups of this code and that should help with allowing us to restart quicker should this sort of thing happen again.
We are looking into backup solutions for the images themselves, though given the speed of change and the size of the data it is slightly more difficult than the code.
In short, we had a near total hard drive failure within a week of launching the gallery.
This has caused us considerable downtime in attempting to recover the system.
We did not have backups of the system, as it was brand new.
We will try to provide more consistent ant redundancy in the future.
Rest assured that the actual drawing servers are a fair bit stronger then the gallery server.
Murphys law took full effect here though and we got hit in one of the few places we had not made strong yet.
We are extremely sorry about the downtime and confusion, hopefully the gallery’s new home will stave off these issues.
–FDT
So, Figured I owe everyone an update.
The gallery is and has been down again for a while now.
There was a misunderstanding on my part of what the host had done.
They did not migrate the repaired drives to a new machine as I had previously thought.
They placed the repaired drives back into the same box, which came online and started doing data checks in the background but immediately started having problems writing to the drives.
They belived the issue was related to the data checks (an array rebuild) failing under the load of the websites.
They took the OS offline to do the array rebuild without any load.
Then, the array rebuild failed with no load.
They are now running a final test on the drives to verify they are working correctly.
If they are, then the problem most likely lies with the raid controller itself.
They will then replace the raid controller in the server, and rebuild the array one more time.
If they allow the OS to run while it rebuilds, we might be up in 3-4 hours.
If they dont, Its gonna be another 10-12.
We are deeply sorry about the issues, hopefully this gets sorted out soon.
–FDT
So, it turns out that the machine we were running the gallery on was unable to remain online long enough to properly offload the data.
Our host has performed a ddrescue and migration to recover the data and migrate the machine.
Its taken a while, but we are now off that god forsaken failing server, and on to a brand new box!
This should allow us to run much smoother now, and not go offline every 5 hours!
Hopefully this is the end of the gallery server nightmare.
–FDT
Hey again,
Our gallery is back up for the moment!
Our host is still doing some analysis on the machine to see exactly what went wrong and strengthen against it in the future.
But I figured i’d at least post something in the mean time.
This article is going to be mostly for the tech geeks among us,
But feel free to read along if you are just curious whats been going on with the gallery or what we experience behind the scenes.
We had three major issues that caused our gallery to experience downtime, slowness, and errors for the past few days.
The first issue was the driver we were using for our hard drive was in legacy mode more or less.
This caused uploads to lag randomly and error out at times, along with slow image and thumbnail loads.
We became aware of this problem rather quickly, and had it ironed out within about 36 hours.
This one lies on us, I should have been more aware of the difference in speed between the two modes.
I am acutely aware now and this should not happen again.
The second issue we ran into was a failure in our hosts raid array.
This caused complete and total downtime of the gallery, with 502 gateway unavailable error messages when you tried to go to it.
The raid array manages hard drives, if anything is wrong with it it will shut down immediately to prevent data corruption.
The process to bring the raid array back online takes them a couple hours minimum.
Unfortunately, this has happened twice in three days, and three times in two weeks.
They are currently investigating the raid array to try to remedy the problem.
Honestly, This may happen again sometime in the next week to two. I am not convinced they have it stabilized yet.
We are hoping they can keep it under control though.
The third and final issue we’ve ran into was a glitch in our hosts internal networking.
This has caused the on and off lag and long page loads in the gallery.
We have an internal network to send data between our servers in the datacenter.
For some reason, the machine that runs the gallery is having difficulty reaching our database via the internal network.
It has intermittent periods of extremely high connection latency (lag).
It took us quite a while and a lot of back and forth with our hosts tech team to narrow it down to the internal network as the culprit.
We managed to re-route the connection so it bypasses the bad network, and it appears to have fixed the latency issues.
So that’s where we are currently at.
Its been a long couple days for us here trying to keep up with these bugs and issues that have been popping up.
Things seem to be calming down a bit for now, but I could write another one of these tomorrow saying the exact opposite.
We will keep you posted, enjoy the improvements for now.
Hopefully things stay stable and we can move forward with other features soon.–FDT
Hotfix 11.07B is out.
This should allow users to save locally automatically if the gallery is down.
It was supposed to be in 11.07A but that feature was broken.
Which brings me to my next point:
Our gallery has been down a bunch!
Not to mention slow when it is up.
Dont think we haven’t noticed.
Its even down right now, which is why I am pushing this update.
Our host has taken notice and is aware that the machine we are on is having issues.
They are working to bring it back up, and will likely be performing some maintenance soon to try to prevent this in the future.
We will continue to work hard to support this gallery launch,
Please bear with us as we iron out the bugs!–FDT
A hotfix is being released:
11.07A
This hotfix fixes some save glitchyness, preventing multiple saves to the gallery at once and providing a useful popup when a user tries.
(EDIT: this hotfix had a failed launch during the early half of the day, it is not currently out)(Hotfix was re-released successfully about 3-4 hours after failure)