On Fri, 15 Dec 2006 10:36:06 -0500, Jason Dixon <[EMAIL PROTECTED]> wrote:
> 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? <snip> > * status st > Automatically selected Storage: Overland2000 > Connecting to Storage daemon Overland2000 at foobar01:9103 > (.... timing out... ) I just noticed that if I wait, the prompt returns with status after approximately 10 minutes. It behaves normally after that. I have not tested any backups yet... I'd like to clarify this behavior before I destroy our old backups. The new server is running bacula-1.38.11-3 (sqlite) on RHEL 4. The old server is running bacula-1.38.10-1 (sqlite) on CentOS 3. 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
