except that there's no log file being created by this program, and the entry isn't saying who's trying to create it. (I got this same error on a system with a Plesk control panel, and the hosting guys finally discovered it was because the system was creating another file with the wrong userid, so it generated an error on the su_exec.log file, which caused the exact same error to be displayed as here. Only in that case, it at least showed the name of the log file it was having trouble with.)
Yeah, I see it a lot. Once I got the perms fixed on another box, I was able to run this script just fine. It installs a bunch of other stuff. The problem was that I couldn't get the other stuff to run on that machine.
This script has been used by hundreds of people this week to install this app. The problem is that it was developed to work primarily under defaults that cPanel uses. Two people referred me to DreamHost and both said that cPanel is used here. After signing up, it appears that it's not. So now I've got to keep slogging through all these weird issues until I can get the script to work.
The only thing that needs to be changed in this script is the first line that tells where perl is located. I found something on the wiki that says it's in /usr/bin/perl, but I'm not totally convinced of that.
I put this info in the support ticket I submitted. I'm still waiting for a reply. It's a brand new product that was released this past Tuesday to a few hundred people, called JVM2 Fantasos. Does that help?