Package: couriergrey Version: 0.3.2-3 Severity: important Dear Maintainer,
I recently installed couriergrey instead of my hacked version of greylistd, mostly so I would have a supported solution. This started with discovering that after a few hours, email stopped pouring in entirely. A quick grep of 'grey' in /var/log/mail.log showed lines like these: Nov 2 15:16:13 guardian couriergrey[12274]: ThreadError caught in main thread: Error creating thread: Resource temporarily unavailable Nov 2 15:23:11 guardian couriergrey[12274]: ThreadError caught in main thread: Error creating thread: Resource temporarily unavailable Nov 2 15:56:20 guardian couriergrey[12274]: ThreadError caught in main thread: Error creating thread: Resource temporarily unavailable Nov 3 02:19:48 guardian couriergrey[12274]: ThreadError caught in main thread: Error creating thread: Resource temporarily unavailable Nov 3 04:13:15 guardian couriergrey[12274]: ThreadError caught in main thread: Error creating thread: Resource temporarily unavailable My only quick solution was to do '/etc/init.d/courier-mta restart' I did this about five hours ago and then started looking at what was happening with the process. RSS was small at the start, VSZ was moderate, in the five digit range. I looked again fifteen minutes ago, and got this (the repeat done within two minutes): guardian:/etc/courier# ps auxw | head -1 ; ps auxw | grep grey USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND daemon 1759 0.0 0.4 2670576 4476 ? S nov03 0:00 couriergrey root 9252 0.0 0.0 5896 804 pts/5 S+ 04:34 0:00 grep grey guardian:/etc/courier# ps auxw | head -1 ; ps auxw | grep grey USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND daemon 1759 0.0 0.4 2670576 4476 ? S nov03 0:00 couriergrey root 9360 0.0 0.0 5896 800 pts/5 S+ 04:35 0:00 grep grey guardian:/etc/courier# ps auxw | head -1 ; ps auxw | grep grey USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND daemon 1759 0.0 0.4 2678772 4480 ? S nov03 0:00 couriergrey root 9834 0.0 0.0 5896 796 pts/5 S+ 04:36 0:00 grep grey guardian:/etc/courier# ps auxw | head -1 ; ps auxw | grep grey USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND daemon 1759 0.0 0.4 2678772 4480 ? S nov03 0:00 couriergrey root 9839 0.0 0.0 5896 804 pts/5 S+ 04:36 0:00 grep grey guardian:/etc/courier# ps auxw | head -1 ; ps auxw | grep grey USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND daemon 1759 0.0 0.4 2686968 4484 ? S nov03 0:00 couriergrey root 9907 0.0 0.0 5896 804 pts/5 S+ 04:38 0:00 grep grey Looking again now, this is what I get: guardian:/etc/courier# ps auxw | head -1 ; ps auxw | grep grey USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND daemon 1759 0.0 0.4 2703360 4484 ? S nov03 0:00 couriergrey root 12861 0.0 0.0 5896 804 pts/5 S+ 04:55 0:00 grep grey It looks to me like VSZ is steadily growing, and I'm wondering if this could be the cause of my issues... As for now, I'm considering setting up a cron job that restarts courier-mta every so often (6 hour interval?), but frankly, I'd rather not have to do that in the long run. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages couriergrey depends on: ii courier-mta 0.68.2-1+b1 ii libc6 2.17-93 ii libgcc1 1:4.8.2-1 ii libgdbm3 1.8.3-12 ii libglib2.0-0 2.36.4-1 ii libglibmm-2.4-1c2a 2.36.2-1 ii libpopt0 1.16-7 ii libsigc++-2.0-0c2a 2.2.10-0.2 ii libstdc++6 4.8.2-1 couriergrey recommends no packages. couriergrey suggests no packages. -- Configuration Files: /etc/couriergrey/whitelist_ip changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
