I have exactly the same :
* vmware ESXi
* Intel 64bit processor
* bacula 3.0.3 from official sources, without any patch

but I'm running Hardy/8.04.

Did you build something else on your server or is everything out of the box from Ubuntu ?


I tested Mandriva X64, bacula seems to work well.

I really don't know what's happening.


mehma sarja wrote :

I built 3.0.3 myself with no changes to source code. I am using postgresql which I installed using a binary file - the Ubuntu install would not run right.
Now to the question of amd vs intel. The processor is Intel 64 bit, I think that's called amd64. I am on a Vmware esxi VM (Ubuntu 64 bit 9.0.4)

Mehma
===

On Wed, Jan 27, 2010 at 9:21 AM, le dahut <le.dahut AT laposte DOT net <mailto:le.dahut AT laposte DOT net>> wrote:

   A last question, are you sure that you're running a Ubuntu amd64
   version and not just a x86 version on a 64bit hardware ?


   mehma sarja wrote :

       I run dir and sd on ubuntu 9.0.4 amd64 using bacula 3.0.3 - no
       problems.
       Mehma
       ===

       On Wed, Jan 27, 2010 at 3:12 AM, le dahut <le.dahut AT laposte DOT net

       <mailto:le.dahut AT laposte DOT net> <mailto:le.dahut AT laposte DOT net

       <mailto:le.dahut AT laposte DOT net>>> wrote:



          le dahut wrote :
           >
           > le dahut wrote :
           >> Hello,
           >>
           >> I'm using bacula 3.0.3 on Ubuntu Hardy and I have a
       strange problem.
           >>
           >> I cannot connect bacula-dir with bconsole.
           >>
           >
           > I've some additional informations :
           > * all iptables rules are flushed/erased, all policies are
       on ACCEPT
           > * hosts.allow and hosts.deny are OK
           > * bacula-dir and bconsole are running on the same machine
       (as it
          appears
           > with 127.0.0.1 in the debug log)
           >
           > With 'strace bconsole' the end of the debug is :
           > """
           > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
           > setsockopt(3, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
           > connect(3, {sa_family=AF_INET, sin_port=htons(9101),
           > sin_addr=inet_addr("127.0.0.1")}, 16) = 0
           > setsockopt(3, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
           > futex(0x7f695e5da584, 0x85 /* FUTEX_??? */, 1) = 1
           > futex(0x7f695e5da540, 0x81 /* FUTEX_??? */, 1) = 1
           > nanosleep({0, 100000}, NULL)            = 0
           > futex(0x7f695e5da584, 0x85 /* FUTEX_??? */, 1) = 1
           > futex(0x7f695e5da540, 0x81 /* FUTEX_??? */, 1) = 1
           > nanosleep({0, 100000}, NULL)            = 0
           > write(3, "\0\0\0\32Hello *UserAgent* calling\n", 30) = 30
           > read(3,
           > """
           > and then nothing else, bconsole seems to wait for
       bacula-dir to
          answer


          This bug occurs on amd64 only. Bacula on X86 runs well.


          * The connection with bconsole to an amd64 DIRECTOR is impossible

          * The connection from a x86 DIRECTOR to an amd64 SD fails
       with "bad
          password" (but the password are the same, the same conf file
       runs on
          x86)

          * The connection from a x86 DIRECTOR to as amd64 FD is OK =>
       I can
          backup if DIR and SD are on x86 and FD on amd64.


          Did someone test bacula on amd64 ?
          On Ubuntu/amd64 ? If yes, which version ?