On 2010-01-12 17:58, Sam Varshavchik wrote: > Cedric Fontaine (Easy Soft) writes: > >> Hello, >> >> I tried to test authdaemond with authtest but I always received : >> >> ERR: authdaemon: s_connect() failed: Connection refused >> ERR: [Hint: perhaps authdaemond is not running?] >> Authentication FAILED: Connection refused >> >> The process seems to be running well >> root 7810 0.0 0.0 1660 432 ? S 21:35 0:00 >> /usr/local/sbin/courierlogger -pid=/usr/local/var/spool/authdaemon/pid >> -start /usr/local/libexec/courier-authlib/authdaemond >> root 7811 0.0 0.0 5624 1452 ? S 21:35 0:00 >> /usr/local/libexec/courier-authlib/authdaemond > > Perhaps you've previously had a different version of courier-authlib > installed, configured differently, and you're invoking authtest from a > different version that was configured to connect to a different socket.
And how can I debug that situation ? How can I find where it tries to connect to ? Which socket should authdaemon listen to ? -- Cordialement, Cedric Fontaine EASY SOFT SA www.easysoft.eu & NOZUMI SOLUTIONS inc. www.nozumi.ca Connaissez vous notre portail de reservation d'hotels ? www.easyresort.fr ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
