No it is not the problem, when I restart ldap, it is Mysql that listens on 9101, when I restart Mysql, Sympa listens on 9101, when I restart Sympa, etc... finally I get to the process bacula-dir, and when I kill its PID, nothing listens on port 9101 any more and THEN I can restart bacula-dir and find a well working bacula-director.
This appears on many servers. What's happening with port 9101 ? Martin Simmons a écrit : >>>>>> On Wed, 02 Jan 2008 15:23:09 +0100, le dahut said: >> Hello, >> >> I wrote a few weeks ago about the error "Cannot bind port 9101". >> >> Here is an output from once I have stopped bacula-director using the >> standard inti scripts : >> >> And from : >> [EMAIL PROTECTED]:~# netstat -anpee|grep 91 >> tcp 0 0 0.0.0.0:9101 0.0.0.0:* LISTEN 0 >> 10165548 20136/slapd > > That is bizare, slapd (presumably) is actually listening on that port. Maybe > your /etc/services is corrupted so all names map to 9101? Or you get the > services db from NIS etc and that is corrupt (check the "services" line in > /etc/nsswitch.conf)? > > __Martin > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
