Hey all, I upgraded some servers today from Debian Lenny to Debian Squeeze, and after the upgrade I started getting dovecot crashes. I was on 2.0.13 but got these there as well, and hoped upgrading to 2.0.16 would help. It didn't. Anyone have an idea?
Cor
Dec 18 23:32:21 userimap1 kernel: [263492.245530] __ratelimit: 122 callbacks suppressed Dec 18 23:32:21 userimap1 kernel: [263492.245536] imap[19665]: segfault at 7f108efb7f60 ip 00007f108ecd37e0 sp 00007fff73c3d658 error 5 in libc-2.11.2.so[7f108ec5d000+158000] Dec 18 23:32:21 userimap1 kernel: [263492.245663] BUG: Bad page map in process imap pte:00000001 pmd:09767067 Dec 18 23:32:21 userimap1 kernel: [263492.252563] page:ffffea0000000000 flags:(null) count:-84 mapcount:-84 mapping:(null) index:0 Dec 18 23:32:21 userimap1 kernel: [263492.261186] addr:00007f108ef46000 vm_flags:08000070 anon_vma:(null) mapping:ffff88012b6e5238 index:2e9 Dec 18 23:32:21 userimap1 kernel: [263492.270804] vma->vm_ops->fault: filemap_fault+0x0/0x460 Dec 18 23:32:21 userimap1 kernel: [263492.276172] vma->vm_file->f_op->mmap: generic_file_mmap+0x0/0x60 Dec 18 23:32:21 userimap1 kernel: [263492.282424] Pid: 19665, comm: imap Tainted: G B 2.6.32.36-xsserver #1 Dec 18 23:32:21 userimap1 kernel: [263492.282429] Call Trace: Dec 18 23:32:21 userimap1 kernel: [263492.282441] [<ffffffff81103ee5>] print_bad_pte+0x1d5/0x280 Dec 18 23:32:21 userimap1 kernel: [263492.282448] [<ffffffff8110568a>] unmap_vmas+0xa1a/0xa20 Dec 18 23:32:21 userimap1 kernel: [263492.282458] [<ffffffff8137e501>] ? sch_direct_xmit+0x81/0x1d0 Dec 18 23:32:21 userimap1 kernel: [263492.282465] [<ffffffff8110b60d>] exit_mmap+0xbd/0x190 Dec 18 23:32:21 userimap1 kernel: [263492.282473] [<ffffffff81059cbd>] mmput+0x4d/0x120 Dec 18 23:32:21 userimap1 kernel: [263492.282481] [<ffffffff8105f282>] exit_mm+0x112/0x150 Dec 18 23:32:21 userimap1 kernel: [263492.282488] [<ffffffff8106104d>] do_exit+0x13d/0x800 Dec 18 23:32:21 userimap1 kernel: [263492.282496] [<ffffffff81072f31>] ? __dequeue_signal+0xe1/0x200 Dec 18 23:32:21 userimap1 kernel: [263492.282503] [<ffffffff81061765>] do_group_exit+0x55/0xd0 Dec 18 23:32:21 userimap1 kernel: [263492.282510] [<ffffffff81075251>] get_signal_to_deliver+0x1e1/0x3e0 Dec 18 23:32:21 userimap1 kernel: [263492.282517] [<ffffffff8100b315>] do_signal+0x75/0x7d0 Dec 18 23:32:21 userimap1 kernel: [263492.282523] [<ffffffff81103203>] ? print_vma_addr+0xb3/0x120 Dec 18 23:32:21 userimap1 kernel: [263492.282533] [<ffffffff8143856e>] ? printk+0x41/0x43 Dec 18 23:32:21 userimap1 kernel: [263492.282541] [<ffffffff81036436>] ? __bad_area_nosemaphore+0xf6/0x1e0 Dec 18 23:32:21 userimap1 kernel: [263492.282547] [<ffffffff810365ee>] ? bad_area_access_error+0x4e/0x60 Dec 18 23:32:21 userimap1 kernel: [263492.282553] [<ffffffff8100bac7>] do_notify_resume+0x57/0x60 Dec 18 23:32:21 userimap1 kernel: [263492.282559] [<ffffffff8100cadc>] retint_signal+0x48/0x8c
# 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32.36-xsserver x86_64 Debian 6.0.3 auth_cache_size = 1 M auth_verbose = yes base_dir = /var/run/dovecot/ default_vsz_limit = 2 G disable_plaintext_auth = no first_valid_uid = 20 lock_method = dotlock login_greeting = User-IMAP ready. login_trusted_networks = 194.109.26.128/27 mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes mailbox_idle_check_interval = 1 mins maildir_stat_dirs = yes mmap_disable = yes namespace { inbox = yes location = maildir:%Nu:INDEX=/var/spool/mail/dovecot-control/indexes/%1u/%2u/%u:INBOX=%Nu:CONTROL=/var/spool/mail/dovecot-control/%1u/%2u/%u/INBOX prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot.masterusers driver = passwd-file master = yes } passdb { args = cache_key=%u%r dovecot driver = pam } plugin { quota = fs:User quota } protocols = imap service auth { client_limit = 5000 } service imap-login { process_min_avail = 8 service_count = 0 vsz_limit = 2 G } service imap { process_limit = 4096 vsz_limit = 2 G } shutdown_clients = no ssl_cert =
Have you tried using a modern kernel? that one is about 2 years old.
On Mon, 2011-12-19 at 00:32 +0100, Cor Bosman wrote:
Hey all, I upgraded some servers today from Debian Lenny to Debian Squeeze, and after the upgrade I started getting dovecot crashes. I was on 2.0.13 but got these there as well, and hoped upgrading to 2.0.16 would help. It didn't. Anyone have an idea?
Cor
# 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32.36-xsserver x86_64 Debian 6.0.3
Noel Butler noel.butler@ausics.net wrote:
On Mon, 2011-12-19 at 00:32 +0100, Cor Bosman wrote:
# 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32.36-xsserver x86_64 Debian 6.0.3
Have you tried using a modern kernel? that one is about 2 years old.
Well, this _is_ the kernel from Debian Stable and based on the Long-Term-Release from the kernel maintainers.
Besides, from the suffix i assume this may be a virtual server, so it may be not possible for Cor to even change the kernel himself.
Grüße, Sven.
-- Sigmentation fault. Core dumped.
On Mon, 2011-12-19 at 02:32 +0100, Sven Hartge wrote:
Noel Butler noel.butler@ausics.net wrote:
On Mon, 2011-12-19 at 00:32 +0100, Cor Bosman wrote:
# 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32.36-xsserver x86_64 Debian 6.0.3
Have you tried using a modern kernel? that one is about 2 years old.
Well, this _is_ the kernel from Debian Stable and based on the Long-Term-Release from the kernel maintainers.
So what? It is not anything current, that the kernel dev team would waste their time on. Please remember, there is a massive difference between the kernel maintainers, and the debian kernel package maintainers, do not confuse the two, because the later have nothing to do with the former.
Besides, from the suffix i assume this may be a virtual server, so it may be not possible for Cor to even change the kernel himself.
Given who Cor is, I'd be actually horrified if he was running any of his plethora of mail servers on a virtual server. hint: don't read too much into the uname value.
On 19-12-11 4:13 AM, Noel Butler wrote:
On Mon, 2011-12-19 at 02:32 +0100, Sven Hartge wrote:
Noel Butlernoel.butler@ausics.net wrote:
On Mon, 2011-12-19 at 00:32 +0100, Cor Bosman wrote:
# 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32.36-xsserver x86_64 Debian 6.0.3
Have you tried using a modern kernel? that one is about 2 years old.
Well, this _is_ the kernel from Debian Stable and based on the Long-Term-Release from the kernel maintainers.
So what? It is not anything current, that the kernel dev team would waste their time on.
The kernel developers actually do "waste their time" on the 2.6.32.x kernel. It's a long-term stable kernel, there are frequent releases on kernel.org (I admit, .36 is a bit long in the tooth, latest is .50, released about 2 weeks ago).
Mike.
On 19.12.2011, at 1.32, Cor Bosman wrote:
Hey all, I upgraded some servers today from Debian Lenny to Debian Squeeze, and after the upgrade I started getting dovecot crashes. I was on 2.0.13 but got these there as well, and hoped upgrading to 2.0.16 would help. It didn't. Anyone have an idea?
Dec 18 23:32:21 userimap1 kernel: [263492.245536] imap[19665]: segfault at 7f108efb7f60 ip 00007f108ecd37e0 sp 00007fff73c3d658 error 5 in libc-2.11.2.so[7f108ec5d000+158000]
gdb backtrace of the crash would be helpful: http://dovecot.org/bugreport.html
Dec 18 23:32:21 userimap1 kernel: [263492.245663] BUG: Bad page map in process imap pte:00000001 pmd:09767067
Looks more like a kernel bug though.
I installed a newer kernel on these boxes, and it's fixed. Seems to be a problem with the stock debian squeeze kernel. Not a dovecot issue, but others with a stable squeeze box might see similar problems so good to have it in the archive :)
regards,
Cor
On 20/12/2011 09:11, Cor Bosman wrote:
I installed a newer kernel on these boxes, and it's fixed. Seems to be a problem with the stock debian squeeze kernel. Not a dovecot issue, but others with a stable squeeze box might see similar problems so good to have it in the archive :)
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
2011/12/20 Ron Leach ronleach@tesco.net:
On 20/12/2011 09:11, Cor Bosman wrote:
I installed a newer kernel on these boxes, and it's fixed. Seems to be a problem with the stock debian squeeze kernel. Not a dovecot issue, but others with a stable squeeze box might see similar problems so good to have it in the archive :)
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
-- Chris
am 22.12.11 00:15 schrieb Christopher Stolzenberg
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
-- Chris
-- Mit freundlichen Grüßen, with kind regards, Jim Knuth
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
-- Chris
On Thu, 2011-12-22 at 00:49 +0100, Christopher Stolzenberg wrote:
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
-- Chris
Reasons for debian: They have largest number of packages! ... oh Wait! thats because they break up simple packages into 8-10 sub packages where as other distros use single or split in two .. yeah, scratch that... you're right, no pro's that I can think of ;)
Ahhh just before I hit send I remember one, debian, like windows, is an ideal distro on a server in a Colo that charges for remote hands (incl reboots), cause they have the highest fail rate.
Most stable OS's from colo are freebsd, slackware, RHEL, CentOS (ok same thing) and SuSE, and surprisingly, we once had a customer with an old win2K box back in mid 00's, that was very well behaved, and it was busy, they ran a concert/band/event ticketing site on it, truly amazed me that box.
Worse OS's would be netbsd, fedora, debian, ubuntu, mint, windows* .. but very very nice money earners for remote hands :P
On Dec 21, 2011 9:13 PM, "Noel Butler" noel.butler@ausics.net wrote:
On Thu, 2011-12-22 at 00:49 +0100, Christopher Stolzenberg wrote:
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
Indeed; very many of us use Debian stable. Which kernel did you
install
that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
I'm with Jim. Debian has served me well for years. This is just distro-bias. Sure, you need modicum more sense and hands on experience, but that's not bad thing in a production environment..
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front, with Ubuntu panting along behind..
Simon
Reasons for debian: They have largest number of packages! ... oh Wait! thats because they break up simple packages into 8-10 sub packages where as other distros use single or split in two .. yeah, scratch that... you're right, no pro's that I can think of ;)
Ahhh just before I hit send I remember one, debian, like windows, is an ideal distro on a server in a Colo that charges for remote hands (incl reboots), cause they have the highest fail rate.
Most stable OS's from colo are freebsd, slackware, RHEL, CentOS (ok same thing) and SuSE, and surprisingly, we once had a customer with an old win2K box back in mid 00's, that was very well behaved, and it was busy, they ran a concert/band/event ticketing site on it, truly amazed me that box.
Worse OS's would be netbsd, fedora, debian, ubuntu, mint, windows* .. but very very nice money earners for remote hands :P
On Wed, 2011-12-21 at 23:18 -0500, Simon Brereton wrote:
I'm with Jim. Debian has served me well for years. This is just distro-bias. Sure, you need modicum more sense and hands on experience,
distro holy ways will outlast the real world holy wars, we each have a distro we all stand by, else there would only be one distro.
but that's not bad thing in a production environment..
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front, with Ubuntu panting along behind..
Simon
I'm yet to meet a debian based admin who uses source, they only seem to think that apt is only way of installing stuff. They are scared of conflicts, who knows. Most the servers in the DC's I've run or worked in are all either freebsd, RHEL, slackware or gentoo, the later two being my personal favourites, that said, I do use ubuntu LTS on pc's/laptop, if there was no LTS however, I'd likely go back to fedora.
Ahhh just before I hit send I remember one, debian, like windows, is an ideal distro on a server in a Colo that charges for remote hands (incl reboots), cause they have the highest fail rate.
Most stable OS's from colo are freebsd, slackware, RHEL, CentOS (ok same thing) and SuSE, and surprisingly, we once had a customer with an old win2K box back in mid 00's, that was very well behaved, and it was busy, they ran a concert/band/event ticketing site on it, truly amazed me that box.
Worse OS's would be netbsd, fedora, debian, ubuntu, mint, windows* .. but very very nice money earners for remote hands :P
Am 22.12.2011 08:23, schrieb Noel Butler:
On Wed, 2011-12-21 at 23:18 -0500, Simon Brereton wrote:
I'm with Jim. Debian has served me well for years. This is just distro-bias. Sure, you need modicum more sense and hands on experience,
distro holy ways will outlast the real world holy wars, we each have a distro we all stand by, else there would only be one distro.
but that's not bad thing in a production environment..
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front, with Ubuntu panting along behind..
Simon
I'm yet to meet a debian based admin who uses source, they only seem to think that apt is only way of installing stuff. They are scared of conflicts, who knows. Most the servers in the DC's I've run or worked in are all either freebsd, RHEL, slackware or gentoo, the later two being my personal favourites, that said, I do use ubuntu LTS on pc's/laptop, if there was no LTS however, I'd likely go back to fedora.
X-mas is comming, we are waiting to get the perfect OS presented, so lets pray *g by the way ,where is the match to the dovecot list topic anyone identified the kernel bug?
Ahhh just before I hit send I remember one, debian, like windows, is an ideal distro on a server in a Colo that charges for remote hands (incl reboots), cause they have the highest fail rate.
Most stable OS's from colo are freebsd, slackware, RHEL, CentOS (ok same thing) and SuSE, and surprisingly, we once had a customer with an old win2K box back in mid 00's, that was very well behaved, and it was busy, they ran a concert/band/event ticketing site on it, truly amazed me that box.
Worse OS's would be netbsd, fedora, debian, ubuntu, mint, windows* .. but very very nice money earners for remote hands :P
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
On 2011-12-21 11:18 PM, Simon Brereton simon.brereton@buongiorno.com wrote:
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front,
Been using gentoo since about 2003 and never looked back... best and easiest distro to maintain, bar none, and the best support and documentation too.
--
Best regards,
Charles
On Thu, 22 Dec 2011 06:13:36 -0500 Charles Marcus articulated:
On 2011-12-21 11:18 PM, Simon Brereton simon.brereton@buongiorno.com wrote:
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front,
Been using gentoo since about 2003 and never looked back... best and easiest distro to maintain, bar none, and the best support and documentation too.
I have been a FreeBSD user since 2000. Dovecot and Postfix run well on the OS. Postfix should since it was developed on FreeBSD. Other than that though, most other apps require extensive patching in order to get them to work. And when it comes to drivers for modern devices, you can pretty much forget about it. After more than five years they still have not developed drivers for wireless "N" protocol devices. However, like Firefox, they do enjoy bumping versions numbers sans any true or radical improvement.
Just my 2¢.
-- Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
Have you ever considered the irony in the fact that we celebrate Christ's birthday every year by ignoring the fact that he would have celebrated Hanukkah?
On Thu, 2011-12-22 at 06:31 -0500, Jerry wrote:
On Thu, 22 Dec 2011 06:13:36 -0500 Charles Marcus articulated:
On 2011-12-21 11:18 PM, Simon Brereton simon.brereton@buongiorno.com wrote:
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front,
Been using gentoo since about 2003 and never looked back... best and easiest distro to maintain, bar none, and the best support and documentation too.
I have been a FreeBSD user since 2000. Dovecot and Postfix run well on the OS. Postfix should since it was developed on FreeBSD. Other than that though, most other apps require extensive patching in order to get them to work. And when it comes to drivers for modern devices, you can pretty much forget about it. After more than five years they still have not developed drivers for wireless "N" protocol devices. However, like Firefox, they do enjoy bumping versions numbers sans any true or radical improvement.
Just my 2¢.
Tis a shame that, freebsd used to leave linux behind in resource management, but in last 5 or so years, its been other way around and I kinda agree its like "time stood still"
On 22/12/2011 11:13, Charles Marcus wrote:
On 2011-12-21 11:18 PM, Simon Brereton simon.brereton@buongiorno.com wrote:
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front,
Been using gentoo since about 2003 and never looked back... best and easiest distro to maintain, bar none, and the best support and documentation too.
Wait... Back up... You mean there are *other* distributions of linux? I thought they were all just gentoo derivatives..?!!
:-)
Ed W
On 12/31/2011 02:20 PM Ed W wrote:
Wait... Back up... You mean there are *other* distributions of linux? I thought they were all just gentoo derivatives..?!!
:-)
Huh, I thought everything would be based on LFS [http://www.linuxfromscratch.org/lfs/].
Happy new year to the all Dovecot admins and Timo San.
Regards, Pascal
The trapper recommends today: cafebabe.1136514@localdomain.org
On Sat, 31 Dec 2011 13:20:53 +0000 Ed W articulated:
On 22/12/2011 11:13, Charles Marcus wrote:
On 2011-12-21 11:18 PM, Simon Brereton simon.brereton@buongiorno.com wrote:
It would be interesting to chart the number of threads caused by each distro. I don't know who would have the least, but I suspect gentoo and centos would be out in front,
Been using gentoo since about 2003 and never looked back... best and easiest distro to maintain, bar none, and the best support and documentation too.
Wait... Back up... You mean there are *other* distributions of linux? I thought they were all just gentoo derivatives..?!!
Be careful, you are going to get all of the FreeBSD aficionados panties in a knot. They claim the best documentation. Of course, what do they have to document?
Am 22.12.2011 00:49, schrieb Christopher Stolzenberg:
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
-- Chris
dont feed trolls
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
On Thu, 2011-12-22 at 08:08 +0100, Robert Schetterer wrote:
Am 22.12.2011 00:49, schrieb Christopher Stolzenberg:
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
-- Chris
dont feed trolls
Why is it when someone disagrees with someone's opinion they are labelled a troll, maybe because it hits a raw nerve huh? I dunno, and frankly don't care, but you have no right to do so just because you don't agree with Christophers statements.
Am 22.12.2011 08:27, schrieb Noel Butler:
On Thu, 2011-12-22 at 08:08 +0100, Robert Schetterer wrote:
Am 22.12.2011 00:49, schrieb Christopher Stolzenberg:
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
-- Chris
dont feed trolls
Why is it when someone disagrees with someone's opinion they are labelled a troll, maybe because it hits a raw nerve huh? I dunno, and frankly don't care, but you have no right to do so just because you don't agree with Christophers statements.
Hi Noel. this has left the topic of the dovecot list, after all , everyone is free to use what he likes and what fits best to solute the tec problem/task he/she likes to solve these everlasting os discussions are leading to nirvana are heavy boring, doesnt help on fixing the asked tec problem
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
On Thu, 2011-12-22 at 08:42 +0100, Robert Schetterer wrote:
Am 22.12.2011 08:27, schrieb Noel Butler:
On Thu, 2011-12-22 at 08:08 +0100, Robert Schetterer wrote:
Am 22.12.2011 00:49, schrieb Christopher Stolzenberg:
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
> Indeed; very many of us use Debian stable. Which kernel did you install > that is 2.0.16-friendly, and was this from Debian stable's updates > system? > > regards, Ron
Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
-- Chris
dont feed trolls
Why is it when someone disagrees with someone's opinion they are labelled a troll, maybe because it hits a raw nerve huh? I dunno, and frankly don't care, but you have no right to do so just because you don't agree with Christophers statements.
Hi Noel. this has left the topic of the dovecot list, after all , everyone is free to use what he likes and what fits best to solute the tec problem/task he/she likes to solve these everlasting os discussions are leading to nirvana are heavy boring, doesnt help on fixing the asked tec problem
Still, everyone is entitled to their opinion, including Christopher, perhaps it was not the right place for his comment, but none the less he made it, so he must feel that way, we should respect that without placing labels on him. This also is not the kernel list, since updating to a kernel released in the 21st century Cor's issue has gone away, so this thread is now rather entirely pointless on the Dovecot list. So I'll my participation in this thread, since its nearly 6pm, and tonight we have lots of prawns and lots and lots of beer and bourbon ;)
Merry Christmas to those who celebrate it.
On 22.12.2011 08:52, Noel Butler wrote:
On Thu, 2011-12-22 at 08:42 +0100, Robert Schetterer wrote:
Am 22.12.2011 08:27, schrieb Noel Butler:
On Thu, 2011-12-22 at 08:08 +0100, Robert Schetterer wrote:
Am 22.12.2011 00:49, schrieb Christopher Stolzenberg:
2011/12/22 Jim Knuth jk@jkart.de:
am 22.12.11 00:15 schrieb Christopher Stolzenberg
>> Indeed; very many of us use Debian stable. Which kernel did you install >> that is 2.0.16-friendly, and was this from Debian stable's updates >> system? >> >> regards, Ron > > > Debian for production servers??? That sounds dangerous.
sorry, but that`s absolutely bulls*it. *lol* Where have you read then THIS?
My own experience!
Reasons against Debian:
- No LSB certification (Linux Standard Base)
- No hardware certification (IBM, Dell, HP ...)
- Incompatible with some Broadcom NICs
- Full of bugs
- Free Kernel (non-free firmware removed... lol)
- Obsolete kernel (incompatible with new hardware)
- Obsolete packages
- Only one year support for oldstable *lol*
- Long delay for security updates
-- Chris
dont feed trolls
Why is it when someone disagrees with someone's opinion they are labelled a troll, maybe because it hits a raw nerve huh? I dunno, and frankly don't care, but you have no right to do so just because you don't agree with Christophers statements.
Hi Noel. this has left the topic of the dovecot list, after all , everyone is free to use what he likes and what fits best to solute the tec problem/task he/she likes to solve these everlasting os discussions are leading to nirvana are heavy boring, doesnt help on fixing the asked tec problem
Still, everyone is entitled to their opinion, including Christopher, perhaps it was not the right place for his comment, but none the less he made it, so he must feel that way, we should respect that without placing labels on him. This also is not the kernel list, since updating to a kernel released in the 21st century Cor's issue has gone away, so this thread is now rather entirely pointless on the Dovecot list. So I'll my participation in this thread, since its nearly 6pm, and tonight we have lots of prawns and lots and lots of beer and bourbon ;)
jeppa no need to flame ever
cheers !
Merry Christmas to those who celebrate it.
celebrate ,is a good idea, anytime
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
This also is not the kernel list, since updating to a kernel released in the 21st century Cor's issue has gone away, so this thread is now rather entirely pointless on the Dovecot list. So I'll my participation in
Actually, it hasn't. For the last few days we've been trying to pinpoint the problem by running half a dozen servers with different kernels and options. This 'kernel released in the 20th century' we have this problem with is the current stable kernel for debian. So instead of starting a distro war (and I thought canon/nikon, mac/pc were bad), lets be a bit more constructive. Plenty of people use the stable debian release.
It's happening on about half of our imap servers (20 or so), but on none of our other debian servers (hundreds). So it's not so weird to suspect a dovecot link. But it looks like it may be a driver issue on a specific range of hardware we use.
Once we find the issue, i'll report back. Until then, this doesn't look like a dovecot problem.
Cor
On Thu, Dec 22, 2011 at 09:22:07AM +0100, Cor Bosman wrote:
[..]
Actually, it hasn't. For the last few days we've been trying to pinpoint the problem by running half a dozen servers with different
In your initial posting you mentioned this happens on a machine wich was updated from Lenny to Squeeze. Did you try a fresh install? Sometimes I had some kernel related troubles in case of updateting releases.
[..]
Once we find the issue, i'll report back. Until then, this doesn't look like a dovecot problem.
Most likely it will be best to ask on a debian list.
Dennis
On Thu, 2011-12-22 at 09:22 +0100, Cor Bosman wrote:
This also is not the kernel list, since updating to a kernel released in the 21st century Cor's issue has gone away, so this thread is now rather entirely pointless on the Dovecot list. So I'll my participation in
Actually, it hasn't. For the last few days we've been trying to pinpoint the problem by running half a dozen servers with different kernels and options. This 'kernel released in the 20th century' we have this problem with is the current stable kernel for debian. So instead of starting a distro war (and I thought canon/nikon, mac/pc were bad), lets be a bit more constructive. Plenty of people use the stable debian release.
Ahh OK, your previous message said it was resolved, did the traceback show anything?
It's happening on about half of our imap servers (20 or so), but on none of our other debian servers (hundreds). So it's not so weird to suspect a dovecot link. But it looks like it may be a driver issue on a specific range of hardware we use.
maybe install a slackware or gentoo box and add it into the farm and see if same problem exists there as well, if so, clearly dovecot, if not, clearly debian, its why I still keep a RHEL box handy, it sits attached to the "dev" unit until I need it to assist to prove/disprove something.
All the best.
Am 22.12.2011 00:15, schrieb Christopher Stolzenberg:
2011/12/20 Ron Leach ronleach@tesco.net:
On 20/12/2011 09:11, Cor Bosman wrote:
I installed a newer kernel on these boxes, and it's fixed. Seems to be a problem with the stock debian squeeze kernel. Not a dovecot issue, but others with a stable squeeze box might see similar problems so good to have it in the archive :)
Indeed; very many of us use Debian stable. Which kernel did you install that is 2.0.16-friendly, and was this from Debian stable's updates system?
regards, Ron
Debian for production servers??? That sounds dangerous.
nonsense, Debian and clones are widly used for massive big server Farms
-- Chris
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
On Mon, 19 Dec 2011, Cor Bosman wrote:
# OS: Linux 2.6.32.36-xsserver x86_64 Debian 6.0.3
Are you sure you didn't roll your own kernel? Debian kernels I know don't use the ".36" suffix, but ship as 2.6.32-something and use their own internal version numbering.
For example, I found this on packages.debian.org: linux-image-2.6.32-5-amd64 (2.6.32-38) According to changelog, this actually carries patches from 2.6.32.46, yet only shows in uname as 2.6.32-5-amd64.
Also a friendly reminder for the question asked by Ron Leach: which kernel version did you install that appears to be Dovecot-friendlier? Would be very useful to have that in the archives as well.
By the way, happy holidays to everyone ;-)
-- Maarten
participants (16)
-
Charles Marcus
-
Christopher Stolzenberg
-
Cor Bosman
-
Dennis Guhl
-
Ed W
-
Jerry
-
Jim Knuth
-
Maarten Bezemer
-
Miquel van Smoorenburg
-
Noel Butler
-
Pascal Volk
-
Robert Schetterer
-
Ron Leach
-
Simon Brereton
-
Sven Hartge
-
Timo Sirainen