 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
2 messages in net.sourceforge.lists.courier-sqwebmail[sqwebmail] BUG? sqwebmail eats mem a...| From | Sent On | Attachments |
|---|---|---|
| ki...@mikroweb.hu | Sep 26, 2006 3:34 pm | |
| kiru | Sep 28, 2006 5:41 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [sqwebmail] BUG? sqwebmail eats mem and writes continually into winchester | Actions... |
|---|---|---|
| From: | ki...@mikroweb.hu (ki...@mikroweb.hu) | |
| Date: | Sep 26, 2006 3:34:58 pm | |
| List: | net.sourceforge.lists.courier-sqwebmail | |
Hi list!
I just upgraded from earlier (from about 1-2 years) sqwebmail to 0.53.2-3 debian version.
I have a problem with the new version. Unknown sqwebmail event triggers that I think it runs into endless cycle.
my ps auxf shows: --- USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND 119 31792 3.7 29.7 433900 267472 ? D 00:53 28:33 /usr/lib/courier/courier/sqwebmaild 119 31818 0.0 0.0 3152 532 ? S 00:57 0:00 \_ gzip -c 119 3485 3.8 29.3 420168 264552 ? D 01:20 27:53 /usr/lib/courier/courier/sqwebmaild 119 31696 0.0 0.0 3124 532 ? S 01:36 0:00 \_ gzip -c 119 2597 4.1 3.3 36464 29816 ? D 12:35 2:15 /usr/lib/courier/courier/sqwebmaild 119 9894 0.0 0.0 3160 704 ? S 12:35 0:00 \_ gzip -c root 10951 0.0 0.0 6628 192 ? S 13:28 0:00 /usr/lib/courier/courier/sqwebmaild root 3790 0.0 0.0 6628 192 ? S 13:28 0:00 /usr/lib/courier/courier/sqwebmaild root 16962 0.0 0.0 6628 376 ? S 13:29 0:00 /usr/lib/courier/courier/sqwebmaild root 29613 0.0 0.0 6628 376 ? S 13:29 0:00 /usr/lib/courier/courier/sqwebmaild root 19468 0.0 0.0 6628 192 ? S 13:29 0:00 /usr/lib/courier/courier/sqwebmaild 119 31792 3.7 29.7 433900 267472 ? D 00:53 28:33 /usr/lib/courier/courier/sqwebmaild 119 31818 0.0 0.0 3152 532 ? S 00:57 0:00 \_ gzip -c 119 3485 3.8 29.3 420168 264552 ? D 01:20 27:53 /usr/lib/courier/courier/sqwebmaild 119 31696 0.0 0.0 3124 532 ? S 01:36 0:00 \_ gzip -c 119 2597 4.1 3.3 36464 29816 ? D 12:35 2:15 /usr/lib/courier/courier/sqwebmaild 119 9894 0.0 0.0 3160 704 ? S 12:35 0:00 \_ gzip -c root 10951 0.0 0.0 6628 192 ? S 13:28 0:00 /usr/lib/courier/courier/sqwebmaild root 3790 0.0 0.0 6628 192 ? S 13:28 0:00 /usr/lib/courier/courier/sqwebmaild root 16962 0.0 0.0 6628 376 ? S 13:29 0:00 /usr/lib/courier/courier/sqwebmaild root 29613 0.0 0.0 6628 376 ? S 13:29 0:00 /usr/lib/courier/courier/sqwebmaild root 19468 0.0 0.0 6628 192 ? S 13:29 0:00 /usr/lib/courier/courier/sqwebmaild ---
I don't known sqwebmail internals. I don't see any warning in syslog. The 119 user is exim4. I think the problem is with these processes and it's call of gzip. I upgraded together the kernel of the system from 2.6.8.1 to 2.7.17.11 with grsec. The system is smp if it matters.
Regards --- kiru ----