After our last maintenance period, we received some feedback that more advance notice was desired for planned system maintenance. Therefore, we wanted to give you advance notification that we will be completing a system upgrade next week on Saturday, May 8th from 8:30 p.m. to 10:30 p.m. ET. During this time, all Jungle Disk systems and functionality will be down and inaccessible. We hope this advanced notice will give you time to plan accordingly, as we realize Jungle Disk is an important tool for your personal and business use.
We apologize for the inconvenience. Please feel free to refer to this blog for further updates and real-time status check during the upgrade.
Thank you for your patience and we will make every effort to keep the maintenance window as short as possible.
34 Comments
RSS feed for comments on this post · TrackBack URI
Subscribe to our feed
lsl said,
April 30, 2010 @ 3:26 pm
Does this hold true for those of us with our own AmazonS3 accounts and lifetime software?
Scott Gibson said,
April 30, 2010 @ 3:28 pm
Yes…this applies to all customers.
Max Smolev said,
April 30, 2010 @ 4:00 pm
Does this mean that ability to create Rackspace Cloud disk will be restored afterwards?
Had to ask, it’s been half a year at least, and site still promises free cloud disk space with no chance to claim it
Scott Gibson said,
April 30, 2010 @ 4:02 pm
@Max – Not for this update…but very soon!
Terry Palmer said,
April 30, 2010 @ 4:43 pm
Define “very soon”. I have also been waiting since Feb to use this service as I purchased the plan under the pretense that Rackspace service was available. We talking May? Aug? Dec?
Scott Gibson said,
April 30, 2010 @ 4:47 pm
We expect to have this option return in May.
Terry Palmer said,
April 30, 2010 @ 4:49 pm
That’s awesome news Scott! Thanks.
Troy said,
April 30, 2010 @ 6:17 pm
I have my own S3 account and an old Jungle Disk account since before RackSpace. Please explain why this would affect me. My account/setup should be completely independent of your servers!
Cameron McElhinny said,
April 30, 2010 @ 6:31 pm
I use junglediskmonitor and Amazon S3 – what part of that setup requires your servers to function?
Alex said,
April 30, 2010 @ 8:00 pm
I am not sure I understand – if my JD client connects to Amazon S3, how your system’s maintenance affects that? I thought JD works directly with the storage services and does not have any layers in between?
Shak said,
April 30, 2010 @ 9:36 pm
I hope this downtime means there will be new features/enhancements coming soon!
Scott said,
April 30, 2010 @ 9:56 pm
Hi there, worldwide audience representative here, what’s ET, East Time ? so that’s where, Florida ? So not the rest of us have to work out when the impact will effect us.
Eric2 said,
May 1, 2010 @ 8:35 am
Hi, can you tell about why this upgrade and what it consists of, or is this a secret ?
Duchy Original said,
May 1, 2010 @ 11:35 am
I thought Jungle Disk only depended on Amazon S3. What is this dependency on your systems?
Elliott said,
May 1, 2010 @ 1:49 pm
Does it really matter what the update is? Will it make you feel better? Seriously? Anddddd if you don’t know what ET is then you have no business even talking on here! Seriously????? Like c’mon ppl look stuff up, and don’t ask stupid questions! Great job rack space people! Love the service! Best out there!
Paul said,
May 1, 2010 @ 6:26 pm
I share the concerns other mention above – I would not have signed up for a service which would go down for system maintenance. I’m already facing a potential point of failure relying on Amazon for my storage. Using JungleDisk, it “feels” like my data is “in the cloud,” but it really isn’t. It’s somewhere at Amazon, subject to technical failures at Amazon, and subject to Amazon’s continued existence. If and when Amazon goes away, so does my data.
By saying …
“During this time, all Jungle Disk systems and functionality will be down and inaccessible.”
… am I to understand that I face the same vulnerability with respect to JungleDisk’s technical health and corporate existence ? So I have TWO points of failure with respect to the security of my data? Either one of which is potentially fatal to my business ?
Tim said,
May 3, 2010 @ 5:57 am
According to timeanddate.com, wikipedia etc there’s no such time zone as ET. I’m assuming you mean EDT? You need to appreciate that not everyone lives in the USA and is not familiar with your domestic usage. Given your global coverage you might announce things like this in UCT so that everyone can work out their own impact! And Elliott, there’s no need to be so rude…
Scott Gibson said,
May 3, 2010 @ 2:14 pm
In regard to Lifetime License owners with personal S3 accounts…there is a small chance that this outage would still affect you.
Jungle Disk does do a check for an valid account initially on software startup, as well as once per day. If Jungle Disk were to do that check during the outage, you would temporarily lose the ability to use Jungle Disk during the remainder of the outage.
cb said,
May 5, 2010 @ 10:31 am
If you now say there are checks built in, probably you should drop the startup one and change the daily check to a weekly, (I doubt any ‘hackers’ want a one week window for doing backups), then you could do all maintenance/changes within the week…
Greg said,
May 10, 2010 @ 10:11 am
After the 5/8 maintenance, all of our RSS feeds stopped working. All feeds get this message: 500 – Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed.
Even if I try to create new feeds, I get the same error. These feeds are vital to our company as they are used to generate verification emails to our customers that their backup is running daily.
Scott Gibson said,
May 10, 2010 @ 10:30 am
We do apologize…we should have these issues resolved shortly.
Jason said,
May 10, 2010 @ 11:55 am
Ever since the May 8th upgrade been getting ” xHTTPBadResult – (404)” errors and the backups have been failing. Is this a known issue that will be resolved or should I submit a ticket?
Scott Gibson said,
May 10, 2010 @ 12:02 pm
This is a known issue and we are working hard to get it resolved.
Jason said,
May 10, 2010 @ 12:30 pm
OK, thanks for your quick reply.
Scott said,
May 10, 2010 @ 6:30 pm
I’m getting the same xHTTPBadResult (404) error (error while submitting backup report). The JD logs show the backup is running OK.
Seth said,
May 10, 2010 @ 6:50 pm
I’ve been getting the same xHTtPBadResult error when doing backups. Disabling backup reports stopped the error. This is acceptable, at least in the short term, since I know you’re working on the problem.
However, I’m quite annoyed at the response I got from your Customer Support people. I reported this error, complete with full copy-and-paste verbiage of the error report, so it should have been quite clear that I was just another victim of a known bug. Infuriatingly, the response I got from CS, at 5 PM EDT, was to say they thought it was a connectivity issue, and I should try disabling my anti-virus and firewall.
Jim said,
May 10, 2010 @ 9:35 pm
Scott Gibson, Is there an ETA on a solution on the “xHTTPBadResult – (404)” errors? And I’ve been searching for two days for a solution — is it normal for this sort of system problem to be buried 20 comments down in a 10-day old news item? Everywhere else you check on the site, everything’s reported to be functioning normally.
Scott Gibson said,
May 11, 2010 @ 7:45 am
We do apologize for the delay in getting this resolved. We are working hard to address the problem and expect that this should be resolved soon.
Greg said,
May 11, 2010 @ 10:35 am
Hi Scott. We have noticed that the RSS feeds for backup reports is broken. No new reports have been created since 5/8. These reports are vital to our customers that have purchased the backup service through us. Is this a known problem at JD? Any ETA on the repair?
Scott Gibson said,
May 11, 2010 @ 1:47 pm
These issues should now be resolved…please let us know if any of you are still seeing issues.
Seth said,
May 11, 2010 @ 4:08 pm
The error messages have stopped, and the backup reports are now being created, for the first time since May 8.
The only remaining problem is that the backup reports are not being emailed out.
Scott said,
May 11, 2010 @ 8:27 pm
Same issue as Seth. Reports are not being emailed even though my feed is set to IMMEDIATE. Status update for when this will be resolved please.
Jason said,
May 13, 2010 @ 11:47 am
I got an report emailed to me this morning. Looks like its working.
Eric2 said,
May 14, 2010 @ 7:05 am
So it was indeed a secret …