bconsole - performance

[Stefan Klatt]

Hi Jörg,

I use bareos 16.3.1 (01Jul16) on two server and have a little problem
with bconsole. It needs a long time to connect to the director on the
same machine.
With 15.2.2 this was really fast.

Regards

Stefan

--
*CaC, Computer and Communication*
Inhaber Stefan Klatt
End-2-End Senior Network Consultant
Triftstrasse 9
60528 Frankfurt
Germany
USt-IdNr.: DE260461592

Tel.: +49-(0)172-6807809
Tel.: +49-(0)69-67808-900
Fax: +49-(0)69-67808-837
Email: stefan...@cac-netzwerk.de
Profil: http://www.cac-netzwerk.de/profil

[Jörg Steffens]

Am 29.08.2016 um 23:46 schrieb Stefan Klatt:
> Hi Jörg,
>
> I use bareos 16.3.1 (01Jul16) on two server and have a little problem
> with bconsole. It needs a long time to connect to the director on the
> same machine.
> With 15.2.2 this was really fast.

I assume, it might be a DNS lookup problem.
Take a look into your bconsole.conf.
Maybe change the address directive to 127.0.0.1.

Jörg
--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer:
S. Dühr, M. Außendorf, Jörg Steffens, P. Storz, M. v. Wieringen

[Bruno Friedmann]

Beside jorg's advise localhost on modern system can also resolv ::1 the ipv6 address. So be sure to be able to connect to it telnet ::1 9101 sould answer. ..

> --
> You received this message because you are subscribed to the Google Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
> To post to this group, send email to bareos...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

[Stefan Klatt]

Hi Jörg,

I tried a view things... and found that bconsole needs only a long time
to connect to the director if I use the name galaxy.cac.local (
192.168.76.2). If I use localhost or one of both IP addresses
(192.168.76.2 or 127.0.0.1) it's fast. I know this seems to be a DNS
problem, but why work all other programs like ping and bareos 15.2
without any problem? Telnet opens immediately a session to
galaxy.cac.local:9101 too.
This happens on two server.

Probably there is glitch in my configuration and I don't see it.

Here my configuration:

CentOS 7.2 actual patchlevel
Bareos 16.3.1 (01 July 2016)
IPv6 disabled
Firewall disabled

hosts:
192.168.76.2 galaxy.cac.local galaxy
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
#::1 localhost localhost.localdomain localhost6
localhost6.localdomain6

Interfaces:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.76.2 netmask 255.255.255.0 broadcast 192.168.76.255
ether 00:50:56:9c:c7:75 txqueuelen 1000 (Ethernet)
RX packets 1348739 bytes 977232768 (931.9 MiB)
RX errors 0 dropped 17 overruns 0 frame 0
TX packets 3443570 bytes 4329168020 (4.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 0 (Lokale Schleife)
RX packets 113353779 bytes 2758091387290 (2.5 TiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 113353779 bytes 2758091387290 (2.5 TiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


bconsole.conf

Director {
Name = galaxy-dir
DIRport = 9101
address = galaxy.cac.local
# address = 192.168.76.2
Password = "XXXXXccccVVVV"
}

Regards

Stefan

Am 30.08.2016 um 18:40 schrieb Jörg Steffens:

> Am 29.08.2016 um 23:46 schrieb Stefan Klatt:
>> Hi Jörg,
>>
>> I use bareos 16.3.1 (01Jul16) on two server and have a little problem
>> with bconsole. It needs a long time to connect to the director on the
>> same machine.
>> With 15.2.2 this was really fast.
> I assume, it might be a DNS lookup problem.
> Take a look into your bconsole.conf.
> Maybe change the address directive to 127.0.0.1.
>
> Jörg

[Jörg Steffens]

Hi,

yes, it certainly looks like a dns problem. Your configuration looks
sane. If I'm not mistaken, it can still relate to your /etc/resolv.conf.

You can start bconsole with debug:

bconsole -d 200 -dt

Maybe this gives some insight.

Jörg

[Stefan Klatt]

Hi Jörg,

normally the hosts file should be first accessed before the DNS server
will be asked.
I saw a few programs like yum which show IPv6 addresses if they have
problem to access the DNS service.
I think CentOS 7.2 has a bug with DNS and IPv6.

My resolf.conf:

search cac.local
nameserver 192.168.76.40
nameserver 192.168.76.41

I disabled IPv6 like described on this page

https://wiki.centos.org/FAQ/CentOS7

with adding the following lines to /etc/sysctl.conf:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

Regards

Stefan

[David Sherer]

I had the same issue. I had to put the computer names into the host file with the respective IP address. Once I did this it worked like a champ.

[Stefan Klatt]

Hi David,

take a look at my hosts:

192.168.76.2 galaxy.cac.local galaxy
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
#::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

Regards

Stefan

[David Sherer]

here is my host file. I actually had to map the Director also for it to connect. The Server-dir is my Bareos Director

127.0.0.1 localhost
127.0.1.1 Server
127.0.0.1 Server-dir

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

# Local Network Machines
192.168.72.2 Admiral