Project

General

Profile

Bug #65502

Plugin installation failure doesn't have any information

Added by Bug Clerk 11 months ago. Updated 10 months ago.

Status:
Closed
Priority:
No priority
Assignee:
Brandon Schneider
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Not to be fixed
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

Screenshot: https://imgur.com/a/C7BYA2H

At present, attempting to install the ZoneMinder plugin seems to fail during the post install script, but there doesn't seem to be a way to determine what went wrong. In the GUI, the only indication is the progress dialog box displaying the text "Exception: RuntimeError: occured, destroyed zoneminder."

Thankfully it does indeed destroy the partial jail so conflicts don't occur with duplicate names (since you can't choose the name of the jail when creating a plugin for some reason), but it would be nice to know if there's something else that can be done, some syslog entry or whatever that tells me any information at all.

Build FreeNAS-11.3-MASTER-201812170909


Related issues

Copied from FreeNAS - Bug #65007: Have middleware return a more verbose error message on plugin failureDone

History

#1 Updated by Bug Clerk 11 months ago

  • Copied from Bug #65007: Have middleware return a more verbose error message on plugin failure added

#2 Updated by Bug Clerk 11 months ago

  • Target version changed from Master - FreeNAS Nightlies to 11.2-U2

#3 Updated by Bug Clerk 11 months ago

  • Status changed from Unscreened to In Progress

#4 Updated by Anthony Takata 11 months ago

Failure message now reads:
zoneminder's post_install.sh had a failure Exception: RuntimeError Message: Last 10 lines: jexec: execvp: /root/post_install.sh: Permission denied Partial plugin destroyed

I think the output isn't being properly html-ified, but unfortunately the post_install.sh script was apparently not intended to have its output scrutinized, so not sure where permission is being denied...

#5 Updated by Dru Lavigne 10 months ago

  • Status changed from In Progress to Closed
  • Target version changed from 11.2-U2 to N/A
  • Reason for Closing set to Not to be fixed

This one is too invasive of a change to safely backport to the 11.2 branch.

Also available in: Atom PDF