Redmine, OS X 10.6, Unable to execute validation program

That’s all I can get.

Download, unzip, run, next step after “choosing directory”, boom, all done.

Found another thread, over a year old, same thing, no response from BitNami.

Very disappointing.

S

9 hours ago from a completely dead in the water 1st time user.

No response.

Wow. Awesome.

I filled out the survey. I said that making it work and supporting it would be a good start.

S

Sorry ssteiner,

We are on Spain and this is another time line. What is the exact error?

Hi,

In this thread the user found the problem, he is trying to install in a chroot and the command “df -h” does not run correctly. Is this your case?

No, I started the bitnami-redmine-0.8.6-0-osx-x86-installer.app which I had copied to my desktop.

It started, asked for an installation directory, which I left at the default: /Applications/redmine-0.8.6-0

Pressed “Next”, a dialog pops up with only the text: Unable to execute validation program

The only thing to do is press OK, which brings you back to the same place in the installer.

Changing the installation directory has no effect, it never gets past that step no matter what I do.

I’m guessing the “validation program” needs admin rights but it never prompts for an admin password so there’s nowhere to go…dead in the water.

S

That’s as far as you can get.

Attached Files

Could you post the result of the “df -h” command in a Terminal?

Hi there

I have the same problem (and actually remember having this before) so have run the command you were asking for. As you will see, JungleDisk is what is causing the problems as it returns some funny negative filesystem block counts.

>df -h

df: negative filesystem block count/size from fs /Volumes/JungleDisk
df: negative filesystem block count/size from fs /Volumes/JungleDisk
df: negative filesystem block count/size from fs /Volumes/JungleDisk
df: negative filesystem block count/size from fs /Volumes/JungleDisk
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s2 113Gi 85Gi 27Gi 76% /
devfs 119Ki 119Ki 0Bi 100% /dev
map -hosts 0Bi 0Bi 0Bi 100% /net
map auto_home 0Bi 0Bi 0Bi 100% /home
vfstool@fuse0 16Gi 14Gi 1.4Gi 91% /private/tmp/7563/C
/dev/disk1s1 4.0Mi 584Ki 3.4Mi 15% /Volumes/MacPorts-1.7.0
http://local.JungleDisk.com:2667/jungle/JungleD… -512Bi 0Bi -512Bi 0% /Volumes/JungleDisk

To correct the issue I simply ejected JungleDisk as a volume, and then ran the installer again. See the updated results of the df command:

df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s2 113Gi 85Gi 27Gi 76% /
devfs 119Ki 119Ki 0Bi 100% /dev
map -hosts 0Bi 0Bi 0Bi 100% /net
map auto_home 0Bi 0Bi 0Bi 100% /home
vfstool@fuse0 16Gi 14Gi 1.4Gi 91% /private/tmp/7563/C
/dev/disk1s1 4.0Mi 584Ki 3.4Mi 15% /Volumes/MacPorts-1.7.0

Hope that helps everyone else who has this problem.

Matthew O’Riordan
http://mattheworiordan.com/

Yes, indeed, Jungle disk is reporting a lot of strange stuff (see below).

The volume onto which I’m attempting to install reports:

/dev/disk2s2 275Gi 149Gi 126Gi 54% /Volumes/WDC-1TB-275GB-BOOT

Unfortunately, all those volumes are backup volumes on S3, many of them are being rsync’d on various cron jobs and there are about 20 of them. In other words, a huge pain in the nect to unmount all of them; not going to happen.

This is the only program out of many dozen that I’ve installed had even the slightest hint of a problem and didn’t even know Jungle Disk was doing such an odd thing…

Anyway, yes, I have the same issue; I’ll just wait for a fix from Bitnami. It obviously shouldn’t be hanging on this oddity from Jungle Disk. I’m going to fire off a report the the Jungle Disk pronedt

Thanks,

S

###########################################################################

1. df -h
   df: negative filesystem block count/size from fs /Volumes/J-aere
   df: negative filesystem block count/size from fs /Volumes/J-aere
   df: negative filesystem block count/size from fs /Volumes/s3-bigmac
   df: negative filesystem block count/size from fs /Volumes/s3-bigmac
   df: negative filesystem block count/size from fs /Volumes/S3host64
   df: negative filesystem block count/size from fs /Volumes/S3host64

Hi,

The Stack checks the free space in the installdir parameter page and it needs the output of “df -h” command. We will work on this to fix this issue. Other options are to use the Virtual Machine or the Amazon EC2 image.

Cheers.

From my conversation with Jungle Disk:

JungleAdam, Nov 17 12:18 am (EST):
We will look into fixing this in a future Jungle Disk release. If you are curious, as far as we can tell this is a combination of buggy behavior on the part of both Mac OS X and Jungle Disk’s webdav implementation – Jungle Disk doesn’t provide a response to part of the WebDAV query and which seems to cause OS X to use an uninitialized memory value for the block size.

Unfortunately I can’t give you better information about when it will be fixed but it is on our list.

Thanks,

Adam

ssteiner, Nov 15 11:22 pm (EST):
Their installers http://bitnami.org/ are having problems running because of this whacked out info being returned by JungleDisk from the `df -h` command.

Clues?

1. df -h
   df: negative filesystem block count/size from fs /Volumes/J-aere
   df: negative filesystem block count/size from fs /Volumes/J-aere
   df: negative filesystem block count/size from fs /Volumes/s3-bigmac
   df: negative filesystem block count/size from fs /Volumes/s3-bigmac
   df: negative filesystem block count/size from fs /Volumes/S3host64

Thanks a lot for this info. We really appreciate it.