Instant Infrastructure
Drupal-6.1 Beta IssuesSubmitted by poushag on Fri, 04/04/2008 - 9:07am.I just finished setting up the JumpBox Drupal Beta. The new runtime is a big improvement, however, I do see a couple problems. I hope you JumpBox folks are monitoring this area and will get back to me soon. Thanks. |
Search |
The timezone issue will be
The timezone issue will be fixed in the next public release of the Drupal JumpBox. Thank you for bringing it to our attention.
drupal update - "fetch list of backups" not working
I ran a backup of drupal in preparation for deploying the update to get rid of the timezone issue. The backup ran OK and I can see the file on the samba share in windows explorer. In the jumpbox restore interface, however, nothing shows up when I try to "fetch list of backups". Any ideas?
And I am still interested in making backups to a subfolder in the samba share. Right now my drupal and mantis backups are all mixed in together on the root of the share. Any progress on that?
Regards.
drupal update - "fetch list of backups" not working
What is your old JumpBox version?
You can try the JumpBox to JumpBox restore mechanism and skip the NFS/SMB share all together.
Oh, do you have a dash in your JumpBox hostname?
I will have to double check the Samba sub-directory but I think it should be fixed in the current beta apps (not in the production apps).
Austin
drupal update - "fetch list of backups" not working
I had already done the direct export->import you suggested. I was just reporting a that the fetch doesn't work. I had backups saved from the drupal-0.9 and was trying to fetch the list in the same version. (This was during pre-upgrade testing.) After deploying the 0.9.1 VM the fetch didn't work on it either.
There is no dash in the hostname (since it is still the default, "drupal" as I recall).
Since you said it should wortk, I tried a backup to a subfolder and I am happy to say that it worked fine.
Timetag information is showing up correctly in 0.9.1, so things are moving in the right direction. Just need to address the fetching issue.
Regards.
drupal update - "fetch list of backups" not working
Ok, so let me confirm this with you. You are using a 0.9.1 JumpBox for Drupal 6. When you configure restores to a valid network share that contain drupal or drupal6 JumpBox backups and click "Fetch List of Backups" you don't get the list of the backups you expect to see?
I have tried this internally with 0.9.1 and our upcoming build and see what I should. The hyphenated hostname bug is fixed so thats not a problem. I have tried with both NFS and SMB network share types.
Is there anything specific about your environment that may contribute to this problem? It doesn't show an error of any kind?
AUstin
drupal update - "fetch list of backups" not working
You got it. No errors. Same settings that were used to create the backups.
The only thing I noted that seemed at all unusual was that the backups had filenames that seemed to include the license key and so were pretty long. But even when combined with the path the total length is not anywhere near 256 characters.
mail logfiles
Would you mind mailing me (godber AT jumpbox com) your admin portal logfiles from one of these failing jumpboxes?
tar -czf /tmp/drupal6-logs.tgz /jumpbox/application_portal/logs
What type of network share are you using?
Austin
Drupal-6.1 Beta Issues
Hi,
Thank you for your feedback. We will look into the timezone situation. Does your network require an outbound http proxy?
Austin
Drupal-6.1 Beta Issues
Our network does use an http proxy but I verified that the configuration was successful. So I am looking to you guys to investigate the Drupal update problem.
WRT correcting the time zone offset, do you have an estimate as to when that release will be?
Drupal-6.1 Beta Issues
The application itself does not provide an outbound HTTP proxy setting so there is no real convenient way for us to make it use your proxy. Had they provided a mechanism we would make an effort to set it. This isn't a JumpBox specific problem.
Not to mention, if you are using a JumpBox, the recommended method of updating your application is getting the JumpBox with the updated application version. So the information provided by Drupal's update check is not terribly useful since it won't tell you when a new JumpBox is available.
We may have an updated release some time next week.
Austin
proxy settings
I disagree with your interpretation that Drupal's update check is not useful. I want to be able to use Drupal from within the Jumpbox VM in a way that is transparent. I want to know when Drupal releases updates. This keeps me informed about the status of the Drupal application relative to security issues and bugfixes.
I would like to suggest that even though this isn't a Jumpbox specific problem, your company might want to consider addressing items like this as part of the added value you bring.
Regards.