Bug#912633: Subject: Re: Bug#912633: courier-imap-ssl: No supported cipher suite with the recent switch to TLS 1.3 in OpenSSL 1.1.1.
Soren The symptom of getting a "imapd-ssl: No supported cipher suites have been found." message might be configuration related. I have a business client that decided to upgrade their mail server on their own this last weekend. It didn't go well for them and they had to call me. They had this same error. I looked in my notes from a few years back when I was doing some other courier upgrades (in 201604xx) and found something related to this which fixed my client's problem and it might fix yours. Check your courierd config file. If you have "TLS_TRUSTCERTS=/usr/lib/courier/rootcerts", comment that out. Add "TLS_TRUSTCERTS=/etc/ssl/certs" I remember seeing your bug a week or two ago. Check this and see if it helps. If it's not related, my apologies.
Bug#889961: courier-authdaemon: Upgrade failures in 0.68.0-4 package
I was working on this yesterday. First noticed it about a week ago. Here are the upstream bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144 https://github.com/systemd/systemd/issues/8085 And the money quotes: "looking at the bigger picture here: This change in systemd, while with security in mind, changes the way PIDfiles have been handled for the last ... forever." "and who will be blamed (again)? systemd of course, "breaking all the things again". And rightfully so. This is systemd breaking shit again for fun. On 02/09/2018 02:33 AM, Amos Jeffries wrote: It seems that the systemd/systemctl is removing the /run/courier/authdaemon/pid file underneath courier. Removing the line "PIDFile=/run/courier/authdaemon/pid" from the installed .service file resolves this problem and upgrade works fine. Amos
Bug#865058: (no subject)
Spectator here chiming in. Just upgraded and the module built okay for me. Likely a local system issue. Good luck getting it figured out OP. -->modinfo /lib/modules/4.9.0-3-amd64/updates/dkms/nvidia-current-drm.ko filename: /lib/modules/4.9.0-3-amd64/updates/dkms/nvidia-current-drm.ko version:375.66 supported: external license:MIT srcversion: C4CEF74C8A748A2437DB582 alias: pci:v10DEd0E00sv*sd*bc04sc80i00* alias: pci:v10DEd*sv*sd*bc03sc02i00* alias: pci:v10DEd*sv*sd*bc03sc00i00* depends:drm,drm_kms_helper,nvidia-modeset vermagic: 4.9.0-3-amd64 SMP mod_unload modversions parm: modeset:Enable atomic kernel modesetting (1 = enable, 0 = disable (default)) (bool)
Bug#840382: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31
Confirmed fixed as of 2:4.4.6+dfsg-2. If there is any release after which, I have not teted. On 10/14/2016 12:08 PM, Mathieu Parent wrote: To the recipients: Do you still have the problem when using latest packages from sid? I cant' reproduce the problem anymore. Thanks Mathieu Parent
Bug#822071: maildrop: Upgrade from courier-maildrop: Default delivery location changed from Maildirs $/HOME/Maildir to /var/mail/$USER
I am sorry this is late. I missed this mail when it came in. On 05/09/2016 10:16 AM, Marcus Wolschon wrote: a) 0.75.0-20 doesn't fix ANYTHING. It just adds a cryptic note to a NEWS file burried in /usr/share/doc . The existing /etc/courier/maildroprc rule file is not moved (is conversion needed?) to /etc/maildroprc . I agree that it's a really serious issue. Unfortunately the problem lies with the new guy uploading the packages. Until that changes, I don't expect this to get fixed right. You might want to start using courier from source. I would suggest installing apt-listbugs and apt-listchanges if you don't already have them installed. They will help you (the admin) be more aware of bugs, changes, and NEWS items when upgrading packages. b) How shall admins affected by this handle the tons of email that ended up in/var/spool/mail/ to get it delivered using the fixed maildrop rules? courier has no command do read mailspool files and pipe them through the delivery pipeline. I can't remember the exact format of the command I used to re-deliver all of the mail. It was something like this in a root bash shell: for EACH in /var/spool/mail/* ; do formail -d -n 5 -s maildrop < $EACH ; done ; unset EACH After this, delete the old mail spool files. The intent here is to tell formail to pipe the old messages back into maildrop. You might need to give the full path to maildrop there. Also, I forget the exact flags for formail. You should definitely test this on a maildir with one one or two messages in it first before you try to re-deliver everything. I get the feeling I forgot something important. Beware that if you re-deliver like this all the mail mail be re-processed (spamassassin, clamav, etc) depending on how you have your system set up.
Bug#822071: maildrop: Upgrade from courier-maildrop: Default delivery location changed from Maildirs $/HOME/Maildir to /var/mail/$USER
Package: maildrop Version: 2.8.3-0.1 Severity: grave Justification: causes non-serious data loss Recently I decided to upgrade courier (mta and imap) on one of my mail servers. It was a disaster. The quality of these packages is abysmal and dangerous. This is one of the many serious, grave, and critical bugs I ran into during that process. It appears that the default mail delivery location in maildrop/courier-maildrop has changed from being Maildirs ($HOME/Maildir) to spool files (/var/mail/). Upon upgrading my courier system, I found that new mail was being delivered to mailspool files in /var/mail instead of Maildirs, as it was previously. I don't know why this change has happened as I don't have much time to look into it, but it is definitely a default behavior change. This could definiely lead to data loss, and at the very least will be a pain if the admin has re-deliver the mail spool contents back to the Maildirs. A workaround is to configure the new /etc/maildroprc file DEFAULT parameter, which is convinently already typed out with the correct arguments and just needs to be uncommented. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages maildrop depends on: ii courier-authlib 0.66.4-7 ii libc62.22-7 ii libcourier-unicode1 1.4-2 ii libgcc1 1:5.3.1-14 ii libgdbm3 1.8.3-13.1 ii libpcre3 2:8.38-3.1 ii libstdc++6 5.3.1-14 Versions of packages maildrop recommends: ii courier-mta [mail-transport-agent] 0.75.0-18 maildrop suggests no packages. -- Configuration Files: /etc/maildroprc changed: DEFAULT="$HOME/Maildir" -- no debconf information
Bug#822068: courier-imap: init scripts completely broken
Package: courier-imap Version: 4.16.2+0.75.0-18 Severity: grave Justification: renders package unusable Recently I decided to upgrade courier (mta and imap) on one of my mail servers. It was a disaster. The quality of these packages is abysmal and dangerous. This is one of the many serious, grave, and critical bugs I ran into during that process. I have the following courier-related init scritps on my system: courier-mta: /etc/init.d/courier courier-authdaemon: /etc/init.d/courier-authdaemon courier-mta: /etc/init.d/courierfilter courier-imap: /etc/init.d/courier-imap courier-imap: /etc/init.d/courier-imap-ssl courier-mta: /etc/init.d/courier-msa courier-mta: /etc/init.d/courier-mta courier-mta: /etc/init.d/courier-mta-ssl Nearly all of these init scripts are broken in many ways. Almost nothing works. I would be shocked if any of this passes requirements of the Debian policy. There is no stdout or stderr provided from the init script. Failures result in no output. Success results in no output. There is no error/sanity checking. stop|status|restart|try-restart|force-reload are all broken. start is broken on multiple init scripts. The status argument fails and is not implemented on any of them that I can see. The stop argument fails to stop running daemons/programs. The only courier init script which behaves somewhat reasonably is /etc/init.d/courier-authdaemon -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages courier-imap depends on: ii courier-authlib 0.66.4-7 ii courier-base0.75.0-18 ii courier-mta [mail-transport-agent] 0.75.0-18 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.22-7 ii libcourier-unicode1 1.4-2 ii libgamin0 [libfam0] 0.1.10-5 ii libgdbm31.8.3-13.1 ii libidn111.32-3 ii sysvinit-utils 2.88dsf-59.3 courier-imap recommends no packages. Versions of packages courier-imap suggests: ii courier-doc 0.75.0-18 ii mutt [imap-client]1.5.24-1+b1 ii s-nail [imap-client] 14.8.8-1 -- Configuration Files: /etc/courier/imapd changed [not included] /etc/courier/imapd-ssl changed [not included] /etc/courier/imapd.cnf [Errno 13] Permission denied: u'/etc/courier/imapd.cnf' -- no debconf information
Bug#822067: courier-mta: init scripts completely broken
Package: courier-mta Version: 0.75.0-18 Severity: grave Justification: renders package unusable Recently I decided to upgrade courier (mta and imap) on one of my mail servers. It was a disaster. The quality of these packages is abysmal and dangerous. This is one of the many serious, grave, and critical bugs I ran into during that process. I have the following courier-related init scritps on my system: courier-mta: /etc/init.d/courier courier-authdaemon: /etc/init.d/courier-authdaemon courier-mta: /etc/init.d/courierfilter courier-imap: /etc/init.d/courier-imap courier-imap: /etc/init.d/courier-imap-ssl courier-mta: /etc/init.d/courier-msa courier-mta: /etc/init.d/courier-mta courier-mta: /etc/init.d/courier-mta-ssl Nearly all of these init scripts are broken in many ways. Almost nothing works. I would be shocked if any of this passes requirements of the Debian policy. There is no stdout or stderr provided from the init script. Failures result in no output. Success results in no output. There is no error/sanity checking. stop|status|restart|try-restart|force-reload are all broken. start is broken on multiple init scripts. The status argument fails and is not implemented on any of them that I can see. The stop argument fails to stop running daemons/programs. The only courier init script which behaves somewhat reasonably is /etc/init.d/courier-authdaemon -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages courier-mta depends on: ii courier-authlib0.66.4-7 ii courier-base 0.75.0-18 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.22-7 ii libcourier-unicode11.4-2 ii libgcc11:5.3.1-14 ii libgdbm3 1.8.3-13.1 ii libidn11 1.32-3 ii libnet-cidr-perl 0.17-1 ii libperl5.225.22.1-10 ii libstdc++6 5.3.1-14 ii sysvinit-utils 2.88dsf-59.3 courier-mta recommends no packages. Versions of packages courier-mta suggests: ii bsd-mailx [mail-reader] 8.1.2-0.20160123cvs-2 ii courier-doc 0.75.0-18 ii courier-filter-perl 0.200+ds-4 pn couriergrey ii emacs24 [mail-reader]24.5+1-6+b2 ii mutt [mail-reader] 1.5.24-1+b1 ii s-nail [mail-reader] 14.8.8-1 -- Configuration Files: /etc/courier/aliases/system [Errno 13] Permission denied: u'/etc/courier/aliases/system' /etc/courier/courierd changed [not included] /etc/courier/dsnheader.txt changed [not included] /etc/courier/esmtpauthclient [Errno 13] Permission denied: u'/etc/courier/esmtpauthclient' /etc/courier/esmtpd changed [not included] /etc/courier/esmtpd-msa changed [not included] /etc/courier/esmtpd-ssl changed [not included] /etc/courier/esmtpd.cnf [Errno 13] Permission denied: u'/etc/courier/esmtpd.cnf' /etc/courier/smtpaccess/default [Errno 13] Permission denied: u'/etc/courier/smtpaccess/default' /etc/init.d/courier-mta changed [not included] /etc/init.d/courier-mta-ssl changed [not included] -- debconf information excluded
Bug#822070: courier-mta: Transition from "daemon" user to "courier" user is handled terribly
Package: courier-mta Version: 0.75.0-18 Severity: grave Justification: renders package unusable Recently I decided to upgrade courier (mta and imap) on one of my mail servers. It was a disaster. The quality of these packages is abysmal and dangerous. This is one of the many serious, grave, and critical bugs I ran into during that process. It appears that recently a change was made to transition the courier-* system away from the generic "daemon" user towards the "courier" user. This is good and probably should have been a done a long time ago. However, this process is being handled terribly and will almost certainly result in broken mail systems and possibly (confirmed in my case) data loss. First, the administrator needs to be made aware of this change. It needs to be a NEWS item, there should probably be a confirmation dialog prompting the user for acknowledgment, and it needs to be documented, which it currently is not short of a tiny changelog line. In the case of /etc/courier/esmtpd, the MAILUSER and MAILGROUP parameters need to be checked and the administrator should be VIOLENTLY notified if these need to get updated. There may be other configuration items which need updating which I am not aware of. I use only a portion of the courier suite. Proper file permissions need to be set. in my case, the courier system could not read any of my .pem files and some other files/directories because they were set to ownership root:courier but had permissions -rw---. A chmod g+r should probably be done against similar files. A change like this needs to be done carefully and with consideration. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages courier-mta depends on: ii courier-authlib0.66.4-7 ii courier-base 0.75.0-18 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.22-7 ii libcourier-unicode11.4-2 ii libgcc11:5.3.1-14 ii libgdbm3 1.8.3-13.1 ii libidn11 1.32-3 ii libnet-cidr-perl 0.17-1 ii libperl5.225.22.1-10 ii libstdc++6 5.3.1-14 ii sysvinit-utils 2.88dsf-59.3 courier-mta recommends no packages. Versions of packages courier-mta suggests: ii bsd-mailx [mail-reader] 8.1.2-0.20160123cvs-2 ii courier-doc 0.75.0-18 ii courier-filter-perl 0.200+ds-4 pn couriergrey ii emacs24 [mail-reader]24.5+1-6+b2 ii mutt [mail-reader] 1.5.24-1+b1 ii s-nail [mail-reader] 14.8.8-1 -- Configuration Files: /etc/courier/aliases/system [Errno 13] Permission denied: u'/etc/courier/aliases/system' /etc/courier/courierd changed [not included] /etc/courier/dsnheader.txt changed [not included] /etc/courier/esmtpauthclient [Errno 13] Permission denied: u'/etc/courier/esmtpauthclient' /etc/courier/esmtpd changed [not included] /etc/courier/esmtpd-msa changed [not included] /etc/courier/esmtpd-ssl changed [not included] /etc/courier/esmtpd.cnf [Errno 13] Permission denied: u'/etc/courier/esmtpd.cnf' /etc/courier/smtpaccess/default [Errno 13] Permission denied: u'/etc/courier/smtpaccess/default' /etc/init.d/courier-mta changed [not included] /etc/init.d/courier-mta-ssl changed [not included] -- debconf information excluded
Bug#822066: courier-mta-ssl init script broken
Package: courier-mta Version: 0.75.0-18 Severity: grave Justification: renders package unusable Recently I decided to upgrade courier (mta and imap) on one of my mail servers. It was a disaster. The quality of these packages is abysmal and dangerous. This is one of the many serious, grave, and critical bugs I ran into during that process. The following init script is broken: /etc/init.d/courier-mta-ssl The offening line is: DO_START=$(sed -ne 's/^ESMTPDSSLSTART=\([^[:space:]]*\)/\1/p' /etc/courier/esmtpd-msa | tr "A-Z" "a-z") This is the wrong configuration file. The result will be either a broken system or worse an insecure system where a daemon is running when it should not be. Corrected: DO_START=$(sed -ne 's/^ESMTPDSSLSTART=\([^[:space:]]*\)/\1/p' /etc/courier/esmtpd-ssl | tr "A-Z" "a-z") -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages courier-mta depends on: ii courier-authlib0.66.4-7 ii courier-base 0.75.0-18 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.22-7 ii libcourier-unicode11.4-2 ii libgcc11:5.3.1-14 ii libgdbm3 1.8.3-13.1 ii libidn11 1.32-3 ii libnet-cidr-perl 0.17-1 ii libperl5.225.22.1-10 ii libstdc++6 5.3.1-14 ii sysvinit-utils 2.88dsf-59.3 courier-mta recommends no packages. Versions of packages courier-mta suggests: ii bsd-mailx [mail-reader] 8.1.2-0.20160123cvs-2 ii courier-doc 0.75.0-18 ii courier-filter-perl 0.200+ds-4 pn couriergrey ii emacs24 [mail-reader]24.5+1-6+b2 ii mutt [mail-reader] 1.5.24-1+b1 ii s-nail [mail-reader] 14.8.8-1 -- Configuration Files: /etc/courier/aliases/system [Errno 13] Permission denied: u'/etc/courier/aliases/system' /etc/courier/courierd changed [not included] /etc/courier/dsnheader.txt changed [not included] /etc/courier/esmtpauthclient [Errno 13] Permission denied: u'/etc/courier/esmtpauthclient' /etc/courier/esmtpd changed [not included] /etc/courier/esmtpd-msa changed [not included] /etc/courier/esmtpd-ssl changed [not included] /etc/courier/esmtpd.cnf [Errno 13] Permission denied: u'/etc/courier/esmtpd.cnf' /etc/courier/smtpaccess/default [Errno 13] Permission denied: u'/etc/courier/smtpaccess/default' /etc/init.d/courier-mta changed [not included] /etc/init.d/courier-mta-ssl changed [not included] -- debconf information excluded
Bug#822065: courier-mta: init script references the wrong configuration file; completely broken.
Package: courier-mta Version: 0.75.0-18 Severity: grave Justification: renders package unusable Recently I decided to upgrade courier (mta and imap) on one of my mail servers. It was a disaster. The quality of these packages is abysmal and dangerous. This is one of the many serious, grave, and critical bugs I ran into during that process. The following init script is broken: /etc/init.d/courier-mta The offening line is: DO_START=$(sed -ne 's/^ESMTPDSSLSTART=\([^[:space:]]*\)/\1/p' /etc/courier/esmtpd-msa | tr "A-Z" "a-z") This is the wrong configuration statement and file. The result will be either a broken system or worse an insecure system where a daemon is running when it should not be. Corrected: DO_START=$(sed -ne 's/^ESMTPDSTART=\([^[:space:]]*\)/\1/p' /etc/courier/esmtpd | tr "A-Z" "a-z") -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages courier-mta depends on: ii courier-authlib0.66.4-7 ii courier-base 0.75.0-18 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.22-7 ii libcourier-unicode11.4-2 ii libgcc11:5.3.1-14 ii libgdbm3 1.8.3-13.1 ii libidn11 1.32-3 ii libnet-cidr-perl 0.17-1 ii libperl5.225.22.1-10 ii libstdc++6 5.3.1-14 ii sysvinit-utils 2.88dsf-59.3 courier-mta recommends no packages. Versions of packages courier-mta suggests: ii bsd-mailx [mail-reader] 8.1.2-0.20160123cvs-2 ii courier-doc 0.75.0-18 ii courier-filter-perl 0.200+ds-4 pn couriergrey ii emacs24 [mail-reader]24.5+1-6+b2 ii mutt [mail-reader] 1.5.24-1+b1 ii s-nail [mail-reader] 14.8.8-1 -- Configuration Files: /etc/courier/aliases/system [Errno 13] Permission denied: u'/etc/courier/aliases/system' /etc/courier/courierd changed [not included] /etc/courier/dsnheader.txt changed [not included] /etc/courier/esmtpauthclient [Errno 13] Permission denied: u'/etc/courier/esmtpauthclient' /etc/courier/esmtpd changed [not included] /etc/courier/esmtpd-msa changed [not included] /etc/courier/esmtpd-ssl changed [not included] /etc/courier/esmtpd.cnf [Errno 13] Permission denied: u'/etc/courier/esmtpd.cnf' /etc/courier/smtpaccess/default [Errno 13] Permission denied: u'/etc/courier/smtpaccess/default' /etc/init.d/courier-mta changed [not included] /etc/init.d/courier-mta-ssl changed [not included] -- debconf information excluded
Bug#820752: nfs-kernel-server: nfs server fails to start: nfds module can not be loaded: failed to allocate reply cache
Package: nfs-kernel-server Version: 1:1.2.8-9 Severity: grave Justification: renders package unusable Relatively new system and I'm trying to get nfsd working, but it fails. After looking at journalctl, it seems that the nfsd module can not be loaded: Apr 11 17:37:50.511723 myhost kernel: Installing knfsd (copyright (C) 1996 o...@monad.swb.de). Apr 11 17:37:50.511864 myhost kernel: modprobe: page allocation failure: order:4, mode:0x2040d0 Apr 11 17:37:50.511949 myhost kernel: CPU: 3 PID: 15440 Comm: modprobe Not tainted 4.3.0-1-amd64 #1 Debian 4.3.3-7 Apr 11 17:37:50.512036 myhost kernel: Hardware name: Motherboard by ZOTAC ZBOX-CI320NANO series/ZBOX-CI320NANO series, BIOS B219P026 05/19/2015 Apr 11 17:37:50.512118 myhost kernel: 2423ca77 812ddcf9 002040d0 Apr 11 17:37:50.512185 myhost kernel: 81164947 8802362120c0 002040d0 Apr 11 17:37:50.512251 myhost kernel: 2423ca77 0004 2423ca77 8802362120c0 Apr 11 17:37:50.512316 myhost kernel: Call Trace: Apr 11 17:37:50.512380 myhost kernel: [] ? dump_stack+0x40/0x57 Apr 11 17:37:50.512445 myhost kernel: [] ? warn_alloc_failed+0xf7/0x150 Apr 11 17:37:50.512514 myhost kernel: [] ? __alloc_pages_nodemask+0x2e8/0xa10 Apr 11 17:37:50.512579 myhost kernel: [] ? kmem_getpages+0x5b/0x100 Apr 11 17:37:50.512660 myhost kernel: [] ? fallback_alloc+0x1ae/0x1f0 Apr 11 17:37:50.512728 myhost kernel: [] ? nfsd_reply_cache_init+0xa4/0x100 [nfsd] Apr 11 17:37:50.512793 myhost kernel: [] ? __kmalloc+0x17c/0x1c0 Apr 11 17:37:50.512862 myhost kernel: [] ? trace_event_define_fields_nfsd_stateid_class+0xab/0xab [nfsd] Apr 11 17:37:50.512927 myhost kernel: [] ? nfsd_reply_cache_init+0xa4/0x100 [nfsd] Apr 11 17:37:50.512992 myhost kernel: [] ? init_nfsd+0x4b/0xf55 [nfsd] Apr 11 17:37:50.513059 myhost kernel: [] ? do_one_initcall+0xb2/0x200 Apr 11 17:37:50.513123 myhost kernel: [] ? do_init_module+0x5b/0x1dc Apr 11 17:37:50.513195 myhost kernel: [] ? load_module+0x2173/0x2780 Apr 11 17:37:50.513259 myhost kernel: [] ? __symbol_put+0x60/0x60 Apr 11 17:37:50.513323 myhost kernel: [] ? kernel_read+0x4b/0x70 Apr 11 17:37:50.513388 myhost kernel: [] ? SyS_finit_module+0xae/0xe0 Apr 11 17:37:50.513460 myhost kernel: [] ? system_call_fast_compare_end+0xc/0x67 Apr 11 17:37:50.513528 myhost kernel: Mem-Info: Apr 11 17:37:50.513599 myhost kernel: active_anon:11872 inactive_anon:9752 isolated_anon:0 active_file:405288 inactive_file:489975 isolated_file:0 unevictable:0 dirty:4 writeback:0 unstable:0 slab_reclaimable:808833 slab_unreclaimable:19398 mapped:12138 shmem:5128 pagetables:2759 bounce:0 free:258703 free_pcp:49 free_cma:0 Apr 11 17:37:50.513675 myhost kernel: Node 0 DMA free:15896kB min:20kB low:24kB high:28kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB managed:15900kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:4kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes Apr 11 17:37:50.513742 myhost kernel: lowmem_reserve[]: 0 2870 7861 7861 Apr 11 17:37:50.513811 myhost kernel: Node 0 DMA32 free:703004kB min:4112kB low:5140kB high:6168kB active_anon:13524kB inactive_anon:17448kB active_file:500576kB inactive_file:512192kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3018236kB managed:2942260kB mlocked:0kB dirty:0kB writeback:0kB mapped:16376kB shmem:5232kB slab_reclaimable:1151992kB slab_unreclaimable:29404kB kernel_stack:1152kB pagetables:4056kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Apr 11 17:37:50.514824 myhost kernel: lowmem_reserve[]: 0 0 4990 4990 Apr 11 17:37:50.514899 myhost kernel: Node 0 Normal free:315912kB min:7152kB low:8940kB high:10728kB active_anon:33964kB inactive_anon:21560kB active_file:1120576kB inactive_file:1447708kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:5242880kB managed:5110500kB mlocked:0kB dirty:16kB writeback:0kB mapped:32176kB shmem:15280kB slab_reclaimable:2083336kB slab_unreclaimable:48188kB kernel_stack:1440kB pagetables:6980kB unstable:0kB bounce:0kB free_pcp:188kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Apr 11 17:37:50.516638 myhost kernel: lowmem_reserve[]: 0 0 0 0 Apr 11 17:37:50.516721 myhost kernel: Node 0 DMA: 2*4kB (UE) 2*8kB (UE) 2*16kB (UE) 1*32kB (E) 3*64kB (UE) 2*128kB (UE) 2*256kB (UE) 1*512kB (E) 2*1024kB (UE) 2*2048kB (EM) 2*4096kB (M) = 15896kB Apr 11 17:37:50.516789 myhost
