Reynier Perez Mira wrote:
> Well I add this line: "127.0.0.1 gsdserver" to the hosts file and the same
> error still appear. Why?
That likely means that either the director is not listening on that port,
possibly because it's not running, or you've got a firewall rule blocking it.
To confirm thi
erez Mira
> CC: bacula-users@lists.sourceforge.net
> Asunto: Re: [Bacula-users] bconsole can't connect with bacula-director
>
> Reynier Perez Mira wrote:
> >> gsdserver doesn't resolve to the host that the director is
> running on
> >
> > Maybe,
Reynier Perez Mira wrote:
>> gsdserver doesn't resolve to the host that the director
>> is running on
>
> Maybe, this is the main error. When I restart Apache this error show up:
>> /etc/init.d/apache2 restart
> * Restarting web server apache2
>
On Jan 13, 2008 7:09 PM, Reynier Perez Mira <[EMAIL PROTECTED]> wrote:
> > gsdserver doesn't resolve to the host that the director
> > is running on
>
> Maybe, this is the main error. When I restart Apache this error show up:
> > /etc/init.d/apache2 restart
> * Restarting web server apache2
> apa
> gsdserver doesn't resolve to the host that the director
> is running on
Maybe, this is the main error. When I restart Apache this error show up:
> /etc/init.d/apache2 restart
* Restarting web server apache2
apache2: Could not reliably determine
Reynier Perez Mira wrote:
> bconsole Connecting to Director gsdserver:9101 13-ene 17:51 bconsole JobId
> 0: Fatal error: bsock.c:129 Unable to connect to Director daemon on
> gsdserver:9101. ERR=Conexión rechazada
I'm going to guess that the ERR here is something along the lines of
connection ref
