Freenas Sorry An Error Occurred
Contents |
going into TrueNAS-9.10.1 Release No Target Version Target - 9.10.1-U1 (All) Target - 9.10.1-U1 (Open) Target - 9.10.1-U1 (RFR) Target - 9.10.1-U2 (All) Target - some error occurred freenas plugin plex 9.10.1-U2 (Open) Target - 9.10.1-U3 (All) Target - 9.10.1-U3 (Open) Target - freenas plugin some error occurred 9.10.2 (All) Target - 9.10.2 (Open) Unassigned Unscreened staged for FreeNAS-9.10.1 Bug #328 GUI might break (Services Tab) freenas plex media server not starting Added by sbx - over 5 years ago. Updated over 5 years ago. Status:ClosedStart date:Priority:ImportantDue date:Assignee:-% Done:0%Category:GUITarget version:- Seen in: Hardware Configuration: ChangeLog Entry: Description After creating shares and
Install Plex On Freenas
volumes and destroying them again for I while I suddenly might not select the 'Services' Tab anymore. When clicking on it (no matter if via tab or tree structure) I only get (German!) message saying: 'Es ist ein Fehler aufgetreten.' (An error has occurred). Now it is impossible for me to start or stop services via GUI. I have the feeling anyway, that the GUI does not read the settings or the state of the system on every boot, but relies on what's written in the db. This is how inconsistencies might occur (I had this once in the last couple of hours when trying to delete a volume). But I already installed from scratch afterwards. History #1 Updated by William Grzybowski over 5 years ago Hello, Thanks for your report. We need a way to reproduce this, though.Without the exact procedures it is almost impossible to find the issue. We have been trying to create shares/volumes and destroying them but it does not seem to be enough. #2 Updated by sbx - over 5 years ago Hi william thanks for responding so quickly. I cannot reproduce this either. But there seems to be a problem with the database being kept consistent with the state of the system (don't know how to exactly describe this). For instance, after reinstalling the system (no upgrade) and importing a volume from a previous install (FN
»reddit.comfreenascommentsWant to join? Log in or sign up in seconds.|Englishlimit my search to /r/freenasuse the following search parameters to narrow your results:subreddit:subredditfind submissions in "subreddit"author:usernamefind submissions by "username"site:example.comfind submissions from "example.com"url:textsearch for "text" in urlselftext:textsearch for "text" in self post contentsself:yes (or self:no)include (or exclude) self postsnsfw:yes (or nsfw:no)include (or exclude) results marked as NSFWe.g. subreddit:aww site:imgur.com dogsee the search https://bugs.freenas.org/issues/328 faq for details.advanced search: by author, subreddit...this post was submitted on 05 May 20148 points (90% upvoted)shortlink: remember mereset passwordloginSubmit a new linkSubmit a new text postfreenassubscribeunsubscribe4,972 readers~12 users here nowOfficial website: FreeNAS.org created by bbatsella community https://www.reddit.com/r/freenas/comments/24sciv/my_experiences_with_freenas_over_the_past_6_months/ for 6 yearsmessage the moderatorsMODERATORSbbatsellabout moderation team »discussions in /r/freenas<>XBlack screen after click normal bootup4 points · 4 comments Did I lose redundancy replacing with larger drive?3 points · 3 comments Help! Snapshot not recursive data recovery16 points · 7 comments Requesting help troubleshooting frequent arp moves3 points · 3 comments Importing Ubuntu ZFS into FreeNAs3 points · 10 comments Mirrors vs. RAIDZ again0 points · 4 comments Requesting feedback for FreeNAS build1 points · 8 comments $350 budget build, need advice8 points · 24 comments SSD Pool Slow Performance1 points · 1 comment Backing up/Restoring PoolThis is an archived post. You won't be able to vote or comment. 789My ex
going into TrueNAS-9.10.1 Release No Target Version Target - 9.10.1-U1 (All) Target - 9.10.1-U1 (Open) Target - 9.10.1-U1 (RFR) https://bugs.pcbsd.org/issues/3536 Target - 9.10.1-U2 (All) Target - 9.10.1-U2 (Open) Target - 9.10.1-U3 (All) Target - 9.10.1-U3 (Open) Target - 9.10.2 (All) Target - 9.10.2 (Open) Unassigned Unscreened staged for FreeNAS-9.10.1 Bug #3536 Plugin Jail fails to function if default gateway is on a VLAN interface Added by Snax - almost 3 years error occurred ago. Updated almost 3 years ago. Status:ClosedStart date:11/29/2013Priority:Nice to haveDue date:Assignee:William Grzybowski% Done:0%Category:JailsTarget version:9.2.0-RELEASE Seen in:9.1.1-RELEASE Hardware Configuration: ChangeLog Entry: Description The plugin jail system fails when an interface has VLANs and the default gateway is necessarily on a VLAN. The result is FreeNAS generates a "Sorry, an error occurred" message with some error occurred the following in the log window: manage.py: [freeadmin.navtree:216] Failed to generate navtree for app freenasUI.jails: 'sipcalc_ipv4_type' object has no attribute 'host_address' I have a LAGG with two VLANs on it. On one of the VLANs is the default gateway. In such a configuration, I cannot assign the default gateway to the LAGG, which is what the plugin jail system is limited to expecting. If I remove the VLANs and instead assign an IP address and default gateway directly to the LAGG, everything works and the jails are visible. But in doing so, I loose the ability to have VLANs. This means that, if someone has more than one physical interface and needs to do redundancy, including VLANs, the plugin system become completely useless, which is an unfortunate limitation. If would be great if this could be fixed so that the jail works regardless of what interface type the default gateway is on. Thanks Unf