| Title: | Mailworks-unix |
| Notice: | V2.0.4 now available -- see Note 4.37 5 |
| Moderator: | TAMARA::NEUMAN::Neumann |
| Created: | Wed Jun 02 1993 |
| Last Modified: | Tue Jun 03 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1384 |
| Total number of notes: | 5851 |
Hi, and thanks in advance
Mailworks 2.0-4
We had a situation where a number of mailworks servers conencting to a
remote Mailbus 400 MTA, stopped looking for inbound X.400 mail, after
the remote MTA machine had been unavailable for an approx an hour, but
subsequently became available again.
The usr partition had not filled up on any of the mailworks machines,
and there didn't appear to be anything in the logfiles.
The mailworks servers did continue to send X.400 mail, however it just
built up in the MTA .
To resolve this we stopped and started the mailworks servers with a
S91Mailworks stop and then start, this then causes file cab errors on
the teamlinks clients, and hence extra annoynance for the users.
My questions are then
1. Is there anything to try in the Mailworksrc file to help with this
situation ?
2. If this situation arises again, could we just stop and restart the
X488grecv process, and hence eliminate the filecab errors for the users
? I ask this because the users as a I said could still send mail and
browse their mail drawer o.k.
Thanks again
Andy Hillis
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1379.1 | Some more questions | TAMARA::NEUMAN::Neumann | Stan Neumann | Fri May 23 1997 12:13 | 16 |
First of all, it is safe to stop and restart x488grecv while the system is running, and as you guessed, that would be a *lot* less disruptive to connected users. We did have a problem with the process re-establishing its connection to the MTA, but we thought that we had fixed it with ECO4. In the /var/mta/mta_api_server_address file, do you have LOCAL set as the configuration? Are there any entries in the /var/opt/DMW/logs/x488glog file around this time? If so, can you post an extract of those entries? -Stan | |||||
| 1379.2 | happened again | WOTVAX::HILLIS | Fri May 23 1997 18:01 | 22 | |
Stan
Thanks for the reply.
This problem happened again yesterday (thurs), again for no apparent
reason. We stopped and started the X488grecv process to carry on. Again
there was nothing relevant in the x488glog. I did notice on the
servers that failed, that the process state for X488grecv was IW. I
tried to wake the process with a signal but had to kill -9, and then
restart.
For this occurence by the way, the MTA did not go away at any stage.
The entry in mta_api_server_address is TCP on all remote servers.
When this problem occurs, it seems to effect all the rmeote servers at
the smae time, which leads me to think its aproblem at the MTA end,
however I can see no cause for this on that machine, everything looks
normal.
Thanks again for your help
Andy
| |||||
| 1379.3 | Any ideas? | KERNEL::16.182.96.116::houldingj | Thu May 29 1997 04:31 | 7 | |
Hi Has anyone any ideas on how to progress on this one? Cheers Jill | |||||