GUI error django error

[jet09]

I just update my FreeNAS 9.3.1 and after system reboot I'm getting the error below. I'm also unable to access my shares from Windows 7 pc.

Code:

An error occurred.

Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

Faithfully yours, nginx.

Nginx service is started but django service is throwing errors. What is the best way for me to fix this? Thanks in advanced.

Code:

nas# service django start
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/manage.py", line 42, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 280, in execute
    translation.activate('en-us')
  File "/usr/local/lib/python2.7/site-packages/django/utils/translation/__init__.py", line 130, in activate
    return _trans.activate(language)
  File "/usr/local/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 188, in activate
    _active.value = translation(language)
  File "/usr/local/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 177, in translation
    default_translation = _fetch(settings.LANGUAGE_CODE)
  File "/usr/local/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 159, in _fetch
    app = import_module(appname)
  File "/usr/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
    __import__(name)
ImportError: No module named vcp

 

[dlavigne]

You should not be getting a traceback. Please create a bug at bugs.freenas.org that includes the full text of the traceback and post the bug # here.

 

[jet09]

Thanks. Bug #12136

 

[jet09]

beadm rollback solved the problem

 

[emb]

beadm rollback solved the problem

Can you elaborate on how to do this. I have the exact same problem. Thanks.

 

[jet09]

beadm allows you to manage ZFS Boot Environments (BE). With that being said please do this at your own risk since I don't know if this will work for you or not.

1. Login as root
2. List the boot environments

Code:

nas# beadm list
BE                              Active Mountpoint  Space Created                 Nickname
default                         -      -            2.4M 2015-04-17 00:17        default
Initial-Install                 -      -            2.9M 2015-04-17 00:24        Initial-Install
FreeNAS-9.3-STABLE-201504152200 -      -           38.7M 2015-04-19 01:35        FreeNAS-9.3-STABLE-201504152200
FreeNAS-9.3-STABLE-201505040117 -      -          133.3M 2015-05-07 23:42        FreeNAS-9.3-STABLE-201505040117

FreeNAS-9.3-STABLE-201506292332 -      -          265.1M 2015-07-08 22:28        FreeNAS-9.3-STABLE-201506292332
FreeNAS-9.3-STABLE-201509022158 -      -          183.8M 2015-09-13 14:35        FreeNAS-9.3-STABLE-201509022158
FreeNAS-9.3-STABLE-201510290351 NR     /            1.7G 2015-10-30 10:03        FreeNAS-9.3-STABLE-201510290351
FreeNAS-9.3-STABLE-201509282017 -      -          518.2M 2015-10-30 10:25        FreeNAS-9.3-STABLE-201509282017

You can see which is currently active. I recommend creating a new BE to rollback to.

3. Create new BE

Code:

beadm create [name]

You can run beadm list to make sure the new one was created.

4. Activate the last know good BE. Look at the created date. For me it was the one in bold. The one below it is the newest (broken one).

Code:

beadm activate FreeNAS-9.3-STABLE-201510290351

5. reboot

Hopefully this works for you! More info here.

 

[Clevinger]

I too am having this problem after the most recent update today. Have not checked the box (because it's headless and I don't have ssh set up) for the specific error yet but I'd wager it's the same. Happened after restart during the update. Plex plugin still works and the media that it has access to is still available through Plex, however the drive won't mount normally. Going to try a beadm rollback (if I can figure out how that works) in a few days but otherwise watching this thread for updates. Thanks!

 

[emb]

Worked perfectly. Thank you.

 

[Clevinger]

That worked! But what now? Did you update again without issue or are you stuck on an old version? I don't want to update if it's only going to give me the same error.

 

[emb]

I have since updated to FreeNAS-9.3-STABLE-201511040813 without issue.

 

[jet09]

Just updated it today to FreeNAS-9.3-STABLE-201511040813 without any problem.