I’m a new customer with Percussion attempting to install CM1 on a linux virtual machine and I’m having all kinds of problems. My basic steps:
-
Create the virtual machine and install the OS.
-
Install VMware tools (not 100% neccessary, but recommended)
-
Install gawk and sysv-rc-conf
-
Create user for CM1 install (named mine “cm1”)
-
Grab the install package and unpackage it
-
Run linux/setup/SetupConsole.sh
-
Run Percussion/InstallDaemon.sh
-
See the pretty interface at http://my_ip:9992/cm
Here’s my story:
My first attempt was with Ubuntu 9.10. I abandoned step 2 (installing VMware tools) after some difficulty and decided to come back to it later. Steps 3-6 were easy, though for some reason it took a while to download stuff, as if my network were throttled. The biggest problem presented when I attempted step 7 (installing the daemon):
# ./InstallDaemon.sh
./InstallDaemon.sh: 111: Syntax error: Bad fd number
# ./InstallDaemon.awk
: command not found: line 1: {
: command not found: line 2:
./InstallDaemon.awk: line 3: syntax error near unexpected token `('
'/InstallDaemon.awk: line 3: ` n=split( SERVER_DIR, path, ":" )
I looked at some code and couldn’t figure out what was wrong, I decided to try another OS – Debian 5. Oddly, Debian ran faster, downloaded stuff faster, and generally worked more like the well-oiled OS that is linux. Everything went fine up through step 7 (no odd script errors), so I decided to try running CM1 as an application (instead of a daemon) to test it out.
I go to the web interface and BAM! there’s my login page. I don’t know what to put in to that login prompt, but there it is.
So I decide to shut down the application and make sure it runs the same as a daemon. After I do that, I go to the web interface and… uh… get a 404 error.
Well OK, let’s try rebooting the server.
Same problem.
Ok, let’s try stopping the daemon to see if running it as an application still works. I stop the daemon (seemingly no problem) and start the application.
Same problem.
Oddly, the error shows up even if I stop the daemon and don’t start the application. Is it possible that the daemon is refusing to stop when it’s told?
I contacted support, but has anyone else run into this problem? If so, did you ever figure out how to fix it?
EDIT: Belay that order, lieutenant! I figured it out. It was a problem with my /etc/rcx.d/ files.
It turns out that the InstallDaemon script creates all kinds of crap in your rc directories that it doesn’t need:
/etc/rc2.d/S20PercussionD
/etc/rc3.d/S20PercussionD
/etc/rc4.d/S20PercussionD
/etc/rc5.d/S20PercussionD
…when all you really need is:
/etc/rc2.d/S15RhythmyxD
/etc/rc2.d/K15RhythmyxD
Not sure why it has all those extra startup jobs, but they cause problems. I moved them to /etc/rcX.d/no.S20PercussionD, rebooted the server, and now I get a login page when I try to get to the web interface. Now I just have to figure out my login information.