[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, updated Linux kernel to 3.13.0-45-generic which fixes some ipv6 related problems, but pinger crash is still there. Here attached the crash file collected during last crash with the new kernel. Thanks in advance. ** Attachment added: _usr_lib_squid3_pinger.0.crash https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4310461/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, updated Linux kernel to 3.13.0-45-generic which fixes some ipv6 related problems, but pinger crash is still there. Here attached the crash file collected during last crash with the new kernel. Thanks in advance. ** Attachment added: _usr_lib_squid3_pinger.0.crash https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4310461/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+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 1404374] Re: Apparently ipv6-related crash in Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu 1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 (Ubuntu 3.13
This bug ipv6 related affect also me with thew same kernel: Dec 19 10:44:05 srvproxy01 kernel: [255240.230586] BUG: unable to handle kernel paging request at 1268 Dec 19 10:44:05 srvproxy01 kernel: [255240.230746] IP: [816c0eab] ip6_xmit+0x19b/0x410 Dec 19 10:44:05 srvproxy01 kernel: [255240.230862] PGD 0 Dec 19 10:44:05 srvproxy01 kernel: [255240.230908] Oops: [#1] SMP Dec 19 10:44:05 srvproxy01 kernel: [255240.230981] Modules linked in: btrfs raid6_pq xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables kvm_amd kvm amd64_edac_mod radeon k10temp edac_core edac_mce_amd ttm drm_kms_helper sp5100_tco i2c_piix4 drm i2c_algo_bit shpchp lp mac_hid parport pata_acpi ahci hid_generic usbhid hid pata_atiixp libahci tg3 e1000e ptp pps_core Dec 19 10:44:05 srvproxy01 kernel: [255240.232075] CPU: 1 PID: 23157 Comm: squid3 Not tainted 3.13.0-43-generic #72-Ubuntu Dec 19 10:44:05 srvproxy01 kernel: [255240.232217] Hardware name: HP ProLiant MicroServer, BIOS O41 07/29/2011 Dec 19 10:44:05 srvproxy01 kernel: [255240.232345] task: 880192e93000 ti: 8800b7c9a000 task.ti: 8800b7c9a000 Dec 19 10:44:05 srvproxy01 kernel: [255240.232481] RIP: 0010:[816c0eab] [816c0eab] ip6_xmit+0x19b/0x410 Dec 19 10:44:05 srvproxy01 kernel: [255240.232633] RSP: 0018:8800b7c9bb10 EFLAGS: 00010206 Dec 19 10:44:05 srvproxy01 kernel: [255240.232730] RAX: 1000 RBX: 8801939222e8 RCX: 0001 Dec 19 10:44:05 srvproxy01 kernel: [255240.232859] RDX: 8189cc00 RSI: 0028 RDI: 880194cac9c0 Dec 19 10:44:05 srvproxy01 kernel: [255240.232988] RBP: 8800b7c9bb70 R08: R09: 000167b0 Dec 19 10:44:05 srvproxy01 kernel: [255240.233117] R10: R11: R12: 8800bf8b8000 Dec 19 10:44:05 srvproxy01 kernel: [255240.233245] R13: 880194cac9c0 R14: 0060 R15: 8800b7c9bb88 Dec 19 10:44:05 srvproxy01 kernel: [255240.233376] FS: 7fbb85bd3780() GS:88019fc8() knlGS: Dec 19 10:44:05 srvproxy01 kernel: [255240.233519] CS: 0010 DS: ES: CR0: 80050033 Dec 19 10:44:05 srvproxy01 kernel: [255240.233625] CR2: 1268 CR3: ca7e9000 CR4: 07e0 Dec 19 10:44:05 srvproxy01 kernel: [255240.233753] Stack: Dec 19 10:44:05 srvproxy01 kernel: [255240.233793] 8800bf8b8000 8800b7c9bb70 8800cb2798f4 008e Dec 19 10:44:05 srvproxy01 kernel: [255240.233949] 81cda780 06010001 8800b7c9bb9c 8800bf8b8000 Dec 19 10:44:05 srvproxy01 kernel: [255240.234104] 8801939222e8 8800bf8b86e0 0014 880194cac9c0 Dec 19 10:44:05 srvproxy01 kernel: [255240.234259] Call Trace: Dec 19 10:44:05 srvproxy01 kernel: [255240.234317] [816f0c9d] inet6_csk_xmit+0x7d/0xd0 Dec 19 10:44:05 srvproxy01 kernel: [255240.234423] [81677519] tcp_transmit_skb+0x469/0x8d0 Dec 19 10:44:05 srvproxy01 kernel: [255240.234532] [81677ac0] tcp_write_xmit+0x140/0xb10 Dec 19 10:44:05 srvproxy01 kernel: [255240.234638] [816786fe] __tcp_push_pending_frames+0x2e/0xc0 Dec 19 10:44:05 srvproxy01 kernel: [255240.234759] [81669d38] tcp_sendmsg+0x118/0xdb0 Dec 19 10:44:05 srvproxy01 kernel: [255240.234860] [8166b612] ? tcp_recvmsg+0x6c2/0xb80 Dec 19 10:44:05 srvproxy01 kernel: [255240.234968] [81693624] inet_sendmsg+0x64/0xb0 Dec 19 10:44:05 srvproxy01 kernel: [255240.235071] [813137f7] ? apparmor_socket_sendmsg+0x17/0x20 Dec 19 10:44:05 srvproxy01 kernel: [255240.235191] [8160b63e] sock_aio_write+0xfe/0x130 Dec 19 10:44:05 srvproxy01 kernel: [255240.235299] [811bd4ba] do_sync_write+0x5a/0x90 Dec 19 10:44:05 srvproxy01 kernel: [255240.235402] [811bdd3d] vfs_write+0x1ad/0x1f0 Dec 19 10:44:05 srvproxy01 kernel: [255240.235502] [811be679] SyS_write+0x49/0xa0 Dec 19 10:44:05 srvproxy01 kernel: [255240.235599] [817316ad] system_call_fastpath+0x1a/0x1f Dec 19 10:44:05 srvproxy01 kernel: [255240.235707] Code: 00 89 83 b4 00 00 00 49 8b 45 20 ff 50 20 39 43 68 77 6d 48 8b 43 58 48 83 e0 fe 48 8b 80 48 01 00 00 48 85 c0 0f 84 51 02 00 00 48 8b 80 68 02 00 00 65 48 ff 40 28 8b 53 68 65 48 01 50 30 48 Dec 19 10:44:05 srvproxy01 kernel: [255240.236427] RIP [816c0eab] ip6_xmit+0x19b/0x410 Dec 19 10:44:05 srvproxy01 kernel: [255240.236533] RSP 8800b7c9bb10 Dec 19 10:44:05 srvproxy01 kernel: [255240.236599] CR2: 1268 Dec 19 10:44:05 srvproxy01 kernel: [255240.254766] ---[ end trace 07277f33210412d5 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404374 Title: Apparently
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, I tried removing all and reinstallig all from repository. the step i followed: 2056 sudo apt-get remove squidclient 2057 sudo apt-get remove squid3-common (this also remove squid3) 2058 sudo apt-get clean squid3-common 2059 sudo apt-get clean squid3 2060 sudo apt-get clean squidclient 2061 sudo apt-get install squid3 squid3-common squidclient Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto I seguenti pacchetti sono stati installati automaticamente e non sono più richiesti: linux-headers-3.13.0-40 linux-headers-3.13.0-40-generic linux-image-3.13.0-40-generic linux-image-extra-3.13.0-40-generic Usare apt-get autoremove per rimuoverli. Pacchetti suggeriti: squid-cgi squid-purge smbclient winbindd I seguenti pacchetti NUOVI saranno installati: squid3 squid3-common squidclient 0 aggiornati, 3 installati, 0 da rimuovere e 1 non aggiornati. È necessario scaricare 1.970 kB di archivi. Dopo quest'operazione, verranno occupati 6.679 kB di spazio su disco. Scaricamento di:1 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/main squid3-common all 3.3.8-1ubuntu6.2 [153 kB] Scaricamento di:2 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/main squid3 amd64 3.3.8-1ubuntu6.2 [1.787 kB] Scaricamento di:3 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/universe squidclient amd64 3.3.8-1ubuntu6.2 [31,1 kB] Recuperati 1.970 kB in 4s (441 kB/s) Selezionato il pacchetto squid3-common non precedentemente selezionato. (Lettura del database... 101279 file e directory attualmente installati.) Preparing to unpack .../squid3-common_3.3.8-1ubuntu6.2_all.deb ... Unpacking squid3-common (3.3.8-1ubuntu6.2) ... Selezionato il pacchetto squid3 non precedentemente selezionato. Preparing to unpack .../squid3_3.3.8-1ubuntu6.2_amd64.deb ... Unpacking squid3 (3.3.8-1ubuntu6.2) ... Selezionato il pacchetto squidclient non precedentemente selezionato. Preparing to unpack .../squidclient_3.3.8-1ubuntu6.2_amd64.deb ... Unpacking squidclient (3.3.8-1ubuntu6.2) ... Processing triggers for ufw (0.34~rc-0ubuntu2) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Configurazione di squid3-common (3.3.8-1ubuntu6.2)... Configurazione di squid3 (3.3.8-1ubuntu6.2)... squid3 start/running, process 8150 Skipping profile in /etc/apparmor.d/disable: usr.sbin.squid3 Configurazione di squidclient (3.3.8-1ubuntu6.2)... /var/log/squid3/cache.log 2014/12/19 13:38:07.606| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/19 13:38:07.606| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': munmap_chunk(): invalid pointer: 0x7f430603a260 *** crash report attached. Hope this time we had better luck with this . ** Attachment added: crash file https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4284149/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+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 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, sorry but I'm not expert, but reading documentation, maybe i have to prepare crash report before sending it: here you can find a crash report prepared with apport-cli -c /var/crash/_usr_lib_squid3_pinger.0.crash hope this help. ** Attachment added: crash report prepared with apport-cli https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4284353/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+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 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, I tried removing all and reinstallig all from repository. the step i followed: 2056 sudo apt-get remove squidclient 2057 sudo apt-get remove squid3-common (this also remove squid3) 2058 sudo apt-get clean squid3-common 2059 sudo apt-get clean squid3 2060 sudo apt-get clean squidclient 2061 sudo apt-get install squid3 squid3-common squidclient Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto I seguenti pacchetti sono stati installati automaticamente e non sono più richiesti: linux-headers-3.13.0-40 linux-headers-3.13.0-40-generic linux-image-3.13.0-40-generic linux-image-extra-3.13.0-40-generic Usare apt-get autoremove per rimuoverli. Pacchetti suggeriti: squid-cgi squid-purge smbclient winbindd I seguenti pacchetti NUOVI saranno installati: squid3 squid3-common squidclient 0 aggiornati, 3 installati, 0 da rimuovere e 1 non aggiornati. È necessario scaricare 1.970 kB di archivi. Dopo quest'operazione, verranno occupati 6.679 kB di spazio su disco. Scaricamento di:1 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/main squid3-common all 3.3.8-1ubuntu6.2 [153 kB] Scaricamento di:2 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/main squid3 amd64 3.3.8-1ubuntu6.2 [1.787 kB] Scaricamento di:3 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/universe squidclient amd64 3.3.8-1ubuntu6.2 [31,1 kB] Recuperati 1.970 kB in 4s (441 kB/s) Selezionato il pacchetto squid3-common non precedentemente selezionato. (Lettura del database... 101279 file e directory attualmente installati.) Preparing to unpack .../squid3-common_3.3.8-1ubuntu6.2_all.deb ... Unpacking squid3-common (3.3.8-1ubuntu6.2) ... Selezionato il pacchetto squid3 non precedentemente selezionato. Preparing to unpack .../squid3_3.3.8-1ubuntu6.2_amd64.deb ... Unpacking squid3 (3.3.8-1ubuntu6.2) ... Selezionato il pacchetto squidclient non precedentemente selezionato. Preparing to unpack .../squidclient_3.3.8-1ubuntu6.2_amd64.deb ... Unpacking squidclient (3.3.8-1ubuntu6.2) ... Processing triggers for ufw (0.34~rc-0ubuntu2) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Configurazione di squid3-common (3.3.8-1ubuntu6.2)... Configurazione di squid3 (3.3.8-1ubuntu6.2)... squid3 start/running, process 8150 Skipping profile in /etc/apparmor.d/disable: usr.sbin.squid3 Configurazione di squidclient (3.3.8-1ubuntu6.2)... /var/log/squid3/cache.log 2014/12/19 13:38:07.606| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/19 13:38:07.606| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': munmap_chunk(): invalid pointer: 0x7f430603a260 *** crash report attached. Hope this time we had better luck with this . ** Attachment added: crash file https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4284149/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, sorry but I'm not expert, but reading documentation, maybe i have to prepare crash report before sending it: here you can find a crash report prepared with apport-cli -c /var/crash/_usr_lib_squid3_pinger.0.crash hope this help. ** Attachment added: crash report prepared with apport-cli https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4284353/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, I recreated the error so the crash report is related to the following log entry: /var/log/squid3/cache.log 2014/12/18 14:09:24.128| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1016] off to ICMPv6 module. 2014/12/18 14:09:24.128| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1016]. 2014/12/18 14:09:24.128| cc(206) SendEcho: x=40 2014/12/18 14:09:24.128| c(116) Log: pingerLog: 1418908164.128595 [2a00:1450:4002:801::1016]0 2014/12/18 14:09:24.162| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/18 14:09:24.162| c(116) Log: pingerLog: 1418908164.162822 [2a00:1450:4002:801::1016]129 Echo Reply 34ms 1 hops 2014/12/18 14:09:24.162| nger.cc(235) SendResult: return result to squid. len=78 2014/12/18 14:09:24.596| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/18 14:09:24.596| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': free(): invalid size: 0x7f4adde3e260 *** /var/log/kern.log Dec 18 07:05:07 srvproxy01 kernel: [155746.408903] pinger[21467]: segfault at 7f536c00 ip 7f536a5a38ac sp 7fffa49c1c48 error 4 in libc-2.19.so[7f536a52+1bb000] and crash report attached ** Attachment added: Crash report https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4283480/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+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 1384943] Re: [SRU] Pinger crashes with segfault in libc
I installed the archive package instead and I have this error in the log: 2014/12/18 16:32:35.829| cc(263) Recv: 32 bytes from [fe80::206:4fff:fe9b:d135] 2014/12/18 16:32:40.831| cc(263) Recv: 24 bytes from [fe80::206:4fff:fe9b:d135] 2014/12/18 16:32:45.830| cc(263) Recv: 32 bytes from [fe80::206:4fff:fe9b:d135] 2014/12/18 16:32:50.458| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/18 16:32:50.458| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': munmap_chunk(): invalid pointer: 0x7fdf07d5c260 *** 2014/12/18 16:38:25| recv: (111) Connection refused 2014/12/18 16:38:25| Closing Pinger socket on FD 18 no entry in kern.log this time attached you can find crash file ** Attachment added: Crash report https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4283538/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+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 1384943] Re: [SRU] Pinger crashes with segfault in libc
Hi Jorge, I recreated the error so the crash report is related to the following log entry: /var/log/squid3/cache.log 2014/12/18 14:09:24.128| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1016] off to ICMPv6 module. 2014/12/18 14:09:24.128| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1016]. 2014/12/18 14:09:24.128| cc(206) SendEcho: x=40 2014/12/18 14:09:24.128| c(116) Log: pingerLog: 1418908164.128595 [2a00:1450:4002:801::1016]0 2014/12/18 14:09:24.162| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/18 14:09:24.162| c(116) Log: pingerLog: 1418908164.162822 [2a00:1450:4002:801::1016]129 Echo Reply 34ms 1 hops 2014/12/18 14:09:24.162| nger.cc(235) SendResult: return result to squid. len=78 2014/12/18 14:09:24.596| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/18 14:09:24.596| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': free(): invalid size: 0x7f4adde3e260 *** /var/log/kern.log Dec 18 07:05:07 srvproxy01 kernel: [155746.408903] pinger[21467]: segfault at 7f536c00 ip 7f536a5a38ac sp 7fffa49c1c48 error 4 in libc-2.19.so[7f536a52+1bb000] and crash report attached ** Attachment added: Crash report https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4283480/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
I installed the archive package instead and I have this error in the log: 2014/12/18 16:32:35.829| cc(263) Recv: 32 bytes from [fe80::206:4fff:fe9b:d135] 2014/12/18 16:32:40.831| cc(263) Recv: 24 bytes from [fe80::206:4fff:fe9b:d135] 2014/12/18 16:32:45.830| cc(263) Recv: 32 bytes from [fe80::206:4fff:fe9b:d135] 2014/12/18 16:32:50.458| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/18 16:32:50.458| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': munmap_chunk(): invalid pointer: 0x7fdf07d5c260 *** 2014/12/18 16:38:25| recv: (111) Connection refused 2014/12/18 16:38:25| Closing Pinger socket on FD 18 no entry in kern.log this time attached you can find crash file ** Attachment added: Crash report https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4283538/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
I download 6.2 source package and recompile it on my ubuntu 14.04 trusty system but now pinger have some problems: It seems that if pinger receive a Packet too big ICMP v6 packet while is pinging an ipv6 address run into strange errors, here is what I found in the log activating debug: 2014/12/17 11:06:20.182| cc(206) SendEcho: x=40 2014/12/17 11:06:20.182| c(116) Log: pingerLog: 1418810780.182442 [2a00:1450:4002:801::1016]0 2014/12/17 11:06:20.204| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/17 11:06:20.204| c(116) Log: pingerLog: 1418810780.204457 [2a00:1450:4002:801::1016]129 Echo Reply 22ms 1 hops 2014/12/17 11:06:20.204| nger.cc(235) SendResult: return result to squid. len=78 2014/12/17 11:06:20.577| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:06:20.578| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': munmap_chunk(): invalid pointer: 0x7f5550efb260 *** 2014/12/17 11:17:24.223| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1016] off to ICMPv6 module. 2014/12/17 11:17:24.223| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1016]. 2014/12/17 11:17:24.223| cc(206) SendEcho: x=40 2014/12/17 11:17:24.224| c(116) Log: pingerLog: 1418811444.223975 [2a00:1450:4002:801::1016]0 2014/12/17 11:17:24.246| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/17 11:17:24.246| c(116) Log: pingerLog: 1418811444.246856 [2a00:1450:4002:801::1016]129 Echo Reply 23ms 1 hops 2014/12/17 11:17:24.247| nger.cc(235) SendResult: return result to squid. len=78 2014/12/17 11:17:24.618| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:17:24.618| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': free(): invalid size: 0x7f32eb024260 *** 2014/12/17 11:19:27.987| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1015] off to ICMPv6 module. 2014/12/17 11:19:27.987| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1015]. 2014/12/17 11:19:27.987| cc(206) SendEcho: x=40 2014/12/17 11:19:27.987| c(116) Log: pingerLog: 1418811567.987412 [2a00:1450:4002:801::1015]0 2014/12/17 11:19:28.004| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:19:28.004| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': double free or corruption (out): 0x7f155f608260 *** 2014/12/17 11:20:14| recv: (111) Connection refused 2014/12/17 11:20:14| Closing Pinger socket on FD 28 after every one of this error pinger exit. If I restart squid I came into the error again since my ipv6 is a tunnel and i can get a lot of this ICMP packet too. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+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 1384943] Re: [SRU] Pinger crashes with segfault in libc
I download 6.2 source package and recompile it on my ubuntu 14.04 trusty system but now pinger have some problems: It seems that if pinger receive a Packet too big ICMP v6 packet while is pinging an ipv6 address run into strange errors, here is what I found in the log activating debug: 2014/12/17 11:06:20.182| cc(206) SendEcho: x=40 2014/12/17 11:06:20.182| c(116) Log: pingerLog: 1418810780.182442 [2a00:1450:4002:801::1016]0 2014/12/17 11:06:20.204| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/17 11:06:20.204| c(116) Log: pingerLog: 1418810780.204457 [2a00:1450:4002:801::1016]129 Echo Reply 22ms 1 hops 2014/12/17 11:06:20.204| nger.cc(235) SendResult: return result to squid. len=78 2014/12/17 11:06:20.577| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:06:20.578| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': munmap_chunk(): invalid pointer: 0x7f5550efb260 *** 2014/12/17 11:17:24.223| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1016] off to ICMPv6 module. 2014/12/17 11:17:24.223| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1016]. 2014/12/17 11:17:24.223| cc(206) SendEcho: x=40 2014/12/17 11:17:24.224| c(116) Log: pingerLog: 1418811444.223975 [2a00:1450:4002:801::1016]0 2014/12/17 11:17:24.246| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/17 11:17:24.246| c(116) Log: pingerLog: 1418811444.246856 [2a00:1450:4002:801::1016]129 Echo Reply 23ms 1 hops 2014/12/17 11:17:24.247| nger.cc(235) SendResult: return result to squid. len=78 2014/12/17 11:17:24.618| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:17:24.618| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': free(): invalid size: 0x7f32eb024260 *** 2014/12/17 11:19:27.987| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1015] off to ICMPv6 module. 2014/12/17 11:19:27.987| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1015]. 2014/12/17 11:19:27.987| cc(206) SendEcho: x=40 2014/12/17 11:19:27.987| c(116) Log: pingerLog: 1418811567.987412 [2a00:1450:4002:801::1015]0 2014/12/17 11:19:28.004| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:19:28.004| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': double free or corruption (out): 0x7f155f608260 *** 2014/12/17 11:20:14| recv: (111) Connection refused 2014/12/17 11:20:14| Closing Pinger socket on FD 28 after every one of this error pinger exit. If I restart squid I came into the error again since my ipv6 is a tunnel and i can get a lot of this ICMP packet too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304953] Re: ntlm_auth reports Broken Helper: BH NT_STATUS_UNSUCCESSFUL NT_STATUS_UNSUCCESSFUL
I have the same problem authenticating users with ntlm_auth and squid3. I confirm that the method described works also for fixing also in this case. Thanks Alex -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304953 Title: ntlm_auth reports Broken Helper: BH NT_STATUS_UNSUCCESSFUL NT_STATUS_UNSUCCESSFUL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache-mod-auth-ntlm-winbind/+bug/1304953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
