smtpd core dumps on Solaris

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

smtpd core dumps on Solaris

Eugene Krasikov-2
Hello all,

I have Postfix 2.5.1 running on Solaris 10 SPARC. The problem is that smtpd daemon crashes occasionally. Some core dump related information is placed below.
Probably the cause is non-null-terminated string somewhere? I understand that the reason isn't probably Postfix, but Solaris; anyway, has anybody seen this bug before or can tell something about it? I can't found anything related in Solaris bugs description or google.


core.smtpd.16849.100  core.smtpd.17835.100  core.smtpd.18771.100  core.smtpd.18947.100 
root@mx1 /var/tmp# pflags core.smtpd.18947.100
core 'core.smtpd.18947.100' of 18947:   smtpd -n smtp -t inet -u -o stress= -o receive_override_options=no_add
        data model = _LP64  flags = ORPHAN|MSACCT|MSFORK
 /1:    flags = 0
        sigmask = 0xffffbefc,0x0000ffff  cursig = SIGSEGV

root@mx1 /var/tmp# pstack core.smtpd.18947.100
core 'core.smtpd.18947.100' of 18947:   smtpd -n smtp -t inet -u -o stress= -o receive_override_options=no_add
 ffffffff7eb3b650 strlen (1001adb90, ffffffff7fffe988, 10019c140, 1001ab900, 1001afdc0, 0) + 50
 ffffffff7ee31620 getipnodebyaddr (ffffffff7ffff134, 4, 10019b8a0, ffffffff7fffe988, b48, 0) + 558
 ffffffff7f1069a4 getnameinfo (ffffffff7ffff130, 6f2e, ffffffff7fffeb14, 2, 0, 4) + 12c
 000000010004d3a0 sockaddr_to_hostname (401, 10, ffffffff7fffeb14, 0, 0, 100000) + 48
 00000001000231e8 smtpd_peer_init (ffffffff7ffff0c0, 100173000, 2, 100173000, 100173, 1001705e8) + 604
 0000000100022a7c smtpd_state_init (ffffffff7ffff0c0, 100062, 100000, 100173000, 100173, 100000) + 17c
 0000000100016558 ???????? (1001a0370, ffffffff7ffffdf9, 100000, 10005d000, 10005d, 100000)
 000000010002551c ???????? (100000, 1001a0370, 100171000, 100171, 100000, 100171000)
 00000001000259d8 ???????? (100171, 6, 62, 100171f88, 100000, 1c)
 0000000100048748 event_loop (100198040, 1, 6, ffffffff7ffff64f, 10006a898, ffffffff7ffff648) + 408
 0000000100027c64 single_server_main (1, 10017c1d0, 100197800, 9, 64, c) + 1e80
 0000000100016e60 main (c, ffffffff7ffffc88, 100016000, 100016, 100000, 100016670) + 114
 000000010000fb1c _start (0, 0, 0, 0, 0, 0) + 17c

--
Thank you,
Eugene Krasikov
Reply | Threaded
Open this post in threaded view
|

Re: smtpd core dumps on Solaris

Wietse Venema
Eugene Krasikov:
> Hello all,
>
> I have Postfix 2.5.1 running on Solaris 10 SPARC. The problem is that smtpd
> daemon crashes occasionally. Some core dump related information is placed
> below.
> Probably the cause is non-null-terminated string somewhere? I understand

The getnameinfo() SYSTEM LIBRARY function does not have null-terminated
string INPUT arguments. Perhaps you have been making changes in
nsswitch.conf.

        Wietse

> that the reason isn't probably Postfix, but Solaris; anyway, has anybody
> seen this bug before or can tell something about it? I can't found anything
> related in Solaris bugs description or google.
>
>
> core.smtpd.16849.100  core.smtpd.17835.100  core.smtpd.18771.100
> core.smtpd.18947.100
> root@mx1 /var/tmp# pflags core.smtpd.18947.100
> core 'core.smtpd.18947.100' of 18947:   smtpd -n smtp -t inet -u -o stress=
> -o receive_override_options=no_add
>         data model = _LP64  flags = ORPHAN|MSACCT|MSFORK
>  /1:    flags = 0
>         sigmask = 0xffffbefc,0x0000ffff  cursig = SIGSEGV
>
> root@mx1 /var/tmp# pstack core.smtpd.18947.100
> core 'core.smtpd.18947.100' of 18947:   smtpd -n smtp -t inet -u -o stress=
> -o receive_override_options=no_add
>  ffffffff7eb3b650 strlen (1001adb90, ffffffff7fffe988, 10019c140, 1001ab900,
> 1001afdc0, 0) + 50
>  ffffffff7ee31620 getipnodebyaddr (ffffffff7ffff134, 4, 10019b8a0,
> ffffffff7fffe988, b48, 0) + 558
>  ffffffff7f1069a4 getnameinfo (ffffffff7ffff130, 6f2e, ffffffff7fffeb14, 2,
> 0, 4) + 12c
>  000000010004d3a0 sockaddr_to_hostname (401, 10, ffffffff7fffeb14, 0, 0,
> 100000) + 48
>  00000001000231e8 smtpd_peer_init (ffffffff7ffff0c0, 100173000, 2,
> 100173000, 100173, 1001705e8) + 604
>  0000000100022a7c smtpd_state_init (ffffffff7ffff0c0, 100062, 100000,
> 100173000, 100173, 100000) + 17c
>  0000000100016558 ???????? (1001a0370, ffffffff7ffffdf9, 100000, 10005d000,
> 10005d, 100000)
>  000000010002551c ???????? (100000, 1001a0370, 100171000, 100171, 100000,
> 100171000)
>  00000001000259d8 ???????? (100171, 6, 62, 100171f88, 100000, 1c)
>  0000000100048748 event_loop (100198040, 1, 6, ffffffff7ffff64f, 10006a898,
> ffffffff7ffff648) + 408
>  0000000100027c64 single_server_main (1, 10017c1d0, 100197800, 9, 64, c) +
> 1e80
>  0000000100016e60 main (c, ffffffff7ffffc88, 100016000, 100016, 100000,
> 100016670) + 114
>  000000010000fb1c _start (0, 0, 0, 0, 0, 0) + 17c
>
> --
> Thank you,
> Eugene Krasikov

Reply | Threaded
Open this post in threaded view
|

Re: smtpd core dumps on Solaris

Eugene Krasikov-2
Just for information.

IP-address to resolve has "PTR ." reverse record in every core dump.
Seems to be a Solaris problem, see Bug ID 6613211
(http://bugs.opensolaris.org/view_bug.do?bug_id=6613211).

Thank you,
Eugene Krasikov
Reply | Threaded
Open this post in threaded view
|

Re: smtpd core dumps on Solaris

Wietse Venema
Eugene Krasikov:
> Just for information.
>
> IP-address to resolve has "PTR ." reverse record in every core dump.
> Seems to be a Solaris problem, see Bug ID 6613211
> (http://bugs.opensolaris.org/view_bug.do?bug_id=6613211).

It may help to expedite the bugfixing if you reproduce this with
the minimal getnameinfo test program in the Postfix source.

postfix-x.x.x/auxiliary/name-addr-test/getnameinfo.c

Otherwise some may argue with you.

        Wietse