Urgent! SMTP/SASL problem after Kernel update

Discussion in 'Installation/Configuration' started by teves, Mar 26, 2007.

  1. teves

    teves Member

    Hello,

    after updating the kernel on my Suse 10.1 perfect setup / ispconfig 2.28 server I cannot send mail anymore.

    A
    tail /var/log/messages
    gives me
    Mar 26 09:17:23 whitespace kernel: saslauthd[27570]: segfault at 00000000745dc280 rip 00002b3a74d1b6b0 rsp 00007fff36bd4528 error 4
    Mar 26 09:17:24 whitespace kernel: saslauthd[27571]: segfault at 00000000745dc280 rip 00002b3a74d1b6b0 rsp 00007fff36bd4528 error 4
    Mar 26 09:17:32 whitespace kernel: saslauthd[27572]: segfault at 00000000745dc280 rip 00002b3a74d1b6b0 rsp 00007fff36bd4528 error 4
    Mar 26 09:17:32 whitespace kernel: saslauthd[27573]: segfault at 00000000745dc280 rip 00002b3a74d1b6b0 rsp 00007fff36bd4528 error 4


    tail /var/log/mail.warn
    results in
    Mar 26 09:29:18 whitespace postfix/smtpd[27802]: warning: 203.210.253.236: hostname adsl.hnpt.com.vn verification failed: Name or service not known
    Mar 26 09:30:21 whitespace postfix/smtpd[27847]: warning: SASL authentication failure: size read failed
    Mar 26 09:30:21 whitespace postfix/smtpd[27847]: warning: SASL authentication failure: Password verification failed
    Mar 26 09:30:21 whitespace postfix/smtpd[27847]: warning: p57A4C18A.dip0.t-ipconnect.de[87.164.193.138]: SASL PLAIN authentication failed
    Mar 26 09:30:21 whitespace postfix/smtpd[27847]: warning: SASL authentication failure: size read failed


    What has happened here? What can I do?
    This is really urgent because I have ~150 Domains running here... :(

    Thank you,
    regards, Tom
     
  2. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Hi Tom,

    did you reboot your server after installing the kernel?
     
  3. teves

    teves Member

    Hallo,

    yes I did (and did it once again now).

    regards, Tom
     
  4. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Are there any sasl updates pending? Please amke sure that you have disabled apparmor, maybe it is enabled again after the kernel update.
     
  5. teves

    teves Member

    Hello,

    no I have the most actual sasl package.
    apparmor is not running.
    Would it be an option to downgrade the kernel to the old version?

    regards, Tom
     
  6. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Maybe, but I'am not sure if this might cause other trouble. Can you select an older kernel in grub when you boot or does SuSE removes the older kernel after the update? Segfaults might also be caused by hardware problems, But its not so likely that your hardware gets problems at the same time you updated your kernel.

    Maybe one of the other users has a good idea?
     
  7. teves

    teves Member

    Hello,

    well I will just take the risk now.
    I need to find a solution NOW. In the worst case I will have to copy the status of yesterday back onto the first harddisk - I have two harddisks and did a dd from a to b before upgrading yesterday - but it would take a few hours at least.

    Hm. It does not seem to work. I still get the segmentation fault.
    I have also downgraded sasl now without success.
    Any ideas?

    regards, Tom
     
  8. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    You can try to check your hardware with e.g. memcheck. Maybe its really a hardware problem, e.g. instable ram, that was triggered by the reboot.
     
  9. teves

    teves Member

    Hi,

    I cannot tell if it is a hardware problem, but I don't believe it. Everything worked perfectly until now, and at the moment everything else (only exception: sasl) works perfectly.
    This would be a strange hardware problem. (Well ok, I've seen a lot. ;) )

    Anyway: I don't believe in a hardware problem.

    Thank you,
    Tom
     
  10. teves

    teves Member

    Hello,

    testsaslauthd -u web**_info -p *******

    gives me the message

    size read failed

    Any ideas?

    regards, Tom
     
  11. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Maybe has the sasl update overwritten some config files. Please compare your config fils with the configuration described in the perfect setup howto.
     
  12. teves

    teves Member

    Hello,

    well I don't know how to check this. Which files would I have to check?

    The 'postconf -e' commands writes into /etc/postfix/master.cf, right?
    but I can't find entries like 'mydomain =' in the master.cf

    regards, Tom
     
  13. teves

    teves Member

    Hello,

    I have perhaps found an error.

    tail /var/log/messages gave me:

    Mar 26 10:54:36 whitespace saslauthd[7393]: ipc_init : listening on socket: /var/run/sasl2//mux

    There is a double slash between sasl2 and mux. This must be an error. The question is: can it be THE error? Where can I find that path in the sasl config?

    regards, Tom
     
  14. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    try to compare the files that you have with the results expected by the postconf commands and especially the part where sasl files where edited with vi.

    maybe you have a main.cf.rpmnew file or a similar filename that yast may have created when updating the pacakges.

    Yes, postconf edits the main.cf file.

    Dont forget to make a backup of the current main.cf before you change something :)
     
  15. teves

    teves Member

    Hello,

    the main.cf seems to be ok like in the perfect setup.


    regards, Tom
     
  16. teves

    teves Member

    Hello,

    ok, I have something here:

    I have changes the /etc/sysconfig/saslauthd from
    SASLAUTHD_AUTHMECH=shadow
    to
    SASLAUTHD_AUTHMECH=pam

    Now I can send mail. But why is that, and what can be the real problem?


    regards, Tom
     
  17. teves

    teves Member

    Hello,


    could someone please tell me what changes

    SASLAUTHD_AUTHMECH=pam

    in the /etc/sysconfig/saslauthd does to my Server?
    Some people from the threads I found yesterday, concerning the problem I had, found their solution in changing 'pam' to 'shadow' on their servers.
    To me it was vice versa, and I'd very much like to know why.
    At least I'd like to know what changes that setting does to my system.
    And what would I have to do to change it back, if necessary?

    Could someone please tell me!


    Thank you,
    regards,
    Tom
     
  18. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Tis switches PAM authentication from shadow to pam. Thats both fina, as pam uses shadow internally to authenticate your users. Maybe the shadow authentication is broken or not supported anymore in the updated package.
     

Share This Page