A minor update for all of our products is now available. Jungle Disk 3.01 fixes several issues that were found since the initial release of 3.00. We normally would wait a bit longer before releasing a minor update, however we wanted to make sure these fixes were available before enabling automatic updates.
You can download the new version from our Download Center. The release notes for each product are linked from the download page. We’ve enabled automatic updates, so you should also be able to update on Windows/Mac by selecting Check for Updates from the Help menu.
Also, I’m pleased to announce that we’ve taken the new Jungle Disk web interface out of beta. Jungle Disk Desktop and Workgroup users can now access the new interface via https://www.myjungledisk.com. Workgroup users can also use their workgroup domain, although it is no longer required.
31 Comments
RSS feed for comments on this post · TrackBack URI
Subscribe to our feed
Brian Sullivan said,
November 20, 2009 @ 6:36 pm
Hmm workgroup upgrade seems to have lost all my disk mappings (on both Vista and XP machine) – not exactly seamless — had to frig around and shut mappings off and reapply them to get access to stuff — and the old shortcut I used to access the disk (Rackspace CF) seems now defunct with no obvious replacement.
To top it off the mappings even after being reset disappear on a reboot — this is not good. This renders the product bordering on useless for the normal user.
I recommend people do not install this upgrade.
MB said,
November 20, 2009 @ 9:34 pm
Is there a list of fixes for each version available?
Brian Sullivan said,
November 20, 2009 @ 9:34 pm
This only seems to happen if I login immediately after reboot. If I wait a while it seems to reconnect the network mappings and make them available. Some sort of timing issue then.
What can I say — I am impatient – and I am guessing many are as well. At least there is a work around.
Toffer Peak said,
November 20, 2009 @ 9:46 pm
“The release notes for each product are linked from the download page.”
Jungle Dave said,
November 20, 2009 @ 10:44 pm
Hi Brian –
We’ve attempted to reproduce the issue and so far have been unable to. It likely is timing related – if the drives are being mapped exactly while you are logging in, Windows Explorer may not be notified. If they are mapped earlier or later it picks them up.
If for some reason this happens again, you can get them to appear by simply selecting “Remap Network Drive” from the Online Disk menu in Jungle Disk Monitor.
Chris said,
November 21, 2009 @ 7:01 am
Hi Dave,
This blog post in its entirety appears to be loading as the release notes when checking for updates on 3.0 on OSX – not sure if that is intended?
Cheers,
Michael said,
November 21, 2009 @ 11:19 am
I’ve noticed no automatic updates for Linux. Is it possible to have an Ubuntu repository to pull updates from?
chris said,
November 21, 2009 @ 12:09 pm
I too am having problems with this update (3.01) – and I have never had problems with an update before. Upon reboot (Windows 7 x64), I get a screen that tells me of an error in making some connection – sorry I didn’t write it down, and now I cannot get it back. Because now when it starts it is giving me the ‘first time setup’ screen, and asking for my account info. WTF? Not a happy camper, I don’t have hours to spend messing around with this stuff. What can I do to make it just work, like it did for the last two years until this morning?
Isaac Good said,
November 21, 2009 @ 4:54 pm
After install and reboot windows 7 started verrrrry slowly and anything associated with network wasn’t working, had to disable the service, restart again, just to get it to uninstall. And I don’t see 3.0 available anymore so i guess i just sit unprotected until a new version comes along.
rick said,
November 21, 2009 @ 5:12 pm
Could you define how unaided automatic updates work, which is as I recall the way that updates for Server are supposed to happen (as opposed to the management client, where you’re asked)? I assume it waits between jobs, but I’m just guessing as to the timing of when it happens and how often it checks for new versions.
Jungle Dave said,
November 21, 2009 @ 7:11 pm
Michael – we’re planning on setting one up, but don’t have it done yet.
Jungle Dave said,
November 21, 2009 @ 7:11 pm
Rick – that’s an option only on the Windows version. It checks once a day and waits until idle to pull and install the update.
Jungle Dave said,
November 21, 2009 @ 7:12 pm
Isaac – there shouldn’t have been anything changed in 3.01 to cause those symptoms, and we haven’t had any other reports of that. Were you running 3.0 before? Please contact us via http://support.jungledisk.com so we can help diagnose the issue.
Brian Sullivan said,
November 21, 2009 @ 8:01 pm
Jungle Dave – it does seem timing related – I am able to reproduce it every time on both Vista and XP machines on my network. I reboot and login as soon as the password prompt comes up — mapped drives do not appear. If I go away and wait for a few minutes and come back to login all the mappings work. The “Remap Network Drive” work around is a bit tedious when you have 8 or so to reconnect. A few of my users are non-techies — this is beyond their normal capability.
Brian Sullivan said,
November 21, 2009 @ 8:11 pm
Dependent on some service perhaps that takes a while to get started?
Zaro Mulivan said,
November 21, 2009 @ 8:30 pm
I love the cosmetic update, but its slowed down my Windows 7 startup and shutdown considerably. Im using an Intel X25m ssd and my bootup times went from about 32 seconds to over a minute after I installed 3.01. Shutdown hands for several minutes whereby before it was only a few seconds. Whats going on guys?
rick said,
November 22, 2009 @ 1:45 am
Server: After the end of the first job, and after a short verification phase, it compressed and uploaded something called “Backup Database,” about 83MB. Just curious, what is that?
Also, I recall there being an issue in the beta with Exchange transaction logs not being flushed despite JD’s use of VSS. We noticed the same thing with Exchange 2003 on Server 2003 R2–all the logs are still there afterwards. Any progress on this front?
rick said,
November 22, 2009 @ 12:29 pm
I should add, as in the earlier post about Exchange on the beta boards, that the log shows E00.log not being backed up, which may be the crux of the above issue. Details below. I notice also that a few other non-Exchange files also get this same odd Exception code: encrypted files, for one. They’re most definitely not “missing.”
Error Details (Jungle Disk Server Edition 3.01 Win32)
————————
Backup: Failed to backup single file: E00.log
Exception Code: xFileNotFound (18)
Time: Sun Nov 22 04:54:29 2009
Detailed Message: Missing file for backup: H:\Exchange Database Files\Exchsrvr\MDBDATA\E00.log (skipped)
Error Location: BlockBackupManager.cpp:761 BlockBackupManager::BackupFile
via BlockBackupManager.cpp:671 BlockBackupManager::RunFileBackup
Jungle Dave said,
November 22, 2009 @ 9:35 pm
rick – the backup database stores metadata about the backup including the mappings between blocks and files. we’re working on the exchange issue for the next release.
rick said,
November 23, 2009 @ 1:35 am
Thanks. Is this still accurate regarding files encrypted in NTFS?
http://support.jungledisk.com/forums/30233/entries/20734
Every day or two we’ll receive a spate of these warnings in the client, and also in Event Viewer (unfortunately–wish there was a way to not write them to EV but rather to a JD log elsewhere). The ones tonight, for example, lasted about 20 minutes. Is this expected once in a while? There was no job happening at the time.
Description:
Connection to gateway failed: xGatewayTransport – Connection to gateway failed.
OR
Description:
Error Details (Jungle Disk Server Edition 3.01 Win32)
————————
Error receiving data from gateway
Exception Code: xSSLConnectFailed (53)
Time: Sun Nov 22 22:30:03 2009
Detailed Message: HTTPS connection failed: Unknown SSL protocol error in connection to g0.gateway.jungledisk.com:443 [g0.gateway.jungledisk.com]
Error Location: JungleHTTP.cpp:825 JungleHTTP::MakeRequest
via JXRTransport.cpp:634 JDGatewayConnection::ExecuteAsyncThread
Jungle Dave said,
November 23, 2009 @ 10:52 am
rick – we had some hiccups this weekend with the gateway server system which is used to coordinate connections between the server and management client. The huge influx of upgrades and new users required us to deploy additional capacity and the reconfiguration process takes a few minutes right now. It should be back to normal now.
Aelver said,
November 23, 2009 @ 11:07 am
I’m having the same problem currently:
Error Details (Jungle Disk Desktop 3.01 Mac Intel)
————————
Error receiving data from gateway
Exception Code: xSSLConnectFailed (53)
Time: Mon Nov 23 09:06:03 2009
Detailed Message: HTTPS connection failed: Unknown SSL protocol error in connection to g0.gateway.jungledisk.com:443 [g0.gateway.jungledisk.com]
Error Location: JungleHTTP.cpp:825
via JXRTransport.cpp:634
morten said,
November 23, 2009 @ 11:41 am
Same here, constant errors:
Error receiving data from gateway
Error Details (Jungle Disk Desktop 3.01 Mac Intel)
————————
xSSLConnectFailed – HTTPS connection failed: Unknown SSL protocol error in connection to g0.gateway.jungledisk.com:443 [g0.gateway.jungledisk.com]
Exception Code: xSSLConnectFailed (53)
Time: Mon Nov 23 16:14:52 2009
Detailed Message: HTTPS connection failed: Unknown SSL protocol error in connection to g0.gateway.jungledisk.com:443 [g0.gateway.jungledisk.com]
Error Location: JungleHTTP.cpp:825
via JXRTransport.cpp:634
Mike said,
November 23, 2009 @ 1:36 pm
I’m getting this error after this morning’s “upgrade”…
Informational Details (Jungle Disk Desktop 3.01 Mac Intel)
————————
Startup error details
Exception Code: xGatewayTransport (131)
Time: Mon Nov 23 09:33:47 2009
Detailed Message: Connection to gateway failed.
Error Location: JXRTransport.cpp:200
via JXRTransport.cpp:222
via BucketFileChangesProxy.cpp:216
via JungleDiskManager.cpp:308
via JDManagerProxy.cpp:187
other chris said,
November 23, 2009 @ 2:01 pm
I am having same problems with xGatewayTransport errors – this is what required my reconfig of JD yesterday after the new version install. But once the PC went to sleep, this error popped up again on every wakeup. On startup, it prevents startup unless I choose to reconfig JD from zero.
Error on startup:
xGatewayTransport – Connection to gateway failed.
Please contact support with the detailed error information below.
Informational Details (Jungle Disk Desktop 3.01 Win64)
————————
Startup error details
Exception Code: xGatewayTransport (131)
Time: Mon Nov 23 12:56:45 2009
Detailed Message: Connection to gateway failed.
Error Location: JXRTransport.cpp:200 JDGatewayConnection::Connect
via JXRTransport.cpp:222 JDGatewayConnection::Connect
via BucketFileChangesProxy.cpp:216 BucketFileChangesProxy::Connect
via JungleDiskManager.cpp:308 JungleDiskManager::Startup
via JDManagerProxy.cpp:187 JDManagerProxy::Startup
Brandon Oelling said,
November 23, 2009 @ 2:03 pm
Receiving the same gateway connect issues as above. What is the ETA on resolution? In the interim, all backups have ceased functioning through the desktop client.
Mark said,
November 23, 2009 @ 2:36 pm
Is there going to be a reseller edition of the server version? I see the reseller client was updated in the downloads section, but only the workgroup version.
Jungle Dave said,
November 23, 2009 @ 2:54 pm
Mark – we expect to have a reseller version of the server edition by end of the year.
Jungle Dave said,
November 23, 2009 @ 2:57 pm
For those experiencing the gateway errors – we’ve just completed putting additional capacity online to deal with the surge in traffic today. It took longer than expected due to some issues with EC2 that I won’t get into now. If you’re still seeing issues, or if your Server Edition Management client doesn’t see your servers, you may need to restart the service. If that still isn’t working, please contact support and we’ll get it sorted out.
Regarding the issues with Desktop not starting up – this was an issue missed during the beta process. The gateway being unavailable for any reason should not affected the functionality of the Desktop client. We apologize for this and will get it fixed in the next release.
Brandon Oelling said,
November 23, 2009 @ 3:40 pm
Thanks for the fix … we’re up and running.
Jed said,
December 1, 2009 @ 6:56 pm
The new web interface is a significant loss in functionality. The UI is prettier and what-not, if you love JavaScript, etc.
I used to be able to link directly to files… now it is a 404. (Please add an error handler to check if it is possible to do the login then force the download!!!)
So sad.