trivial-rewrite valid_ipv4_hostaddr warning

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

trivial-rewrite valid_ipv4_hostaddr warning

d.hill
I'm getting a very few (only one so far today) warnings in the maillog:

May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning: valid_ipv4_hostaddr: invalid octet count:

and was just curious as to what it is referring to. I went back a few days
worth of logs and do not find the warning.

Postfix v2.5.1 is running on FreeBSD 6.1-RELEASE.

-d
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: trivial-rewrite valid_ipv4_hostaddr warning

Victor Duchovni
On Fri, May 09, 2008 at 04:35:10PM +0000, D Hill wrote:

> I'm getting a very few (only one so far today) warnings in the maillog:
>
> May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning:
> valid_ipv4_hostaddr: invalid octet count:
>
> and was just curious as to what it is referring to. I went back a few days
> worth of logs and do not find the warning.
>
> Postfix v2.5.1 is running on FreeBSD 6.1-RELEASE.

Seen any sender or recipient addresses of the form: user@[192.0.2.1],
but with the number octets != 4? These might not be logged if rejected
as invalid address syntax.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: trivial-rewrite valid_ipv4_hostaddr warning

Wietse Venema
In reply to this post by d.hill
D Hill:
> I'm getting a very few (only one so far today) warnings in the maillog:
>
> May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning: valid_ipv4_hostaddr: invalid octet count:
>
> and was just curious as to what it is referring to. I went back a few days
> worth of logs and do not find the warning.
>
> Postfix v2.5.1 is running on FreeBSD 6.1-RELEASE.

grep 34285 /var/log/maillog, and look at the record that is
logged after the one that you showed above.

Likely it is reject of some kind.

        Wietse
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: trivial-rewrite valid_ipv4_hostaddr warning

d.hill
On Fri, 9 May 2008 at 13:16 -0400, [hidden email] confabulated:

> D Hill:
>> I'm getting a very few (only one so far today) warnings in the maillog:
>>
>> May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning: valid_ipv4_hostaddr: invalid octet count:
>>
>> and was just curious as to what it is referring to. I went back a few days
>> worth of logs and do not find the warning.
>>
>> Postfix v2.5.1 is running on FreeBSD 6.1-RELEASE.
>
> grep 34285 /var/log/maillog, and look at the record that is
> logged after the one that you showed above.
>
> Likely it is reject of some kind.

Grepping for 34285 I saw no rejects. This was found directly following the
log line mentioned above:

May  9 01:30:06 smtpgate postfix/trivial-rewrite[34285]: table cdb:/usr/local/etc/postfix/cgate_transport(0,lock|no_regsub|fold_fix) has changed -- restarting

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: trivial-rewrite valid_ipv4_hostaddr warning

Wietse Venema
D Hill:

> On Fri, 9 May 2008 at 13:16 -0400, [hidden email] confabulated:
>
> > D Hill:
> >> I'm getting a very few (only one so far today) warnings in the maillog:
> >>
> >> May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning: valid_ipv4_hostaddr: invalid octet count:
> >>
> >> and was just curious as to what it is referring to. I went back a few days
> >> worth of logs and do not find the warning.
> >>
> >> Postfix v2.5.1 is running on FreeBSD 6.1-RELEASE.
> >
> > grep 34285 /var/log/maillog, and look at the record that is
> > logged after the one that you showed above.

Shoot. Rejects are logged by smtpd processes, so 34285 is no good.
Best one can do it seems is this:

$ sed -n '1,/valid_ipv4_hostaddr/d;/smtpd/p' /var/log/maillog | head

        Wietse

> > Likely it is reject of some kind.
>
> Grepping for 34285 I saw no rejects. This was found directly following the
> log line mentioned above:
>
> May  9 01:30:06 smtpgate postfix/trivial-rewrite[34285]: table cdb:/usr/local/etc/postfix/cgate_transport(0,lock|no_regsub|fold_fix) has changed -- restarting
>
>
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: trivial-rewrite valid_ipv4_hostaddr warning

d.hill
On Fri, 9 May 2008 at 14:10 -0400, [hidden email] confabulated:

