On 01/29/2010 08:40 PM, eMJay wrote:
>
>
>> I notice that you dont' define the SDPort in the Storage part of
>> -sd.conf. I think it should default to 9103 but it is worth adding to
>> make sure.
>
> I've added it but didn't help
>
>> I suggest that before you run any jobs you try to connect to the
>> director using bconsole. From there issues the status command and see
>> what it says about each component. There is no point trying to run a job
>> until you know that the director can contact each device and find out
>> status.
>
> it was the same as when I tried to connect from window client.. nevertheless
> it was good idea ;)
>
> And here is output from bconsole running on the same machine as bacula server:
>
> Connecting to Storage daemon File-SD at 10.97.53.165:9103
>
> Failed to connect to Storage daemon File-SD.
> ====
> You have messages.
> *messages
> 29-Jan 19:53 a JobId 0: Fatal error: sql_get.c:623 sql_get.c:623 query SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default' failed:
> Unknown column 'ActionOnPurge' in 'field list'
> 29-Jan 19:53 a JobId 0: sql_get.c:623 SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default'
> 29-Jan 19:53 a JobId 0: Fatal error: sql_get.c:623 sql_get.c:623 query SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default' failed:
> Unknown column 'ActionOnPurge' in 'field list'
> 29-Jan 19:53 a JobId 0: sql_get.c:623 SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default'
> 29-Jan 19:53 a JobId 0: Fatal error: Pool Default not in database.
> sql_create.c:181 pool record Default already exists
> 29-Jan 19:53 a JobId 0: Fatal error: sql_get.c:623 sql_get.c:623 query SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default' failed:
> Unknown column 'ActionOnPurge' in 'field list'
> 29-Jan 19:53 a JobId 0: sql_get.c:623 SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default'
> 29-Jan 19:53 a JobId 0: Fatal error: sql_get.c:623 sql_get.c:623 query SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default' failed:
> Unknown column 'ActionOnPurge' in 'field list'
> 29-Jan 19:53 a JobId 0: sql_get.c:623 SELECT
> PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge
> FROM Pool WHERE Pool.Name='Default'
> 29-Jan 19:53 a JobId 0: Fatal error: Pool Default not in database.
> sql_create.c:181 pool record Default already exists
> 29-Jan 19:53 a JobId 0: Fatal error: authenticate.c:120 Director unable to
> authenticate with Storage daemon at "10.97.53.165:9103". Possible causes:
> Passwords or names not the same or
> Maximum Concurrent Jobs exceeded on the SD or
> SD networking messed up (restart daemon).
> Please see
> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION003760000000000000000
> for help.
>
> Maximum concurrent jobs limit is set to 200 and I've also tried to restart SD.
>
Ok here what you should provide to understand what's happen on your server.
Could you post the ./configure you used to build bacula.
In the message log you send, there's clearly a big troube ( fatal error ) with
the DB.
So it should be resolve before any other action.
a status dir should give you the same error log.
I presume the database was corrupted in a way or another which need to be
clarify how.
--
Bruno Friedmann
Reply only to list.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|