 | 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: |
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] strange problem w...| From | Sent On | Attachments |
|---|---|---|
| Tomas Srnka | Oct 11, 2006 12:27 pm | |
| Jay Lee | Oct 11, 2006 12:44 pm | |
| Sam Varshavchik | Oct 11, 2006 3:23 pm | |
| Jorge A. Palacios | Oct 11, 2006 4:23 pm | |
| Sam Varshavchik | Oct 11, 2006 6:27 pm | |
| Tomas Srnka | Oct 11, 2006 9:51 pm |
| 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: | Re: [courier-users] strange problem with authlib daemons | Actions... |
|---|---|---|
| From: | Sam Varshavchik (mrs...@courier-mta.com) | |
| Date: | Oct 11, 2006 3:23:04 pm | |
| List: | net.sourceforge.lists.courier-users | |
Tomas Srnka writes:
Hello, I have a strange problem. My server is running on CentOS 4.4 with latest courier-authlib. I've built RPM on my own. Steps how I built the packages:
$ rpmbuild -ta courier-authlib-0.58.tar.bz2 $ su -c "rpm -Uvh rpm/RPMS/i386/courier-authlib-0.58-1.i386.rpm " $ su -c "rpm -Uvh rpm/RPMS/i386/courier-authlib-userdb-0.58-1.i386.rpm " $ su -c "rpm -Uvh rpm/RPMS/i386/courier-authlib-devel-0.58-1.i386.rpm "
courier-config:
------------------ prefix=/usr/lib/courier exec_prefix=/usr/lib/courier bindir=/usr/lib/courier/bin sbindir=/usr/lib/courier/sbin libexecdir=/usr/lib/courier/libexec sysconfdir=/etc/courier datadir=/usr/lib/courier/share localstatedir=/var/spool/courier mailuser=daemon mailgroup=daemon mailuid=2 mailgid=2 configure_args="'--host=i686-redhat-linux-gnu' '--build=i686-redhat-linux-gnu' '--target=i386-redhat-linux' '--program-prefix=' '--prefix=/usr/lib/courier' '--exec-prefix=/usr/lib/courier' '--bindir=/usr/lib/courier/bin' '--sbindir=/usr/lib/courier/sbin' '--sysconfdir=/etc/courier' '--datadir=/usr/lib/courier/share' '--includedir=/usr/lib/courier/include' '--libdir=/usr/lib/courier/lib' '--libexecdir=/usr/lib/courier/libexec' '--localstatedir=/var/spool/courier' '--sharedstatedir=/usr/lib/courier/com' '--mandir=/usr/share/man' '--infodir=/usr/lib/courier/share/info' '--cache-file=courier.config.cache' '--enable-unicode=iso-8859-1,utf-8' 'CFLAGS=-O2 -g -march=i386 -mcpu=i686' 'CXXFLAGS=-O2 -g -march=i386 -mcpu=i686' 'FFLAGS=-O2 -g -march=i386 -mcpu=i686' 'build_alias=i686-redhat-linux-gnu' 'host_alias=i686-redhat-linux-gnu' 'target_alias=i386-redhat-linux' --with-db=gdbm --enable-utf7-folder-encoding"
The problem is that after 2-3 months I have more than 160 courier-authlib processes running and that's weird. Output of "ps -lfe" is at http://pcaudit.sk/courier-authlib.txt. Can you please help me?
Looks like you have multiple instance of authdaemond started. authdaemond normally employs a lock file to prevent it from being started more than once.
You must be running some kind of a cleanup process that removes authdaemond's lock file in /var/spool/authdaemon.
Additionally, you must have something that periodically tries to start authdaemond. Even if a cleanup process removed authdaemond's lock file and socket, rpm's initscripts normally run only when the server boots.
Did you, in the last month, attempt to start authdaemond yourself, manually?