Hello Chris,
Thanks for providing all these outputs.
It looks that for some reason the Bvfs ls commands didn't return any
output and it caused that the restore file browser was empty. It can
mean that the Bvfs cache wasn't generated correctly.
The empty path="" is OK.
Could you check in the
Update: An example job (Job 1353) can be run successfully using bconsole
commands.
$# bconsole
*restore jobid=1353
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
You have selected the following JobId: 1353
Building directory tree for JobId(s) 1353 ...
Hi Patti,
> Use /dev/sch0, not /dev/sg2. Bear in mind, udev is not your friend. If you
> ever add another tape drive to your library or expand your device fabric,
> these device references will/can change with every system boot. As is, the
> /dev/sgX references can change with reboots, but
Correction, I should have written *WEB* page at Step 3.
Regards
Chris Wilkinson
On Mon, 5 Nov 2018, 9:10 p.m. Chris Wilkinson Here is an extract from baculum-api.log
>
> 1353 is the job I was restoring from.
>
> The path= is blank which is what I see in the API page at Step 3.
>
> ,
Here is an extract from baculum-api.log
1353 is the job I was restoring from.
The path= is blank which is what I see in the API page at Step 3.
, File=/var/www/baculum/protected/API/Class/Bconsole.php, Line=201
(line 67, /var/www/baculum/protected/Common/Class/Logging.php)
Nov 05 20:46:36
William
I believe that message is generated when it tries to do an unload but the tape
is still in the drive.
Try changing the $BACULA_BASE/etc/mtx-changer.conf and set the "offline"
variable to do an eject before an unload.
Then give it a try.
Jeff
-Original Message-
From:
Hello Chris,
I think that there isn't direct relation between changing password and
this problem with 3rd step of the restore wizard.
To check why the files list is empty you can enable debug from the API
side as described here:
Sorry about the /dev/sch0. I've written udev rules to use consistent names
regardless of what udev does - I do use the /dev/sgX for changer
identification. If you've rebooted your system, the output from lsscsi -g may
have changed. You still need the Drive Index line in your bacula-sd.conf .
On Mon, Nov 5, 2018 at 5:22 PM William Muriithi wrote:
>
> Hello,
>
> We have a quantum superloader 3 that seem to be fine when tested through mt
> and mtx command.
>
> [root@eng-backup02 ~]# lsscsi -g
> [0:2:0:0]diskDELL PERC H710P 3.13 /dev/sda /dev/sg0
> [1:0:2:0]tape
Use /dev/sch0, not /dev/sg2. Bear in mind, udev is not your friend. If you
ever add another tape drive to your library or expand your device fabric, these
device references will/can change with every system boot. As is, the /dev/sgX
references can change with reboots, but if you only have
Hello,
We have a quantum superloader 3 that seem to be fine when tested through mt and
mtx command.
[root@eng-backup02 ~]# lsscsi -g
[0:2:0:0]diskDELL PERC H710P 3.13 /dev/sda /dev/sg0
[1:0:2:0]tapeIBM ULTRIUM-HH6 E4J1 /dev/st0 /dev/sg1
[1:0:2:1]
Since I changed the Web and API password in config as you suggested, I'm
finding that Step 3 of the restore wizard shows an empty file selection
list.
Everything else seems to be working just fine.
What could I do to debug the cause of this?
Regards
Chris Wilkinson
On Thu, 25 Oct 2018, 6:20
12 matches
Mail list logo
