[smoothtivo]

I know there are a few people that have been installing Galleon on Linux. I am a bit new to Linux and in the process of installing Galleon on my new linux system. The instructions are a bit confusing to me and I noticed they were updated for version Galleon 1.8. Has anyone got these to work? I am not sure about the 2nd and 3rd step. Anyone have any experience with getting this running?

Thanks,
smoothtivo

Linux

* Install the Java JRE.
* The Java JRE bin directory must be in you system PATH environment variable.
* The JAVA_HOME environment variable must point to the root of the Java JRE installation.
* Disable IPv6.
* Configure your system's name in /etc/hosts under the actual IP address, not 127.0.0.1
* If you are upgrading a previous installation, make a backup of the configure.xml file in the Galleon conf directory.
* Extract the Galleon zip file to a directory.
* Restore the backed up configure.xml file to the Galleon conf directory.
* Make the scripts in the Galleon bin directory executable: chmod a+x *.sh
* Run the Galleon server from the Galleon bin directory: run.sh

 

[azitnay]

Don't let the steps confuse you too much -- just download the JRE (download the RPM from Sun if you want the easiest possible install), and if you run into trouble, ask for help here.

In answer to your question, yes, I have personally run Galleon 1.8.0 fine on a (Fedora Core 4) Linux system.

Drew

 

[smoothtivo]

Sweet thanks for any help.

I have the source files extracted to my home directory and have set the JAVA_HOME to look like this in the run.sh and gui.sh:

JAVA_HOME=/usr/java/jre1.5.0_05

I am assuming that "The Java JRE bin directory must be in you system PATH environment variable." means when i run the program to put the path of java in the command???

Few more questions.
Where do I disable ip6?
What do I put in the host file?

THanks again,

smooth

 

[crumley]

Sweet thanks for any help.
Few more questions.
Where do I disable ip6?
What do I put in the host file?

You may not have to remove ipv6. I run ipv6 and Galleon works fine for me. To see if you are running ipv6 run:
/sbin/lsmod | grep ipv6

If you are running it and you want to stop it, then you will have to prevent the module from loading. The way that works varies a bit between distribtuions, but you'll want to take a look at the /etc/modules* files.

As for the host file, you will want something like :
127.0.0.1 localhost
192.168.0.2 your_hostname

If you are using DHCP to set your ip address, then you may need something a bit different.

 

[azitnay]

Assuming you're using modprobe (Fedora, the only Linux distribution I currently use, does), adding the following lines to /etc/modprobe.conf turns off ipv6:

alias net-pf-10 off
alias ipv6 off

I've never found a reliable way to put it into effect aside from rebooting, but you might be able to stop networking and use depmod.

Drew

 

[smoothtivo]

I am assuming that I have it set up correctly but I get this when I run, run.sh
[[email protected] bin]$ ./run.sh
Exception in thread "main" java.lang.NoClassDefFoundError: while resolving class: org.lnicholls.galleon.util.Tools
at java.lang.VMClassLoader.transformException(java.lang.Class, java.lang.Throwable)

 

[dachtler]

Has anyone looking at this thread made a start/stop file for /etc/init.d for galleon, so you can have it automatically start at boot? I have used one that I found elsewhere on tivocommunity.com (I can't remember where now), and it will work to start galleon if the system is completely booted, but won't work during boot up. Also, the stop command does not work (it uses pkill, which doesn't seem to correctly recognize galleon).

I have 1.9.0 installed and working on Fedora Core 4, except for this one issue.

Thanks,

Jason

 

[crumley]

Hhm, here's the one I use. Note that it is "pkill -f" and that you may have to change the path to your galleon directory. It is a little kludgy because it changes into the galleon bin directory, but that's necessary because of the relative paths in some of the galleon files. It really would be better to define an environment variable for the galleon directory and remove those relative paths.

#!/bin/sh
case "$1" in
start)
echo "Starting Galleon TiVo HME server"
cd /usr/local/galleon/bin; ./run.sh &
;;
stop)
echo "Stopping Galleon TiVo server"
pkill -f galleon
;;
*)
echo "Usage: /etc/init.d/galleon {start|stop}"
exit 1
;;
esac

 

[crumley]

smoothtivo, it looks like it may not be finding all of your galleon installation. Are you sure that you installed all of galleon, and that you are running run.sh from the galleon directory?

 

