Scalix Forums

Hello, it's me again.

I just got done dealing with a big problem on this thread:
http://www.scalix.com/community/viewtopic.php?t=2760

And it apeared that everything was working well. I was doing some testing etc, and I was able to both send and receive mail from SWA, manage things via SAC, etc. Then I tried to use my pop3 client, and I was able to receive mail perfectly fine as I had been able to before. Then I tried to send mail using my client, and I wasn't able to send mail at all, it was as if the server was locking up on the smtp request or something. So then I logged into SWA again to test, and yet again I was able to both send and receive with SWA.

Then I realized that I hadn't rebooted this server since I solved the problem in my last thread, so I rebooted both my router and my server. Now, ever since I did that, I'm unable to connect to the mail server via pop3 or smtp now. So i tried SWA, and I get a popup message saying:

Cannot connect to the mail server mail.domain.com!
The mail server on mail.domain.com appears to be down.

When I try to login to SAC it says:

Could Not login
The administration server is not responding.
You should check the server log files.

I checked the forums, suggestions have been to check several things, and I checked the ones I saw. what I checked are:
/opt/scalix-tomcat/bin/setclasspath.sh - the lines were added to the top as was supposed to be.

ps -aef|grep httpd - httpd is running
ps -aef|grep tomcat - tomcat is running

lsof -i:80 - http is listening on port 80
lsof -i:8009 - localhost.localdomain is listening on several ports, including 8009

I can ping mail.domain.com and it responds properly.

Any suggestions?
Thanks again!
Mito

Hi,

as in the previous post, please post all logfiles again that we had asked you in the other thread. Also, is this box on a dhcp network?

Cheers,

Sascha.

Here's the last 150 lines of caa.log



looks like possibly some kind of java exception, but why that would have changed I don't know...

Oh, and this is not a DHCP network. All IP's (just this machine and the router actually) are static, with no dhcp server running.

The connection on port 389 was refused, so ldap is not running.

Please do omstat -a and look for LDAP Daemon.

Best case, omon ldap should do it.

Cheers,

Sascha.

Wow, should all these things really be aborted?

Strangely, I tried some things, based on the fact that everything was aborted, and this is what transpired:



Then I tried to access my SAC and SWA, and they worked.
This is strange though, as before I rebooted the server (something that I forgot to mention) I did try a 'service scalix restart' and it didn't do any good. Now I will try to send through outlook...

Ok, so I tested my outgoing and incoming mail again, both with SWA and using outlook as a pop3 client, and everything worked. Then I was confused, thinking... why did this happen on a fresh boot?

So I rebooted the server, just to make sure that everything would work on the next time that it boots, and sure enough, it doesn't. I'm getting the same errors as before, and when I do an 'omstat -a' it tells me that all the services are stopped or aborted just like in my post above.

Any ideas where to look to find out why it's doing this on startup?

Mito

Edit: I just tried the cmd 'chkconfig --level 345 scalix on' and rebooted, we'll see how that works...

It worked that time, so apparently the scalix service wasn't set to startup automatically by the installer?

In any case, it's set to install now, just was confusing as I had just expected that it would be set to startup automatically, not sure why it wasn't.

thanks again!

Mito

Hi,

What OS is this machine running?

Thanks,
Yuri

ScalixSupport wrote:Hi,

What OS is this machine running?

Thanks,
Yuri

Fedora Core 4

As I said though, I did get it working, and it did install the service as auto-startup in the original install, just not the uninstall/reinstall.

Also, I checked my services listing via the 'setup' command, and scalix doesn't even show as a valid service, yet all the 'service scalix restart' command etc work properly.

Mito