Upgrade notes to 9.2.1.7

[DrKK]

Gentlemen:

I just did the GUI upgrade from 9.2.1.6 to 9.2.1.7, and I thought I'd report back on the results.

It generally went smoothly. The system's been up for about 15 minutes now, and everything looks probably OK. I have noted the following two gotchas:

1. The UPS service went ape shit. I've upgraded many versions of FreeNAS, of course, and I've never had a problem with the nut/upsd stuff, but when the system came back online for 9.2.1.7, the log was filled with spam about communications problems with the UPS, it sent me email warnings, the whole 9 yards. I plugged and unplugged the UPS, no effect. I wound up having to physically STOP the service, giving it a second, then restarting it. It SEEMS fine now, the ups.log in /var/log looks like it's now giving proper results, I think it's fine now. I am guessing, however, that everytime I boot, I'm going to have to do this. Not sure why this is necessary.
2. There were a few places where there was a couple minutes pause during the upgrade process that really looked like a hung system. You do have to be patient--I thought more patient than before.

 

[xcom]

Thanks for your notes.

 

[DrKK]

Also, the "favicon.ico" on my bookmarks for the GUI has changed to the FreeNAS logo instead of the FreeBSD logo. That's new. Someone must have changed that in the django/nginx interface. Didn't see it mentioned in the notes...

 

[Whattteva]

I posted about the different icon on another thread, I think the title was "Safe to upgrade" if I remember correctly.

 

[cyberjock]

Also, the "favicon.ico" on my bookmarks for the GUI has changed to the FreeNAS logo instead of the FreeBSD logo. That's new. Someone must have changed that in the django/nginx interface. Didn't see it mentioned in the notes...

Pretty sure the ticket on that was closed back in January or February. Been the new icon on the entire 9.2.1 series afaik. My bookmark icons show the old icon for my 9.2.0 boxes and my 9.2.1 boxes show the new icons. ;)

 

[SweetAndLow]

https://bugs.freenas.org/issues/5741

I filled this bug earlier this morning regarding the ups issues.

 

[Whattteva]

Pretty sure the ticket on that was closed back in January or February. Been the new icon on the entire 9.2.1 series afaik. My bookmark icons show the old icon for my 9.2.0 boxes and my 9.2.1 boxes show the new icons. ;)

Shame, I'm rather fond of the old red-themed icon, not so much the new one.

 

[Knowltey]

Main issue I'm having an issue with is the groups becoming not recognized to CIFS clients after a restart, so it becomes very difficult to set permissions from a Windows client for the NAS since I can't add group permissions.

https://bugs.freenas.org/issues/5683

 

[cyberjock]

Main issue I'm having an issue with is the groups becoming not recognized to CIFS clients after a restart, so it becomes very difficult to set permissions from a Windows client for the NAS since I can't add group permissions.

https://bugs.freenas.org/issues/5683

That honestly sounds like a permission issue. I say this for two reasons:

1. I *know* at least 50 companies using groups for permissions and it works.
2. If your client can't list the group permissions that's an obvious misconfiguration of permissions.

 

[Knowltey]

Well problem came around with the 9.2.1.6 version and after a reboot will occur. Happens on a fresh FreeNAS install as well. During the session in which you create the group everything acts normal. Once you restart though it won't tell any CIFS clients that the server has any groups if you attempt to look them up on the search.

It is at lookup of the group name after a reboot. Permissions don't need to be set with the group to recreate the issue as the issue is when you're attempting to set permissions not after.

What I did was go into the groups creation area, create a group, have it assigned to a new ID. Then if you go into the security properties for a directory you can do an advanced search and search for all groups on the NAS and it'll show the group you just created. If you then proceed to reboot the server and try that again it will return zero results after the restart.

The group permissions that I have priorly set up in the past do still work correctly. Just that in the permissions properties pane they show up as just the SID rather than "UserGroup" or whatever name I gave them, and an error message comes through on the NAS log saying it was unable to lookup the SID and the SID in the log that it says it is unable to lookup isn't actually the full SID. (cause of the failure perhaps?)

Unless creating groups in the account section of the GUI is incorrect?

 

