Page 1 of 2
Evaluation period has ended - 11.0.2 GA/postgres Problems
Posted: Wed Feb 28, 2007 10:36 am
by l8er
I searched the forums about "evaluation period has ended" and found posts about that error actually being something else, but in my case, it appears to be real. I'm still running the September 2006 version (11.0.0.434) since I have been unable to get any later version running. (See:
viewtopic.php?t=5385). The problem with more recent versions appears to be with the change from Scalix using "localhost" to requiring the FQDN instead of locathost.
Now I've got an unusable version of Scalix running because of the time bomb, and still can't get later versions running.
Anyone? Please? Thanks.
Posted: Wed Feb 28, 2007 11:13 am
by kanderson
As the prerelease version were not meant for production, you will have to use a current version.
Can you install 11.0.1, and we'll address the issues as they arise? I trust this isn't in production yet, is it? (fingers crossed).
Kev.
Posted: Wed Feb 28, 2007 11:37 am
by l8er
With a hosts file containing:
127.0.0.1 localhost.localdomain localhost
127.0.0.1 mymailserver.com mymailserver
It now looks like almost everything is working. I can log in to SWA and SWA mobile, pop3 send and receive works fine, but - from SWA, sending email does not work. A new email ends up in Drafts after choosing Send and won't go out.
Where do I start looking? Thanks.
Posted: Wed Feb 28, 2007 2:40 pm
by kanderson
Ok, first of all, I hate fixing this because it's really broken, and we're going to have to fix it at some point.
Having said that, you'll want to change the SMTP line in /var/opt/scalix/??webmail/swa.properties so that it's the name of your server that someone can resolve from their desktop (Not the server). Right now it'll say localhost, and so the client would try to submit outbound messages to themself.
Can you give me the output from the following:
omshowmnmp
hostname -f
As well as some details of this server? Is it in production now? What kind of maintenance window do you have for it to be down?
Kev.
Posted: Wed Feb 28, 2007 3:24 pm
by l8er
I am a risk taker - so it is a production box, but I can take it down anytime I need to (there are only 6 users).
omshowmnmp:
wegetresults mymailserver.com
hostname -f
mymailserver.com
The box was put together to run Scalix, but I also have a couple of internal web sites that I host on it, too. It's an AMD Athlon 2.2 Ghz, 1.5 GB RAM, 160 GB drive, Fedora Core 5.
Edit: I changed hosts to this:
127.0.0.1 localhost
192.168.100.254 mymailserver.com mymailserver
Then restarted scalix, scalix-postgres, and scalix-tomcat and now it looks like everything is running and working properly. Whoo-hoo!
Posted: Wed Feb 28, 2007 3:52 pm
by kanderson
That's awesome.
I'll consider this closed.
Kev.
Posted: Wed Feb 28, 2007 5:15 pm
by l8er
Well .... I rebooted the box to make sure everything would work following a reboot and - now I can't login to SWA or SAC. Tried changing things back to they were, restarted the services and still can't login. :(
Posted: Wed Feb 28, 2007 5:21 pm
by kanderson
Simple things first...
Are Apache and Tomcat both running?
Kev.
Posted: Wed Feb 28, 2007 5:46 pm
by l8er
Apache is running, but even for the short time Scalix was working, scalix-tomcat reported it was not running. (Searching the forum seems to indicate this is in error, that it may actually be running). Thanks.
Posted: Wed Feb 28, 2007 5:48 pm
by kanderson
ps aux|grep tomcat
Will show it running or not. Make sure it's only running once.
Kev.
Posted: Wed Feb 28, 2007 5:55 pm
by l8er
OK, this is greek to me:
Code: Select all
ps aux|grep tomcat
root 2267 0.9 7.0 728052 109812 ? Sl 14:57 0:32 /usr/java/jre1.
5.0_06/bin/java -server -Djava.net.preferIPv4Stack=true -Xms512m -Xmx512m -Dscal
ix.instance=/var/opt/scalix/qr -Djava.util.logging.manager=org.apache.juli.Class
LoaderLogManager -Djava.util.logging.config.file=/var/opt/scalix/qr/tomcat/conf/
logging.properties -Djava.endorsed.dirs=/opt/scalix-tomcat/common/endorsed -clas
spath /usr/java/jre1.5.0_06/lib/tools.jar:/opt/scalix-tomcat/bin/bootstrap.jar:/
opt/scalix-tomcat/bin/commons-logging-api.jar -Dcatalina.base=/var/opt/scalix/qr
/tomcat -Dcatalina.home=/opt/scalix-tomcat -Djava.io.tmpdir=/var/opt/scalix/qr/t
omcat/temp org.apache.catalina.startup.Bootstrap start
root 6818 0.0 0.0 4784 656 pts/0 R+ 15:53 0:00 grep tomcat
Posted: Wed Feb 28, 2007 7:03 pm
by l8er
OK, this is strange.
If I have the following in my hosts file and reboot the Scalix box everything works execpt sending email from SWA:
127.0.0.1 localhost.localdomain localhost
127.0.0.1 mymailserver.com mymailserver
If I change the second line to:
192.168.100.254 mymailserver.com mymailserver
Then everything works including sending email from SWA.
However, if I reboot the box, then I can't log in to SWA and SAC until I change the hosts file back to:
127.0.0.1 mymailserver.com mymailserver
But then sending email from SWA is broken ....
Any ideas? Thanks.
Posted: Wed Feb 28, 2007 7:12 pm
by kanderson
The Tomcat stuff looks fine.
First a few basic questions. There are no firewalls on your machine, and SElinux is turned off, right?
Can you post the contents of:
head -n 20 /var/opt/scalix/??/webmail/swa.properties
(That's incomplete, but it should be enough).
Kev.
Posted: Wed Feb 28, 2007 10:23 pm
by l8er
Code: Select all
[root@mymailserver ~]# head -n 20 /var/opt/scalix/qr/webmail/swa.properties
swa.version=11.0
swa.email.domain=mymailserver.com
swa.email.imapServer=mymailserver.com
swa.email.smtpServer=mymailserver.com
swa.email.userNameIncludesDomain=false
swa.system.hasCalendar=true
swa.system.hasRulesWizard=true
swa.system.hasOutOfOffice=true
swa.system.hasAutoRefresh=true
swa.system.hasAutoLogin=true
swa.system.hasChangePassword=true
swa.system.maxAttachmentUploadKilobytes=10240
swa.system.minCheckMailMinutes=3
# Comma-separated list of additional fonts to be displayed in the Rich Text editor
swa.system.addtlEditorFonts=
swa.platform.url=http://mymailserver.com/api
[root@mymailserver ~]#
Posted: Thu Mar 01, 2007 11:15 am
by l8er
While rebooting with mymailserver.com set to 127.0.0.1 in hosts and then changing it to 192.168.100.254 and restarting the Scalix services after the box has booted does work - after some period of time Scalix quits communicating with postgres. (SWA becomes very slow and SWA mobile /m won't work). At that point, if I restart all three scalix services (scalix, scalix-postgres and scalix-tomcat) all is well for a while again.