hi all ...
the official granite pool is down - at no fault of our own ...
here is the official aws post below ...
-------
[RESOLVED] Connectivity Issues in AP-SOUTHEAST-2
On June 4th at 10:25 PM PDT a significant number of EC2 instances and EBS volumes within a single Availability Zone in the AP-SOUTHEAST-2 Region experienced a loss of power. Beginning at this same time, EC2 API calls in the AP-SOUTHEAST-2 Region experienced increased error rates and latencies as well as delays in propagation of instance state data in the affected Availability Zone. Instances and volumes in the other Availability Zones in the AP-SOUTHEAST-2 Region were unaffected. At 11:46 PM PDT, power was restored to the facility and instances and volumes started to recover. At 1:00 AM PDT, 80% of the affected instances and volumes had been recovered by our automated systems. At 2:45 AM PDT the increased error rates and latencies for the EC2 APIs and the delayed propagation of instance state data were fully resolved. A couple of unexpected issues prevented our automated systems from recovering the remaining instances and volumes. The team was able to fix these issues, and by 8:00 AM PDT, all but a small number of instances and volumes were recovered. Since 8:00 AM PDT our teams have been working to recover these remaining instances and volumes. Most of these instances are hosted on hardware which was adversely affected by the loss of power. While we will continue to work to recover any affected instances or volumes, we recommend replacing any remaining affected instances or volumes if possible. Please see
http://aws.amazon.com/instance-help for assistance working with non-responding instances.
-------
what this has done is crash the instance itself - and they have yet to recover the this instance - even though they have fixed their power and production issues ...
this has left us with a predicament that we are trying to resolve currently ...
we are trying to recreate a new instance - based on the last automatic backup of the previous instance ...
this may not work as the backup was made based on the corrupt instance that is what the granite pool is at the moment - a mess ...
we will rebuild a new instance - and currently the new daemon and blockchain are syncing in an effort to retrieve as much transactions as we can ... but this also means that the mpos database may have corrupted also - and as such - transactions could be lost in the process ...
there is no simple solution for this except to restore from an old backup that seems to be still working ( september 2015 ) - and hope that the system can rebuild itself from there ...
we have made quite a few changes since that working backup - with regards to the bonuses for miners and the pool and the settings of the pool ... if the back up works and gets back up and running - we will set the changes back on the pool - and will make sure an alternative measure is taken if indeed this happens again with aws ...
three new pools will be built - each with a different focus - which will happen when the redevelopment of granite starts again in a week or so ... this does not mean they will all be mpos based - but it does mean will have a gamut of pools to work with - regardless of whether this happens again or not ...
support from aws is VERY limited - without paying a large sum of money to get the support - even though its THEIR issue that caused this problem ... so we will work around this within the coming months ...
im still in search of a pool dev to join our ranks - so that these pools will be serviced and maintained and improved - inhouse and on a regular basis ...
a new thread seems imminent - as there doesnt seem to be any way of getting the 'chrysophylax' profile back ...
we do apologize for the hold up - and we will get the pool back up as soon as humanly possible ...
in the meantime - please use the other existing pools to mine granite ( and ozziecoin with some ) ... aikapool - ispace - steakcloud - miningpoolhub - yiimp - zpool ...
if i have left any pools out - ill ammend this post - with links also ... right now - back to the damage control of the pool ...
much appreciated ...
#crysx