On 01/28/2015 1:28 am, Luc Van der Veken wrote:
On 27 January 2015 21:18, dweimer wrote:
it appears to already have determined the IP prior to it hanging.
Putting it back to IP instantly connects.
Yes, but I see it's connecting to another IP address (...5.4 instead of
...1.4).
Was it
dweimer wrote (2015/01/27):
...
Interesting. What did you do right before suddenly actually?
Nothing, or something and somewhere? :o)
It had me scratching my head for a while, because it was still half
working. My nagios and bacula daemons couldn't find any *.local names
anymore, but I
On 01/28/2015 9:09 am, Cejka Rudolf wrote:
dweimer wrote (2015/01/27):
...
Interesting. What did you do right before suddenly actually?
Nothing, or something and somewhere? :o)
It had me scratching my head for a while, because it was still half
working. My nagios and bacula daemons
On 01/28/2015 10:46 AM, dweimer wrote:
host file is default, only has the default local host entries.
root@bacula:/ # cat /etc/hosts | grep -v ^#
::1 localhost localhost.my.domain
127.0.0.1 localhost localhost.my.domain
It isn't just this one hostname that
On 01/27/2015 6:40 am, Cejka Rudolf wrote:
dweimer wrote (2015/01/26):
I did find a work around, but not sure where the problem is for sure,
going to post on FreeBSD list as well. the fix, convert all my
hostnames
in configuration files from fully qualified DNS to IP addresses. I
just
did
On 01/27/2015 8:11 am, dweimer wrote:
On 01/27/2015 6:40 am, Cejka Rudolf wrote:
dweimer wrote (2015/01/26):
I did find a work around, but not sure where the problem is for sure,
going to post on FreeBSD list as well. the fix, convert all my
hostnames
in configuration files from fully
On 01/27/2015 02:17 PM, dweimer wrote:
OK, this is just strange, I rebuilt all the ports on my FreeBSD server,
then changed just the bconsole.conf file back to the DNS name using
bconsole -d 500, it resolves the name then hangs, it will timeout if I
wait long enough.
Does BSD have
On 01/27/2015 2:33 pm, Dimitri Maziuk wrote:
On 01/27/2015 02:17 PM, dweimer wrote:
OK, this is just strange, I rebuilt all the ports on my FreeBSD
server,
then changed just the bconsole.conf file back to the DNS name using
bconsole -d 500, it resolves the name then hangs, it will timeout
On 27 January 2015 21:18, dweimer wrote:
it appears to already have determined the IP prior to it hanging.
Putting it back to IP instantly connects.
Yes, but I see it's connecting to another IP address (...5.4 instead of ...1.4).
Was it supposed to do that because you changed network
dweimer wrote (2015/01/26):
I did find a work around, but not sure where the problem is for sure,
going to post on FreeBSD list as well. the fix, convert all my hostnames
in configuration files from fully qualified DNS to IP addresses. I just
did this on a hunch, but apparently something
...@dweimer.net]
Sent: 27 January 2015 3:38
To: Bacula Users
Subject: Re: [Bacula-users] Bacula 7 on FreeBSD, suddenly can't do anything
On 01/26/2015 8:04 pm, dweimer wrote:
My bconsole program suddenly can't connect to the director, My webacula
setup does very slowly (as in 3 minutes to load a page
On 01/27/2015 10:15 am, Luc Van der Veken wrote:
Probably not what's wrong in your case, it's even a different OS here
(Linux), but the symptoms are so similar that I reply anyway:
* Did you recently install avahi or (Apple's) bonjour / zeroconf?
* Are you using a '.local' TLD for a local
My bconsole program suddenly can't connect to the director, My webacula
setup does very slowly (as in 3 minutes to load a page) give me data.
Everything was running fine when backups ran just after midnight. No
updates were installed since the backups were ran, I have restarted
services,
On 01/26/2015 8:04 pm, dweimer wrote:
My bconsole program suddenly can't connect to the director, My webacula
setup does very slowly (as in 3 minutes to load a page) give me data.
Everything was running fine when backups ran just after midnight. No
updates were installed since the backups were
14 matches
Mail list logo