[azitnay]

Has anyone looking at this thread made a start/stop file for /etc/init.d for galleon, so you can have it automatically start at boot? I have used one that I found elsewhere on tivocommunity.com (I can't remember where now), and it will work to start galleon if the system is completely booted, but won't work during boot up. Also, the stop command does not work (it uses pkill, which doesn't seem to correctly recognize galleon).

I have 1.9.0 installed and working on Fedora Core 4, except for this one issue.

Thanks,

Jason

For your start-at-boot problem, I wonder if bumping down where galleon starts in the chain might help (i.e. maybe it's starting before something else it needs, like networking)... Try giving it a start priority of 99.

Drew

 

[dachtler]

Hhm, here's the one I use. Note that it is "pkill -f" and that you may have to change the path to your galleon directory. It is a little kludgy because it changes into the galleon bin directory, but that's necessary because of the relative paths in some of the galleon files. It really would be better to define an environment variable for the galleon directory and remove those relative paths.

#!/bin/sh
case "$1" in
start)
echo "Starting Galleon TiVo HME server"
cd /usr/local/galleon/bin; ./run.sh &
;;
stop)
echo "Stopping Galleon TiVo server"
pkill -f galleon
;;
*)
echo "Usage: /etc/init.d/galleon {start|stop}"
exit 1
;;
esac

Yup, this is the script. I realized that the version I was using had pkill -f Galleon, with a capital G, which was messing it up. I've now fixed it. I did have it running at 99, and it still didn't load properly, but that's a different problem. Thanks for the help!

 

[smoothtivo]

smoothtivo, it looks like it may not be finding all of your galleon installation. Are you sure that you installed all of galleon, and that you are running run.sh from the galleon directory?

I am running it from the unzipped files\folder (in the bin directory) i got from sourceforge. Do they have to be somewhere when i run them?

-Wes

 

[crumley]

If you didn't move them outside of the galleon directory structure, than that not the problem. By which I mean if you are running from inside GALLEON_TOP_DIR/bin, as opposed to /usr/local/bin, for example, you should be fine.

By the way, have you tried gui.sh? Does it give the same error?

 

[smoothtivo]

im running it from my home folder is that not going to work? Insid e the galleon directory.

 

[smoothtivo]

Here is what I get when I run gui.sh (same errors as run.sh):
[[email protected] bin]$ pwd
/galleon-1.9.0/bin
[[email protected] bin]$ ./gui.sh
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.initializeClass() (/usr/lib/libgcj.so.6.0.0)
at java.lang.Class.forName(java.lang.String, boolean, java.lang.ClassLoader) (/usr/lib/libgcj.so.6.0.0)
at gnu.java.lang.MainThread.run() (/usr/lib/libgcj.so.6.0.0)
Caused by: java.lang.NullPointerException
at java.awt.Window.Window(java.awt.Frame) (/usr/lib/libgcj.so.6.0.0)
at javax.swing.JWindow.JWindow(java.awt.Frame) (/usr/lib/libgcj.so.6.0.0)
at org.lnicholls.galleon.gui.Galleon$SplashWindow.Galleon$SplashWindow() (Unknown Source)
at org.lnicholls.galleon.gui.Galleon.<clinit>() (Unknown Source)
at java.lang.Class.initializeClass() (/usr/lib/libgcj.so.6.0.0)
...2 more

 

[jlgandy]

What are you using for java? If you're not sure take a look at JAVA_HOME. I'm using the rpm's provided by Sun, so mine is JAVA_HOME=/usr/java/jdk1.5.0_05.

Just a guess, but from your output it looks like GCJ... I think Galleon may need Sun's v.1.5 - please correct me if I'm wrong though.

Edit:

http://galleon.sourceforge.net/html/faq.html

Looks like Sun > 1.4.2 is required.

 

[azitnay]

I've definitely never had any luck getting Galleon to run under GCJ.

Drew

 

[crumley]

Up near the top of this thread you say that you set:
JAVA_HOME=/usr/java/jre1.5.0_05

Do you actually have Sun's java installed at that location ?

 

[smoothtivo]

Yes the correct version of sun java is in that folder

 

[smoothtivo]

What does this mean:
" * The Java JRE bin directory must be in you system PATH environment variable."