Am 12.04.2012 17:52, schrieb Carlo Filippetto:
There's any problem with client 64 bit and server 32 bit?
No.
More specifically, I had that running without a problem.
I have a mixture of 32 and 64 bit clients, have recently
switched from 32 to 64 bit on the server, and all the
resulting
Hi,
I have bacula-server installed on a CentOS 5.2, version 5.2.3, kernel i686
Today I installed fot the first time a client with CentOS 6.2 x86_64
(installation made with yum with bacula 5.0.0.9)
I can't understand why I have this error:
12-apr 16:44 megabot-bck-dir JobId 56382: Fatal error:
2012/4/12 Carlo Filippetto carlo.filippe...@gmail.com:
Hi,
I have bacula-server installed on a CentOS 5.2, version 5.2.3, kernel i686
Today I installed fot the first time a client with CentOS 6.2 x86_64
(installation made with yum with bacula 5.0.0.9)
I can't understand why I have this
2012/4/12 John Drescher dresche...@gmail.com
2012/4/12 Carlo Filippetto carlo.filippe...@gmail.com:
Hi,
I have bacula-server installed on a CentOS 5.2, version 5.2.3, kernel
i686
Today I installed fot the first time a client with CentOS 6.2 x86_64
(installation made with yum with
Yes,
but I can't fine the answer
Did you verify the passwords match? If so make sure that no bacula
config file uses 127.0.0.1 or localhost as its IP address.
--
John M. Drescher
--
For Developers, A Lot Can Happen
2012/4/12 John Drescher dresche...@gmail.com
Yes,
but I can't fine the answer
Did you verify the passwords match? If so make sure that no bacula
config file uses 127.0.0.1 or localhost as its IP address.
--
John M. Drescher
I'm sure that the passwd match.
And the conf file don't
There's any problem with client 64 bit and server 32 bit?
No. At least I have not seen that in the 7 to 8 years I have had 64
bit bacula servers and 32 bit clients.
This is the firts client I install with yum, usually I compile it with
--enable-client-only, may be this the problem?
I can not
