Project

General

Profile

Bug #7772

Bacula Plugin - Device "global name 'jail' is not defined" error

Added by Michael Schefczyk over 5 years ago. Updated about 3 years ago.

Status:
Closed: Not To Be Fixed
Priority:
Important
Assignee:
Joshua Ruehlig
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When adding a device, the bacula plugin generates a long error message reported in this forum post:

https://forums.freenas.org/index.php?threads/bacula-add-device-nameerror-global-name-jail-is-not-defined.26928/#post-171758

By my experience, this problem does not occur to the person posting in the forum alone.

This happens also after mounting /mnt/tank/bacula for the jail.

I suspect an error or a lack of documentation.

The system is FreeNAS-9.3-STABLE-201501301837 with the up to date plugin.

2016-04-14_01-44-02.png (141 KB) 2016-04-14_01-44-02.png Alexey Shevchuk, 04/13/2016 03:51 PM
5669

History

#1 Updated by Jordan Hubbard over 5 years ago

  • Assignee changed from Joshua Ruehlig to Suraj Ravichandran
  • Seen in changed from to 9.3-STABLE-201506040752

BRB: Suraj has some theories about an uncaught pyflakes problem that may explain this. Stealing the bug from Joshua.

#2 Updated by Suraj Ravichandran about 5 years ago

  • Status changed from Unscreened to Screened
  • Target version set to Unspecified

This is fixed by : https://github.com/williambr/freenas-bacula/commit/96fee6a849811c80cc35b5bc383d2054ca552e81

I think all we need to do is update the pbi on our server.

#3 Updated by Suraj Ravichandran about 5 years ago

  • Status changed from Screened to Unscreened
  • Assignee changed from Suraj Ravichandran to Joshua Ruehlig

Hi Joshua,

Assigning this to you as it has already been fixed in William's git repo of bacula-plugin (see comment above for links and info).

Could you create and push a new pbi for it accordingly? If not then please close as NTBF.

Thanks for all your contributions to freenas plugins.

#4 Updated by Joshua Ruehlig about 5 years ago

  • Status changed from Unscreened to Screened

Has anyone built a PBI for this?
If so, I can upload it to the repo. Otherwise I'll add this plugin to my github, then test a build once I have time (probably this weekend).

#5 Updated by Michael Schefczyk about 5 years ago

Dear All,

Thank you very much for dealing with this! Having a bacula SD run on the FreeNAS itself instead of on an external linux server mounting a FreeNAS share would be much more efficient. So far, the availabe plugin 5.2.12_3 seems to be the traditional version, right? In addition to the UI issue, my impression is that the SD can be reached from the bacula director but it fails as soon as storage is accessed - which corresponds to the file storage box showing an error.

Regards,

Michael Schefczyk

#6 Updated by Joshua Ruehlig almost 5 years ago

  • Priority changed from Nice to have to Important

sorry I do not have the time to build and maintain this plugin so I take back my previous statement that I would try building this. but, if anyone else wants to build and test an update/fix I an more than willing to post your updated PBI in the Freenas repo.

#7 Updated by Alexey Shevchuk over 4 years ago

5669

Suraj Ravichandran wrote:

This is fixed by : https://github.com/williambr/freenas-bacula/commit/96fee6a849811c80cc35b5bc383d2054ca552e81

I think all we need to do is update the pbi on our server.

Patch works, but here comes another error (when attempting to remove the device)

#8 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Status changed from Screened to Closed: Not To Be Fixed
  • Target version changed from Unspecified to 243

#9 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Target version changed from 243 to N/A

Also available in: Atom PDF