We've migrated a working bacula installation and changer to a new  
server, but bacula seems unable to connect to the storage unit.  All  
of the configuration files were moved intact, with the exception of  
changing the director name and the scsi device.  I am able to see the  
changer and drives via dmesg, proc and mtx, but it simply times out  
when trying a "status storage" in bconsole.  Here is all of the  
diagnostic information I can think of.  Any suggestions?

# dmesg | grep scsi1 | grep Attached
Attached scsi tape st0 at scsi1, channel 0, id 4, lun 0
Attached scsi tape st1 at scsi1, channel 0, id 5, lun 0
Attached scsi generic sg2 at scsi1, channel 0, id 4, lun 0, type 1
Attached scsi generic sg3 at scsi1, channel 0, id 5, lun 0, type 1
Attached scsi generic sg4 at scsi1, channel 0, id 6, lun 0, type 1

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 08 Lun: 00
  Vendor: DP     Model: BACKPLANE     Rev: 1.00
  Type:  Enclosure
Host: scsi0 Channel: 02 Id: 00 Lun: 00
  Vendor: DELL     Model: PERC 5/i     Rev: 1.00
  Type:  Direct-Access
Host: scsi1 Channel: 00 Id: 04 Lun: 00
  Vendor: QUANTUM   Model: SuperDL1     Rev: 5050
  Type:  Sequential-Access        ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
  Vendor: QUANTUM   Model: SuperDL1     Rev: 5050
  Type:  Sequential-Access        ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 06 Lun: 00
  Vendor: OVERLAND   Model: NEO Series     Rev: 0429
  Type:  Sequential-Access        ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: Dell   Model: Virtual CDROM   Rev: 123
  Type:  CD-ROM                ANSI SCSI revision: 02
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: Dell   Model: Virtual Floppy   Rev: 123
  Type:  Direct-Access           ANSI SCSI revision: 02

# mtx -f /dev/sg4 inquiry
Product Type: Medium Changer
Vendor ID: 'OVERLAND'
Product ID: 'NEO Series    '
Revision: '0429'
Attached Changer: No

# netstat -vant | grep 910
tcp     0    0 0.0.0.0:9101        0.0.0.0:*         LISTEN
tcp     0    0 0.0.0.0:9102        0.0.0.0:*         LISTEN
tcp     0    0 0.0.0.0:9103        0.0.0.0:*         LISTEN
tcp     0    0 10.1.1.16:9101        10.1.1.16:32819         TIME_WAIT
tcp     0    0 10.1.1.16:9103        10.1.1.16:32820         TIME_WAIT

# bconsole
Connecting to Director foobar01:9101
1000 OK: foobar01-dir Version: 1.38.11 (28 June 2006)
Enter a period to cancel a command.
* status dir
Using default Catalog name=MyCatalog DB=bacula
foobar01-dir Version: 1.38.11 (28 June 2006) i686-redhat-linux-gnu  
redhat
Daemon started 14-Dec-06 12:47, 1 Job run since started.

Scheduled Jobs:
Level     Type   Pri Scheduled     Name       Volume
============================================================
Incremental   Backup    10  14-Dec-06 20:00   foobar01-DailyINCR  
*unknown*
Incremental   Backup    10  14-Dec-06 20:00   foobar02-DailyINCR  
*unknown*
Incremental   Backup    10  14-Dec-06 20:00   foobar03-DailyINCR  
*unknown*
Incremental   Backup    10  14-Dec-06 20:00   foobar04-DailyINCR  
*unknown*
Full   Backup    11  14-Dec-06 23:10   BackupCatalog *unknown*
====

Running Jobs:
No Jobs running.
====
No Terminated Jobs.
====

* status st
Automatically selected Storage: Overland2000
Connecting to Storage daemon Overland2000 at foobar01:9103
(.... timing out... )


Thanks,

--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to