Re: [Bacula-users] Anyone else encountering connection problems with bacula-5.2.9 fd on OpenBSD?

[Marco v. W. <mv...@pl...>]

Phil Stracchino <alaric <at> metrocast.net> writes:
> 
> On 06/25/2012 02:14 PM, Phil Stracchino wrote:
> No joy with that; failed to compile at all.
Ok interesting with what error when I may ask? Send the output
to me by private email.

> 
> >> What is kind of interesting is running any daemon with -d 100 to see
> >> what addresses it want to bind to.
> 
> And -d100 shows that 5.2.9 ia binding to the correct address and port,
> but dying with a SEGV as soon as it gets the connection handshake request.
> 
Ok great then you are not having the same error. So we can scrap that one.

> spikyfishthing:root:/opt/bacula-5.2.9/etc:24 #
> /opt/bacula-5.2.9/sbin/bacula-fd -v -c
> /opt/bacula-5.2.9/etc/bacula-fd.conf -d100bacula -f
> bacula-fd: filed_conf.c:452-0 Inserting director res: spikyfishthing-mon
> spikyfishthing-fd: jcr.c:140-0 read_last_jobs seek to 188
> spikyfishthing-fd: jcr.c:147-0 Read num_items=10
> spikyfishthing-fd: filed.c:276-0 filed: listening on port 9102
> spikyfishthing-fd: bnet_server.c:95-0 Addresses host[ipv4:10.24.32.1:9102]
> spikyfishthing-fd: bnet.c:768-0 who=client host=��� port=9102
> Bacula interrupted by signal 11: Segmentation violation

The remote host looks fishy.

> Kaboom! bacula-fd, spikyfishthing-fd got signal 11 - Segmentation
> violation. Attempting traceback.
> Kaboom! exepath=/opt/bacula-5.2.9/etc
> Calling: /opt/bacula-5.2.9/etc/btraceback
> /opt/bacula-5.2.9/etc/bacula-fd 18791 /opt/bacula/var
> /opt/bacula-5.2.9/etc/btraceback[47]: /opt/bacula-5.2.9/sbin/bsmtp: not
> found
> 
> Looks like to get bsmtp I have to build the director, which means I have
> to install and select a DB, etc, etc, which I don't really want to do
> since this machine is a firewall and shouldn't have anything unnecessary
> installed.
> 
Shouldn't be needed. its in the btools dir and can be build using
client-only config.

You can always try 5.2.6 to see if its something recent or that its
something older. But without a real backtrace e.g. including a
debugger like gdb its kind of useless as you cannot see what is
going wrong.

Marco