[cyberjock]

It is.. in some cases. Not necessarily in others. Depends on if you are trying to create groups for a domain or not and other factors. But I have no doubt in my mind that your configuration is "unique" in some way. I know it can and does work fine on rebooting and such or iX would have *tons* of calls about it for TrueNAS. But we aren't, so I have to assume this is a misconfigure on your part somewhere. I don't know exactly where as there are many more factors involved than what have just been discussed in this thread. ;)

 

[Knowltey]

I'll try to do another fresh reinstall or such see if I can find anything that may have ended up being unique.

The test I did initially run was done on my Backup Offsite NAS, which should be close enough to fresh, but I didn't have a chance to do a full fresh, so perhaps something fucked up on me in an upgrade somewhere for all I know.

But yeah, it would seem like something with more of an outcry if it was happening to everyone. I used groups for simplification, but since I really only have a small handful of user accounts setting up by user basis wouldn't be too farfetched, I would just prefer to be able to use groups since I have 3 people in a "Users" group and then two other accounts that belong to a group for Services.

 

[cyberjock]

Keep in mind that if you are doing domains many domain settings can have unintended consequences.

I will tell you that workgroups are a mess with CIFS shares. While it can be done it's damn hard to do properly. To be honest, the best way to do FreeNAS with CIFS is to either let your FreeNAS machine be its own domain or put it on a domain. Doing local database instead of its own domain is also an option so long as the administrator can handle all of the synchronizing of usernames and passwords and other smaller aspects that Windows works out for itself when in a domain or connecting to one.

 

[Knowltey]

Yeah, not on a domain at the moment. So perhaps these workgroup issues that you've mentioned is causing it to not stick around between reboots. I believe that other guy in that link to the bug database was also just in workgroup. I may look into seeing if setting up a domain may work to resolve said issue since AD Domain has been something I've been curious about in the past and 9.2.1.7 seems to have the ability to be a domain controller now, I'll just have to do research on testing on getting that set up properly before playing with fire on the production NAS.

 

[Knowltey]

Keep in mind that if you are doing domains many domain settings can have unintended consequences.

I will tell you that workgroups are a mess with CIFS shares. While it can be done it's damn hard to do properly. To be honest, the best way to do FreeNAS with CIFS is to either let your FreeNAS machine be its own domain or put it on a domain. Doing local database instead of its own domain is also an option so long as the administrator can handle all of the synchronizing of usernames and passwords and other smaller aspects that Windows works out for itself when in a domain or connecting to one.

Ok, so I went ahead and did a full fresh test. Installed form ISO, default configs. First thing I noticed was that even on the first boot the default system groups already were not being shown to CIFS clients if you try to look them up. The only thing I did to that point was make a new blank pool and a simply CIFS share to it to make it accessible to perform the test, using basic settings and default CIFS and share settings. Nothing regarding groups or permissions was touched.

Went in and using the group search feature you cannot even get the default groups. This is before I even touched Groups or permissions. So already in the FreeNAS default configuration it is not working.

Moving on I set up a group named "TestGroup" per the instructions in the Wiki, made a new folder in the share and then added them as a group with permissions to the folder. Was able to look the group up by the group name in that session. Then I reboot, try again, can't look up the group and a search to show all groups on the server returns 0 results, not even including the default groups.

Seeing as even in the default configuration it is showing the bug it can't be due to a misconfiguration. Whatever allows the server to send out it's group information to clients is not surviving between reboots.

 

[Robert Smith]

I had the same issue with 9.2.1.6
http://forums.freenas.org/index.php?threads/samba-users-created-but-groups—not.22410/

 

[Knowltey]

I had the same issue with 9.2.1.6
http://forums.freenas.org/index.php?threads/samba-users-created-but-groups—not.22410/

Yep, noticed that as well as one other thread and I had linked to your bug report in the bug database in an earlier post as well.

 

[Robert Smith]

Yep, noticed that as well as one other thread and I had linked to your bug report in the bug database in an earlier post as well.

Good news: a FreeNAS developer was able to reproduce the issue. The developer should be able to fix it, or kick it up to SAMBA team, if it is their fault.