[Bug 1187001] Re: saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b7160000+1ad000]
I think default THREADS=5 in /etc/default/saslauthd, after these all crash [as above] then thats the end of SASL working. (at least that is what happened for me, repeatedly). Setting this to THREADS=0 has worked around the issue (for me anyway) as it makes it fork instead. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1187001 Title: saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1187001/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210952] [NEW] radicale broken CardDAV support esp. with iPhone
Public bug reported: current release package 0.7-1.1 with broken CardDAV (contains mistaken references to caldav instead of cardav in cardav requests) it is fixed in latest git 0.8 ** Affects: radicale (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Package changed: cyrus-sasl2 (Ubuntu) = radicale (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1210952 Title: radicale broken CardDAV support esp. with iPhone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radicale/+bug/1210952/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1208506] Re: vsftpd respawns too fast and fails on server boot with pasv_address pasv_addr_resolve=YES
Hi, thanks for reply - not using network-manager $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 192.168.1.50 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.0.255 gateway 192.168.1.1 mtu 1460 $ cat /etc/init/vsftpd.conf # vsftpd - FTP Daemon # description vsftpd daemon author Chuck Short zul...@ubuntu.com start on runlevel [2345] or net-device-up IFACE!=lo stop on runlevel [!2345] respawn snip -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1208506 Title: vsftpd respawns too fast and fails on server boot with pasv_address pasv_addr_resolve=YES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1208506/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1208506] [NEW] vsftpd respawns too fast and fails on server boot with pasv_address pasv_addr_resolve=YES
Public bug reported: I have just changed my vsftpd config for PASV mode with address resolving (behind NAT) pasv_min_port=21000 pasv_max_port=21050 pasv_addr_resolve=YES pasv_address=abcdefghij.com vsftpd wont start when server boots, presumably because it cant resolve the address specified before the networking is up [ 13.669683] init: vsftpd main process (735) terminated with status 2 [ 13.669703] init: vsftpd main process ended, respawning [ 13.674386] init: vsftpd main process (822) terminated with status 2 [ 13.674408] init: vsftpd main process ended, respawning [ 13.678718] init: vsftpd main process (834) terminated with status 2 [ 13.678739] init: vsftpd main process ended, respawning [ 13.683638] init: vsftpd main process (842) terminated with status 2 [ 13.683657] init: vsftpd main process ended, respawning [ 13.687625] init: vsftpd main process (851) terminated with status 2 [ 13.687646] init: vsftpd main process ended, respawning [ 13.692293] init: vsftpd main process (859) terminated with status 2 [ 13.692314] init: vsftpd main process ended, respawning [ 13.697125] init: vsftpd main process (866) terminated with status 2 [ 13.697145] init: vsftpd main process ended, respawning [ 13.700955] init: vsftpd main process (869) terminated with status 2 [ 13.700975] init: vsftpd main process ended, respawning [ 13.705266] init: vsftpd main process (872) terminated with status 2 [ 13.705285] init: vsftpd main process ended, respawning [ 13.709494] init: vsftpd main process (875) terminated with status 2 [ 13.709514] init: vsftpd main process ended, respawning [ 13.713758] init: vsftpd main process (878) terminated with status 2 [ 13.713777] init: vsftpd respawning too fast, stopped [ 13.952331] init: vsftpd main process (975) terminated with status 2 [ 13.952352] init: vsftpd main process ended, respawning [ 13.964461] init: vsftpd main process (995) terminated with status 2 [ 13.964481] init: vsftpd main process ended, respawning [ 13.971373] init: vsftpd main process (1009) terminated with status 2 [ 13.971394] init: vsftpd main process ended, respawning [ 13.977411] init: vsftpd main process (1017) terminated with status 2 [ 13.977432] init: vsftpd main process ended, respawning [ 13.982285] init: vsftpd main process (1024) terminated with status 2 [ 13.982306] init: vsftpd main process ended, respawning [ 13.987784] init: vsftpd main process (1039) terminated with status 2 [ 13.987805] init: vsftpd main process ended, respawning [ 13.998372] init: vsftpd main process (1060) terminated with status 2 [ 13.998393] init: vsftpd main process ended, respawning [ 14.003019] init: vsftpd main process (1069) terminated with status 2 [ 14.003040] init: vsftpd main process ended, respawning [ 14.008473] init: vsftpd main process (1079) terminated with status 2 [ 14.008493] init: vsftpd main process ended, respawning [ 14.013779] init: vsftpd main process (1083) terminated with status 2 [ 14.013800] init: vsftpd main process ended, respawning [ 14.019692] init: vsftpd main process (1092) terminated with status 2 [ 14.019713] init: vsftpd respawning too fast, stopped [ 15.636887] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 15.636921] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 18.970493] ip_tables: (C) 2000-2006 Netfilter Core Team Manually starting service straight after boot, it then starts fine. (Server is BIND dns server also) $ vsftpd -v vsftpd: version 3.0.2 Using Raring Ringtail 13.04 x64 server ** Affects: vsftpd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1208506 Title: vsftpd respawns too fast and fails on server boot with pasv_address pasv_addr_resolve=YES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1208506/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1187001] Re: saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b7160000+1ad000]
if anyone else is suffering this I installed fail2ban as a workaround, the attacker's IP gets banned before SASL falls over. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1187001 Title: saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1187001/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1187001] [NEW] saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b7160000+1ad000]
Public bug reported: The mail server (raring 13.04 headless) is getting a dictionary attack and saslauthd is crashing with fault in libc thus; /var/log/auth.log Jun 3 11:27:41 ubuntu saslauthd[26789]: do_auth : auth failure: [user=admin] [service=smtp] [realm=] [$ Jun 3 11:27:44 ubuntu saslauthd[26790]: do_auth : auth failure: [user=test] [service=smtp] [realm=] [m$ Jun 3 11:27:48 ubuntu saslauthd[26793]: do_auth : auth failure: [user=www] [service=smtp] [realm=] [me$ Jun 3 11:27:51 ubuntu saslauthd[26789]: do_auth : auth failure: [user=testuser] [service=smtp] [realm=$ Jun 3 11:27:54 ubuntu saslauthd[26790]: do_auth : auth failure: [user=webadmin] [service=smtp] [realm=$ /var/log/mail.log Jun 3 11:27:41 ubuntu postfix/smtpd[1324]: warning: mail.yokozunanet.mn[203.34.37.30]: SASL LOGIN authenticati$ Jun 3 11:27:42 ubuntu postfix/smtpd[1327]: connect from mail.yokozunanet.mn[203.34.37.30] Jun 3 11:27:44 ubuntu postfix/smtpd[1327]: warning: mail.yokozunanet.mn[203.34.37.30]: SASL LOGIN authenticati$ Jun 3 11:27:45 ubuntu postfix/smtpd[1328]: connect from mail.yokozunanet.mn[203.34.37.30] Jun 3 11:27:48 ubuntu postfix/smtpd[1328]: warning: mail.yokozunanet.mn[203.34.37.30]: SASL LOGIN authenticati$ Jun 3 11:27:49 ubuntu postfix/smtpd[1330]: connect from mail.yokozunanet.mn[203.34.37.30] Jun 3 11:27:51 ubuntu postfix/smtpd[1330]: warning: mail.yokozunanet.mn[203.34.37.30]: SASL LOGIN authenticati$ Jun 3 11:27:52 ubuntu postfix/smtpd[1335]: connect from mail.yokozunanet.mn[203.34.37.30] Jun 3 11:27:54 ubuntu postfix/smtpd[1335]: warning: mail.yokozunanet.mn[203.34.37.30]: SASL LOGIN authenticati$ After a time saslauthd service dies, this is from dmesg [775847.232115] saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] [775856.870264] saslauthd[26790]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] [775876.100629] saslauthd[26789]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] [775882.604389] saslauthd[26793]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] [775915.757471] saslauthd[26792]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] uname Linux ubuntu 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:59 UTC 2013 i686 i686 i686 GNU/Linux ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New ** Package changed: apport (Ubuntu) = cyrus-sasl2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1187001 Title: saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1187001/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