> D Hill:
>> On Fri, 9 May 2008 at 13:16 -0400, [hidden email] confabulated:
>>
>>> D Hill:
>>>> I'm getting a very few (only one so far today) warnings in the maillog:
>>>>
>>>> May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning: valid_ipv4_hostaddr: invalid octet count:
>>>>
>>>> and was just curious as to what it is referring to. I went back a few days
>>>> worth of logs and do not find the warning.
>>>>
>>>> Postfix v2.5.1 is running on FreeBSD 6.1-RELEASE.
>>>
>>> grep 34285 /var/log/maillog, and look at the record that is
>>> logged after the one that you showed above.
>
> Shoot. Rejects are logged by smtpd processes, so 34285 is no good.
> Best one can do it seems is this:
>
> $ sed -n '1,/valid_ipv4_hostaddr/d;/smtpd/p' /var/log/maillog | head

Makes sense now:

[d.hill@smtpgate ~]$ sed -n '1,/valid_ipv4_hostaddr/d;/smtpd/p' /var/log/maillog | head
May  9 01:29:33 smtpgate postfix/smtpd[33567]: warning: Illegal address syntax from cpe-66-24-39-189.stny.res.rr.com[66.24.39.189] in MAIL command: <ewrz7o..4@[>

It looks like in the MAIL command there was just an open bracket and
nothing else. That would make an invalid octet count. Now I see where the
warning is coming from.


>>> Likely it is reject of some kind.
>>
>> Grepping for 34285 I saw no rejects. This was found directly following the
>> log line mentioned above:
>>
>> May  9 01:30:06 smtpgate postfix/trivial-rewrite[34285]: table cdb:/usr/local/etc/postfix/cgate_transport(0,lock|no_regsub|fold_fix) has changed -- restarting
>>
>>
>>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: trivial-rewrite valid_ipv4_hostaddr warning

Wietse Venema
D Hill:
> May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning: valid_ipv4_hostaddr: invalid octet count:
>
> and was just curious as to what it is referring to. I went back a few days
> worth of logs and do not find the warning.

Wietse:
> $ sed -n '1,/valid_ipv4_hostaddr/d;/smtpd/p' /var/log/maillog | head

D Hill:
> Makes sense now:
>
> [d.hill@smtpgate ~]$ sed -n '1,/valid_ipv4_hostaddr/d;/smtpd/p' /var/log/maillog | head
> May  9 01:29:33 smtpgate postfix/smtpd[33567]: warning: Illegal address syntax from cpe-66-24-39-189.stny.res.rr.com[66.24.39.189] in MAIL command: <ewrz7o..4@[>
>
> It looks like in the MAIL command there was just an open bracket and
> nothing else. That would make an invalid octet count. Now I see where the
> warning is coming from.

Yes, that matches the warning, as there was zero text after the '['

The sed command goes more than 30 years back.

    -n
        don't print output by default

    1,/valid_ipv4_hostaddr/d
        delete from the first line through the valid_ipv4_hostaddr warning

    /smtpd/p
        print all lines with "smtpd"

Pretty powerful tool for its day.

        Wietse
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: trivial-rewrite valid_ipv4_hostaddr warning

d.hill
On Fri, 9 May 2008 at 14:42 -0400, [hidden email] confabulated:

> D Hill:
>> May  9 01:29:33 smtpgate postfix/trivial-rewrite[34285]: warning: valid_ipv4_hostaddr: invalid octet count:
>>
>> and was just curious as to what it is referring to. I went back a few days
>> worth of logs and do not find the warning.
>
> Wietse:
>> $ sed -n '1,/valid_ipv4_hostaddr/d;/smtpd/p' /var/log/maillog | head
>
> D Hill:
>> Makes sense now:
>>
>> [d.hill@smtpgate ~]$ sed -n '1,/valid_ipv4_hostaddr/d;/smtpd/p' /var/log/maillog | head
>> May  9 01:29:33 smtpgate postfix/smtpd[33567]: warning: Illegal address syntax from cpe-66-24-39-189.stny.res.rr.com[66.24.39.189] in MAIL command: <ewrz7o..4@[>
>>
>> It looks like in the MAIL command there was just an open bracket and
>> nothing else. That would make an invalid octet count. Now I see where the
>> warning is coming from.
>
> Yes, that matches the warning, as there was zero text after the '['
>
> The sed command goes more than 30 years back.
>
>    -n
> don't print output by default
>
>    1,/valid_ipv4_hostaddr/d
> delete from the first line through the valid_ipv4_hostaddr warning
>
>    /smtpd/p
> print all lines with "smtpd"
>
> Pretty powerful tool for its day.

Thanks for the detailed explination of the sed command. It is one beast
I've been meaning to use but haven't tackled yet.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

mail queue growing - restarting postfix fixes problem

m.c.wilkins
In reply to this post by Wietse Venema

Hi,

I set up a new postfix server about two weeks ago.  Twice I have
arrived at work, discovered that I don't have any new mail over night
(which indicates there might be something wrong with the mail server),
logged into the mail server and done a mailq | wc -l and got back
about 40000.  I know that isn't exactly a measurement of the number of
messages in the queues - but it gives me a rough idea that something
is up.  It appeared that mail was not going out.  

I did a postqueue -f, but that didn't help.  I did a
/etc/init.d/postfix restart, and the proverbial floodgates opened and
the queue drained in about 10 mins or so.

Now looking in the log I see that there were no 'removed' messages (or
infact any) from postfix/qmgr for quite sometime.  Here are the last
few:

May 10 00:38:15 mu-mail1 postfix/qmgr[21295]: 6C0F1125B09: from=<[hidden email]>, size=20286, nrcpt=91 (queue active)
May 10 00:38:15 mu-mail1 postfix/smtpd[20955]: disconnect from tur-mm2.massey.ac.nz[130.123.128.139]
May 10 00:38:15 mu-mail1 postfix/qmgr[21295]: AD685125B9E: removed
May 10 00:38:15 mu-mail1 postfix/qmgr[21295]: A076E125BA9: removed
May 10 00:38:15 mu-mail1 postfix/qmgr[21295]: 28CB4125B4B: removed
May 10 00:38:15 mu-mail1 postfix/qmgr[21295]: A3317124F5C: from=<[hidden email]>, size=5927, nrcpt=1 (queue active)
May 10 00:38:15 mu-mail1 postfix/qmgr[21295]: 98271125970: from=<[hidden email]>, size=1811, nrcpt=1 (queue active)

But then none until about 8am when I restarted postfix.  I didn't
check to see if qmgr was running, perhaps it had died?  The above
messages were the last from qmgr anyway.

I can provide some more of the log if it would be useful, or my config
if you want.  One piece of information that might be useful to know is
that in the middle of the night (starting 23:30) I rebuild some big
postfix hash maps, and also a big courier userdb map.  The courier
userdb map contains about 1.2 million lines, and when I have run the
makeuserdb during the day I see the load average on the mailserver
(linux 2.66GHz, 1G RAM) is about 30, and it is very unresponsive to
interactive tasks like vi/less etc.  I am wondering if this intensive
task is causing something to die, like qmgr?  It doesn't happen every
night.

Any thoughts would be appreciated!

Matt Wilkins

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mail queue growing - restarting postfix fixes problem

Wietse Venema
http://www.postfix.org/DEBUG_README.html#logging

Look for obvious signs of trouble
=================================

Postfix logs all failed and successful deliveries to a logfile.
The file is usually called /var/log/maillog or /var/log/mail; the
exact pathname is defined in the /etc/syslog.conf file.

When Postfix does not receive or deliver mail, the first order of
business is to look for errors that prevent Postfix from working
properly:

% egrep '(warning|error|fatal|panic):' /some/log/file | more

Note: the most important message is near the BEGINNING of the
output. Error messages that come later are less useful.

The nature of each problem is indicated as follows:

    * "panic" indicates a problem in the software itself that only
      a programmer can fix. Postfix cannot proceed until this is
      fixed.

    * "fatal" is the result of missing files, incorrect permissions,
      incorrect configuration file settings that you can fix.
      Postfix cannot proceed until this is fixed.

    * "error" reports an error condition. For safety reasons, a
      Postfix process will terminate when more than 13 of these
      happen.

    * "warning" indicates a non-fatal error. These are problems
      that you may not be able to fix (such as a broken DNS server
      elsewhere on the network) but may also indicate local
      configuration errors that could become a problem later.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mail queue growing - restarting postfix fixes problem

m.c.wilkins



Hi,

On Sun, May 11, 2008 at 05:42:58PM -0400, Wietse Venema wrote:
> % egrep '(warning|error|fatal|panic):' /some/log/file | more

Ok, here is the output of

zcat /var/log/maillog.3.gz | egrep '(warning|error|fatal|panic):' | grep -v 'is older than source file'

(note someone updated a map and forgot to postmap hash: it, so I have
removed them from the outout).

I see a bad command startup from cleanup, that a problem?  A couple
alias loops, and the last two lines are from logwatch that creates a
huge email.  Also the courier pop3d is complaining (high load on
machine about then).

Thanks for any help!

matt


May  9 04:25:39 mu-mail1 postfix/smtp[5052]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 05:49:19 mu-mail1 postfix/smtp[7935]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 07:12:19 mu-mail1 postfix/smtp[10917]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 08:04:11 mu-mail1 postfix/smtp[13644]: warning: numeric domain name in resource data of MX record for lanwood.co.nz: 203.114.138.149
May  9 08:05:08 mu-mail1 postfix/smtp[13623]: 40D11125B57: to=<[hidden email]>, relay=mx.racinstation.net[65.254.254.52]:25, delay=5.3, delays=0.01/0/5.1/0.28, dsn=5.1.1, status=bounced (host mx.racinstation.net[65.254.254.52] said: 550 5.1.1 Host 130.123.129.15 error: B1.1.1 (in reply to RCPT TO command))
May  9 08:10:34 mu-mail1 pop3d: error: No such file or directory
May  9 08:10:34 mu-mail1 pop3d: authentication error: No such file or directory
May  9 08:35:39 mu-mail1 postfix/smtp[16340]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 08:39:37 mu-mail1 postfix/local[16149]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 09:24:27 mu-mail1 postfix/smtp[19762]: warning: numeric domain name in resource data of MX record for dna20.com: 66.160.190.249
May  9 09:47:26 mu-mail1 postfix/local[27915]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 09:59:19 mu-mail1 postfix/smtp[30529]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 10:01:48 mu-mail1 pop3d: error: No such file or directory
May  9 10:01:48 mu-mail1 pop3d: authentication error: No such file or directory
<repeat>
May  9 10:04:51 mu-mail1 pop3d: error: No such file or directory
May  9 10:04:51 mu-mail1 pop3d: authentication error: No such file or directory
<repeat>
May  9 10:16:33 mu-mail1 pop3d: error: No such file or directory
May  9 10:16:33 mu-mail1 pop3d: authentication error: No such file or directory
May  9 10:41:30 mu-mail1 postfix/sendmail[6231]: warning: premature end-of-input on /usr/sbin/postdrop -r while reading input attribute name
May  9 10:41:30 mu-mail1 postfix/sendmail[6231]: warning: command "/usr/sbin/postdrop -r" exited with status 11
May  9 10:41:30 mu-mail1 postfix/sendmail[6231]: fatal: rbuchana(23451): unable to execute /usr/sbin/postdrop -r: Success
May  9 10:41:31 mu-mail1 postfix/local[3262]: 9E147125AA2: to=<[hidden email]>, orig_to=<[hidden email]>, relay=local, delay=1.2, delays=0.01/0/0/1.2, dsn=5.3.0, status=bounced (service unavailable. Command output: sendmail: warning: premature end-of-input on /usr/sbin/postdrop -r while reading input attribute name sendmail: warning: command "/usr/sbin/postdrop -r" exited with status 11 sendmail: fatal: rbuchana(23451): unable to execute /usr/sbin/postdrop -r: Success )
May  9 10:57:33 mu-mail1 postfix/smtp[7562]: warning: numeric domain name in resource data of MX record for dna20.com: 66.160.190.249
May  9 11:00:06 mu-mail1 postfix/local[8080]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 11:05:58 mu-mail1 postfix/smtp[7625]: warning: numeric domain name in resource data of MX record for oreganarndt.co.nz: 203.79.125.200
May  9 11:18:19 mu-mail1 pop3d: error: No such file or directory
May  9 11:18:19 mu-mail1 pop3d: authentication error: No such file or directory
May  9 11:22:19 mu-mail1 postfix/smtp[14403]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 11:23:15 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 14589 killed by signal 11
May  9 11:23:15 mu-mail1 postfix/master[24487]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
May  9 11:55:30 mu-mail1 pop3d: error: No such file or directory
May  9 11:55:30 mu-mail1 pop3d: authentication error: No such file or directory
May  9 12:01:36 mu-mail1 pop3d: error: No such file or directory
May  9 12:01:36 mu-mail1 pop3d: authentication error: No such file or directory
May  9 12:02:00 mu-mail1 pop3d: error: No such file or directory
May  9 12:02:00 mu-mail1 pop3d: authentication error: No such file or directory
May  9 12:15:24 mu-mail1 postfix/local[24555]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 12:30:01 mu-mail1 postfix/local[24552]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 12:37:30 mu-mail1 postfix/smtpd[28883]: warning: Illegal address syntax from tur-mm2.massey.ac.nz[130.123.128.139] in RCPT command: <'[hidden email]'>
May  9 12:45:44 mu-mail1 postfix/smtp[24062]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 12:53:55 mu-mail1 postfix/local[28893]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 13:06:11 mu-mail1 postfix/local[1259]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 13:27:13 mu-mail1 postfix/local[5394]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 13:40:11 mu-mail1 postfix/local[5343]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 14:09:10 mu-mail1 postfix/smtp[14561]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 15:32:21 mu-mail1 postfix/smtp[30361]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 15:34:09 mu-mail1 postfix/local[28155]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 15:40:29 mu-mail1 postfix/local[31164]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 15:59:12 mu-mail1 postfix/smtp[679]: warning: numeric domain name in resource data of MX record for mafic.ac.cn: 210.77.146.69
May  9 16:06:38 mu-mail1 postfix/smtp[2468]: warning: numeric domain name in resource data of MX record for eastcoast.familyworks.org.nz: 125.236.215.206
May  9 16:07:05 mu-mail1 pop3d: error: No such file or directory
May  9 16:07:05 mu-mail1 pop3d: authentication error: No such file or directory
May  9 16:07:28 mu-mail1 pop3d: error: No such file or directory
May  9 16:07:28 mu-mail1 pop3d: authentication error: No such file or directory
May  9 16:22:54 mu-mail1 postfix/smtp[7442]: warning: valid_hostname: empty hostname
May  9 16:22:54 mu-mail1 postfix/smtp[7442]: warning: malformed domain name in resource data of MX record for mn.rr.com:
May  9 16:36:30 mu-mail1 postfix/smtp[11970]: warning: numeric domain name in resource data of MX record for fosun.com.cn: 202.136.217.139
May  9 16:55:36 mu-mail1 postfix/smtp[16598]: warning: numeric domain name in resource data of MX record for dslawyer.com: 211.96.225.115
May  9 16:55:59 mu-mail1 postfix/smtp[16302]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 17:17:53 mu-mail1 postfix/local[17540]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May  9 17:21:51 mu-mail1 pop3d: error: No such file or directory
May  9 17:21:51 mu-mail1 pop3d: authentication error: No such file or directory
May  9 17:22:08 mu-mail1 pop3d: error: No such file or directory
May  9 17:22:08 mu-mail1 pop3d: authentication error: No such file or directory
May  9 17:22:23 mu-mail1 pop3d: error: No such file or directory
May  9 17:22:23 mu-mail1 pop3d: authentication error: No such file or directory
May  9 17:24:09 mu-mail1 pop3d: error: No such file or directory
May  9 17:24:09 mu-mail1 pop3d: authentication error: No such file or directory
May  9 18:06:50 mu-mail1 postfix/smtp[23706]: 25B6D125D20: to=<[hidden email]>, relay=mx.baron.co.nz[65.254.254.50]:25, delay=1.7, delays=0.36/0/1/0.3, dsn=5.1.1, status=bounced (host mx.baron.co.nz[65.254.254.50] said: 550 5.1.1 Host 130.123.129.15 error: B1.1.1 (in reply to RCPT TO command))
May  9 18:19:12 mu-mail1 postfix/smtp[27847]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 19:04:19 mu-mail1 postfix/smtp[31800]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:04:34 mu-mail1 postfix/smtp[31809]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:08:52 mu-mail1 postfix/smtp[31809]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:09:37 mu-mail1 postfix/smtp[413]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:15:26 mu-mail1 postfix/smtp[413]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:21:48 mu-mail1 postfix/smtp[404]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:26:14 mu-mail1 postfix/smtp[1406]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:26:14 mu-mail1 postfix/smtp[1409]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:26:15 mu-mail1 postfix/smtp[1419]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:42:29 mu-mail1 postfix/smtp[2390]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 19:42:55 mu-mail1 postfix/smtp[2365]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:43:01 mu-mail1 postfix/smtp[2432]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:43:10 mu-mail1 postfix/smtp[2407]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:47:57 mu-mail1 postfix/smtp[2396]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:59:34 mu-mail1 postfix/smtp[2473]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:59:35 mu-mail1 postfix/smtp[3416]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 19:59:37 mu-mail1 postfix/smtp[3452]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 20:16:15 mu-mail1 postfix/smtp[4552]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 20:16:15 mu-mail1 postfix/smtp[3357]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 20:16:16 mu-mail1 postfix/smtp[4570]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 20:16:17 mu-mail1 postfix/smtp[4569]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 20:17:43 mu-mail1 postfix/smtp[4555]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 20:18:18 mu-mail1 pop3d: error: No such file or directory
May  9 20:18:18 mu-mail1 pop3d: authentication error: No such file or directory
May  9 20:18:33 mu-mail1 pop3d: error: No such file or directory
May  9 20:18:33 mu-mail1 pop3d: authentication error: No such file or directory
May  9 20:20:10 mu-mail1 pop3d: error: No such file or directory
May  9 20:20:10 mu-mail1 pop3d: authentication error: No such file or directory
May  9 20:20:14 mu-mail1 postfix/smtp[3359]: warning: no MX host for i2r.a-star.edu.sg has a valid address record
May  9 20:44:18 mu-mail1 pop3d: error: No such file or directory
May  9 20:44:18 mu-mail1 pop3d: authentication error: No such file or directory
May  9 20:47:41 mu-mail1 pop3d: error: No such file or directory
May  9 20:47:41 mu-mail1 pop3d: authentication error: No such file or directory
May  9 21:05:40 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/smtp pid 8974 killed by signal 11
May  9 21:05:40 mu-mail1 postfix/master[24487]: warning: /usr/libexec/postfix/smtp: bad command startup -- throttling
May  9 21:05:50 mu-mail1 postfix/smtp[8964]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 21:15:56 mu-mail1 postfix/smtp[8912]: warning: no MX host for bounce.intentmail.emsystem.co.uk has a valid address record
May  9 21:16:06 mu-mail1 postfix/smtp[8921]: warning: numeric domain name in resource data of MX record for fseager.com: 218.106.249.54
May  9 22:27:28 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 13874 killed by signal 11
May  9 22:27:28 mu-mail1 postfix/master[24487]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
May  9 22:29:10 mu-mail1 postfix/smtp[13997]: warning: no MX host for kiwionline.co.nz has a valid address record
May  9 23:52:20 mu-mail1 postfix/smtp[18858]: warning: no MX host for kiwionline.co.nz has a valid address record
May 10 00:00:02 mu-mail1 postfix/local[17782]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
<repeat>
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Resource temporarily unavailable
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Input/output error
May 10 00:56:25 mu-mail1 pop3d: authentication error: Resource temporarily unavailable
May 10 00:56:25 mu-mail1 pop3d: authentication error: Resource temporarily unavailable
May 10 00:56:25 mu-mail1 pop3d: authentication error: Resource temporarily unavailable
May  9 16:07:53 mu-mail1 postfix/postdrop[26738]: warning: uid=0: Illegal seek
May 10 04:07:53 mu-mail1 postfix/sendmail[26734]: fatal: root(0): queue file write error
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mail queue growing - restarting postfix fixes problem

Wietse Venema
> May  9 11:23:15 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 14589 killed by signal 11
> May  9 21:05:40 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/smtp pid 8974 killed by signal 11
> May  9 22:27:28 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 13874 killed by signal 11

That is not good. Is this ECC memory?

        Wieste
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mail queue growing - restarting postfix fixes problem

Colin Campbell-2
Hi,

On Sun, 2008-05-11 at 22:10 -0400, Wietse Venema wrote:
> > May  9 11:23:15 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 14589 killed by signal 11
> > May  9 21:05:40 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/smtp pid 8974 killed by signal 11
> > May  9 22:27:28 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 13874 killed by signal 11
>
> That is not good. Is this ECC memory?

Without having followed this too closely I'll stick my neck out here and
suggest it's the result of running up2date/yum regularly without
rebooting. Libraries get updated but the kernel doesn't and this starts
to happen. A reboot will more than likely fix this. I see this a lot.

Colin
--
Colin Campbell
Unix Support/Postmaster/Hostmaster
Citec
+61 7 3227 6334
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mail queue growing - restarting postfix fixes problem

m.c.wilkins
In reply to this post by Wietse Venema

Hi,

On Sun, May 11, 2008 at 10:10:21PM -0400, Wietse Venema wrote:
> > May  9 11:23:15 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 14589 killed by signal 11
> > May  9 21:05:40 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/smtp pid 8974 killed by signal 11
> > May  9 22:27:28 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 13874 killed by signal 11
>
> That is not good. Is this ECC memory?

I agree, it doesn't look good at all.  Yip it is ECC (2GB of 2-way
interleaved PC2100 DDR SDRAM running at up to 266MHz with Advanced
ECC).

Matt Wilkins

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mail queue growing - restarting postfix fixes problem

m.c.wilkins
In reply to this post by Colin Campbell-2


On Mon, May 12, 2008 at 12:22:58PM +1000, Colin Campbell wrote:

> Hi,
>
> On Sun, 2008-05-11 at 22:10 -0400, Wietse Venema wrote:
> > > May  9 11:23:15 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 14589 killed by signal 11
> > > May  9 21:05:40 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/smtp pid 8974 killed by signal 11
> > > May  9 22:27:28 mu-mail1 postfix/master[24487]: warning: process /usr/libexec/postfix/cleanup pid 13874 killed by signal 11
> >
> > That is not good. Is this ECC memory?
>
> Without having followed this too closely I'll stick my neck out here and
> suggest it's the result of running up2date/yum regularly without
> rebooting. Libraries get updated but the kernel doesn't and this starts
> to happen. A reboot will more than likely fix this. I see this a lot.

Well on Apr 05 04:59:08 I received a new kernel (2.6.18-53.1.14.el5)
from redhat.  I suspect I have recieved a whole bunch of library
updates too.  You are correct, I haven't rebooted the box ;-)  Still
running an older kernel 2.6.18-8.el5.

I'll schedule a reboot and see if this happens again.

Thanks!

Matt Wilkins

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: mail queue growing - restarting postfix fixes problem

Ralf Hildebrandt
In reply to this post by m.c.wilkins
* [hidden email] <[hidden email]>:

> May  9 08:39:37 mu-mail1 postfix/local[16149]: warning: unable to lookup :include: file /var/spool/majordomo/lists/itslabs: No such file or directory

You need to fix that as well

--
Ralf Hildebrandt ([hidden email])          [hidden email]
Postfix - Einrichtung, Betrieb und Wartung       Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
If we can dispel the delusion that learning about computers should be
an activity of fiddling with array indexes and worrying whether X is
an integer or a real number, we can begin to focus on programming as a
source of ideas.
Loading...