Scalix Forums

Setup:

- SUSE 9.3
- Upgrade from 9.4.0
- 512 MB on Pentium 4, 1.8Ghz.

Every few days, clients try to Send out email through POP3 connection or webmail, and the following error message is popped up:

"An error occurred sending mail: the mail server sent an incorrect greeting: No resources"

Problem is cleared once the server is restarted.

This server has been running since September without any problem. Problems started a month ago. Only changes to server are SUSE 9.3 online upgrades.

Hi Peter,

When the smtpd relay isn't responding, logon to your Scalix server and type:

omstat -a

and let me know what state the smtpd relay is in. Is it aborted or stopped? If it's Stopped, it means it was shut down. If you're running ommaint, you may want to edit the file and search file the line:

daemon="SMTP Relay"

then 8 lines after that, you'll see a line that reads:

$SX_BIN_DIR/omoff -d0 -a "$daemon" >> $MAINTLOG 2> $STDERR

change that line to read:

$SX_BIN_DIR/omoff -d0 -a -w "$daemon" >> $MAINTLOG 2> $STDERR

which will force omoff to wait for the smtpd daemon to stop before continuing. That way the subsequent omon won't error out because the daemon is still shutting down.

Thanks,
Rachel
[/quote]

I delayed in responding because the problem didn't reappear until this morning.
Here's the omstat -a output:

mail:~ # omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 12.22.05
Notification Server Started 12.22.05 0
Shared memory daemon Started NON-STOP
Notification Monitor Started NON-STOP
Session Monitor Started NON-STOP
Container Access Monitor Started NON-STOP
Item Structure Server Stopped
Database Monitor Started 12.22.05
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 12.22.05
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 12.22.05
SMTP Relay Started 12.22.05
Mime Browser Controller Started 12.22.05

This was the status during the SMTP failure.

After this, the only way I could find to restart the entire server. (Is there a command line to restart the scalix server, along with SMTP?)

I'm not running ommaint to my knowledge and it appears to be a scheduling utility. The omoff file is not editable (not a text file) so I am unclear where the recommended omoff line change is suppose to occur.

Please provide details.

Regards,

- Peter

Some Command line functions you'll want are...

omshut - This stops all of Scalix's services.
omrc - This starts them all up again.

Perhaps more importantly.

omoff -d 0 smtpd

This turns off the smtpd service only, with a delay of 0 mins.

omon smtpd

This restarts smtpd.

omon and omoff should allow you to fix smtpd without affecting people's desktops if you restart it during the day.

Hope those help.

Kev.

Hi

I think my problem is similar to the described one.

At infrequent times the smtpd stops and I get the following output on omstat -a

---
PC Monitor Started NON-STOP 0
Directory Relay Server Started 06:10:10
Notification Server Started 06:10:10 0
Shared memory daemon Started NON-STOP
Notification Monitor Started NON-STOP
Session Monitor Started NON-STOP
Container Access Monitor Started NON-STOP
Item Structure Server Stopped
Database Monitor Started 06:10:10
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 06:10:10
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 06:10:10
SMTP Relay Stopped 08:34:11
Mime Browser Controller Started 06:10:10
----

When I restart the service with omon -a smtpd it works until the next stop. What could be the reason therefore?

KR

Hi,

What does your /var/opt/scalix/logs/fatal log say around the time when SMTP stops?

Cheers,
Yuri

Hi
There´s no entry at the moment I saw the stopped daemon, but early in the morning we had the same problem (some minuted befor 6 am) and my colleagues restarted scalix shortly after 6 am.

At this time the last entries are:
SERIOUS ERROR SMTP Relay (SMTPD Relay Pr) Mon Jul 10 05:57:41 2006
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 1886
Procedure trace follows:
<- inet_ParseArpaAddress
-> nm_ParseORN
<- nm_ParseORN
-> nm_PutFieldStr
-> nm_PutFieldMem
-> nm_AppendFieldMem
-> nm_AddSeparators
<- nm_AddSeparators
-> nm_ParseORN
<- nm_ParseORN
<- nm_AppendFieldMem
<- nm_PutFieldMem
<- nm_PutFieldStr
<- inet_ConvArpaORNToORN
-> mim_CloseMapDir
<- mim_CloseMapDir
Pid of logging process: 1886

SERIOUS ERROR SMTP Relay (SMTPD Relay Pr) Mon Jul 10 05:57:41 2006
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x555a13f6]
/opt/scalix/lib/libom_er.so[0x555a16c5]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x555a184f]
[0xffffe500]
/opt/scalix/lib/libom_mim.so(mim_catchUser+0xad)[0x555dcc1d]
/opt/scalix/bin/ommapsmtp[0x8049f49]
/lib/tls/libc.so.6(__libc_start_main+0xe0)[0x55631250]
/opt/scalix/bin/ommapsmtp[0x8049281]
Pid of logging process: 1886

From this moment on there a no new entries.

KR

Are you running ommaint and have you followed the suggestions listed in the reply to peterz?

Thanks,
Rachel

Please make sure you have upgraded to 10.0.1 as this fixes the error you reported.

Cheers

Dave

ScalixSupport wrote:Please make sure you have upgraded to 10.0.1 as this fixes the error you reported.

10.0.1.6 <- new (first) installation in April...

Franziska

ScalixSupport (Rachel) wrote:Are you running ommaint and have you followed the suggestions listed in the reply to peterz?

I would be pleased, if I would know how to start/use ommaint.

If I red correctly, the ommaint outputs are stored in /var/opt/scalix/logs. And there I only find entry like the one of the fatal or the audit. But I don´t find a advice e.g. to do this

ScalixSupport (Dave) wrote:If it's Stopped, it means it was shut down. If you're running ommaint, you may want to edit the file and search file the line: d
aemon="SMTP Relay"
then 8 lines after that, you'll see a line that reads:
$SX_BIN_DIR/omoff -d0 -a "$daemon" >> $MAINTLOG 2> $STDERR
change that line to read:
$SX_BIN_DIR/omoff -d0 -a -w "$daemon" >> $MAINTLOG 2> $STDERR

What is my mistake?

Franziska

Two days ago we start to get the same error: No resources !

We have two servers which synchronize directory and a couple of BB folders.
in SMERR now i have 64441 messages in one who is not respond with that error!!!!!!!!!!
Please HELP !
Where should i look, and what i should check ?

Ont the two Servers SMTPD Relay is working.
How i can delete messages from SMERR ?

mailq says that there is a 19500 messages ( 15 GB ???! , and there are just 300 MB which should be synchronized - and they are synchronized indeed ).

I can see that there is a SMTP communication between them, but very often the one that has a problem - reports No Resources !
There are always about 131 SMTP connections.
Maybe SMTPD daemon cannot handle more ?!?