Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 0 subscribers
  • Views 13030 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Milter problem with Puremessage for Unix

Hank

Hello

We have had a long-running PureMessage for Unix setup but now today the server just stopped to accept mail. Or rather, it accepts it, but the milter doesn't so the mail comes into the server, but forwarding it to milter doesn't work, it just gives

"PureMessage::Milter::Policy: status write() to parent failed for slot 0"

Milter listens 100025 and talks from 100026

and in the mail-log I get

xxx postfix/smtp[5349]: 81F0A17BD332: to=<yyyy.zz@domain.com>, relay=127.0.0.1[127.0.0.1]:10025, delay=7951, delays=2280/5190/0/480, dsn=4.0.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 450 try later (in reply to end of DATA command))

I have restarted the Milter-service but it dodn't help.

Ane pointers how to proceed or what further information to dig needed a lot...

Some people here are quite angry, so I would appreciate fast answers to deflect their baseball bats.. ;)

wbr, hank

:19493


This thread was automatically locked due to age.
  • 0

    Hi Hank,

    Did anything change recently, like DNS, your OS, IP address or your ISP etc? Do any of the logs in $PMX/var/log show anything? ($PMX is where you chose to install PMX. The default I believe is /opt/pmx).

    Is restarting postfix and PMX as a whole an option?

    Is this all run from a single server?

    Erric

    :19517
  • 0

    There wasn't any change that I was aware - and I should be, if there was ;)

    Actually (and fortunately) we have dual server system and the other is just happily doing what it does every day.

    After the fact I changed the IP of this server and moved the former IP to the working server, because we have a lot of mail so I didn't want to get any more mail misguided.

    In pmx_log I think the first sign of problems is this line:

    4 2011-12-05T21:07:44 [10538,milter] 4EDD1676_10538_15_1: pmx_blocklist: timeout or error querying the blocker daemon
    4 2011-12-05T21:09:21 [10535,milter] 4EDD1676_10535_11_1: pmx_blocklist: timeout or error querying the blocker daemon
    1 2011-12-05T21:09:49 [3174,quarantine] Indexed 12 new messages
    0 2011-12-05T21:23:12 [3047,pmx-blockerd] Error reading from MTA: 104 Connection reset by peer
    0 2011-12-05T21:23:12 [3047,pmx-blockerd] Error reading from MTA: 104 Connection reset by peer
    0 2011-12-05T21:23:12 [3047,pmx-blockerd] Error reading from MTA: 104 Connection reset by peer
    0 2011-12-05T21:23:26 [3047,pmx-blockerd] Error reading from MTA: 104 Connection reset by peer
    0 2011-12-05T21:25:13 [3047,pmx-blockerd] Error reading from MTA: 104 Connection reset by peer
    1 2011-12-05T21:25:58 [3039,Sophos-Engine] sophos: loading DATs from /opt/pmx/etc/data/sophos/4 (was 1): data v2011.12.5.4700004, engine v3.24, SAV v4.70, released 2011/10/03
    1 2011-12-05T21:25:58 [11449,Sophos-SAVI] sophos: loading DATs from /opt/pmx/etc/data/sophos/4: data v2011.12.5.4700004, engine v3.24, SAV v4.70, released 2011/10/03
    1 2011-12-05T21:26:04 [11449,milter] 4EDD15BC_11449_1_1: pmx_spam: loading new data version 2011.12.5.173015

    4 2011-12-05T21:26:05 [10538,milter] 4EDD1676_10538_15_1: error connecting to virus daemon: can't connect to local:/tmp/pmx-vscan.sock: Connection refu
    sed at /opt/pmx/lib/site_perl/5.8.7/i686-linux-thread-multi/PureMessage/Policy/Virus/Client.pm line 39.
    4 2011-12-05T21:26:07 [10535,milter] 4EDD1676_10535_11_1: error connecting to virus daemon: can't connect to local:/tmp/pmx-vscan.sock: Connection refused

    After that it still has worked at least partly with deteriorating performance and finally stalling totally. In other logs I haven't found any problems...

    I have restarted everything, even booted the computer, but no help :(

    hank

    :19533
  • 0

    Hello

    I still don't know how or why, but it started to work after (yet another) server boot and the problem as now is bypassed. Of course the question about the real reason stays... :/

    Thank you for your help, Eric

    :19545
  • 0

    Hi Hank,

    It's good you have more then one server. It looks like the deamons are not starting for some reason. Have you done the normal unix trouble shooting? Checked the memory usage, disk io, etc? Basically made sure that the platform PMX is running on is in good working condition?

    In my experience, problems that go away on their own, return on their own too.

    I can only guess, but if rebooting helped, I wonder if it was a resource issue with the underlaying Unix/Linux OS.

    Erric

    :19569
  • 0

    Hi Hank,

    It looks like there are a number of processes that may be failing, for example pmx-blockerd and the milter (The milter is failing to load virus data).

    These processes can run independantly of each other, so Erric's suggestion to check system resources in general sounds like a good idea.  If you can run any diagnostics on the disk/filesystem that would also be good.

    If you do run into any further urgent problems feel free to call Sophos support. 

    Thanks,

    Tom.

    :19571