Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-10 Thread Frank Sweetser
le dahut wrote: > Here you can find it > http://eole.orion.education.fr/depot/listing.php?repname=Eole&path=%2FOutils%2Feole-bacula%2Ftrunk%2Fbacula%2F&rev=0&sc=0 > > take a look at baculaservice.sh which is a the script used to manage > pre/post-backup/restore (services stop and start) Okay, so

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-10 Thread le dahut
Here you can find it http://eole.orion.education.fr/depot/listing.php?repname=Eole&path=%2FOutils%2Feole-bacula%2Ftrunk%2Fbacula%2F&rev=0&sc=0 take a look at baculaservice.sh which is a the script used to manage pre/post-backup/restore (services stop and start) Frank Sweetser a écrit : > le dah

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-10 Thread Frank Sweetser
le dahut wrote: > Let me explain it all again : > > - bacula-dir uses DirStartUp.py > - Dirstartup.py stop/starts services (samba, ldap, mysql) before/after > backup Can you post DirStartUp.py? -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network E

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-10 Thread le dahut
Let me explain it all again : - bacula-dir uses DirStartUp.py - Dirstartup.py stop/starts services (samba, ldap, mysql) before/after backup - sometimes on '/etc/init.d/bacula-dir restart' I get "Cannot bind port 9101: ERR=Address already in use" 'netstat -anpe|grep 9101' shows that one of the s

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-10 Thread Frank Sweetser
le dahut wrote: > It happens again during some quick test (several bacula-dir restart). > > I've written a DirStartUp.py that stops services before and starts them > after backup. It seems that the services that take the bacula port are > those which are stopped/started by DirStartUp.py. Do the

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-10 Thread le dahut
It happens again during some quick test (several bacula-dir restart). I've written a DirStartUp.py that stops services before and starts them after backup. It seems that the services that take the bacula port are those which are stopped/started by DirStartUp.py. Hopping this can help. le dahu

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-10 Thread le dahut
Does someone see any error in my services file ? le dahut wrote : > You can take a look at /etc/services here > ftp://dev-eole.ac-dijon.fr/Dev/services > > Frank Sweetser a écrit : >> le dahut wrote: >>> Has I said (not directly I assume), it is not corrupted and indeed, many >>> random process

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-09 Thread le dahut
You can take a look at /etc/services here ftp://dev-eole.ac-dijon.fr/Dev/services Frank Sweetser a écrit : > le dahut wrote: >> Has I said (not directly I assume), it is not corrupted and indeed, many >> random processes take successively port 9101 and when I finally restart >> all the incrimin

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-07 Thread Frank Sweetser
le dahut wrote: > Has I said (not directly I assume), it is not corrupted and indeed, many > random processes take successively port 9101 and when I finally restart > all the incriminated services, it ends on a bacula-dir process that > seems not to have been properly killed/closed by the init s

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-07 Thread Ryan Novosielski
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I suspect that it IS corrupt and you are incorrect. le dahut wrote: | Has I said (not directly I assume), it is not corrupted and indeed, many | random processes take successively port 9101 and when I finally restart | all the incriminated services, i

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-07 Thread le dahut
Has I said (not directly I assume), it is not corrupted and indeed, many random processes take successively port 9101 and when I finally restart all the incriminated services, it ends on a bacula-dir process that seems not to have been properly killed/closed by the init script. So why do I get

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-07 Thread Frank Sweetser
le dahut wrote: > 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 ca

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-07 Thread le dahut
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 an

Re: [Bacula-users] port 9101 not closed after bacula-director stop

2008-01-02 Thread Martin Simmons
> 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

[Bacula-users] port 9101 not closed after bacula-director stop

2008-01-02 Thread le dahut
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 : [EMAIL PROTECTED]:~# netstat -n Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Addr