SOLVED Is rsync broken on FreeNAS-9.2.1.5-RELEASE-x64

Status
Not open for further replies.

Oko

Contributor
Joined
Nov 30, 2013
Messages
132
I am just trying to test few backup ideas involving rsync on FreeNAS and I already hit a brick wall. I tried adding a rsync module from GUI of course (essentially just GUI editing of /usr/local/etc/rsync/rsyncd.conf) and I get fail message

Code:
Environment:

Software Version: FreeNAS-9.2.1.5-RELEASE-x64 (80c1d35)
Request Method: POST
Request URL: https://neill-zfs.int.autonlab.org/admin/services/rsyncmod/add/RsyncModForm


Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  107.                     response = middleware_method(request, callback, callback_args, callback_kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/middleware.py" in process_view
  158.         return login_required(view_func)(request, *view_args, **view_kwargs)
File "/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
  22.                 return view_func(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/options.py" in wrapper
  209.                 return self._admin.admin_view(view)(*args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/django/utils/decorators.py" in _wrapped_view
  99.                     response = view_func(request, *args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/django/views/decorators/cache.py" in _wrapped_view_func
  52.         response = view_func(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/site.py" in inner
  144.             return view(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/options.py" in add
  334.             valid &= mf.is_valid(formsets=formsets)
File "/usr/local/www/freenasUI/../freenasUI/common/forms.py" in is_valid
  114.         valid = super(ModelForm, self).is_valid()
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in is_valid
  129.         return self.is_bound and not bool(self.errors)
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in errors
  121.             self.full_clean()
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in full_clean
  273.         self._clean_fields()
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in _clean_fields
  288.                     value = field.clean(value)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/forms.py" in clean
  135.         if FreeNAS_User(user, flags=FLAGS_DBINIT) is None:
File "/usr/local/www/freenasUI/../freenasUI/common/freenasusers.py" in __new__
  394.             obj = FreeNAS_LDAP_User(user, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in __init__
  2132.             self.__get_user(user)
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in __get_user
  2153.             ldap_user = self.get_user(user)
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in get_user
  519.         self.open()
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in open
  215.                     log.debug("FreeNAS_LDAP_Directory.open: started TLS")
File "/usr/local/lib/python2.7/logging/__init__.py" in debug
  1138.             self._log(DEBUG, msg, args, **kwargs)
File "/usr/local/lib/python2.7/logging/__init__.py" in _log
  1268.         record = self.makeRecord(self.name, level, fn, lno, msg, args, exc_info, func, extra)
File "/usr/local/lib/python2.7/logging/__init__.py" in makeRecord
  1242.         rv = LogRecord(name, level, fn, lno, msg, args, exc_info, func)
File "/usr/local/lib/python2.7/logging/__init__.py" in __init__
  284.             self.threadName = threading.current_thread().name
File "/usr/local/lib/python2.7/threading.py" in currentThread
  1160.         return _active[_get_ident()]

Exception Type: ValueError at /admin/services/rsyncmod/add/RsyncModForm
Exception Value: option error


Could anybody give me some clues to what went wrong.
 

Oko

Contributor
Joined
Nov 30, 2013
Messages
132
I am getting something very similar trying to schedule push rsync task which should be trivial. That is just scheduling to run rsync via cron. There is no rsyncd.conf file involved at all.
Code:
Environment:

Software Version: FreeNAS-9.2.1.5-RELEASE-x64 (80c1d35)
Request Method: POST
Request URL: https://neill-zfs.int.autonlab.org/admin/system/rsync/add/


Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  107.                     response = middleware_method(request, callback, callback_args, callback_kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/middleware.py" in process_view
  158.         return login_required(view_func)(request, *view_args, **view_kwargs)
File "/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
  22.                 return view_func(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/options.py" in wrapper
  209.                 return self._admin.admin_view(view)(*args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/django/utils/decorators.py" in _wrapped_view
  99.                     response = view_func(request, *args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/django/views/decorators/cache.py" in _wrapped_view_func
  52.         response = view_func(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/site.py" in inner
  144.             return view(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/options.py" in add
  334.             valid &= mf.is_valid(formsets=formsets)
File "/usr/local/www/freenasUI/../freenasUI/common/forms.py" in is_valid
  114.         valid = super(ModelForm, self).is_valid()
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in is_valid
  129.         return self.is_bound and not bool(self.errors)
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in errors
  121.             self.full_clean()
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in full_clean
  273.         self._clean_fields()
File "/usr/local/lib/python2.7/site-packages/django/forms/forms.py" in _clean_fields
  288.                     value = field.clean(value)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/forms.py" in clean
  135.         if FreeNAS_User(user, flags=FLAGS_DBINIT) is None:
File "/usr/local/www/freenasUI/../freenasUI/common/freenasusers.py" in __new__
  394.             obj = FreeNAS_LDAP_User(user, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in __init__
  2132.             self.__get_user(user)
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in __get_user
  2153.             ldap_user = self.get_user(user)
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in get_user
  519.         self.open()
File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py" in open
  215.                     log.debug("FreeNAS_LDAP_Directory.open: started TLS")
File "/usr/local/lib/python2.7/logging/__init__.py" in debug
  1138.             self._log(DEBUG, msg, args, **kwargs)
File "/usr/local/lib/python2.7/logging/__init__.py" in _log
  1268.         record = self.makeRecord(self.name, level, fn, lno, msg, args, exc_info, func, extra)
File "/usr/local/lib/python2.7/logging/__init__.py" in makeRecord
  1242.         rv = LogRecord(name, level, fn, lno, msg, args, exc_info, func)
File "/usr/local/lib/python2.7/logging/__init__.py" in __init__
  284.             self.threadName = threading.current_thread().name
File "/usr/local/lib/python2.7/threading.py" in currentThread
  1160.         return _active[_get_ident()]

Exception Type: ValueError at /admin/system/rsync/add/
Exception Value: option error
 
D

dlavigne

Guest
Does the traceback persist if you upgrade to 9.2.1.8?
 

Oko

Contributor
Joined
Nov 30, 2013
Messages
132
Does the traceback persist if you upgrade to 9.2.1.8?
I have close to 15 TB of live data on the server and over 50 clients mounted via NFS. I am not really eager to upgrade to 9.2.1.8. I checked the changes from 9.2.1.5 to 9.2.1.8 and there is nothing really interesting for my setting.
I would be happy to try a patch if it doesn't require reboot.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I hate to break it to you, but as a general rule, if you can't upgrade nobody here is likely to help you. There's far more changes made than what is made in the change log and the devs aren't too interested in trying to troubleshoot problems that they are very likely to have already fixed. I've made many posts about everyone being on 9.2.1.7+ and I stand by that. Unless you are going to be on 9.2.1.7+ you are going to find support to be virtually non-existent. :/
 

Oko

Contributor
Joined
Nov 30, 2013
Messages
132
I hate to break it to you, but as a general rule, if you can't upgrade nobody here is likely to help you. There's far more changes made than what is made in the change log and the devs aren't too interested in trying to troubleshoot problems that they are very likely to have already fixed. I've made many posts about everyone being on 9.2.1.7+ and I stand by that. Unless you are going to be on 9.2.1.7+ you are going to find support to be virtually non-existent. :/
I am not stupid and I am fully aware that developers will not look anything past the last stable release. As a system admin I hope you understand my position as well (if it is not broken or at least works for most part don't fix it). This forum is also volunteer and I know that getting a help, real help is a very long stretch. However it never hurts to try ;).
 
Last edited:

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I totally understand (and respect) your position. I deal with people almost daily that are still on 8.x releases of FreeNAS. The problem is you have to maximize the small resources you have. I personally just always assume an upgrade fixes it (and sometimes I'm wrong) but devs pretty much don't want to hear about a problem until you've proved the problem in on "recent" code. As someone who has started dealing with large numbers of customers with all sorts of versions, I tend to get a feel after a while of what builds are good and what are bad. 9.1.0 was bad. 9.1.1 was good. 9.2.0 is good(and is the last samba3 build there is). 9.2.1.x was pretty bad until 9.2.1.6. 9.2.1.6 was good but all versions prior to 9.2.1.6 have a nasty security vulnerability in samba4. 9.2.1.7 fixed a number of bugs but was mostly released because of the samba4 vulnerability. 9.2.1.8 was released which fixed a small number of bugs but was released at the time it was released because of the bash vulnerability. 9.2.1.9 is kind of "floating around" and has a number of bug fixes that will make it in if/when it's released. There is no public 9.2.1.9 but it's floating around with non-critical bug fixes and is very likely to be released if/when there is another nasty security vulnerability warranting another release.

The earlier FreeNAS builds had potentially fatal bugs that have been fixed over time. The later builds are very well polished and didn't have some of those very ugly bugs.

So when I say that you really should be on 9.2.1.7+ I have very good reasons that I don't want to put into a deep discussion on. I can tell you to upgrade to 9.2.1.7+ in a few sentences or I can be stuck writing a lengthy 10 page document explaining it. As a volunteer on this forum (and nobody is paid to post on this forum) guess which answer I give. Unfortunately I also have to have a very low tolerance for easy fixes being rejected because my time is pretty short when you look at the number of posts being made around here. Hopefully you can appreciate the position I'm in as a volunteer (and I think you do). ;) All of the builds after 9.2.1.6 fix things that aren't fatal.

Most tracebacks aren't considered fatal, hence my reasoning to try an upgrade first and see if it fixes your bug. ;)
 
  • Like
Reactions: Oko

Oko

Contributor
Joined
Nov 30, 2013
Messages
132
After upgrading one of the file servers couple of weeks ago from 9.2.1.5 to 9.2.1.9 rsync module works as expected.
 
Status
Not open for further replies.
Top