How do you get ScrumWorks Basic working on Debian Linux?

Edit Subject

Have you tried using the Linux installation instructions located here?

http://www.danube.com/docs/scrumworks...

The error message you are getting looks to be that JBoss didn't get installed properly.

Yes, I followed the instructions.

I am afraid I am confused then. Maybe we are looking at different documentation, which page are you getting the information for the run.jar off of?

To correct my question: The installation went fine, it's running the application that doesn't work.

Got it. Well the error message you are seeing is indicating that JBoss isn't starting for some reason.

You might find the reason in the installdirectory\server\scrumworks\log\ directory, possibly in the boot.log or server.log files.

If the system is running another piece of software that requires JBoss that could be causing a conflict. Additionally, I have seen some cases where an error did occur with the installation, but it didn't flat out stop the script from completing. Granted, those cases were for the Pro version of the software, and that was an issue that we resolved in the Pro version, but it may still be effecting Basic.

In those cases reinstalling fixed the issue. Unfortunately since we don't officially provide support for Basic, my resources and experience with the tool are somewhat limited. We try to help where possible however.

Another thing to note about the Linux installation is that it will not include a run.jar. run.sh is what you are looking for. When you install it should explain how to start it.

If you look through the setup.sh file you should see what I am talking about.

If I don't copy the run.jar file, run.sh complains that it's missing.
I don't have a log directory in the installdirectory.
I don't have any other services running, this is a clean debian installation specifically for scrumworks.
see my commands and their results below

root@awave01:/home/scrumworks/scrumworks-1.8.3/bin# ./run.sh
run.sh: Missing required file: /home/scrumworks/scrumworks-1.8.3/bin/run.jar
root@awave01:/home/scrumworks/scrumworks-1.8.3/bin# cp ../../run.jar .
root@awave01:/home/scrumworks/scrumworks-1.8.3/bin# ./run.sh
=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /home/scrumworks/scrumworks-1.8.3

JAVA: /usr/lib/jvm/java-1.5.0-sun/bin/java

JAVA_OPTS: -server -Xms128m -Xmx768m -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh

CLASSPATH: /home/scrumworks/scrumworks-1.8.3/bin/run.jar:/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar

=========================================================================

Failed to boot JBoss:
java.lang.ClassNotFoundException: org.jboss.system.server.ServerImpl
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.system.server.ServerLoader.createServer(ServerLoader.java:285)
at org.jboss.system.server.ServerLoader.load(ServerLoader.java:267)
at org.jboss.Main.boot(Main.java:194)
at org.jboss.Main$1.run(Main.java:464)
at java.lang.Thread.run(Thread.java:595)
root@awave01:/home/scrumworks/scrumworks-1.8.3/bin# ls -F ../server/scrumworks/
clean-hypersonic/ conf/ data/ deploy/
root@awave01:/home/scrumworks/scrumworks-1.8.3/bin#


Have you tried a clean reinstall yet? As I mentioned some of the older ScrumWorks Pro install scripts could have installation problems, and throw an error in a way that didn't stop the installation. That may be what happened here, if JBoss didn't get fully installed that would certainly cause this issue.

Trying to install @scrumworks on #debian lenny for a client. run.jar was not included in tar, then http://servett.net/tmp/scrum-fail.txt

This reply was created from a merged topic originally titled
See the discussion on this issue at this link.

I've reinstalled several times, removing the scrumworks-1.8.3 folder, unzipped and starting the setup again.
I don't see any errors during the install, only when I try to run the application afterwards.

You may look at the jboss_init.sh script. The error comes down to JBoss not starting up for some reason, whether installation issues, permissions, or other, I'm afraid don't know.

I found the problem. unzip was not installed on the server.

The installer should really complain about not being able to unzip a critical package.

That would make sense. One of the pitfalls of using the free version of the software I am afraid.

Glad it is working for you. If you do decide to use our Pro version I suspect you will find things go a lot smoother for you.

Caleb, I am suffering the same problem. I'm especially disturbed by your last comment. It sounds like the "free" version is completely unsupported.

If ScrumWorks wants the kind of viral uptake it sounds like it deserves, the initial impression should be *a lot* smoother.

I've been struggling with an install on a clean image of Ubuntu 8.04 LTS. After a full day, it's still not working. And, I get the same stupid "run.sh: Missing required file" message.

Tell me why I would upgrade to Pro if basic can't get off it's knees???

-Mark
(A frustrated user)

XP should be fine, I know of no issues with it.

Aside from this community page we don't have an official way to incorporate fixes into updates in the tool. But I can say that pretty much everyone in the company reads the community page, so you can be sure the developers and the Product Owner is reading this.

I run ScrumWorks basic on Debian sid just fine. The things I had to be careful of were: (1) which Java was actually being used, (2) I had to use the JDK, not the JRE, and (3) I had to muck around with IPv6 settings. So, for the first part, I had little luck with any of the JVMs I could get normally -- OpenJDK or any of the others. I had to go get the JRE from Sun directly, and install in /usr/lib/jvm. For the second part, running the JRE still had problems in run.sh (missing jars, if I remember correctly). So, as an experiment, running the JDK got rid of most of those. Finally, at least in Debian sid, the file /etc/sysctl.d/bindv6only.conf sets the kernel default to use IPV6 only. Unfortunately, the JDK doesn't know how to do that properly. So, you need to change that file so it says net.ipv6.bindv6only = 0 and restart sysctl.