From mark.odell at connect.co.uk Tue Apr 29 15:40:23 2008 From: mark.odell at connect.co.uk (Mark O'Dell) Date: Tue, 29 Apr 2008 20:40:23 +0100 Subject: [imapproxy-info] Segmentation fault Message-ID: <874D3D242F17274DA6ACC80C6AD6C9B5031A198F@CNLONEX01.connect.co.uk> Hi, I am trying to get imapproxy working to improve the performance of Squirrelmail, but to no avail. I downloaded, extracted and ran make. First problem is that there was no imapproxyd.conf file created (not sure if this is normal) so I created the following using the README. server_hostname = 127.0.0.1 server_port = 143 listen_port = 10143 cache_expiration_time = 300 proc_username = nobody proc_groupname = nogroup stat_filename = /var/run/pimpstats When it comes to starting the daemon, either through the rc file or just running the command it resturns "Segmentation fault" and nothing else. /var/log/messages records two entries: Apr 29 20:25:06 cnbasem01 in.imapproxyd: main(): Using default configuration file '/etc/imapproxy.conf'. Apr 29 20:25:06 cnbasem01 in.imapproxyd: syslog_facility not specified. Defaulting to LOG_MAIL. Software Fedora 6 Dovecot Postfix imapproxy 1.2.6 (and tried 1.2.5) Regards, Mark O'Dell -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.andrew.cmu.edu/pipermail/imapproxy-info/attachments/20080429/49509c9b/attachment.html From dave64 at andrew.cmu.edu Tue Apr 29 17:12:16 2008 From: dave64 at andrew.cmu.edu (Dave McMurtrie) Date: Tue, 29 Apr 2008 17:12:16 -0400 Subject: [imapproxy-info] Segmentation fault In-Reply-To: <874D3D242F17274DA6ACC80C6AD6C9B5031A198F@CNLONEX01.connect.co.uk> References: <874D3D242F17274DA6ACC80C6AD6C9B5031A198F@CNLONEX01.connect.co.uk> Message-ID: <48178F30.6030700@andrew.cmu.edu> Mark O'Dell wrote: > Hi, > > I am trying to get imapproxy working to improve the performance of > Squirrelmail, but to no avail. > > I downloaded, extracted and ran make. First problem is that there was > no imapproxyd.conf file created (not sure if this is normal) so I > created the following using the README. > > server_hostname = 127.0.0.1 > server_port = 143 > listen_port = 10143 > cache_expiration_time = 300 > proc_username = nobody > proc_groupname = nogroup > stat_filename = /var/run/pimpstats > > When it comes to starting the daemon, either through the rc file or just > running the command it resturns "Segmentation fault" and nothing else. > /var/log/messages records two entries: Check out your syslog.conf file and see where log_mail entries go. See if there are any additional log messages in there. Does it leave a core behind? If so, can you poke at the core with gdb and get me a stack trace? If there's no core, can you strace it and send me the last 50 or so lines of strace output? That should give me some idea of where it's segfaulting. Thanks, Dave From mark.odell at connect.co.uk Wed Apr 30 05:08:49 2008 From: mark.odell at connect.co.uk (Mark O'Dell) Date: Wed, 30 Apr 2008 10:08:49 +0100 Subject: [imapproxy-info] Segmentation fault In-Reply-To: <48178F30.6030700@andrew.cmu.edu> References: <874D3D242F17274DA6ACC80C6AD6C9B5031A198F@CNLONEX01.connect.co.uk> <48178F30.6030700@andrew.cmu.edu> Message-ID: <874D3D242F17274DA6ACC80C6AD6C9B5031A1A35@CNLONEX01.connect.co.uk> Just to add. I have now tried it on another near-identical server and I get the same result -----Original Message----- From: imapproxy-info-bounces at lists.andrew.cmu.edu [mailto:imapproxy-info-bounces at lists.andrew.cmu.edu] On Behalf Of Dave McMurtrie Sent: 29 April 2008 22:12 To: imapproxy-info at lists.andrew.cmu.edu Subject: Re: [imapproxy-info] Segmentation fault Mark O'Dell wrote: > Hi, > > I am trying to get imapproxy working to improve the performance of > Squirrelmail, but to no avail. > > I downloaded, extracted and ran make. First problem is that there was > no imapproxyd.conf file created (not sure if this is normal) so I > created the following using the README. > > server_hostname = 127.0.0.1 > server_port = 143 > listen_port = 10143 > cache_expiration_time = 300 > proc_username = nobody > proc_groupname = nogroup > stat_filename = /var/run/pimpstats > > When it comes to starting the daemon, either through the rc file or > just running the command it resturns "Segmentation fault" and nothing else. > /var/log/messages records two entries: Check out your syslog.conf file and see where log_mail entries go. See if there are any additional log messages in there. Does it leave a core behind? If so, can you poke at the core with gdb and get me a stack trace? If there's no core, can you strace it and send me the last 50 or so lines of strace output? That should give me some idea of where it's segfaulting. Thanks, Dave _______________________________________________ imapproxy-info mailing list imapproxy-info at lists.andrew.cmu.edu https://lists.andrew.cmu.edu/mailman/listinfo/imapproxy-info From dave64 at andrew.cmu.edu Wed Apr 30 07:05:16 2008 From: dave64 at andrew.cmu.edu (Dave McMurtrie) Date: Wed, 30 Apr 2008 07:05:16 -0400 Subject: [imapproxy-info] Segmentation fault In-Reply-To: <874D3D242F17274DA6ACC80C6AD6C9B5031A1A35@CNLONEX01.connect.co.uk> References: <874D3D242F17274DA6ACC80C6AD6C9B5031A198F@CNLONEX01.connect.co.uk> <48178F30.6030700@andrew.cmu.edu> <874D3D242F17274DA6ACC80C6AD6C9B5031A1A35@CNLONEX01.connect.co.uk> Message-ID: <4818526C.5080706@andrew.cmu.edu> Mark O'Dell wrote: > Just to add. I have now tried it on another near-identical server and I > get the same result Hi Mark, I believed you when it was only broken on one server :) Surprisingly, if you've discovered a bug in imapproxy, it wouldn't be the first one. The most helpful thing you could provide would be a stack backtrace of a core file if one has been left behind. This will allow me to know exactly where the problem is. It could be in imapproxy, but it's also possible that it's a problem with one of the libraries that are linked in. If you're not getting a core dump, can you try to determine why (ulimit, for example) and get one? Thanks, Dave From mark.odell at connect.co.uk Wed Apr 30 12:41:51 2008 From: mark.odell at connect.co.uk (Mark O'Dell) Date: Wed, 30 Apr 2008 17:41:51 +0100 Subject: [imapproxy-info] Segmentation fault In-Reply-To: <48185746.2090006@andrew.cmu.edu> References: <874D3D242F17274DA6ACC80C6AD6C9B5031A198F@CNLONEX01.connect.co.uk><48178F30.6030700@andrew.cmu.edu><874D3D242F17274DA6ACC80C6AD6C9B5031A1A35@CNLONEX01.connect.co.uk> <4818526C.5080706@andrew.cmu.edu> <874D3D242F17274DA6ACC80C6AD6C9B5031A1AF6@CNLONEX01.connect.co.uk> <48185746.2090006@andrew.cmu.edu> Message-ID: <874D3D242F17274DA6ACC80C6AD6C9B5031A1C53@CNLONEX01.connect.co.uk> Output as follows [root at cnbasem01 ~]# gdb /usr/local/sbin/in.imapproxyd GNU gdb Red Hat Linux (6.5-8.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db lib rary "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/local/sbin/in.imapproxyd [Thread debugging using libthread_db enabled] [New Thread -1208609088 (LWP 20179)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208609088 (LWP 20179)] main (argc=Cannot access memory at address 0xffffffff ) at src/main.c:429 429 ICC_tptr->next = ICC_tptr + 1; (gdb) bt #0 main (argc=Cannot access memory at address 0xffffffff ) at src/main.c:429