It seems to work for me even without exporting CLASSPATH. I will add it just in case for the future. I know there has been some issue with PHOENIX_HOME, but I have not paid too much attention.

Eric MacAdie

A. Rothman wrote:

I recreated the bug in a virtualbox, and PATH doesn't fix it.


(btw shouldn't the CLASSPATH in your script be exported? does it do anything?)


Amichai


A. Rothman wrote:

Thanks Eric, I'll try adding PATH next time I have some downtime...


I found out about not having environment variables set the hard way - when James wouldn't start at all at first. Then I added JAVA_HOME manually to phoenix.sh which fixed the problem. Are there any non-java components in James that would actually require a PATH?


btw, speaking of environment variables during bootup, I also found that PHOENIX_HOME is being mis-detected in phoenix.sh when booting - submitted a patch.


Amichai


Eric MacAdie wrote:

Here is a script that I use on Ubuntu for James:
http://www.MacAdie.net/opencms/opencms/sites/MacAdie.dot.Net/Java/James/JamesStartScript.html

One problem might be that you are not including the PATH variable in your script. If you are trying to run it as a daemon/service, then the environment that James runs in is pretty empty. You do not get the system variables (like PATH) that you get when you log in.

Eric MacAdie

A. Rothman wrote:
Hi,


I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed as a daemon following the guidelines in the james wiki, and seem to have some DNS problems. If started from the command line, everyting runs fine. But when started by a reboot, the dnsserver* log show that no dns server was auto-detected, as well as java.net.PortUnreachableExceptions when trying to send a message, and the james* log shows the error: "ERROR James: Cannot get IP address(es) for domain.name". I tried to workaround this by explicitly specifying the dns server in the configuration, and now sending messages works ok (no exception), but the latter error remains. So -


1. What reasons might it have to fail at dns autodiscovery only during boot time?

2. Is the error "Cannot get IP address(es) for domain.name" really an error? What implications might this have? Since with the explicitly configured dns server, both sending and receiving messages seem to be ok even with the error shown...

3. Is the dns component really a dns server (as the log name implies)? or a dns client? Should I configure the firewall for a dns server?


Any help would be much appreciated :-)


Amichai

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to