FreeNAS 9.2.1.2-RELEASE is now available

[Sir.Robin]

Only a few seconds for mine.


Sent from my mobile using Tapatalk

 

[Hi-Liter]

A question arises having gone back from 9.2.1.1 to 9.2.1 (couldn't go back to 9.2.0 since I created my zpool on 9.2.1 :() - Can I upgrade from 9.2.1 to 9.2.1.2 directly or would I have to upgrade to 9.2.1.1 first?

I'm asking because I remember there being some upgrade issues to 9.2.1.1.

Does someone have an answer?

 

[jkh]

Does someone have an answer?

Yes. You can go directly (from any previous version of FreeNAS).

 

[kryptoman]

Upgraded with the bad version of 9.2.1.2 yesterday and after light use throughout the day noticed in the evening that the smbd process was sitting pegged at 100% for one of my CPU cores. Looking at the reporting chart for cpu, this had been the case for most of the day, even when server totally idle. My server is xeon based with 16GB RAM and it is in a home environmen- so no extreme usage. I haven't seen this before. I have run the "reroll" update script and rebooted. All seems normal again. I will keep an eye out for this issue and post a bug if it happens again. Is there any information I should try to gather from the system in this state before rebooting if it happens again?

 

[Savell Martin]

Ok so I just upgraded from 9.2.1.1.
Upgrade looked ok except I cannot navigate to my shares via \\freenas using \\ipaddress works.

I also now have this warning:

• 
  WARNING: The WebGUI Address could not bind to 192.168.1.10; using wildcard

Lastly I cannot access any of my plugins via the net, I just get page time out.


This is what I can see in the Console.

Code:

Mar  2 21:58:27 freenas winbindd[2652]: [2014/03/02 21:58:27.659313,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Mar  2 21:58:27 freenas winbindd[2652]:  initialize_winbindd_cache: clearing cache and re-creating with version number 2
Mar  2 21:58:27 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar  2 21:58:28 freenas ntpd_initres[2412]: host name not found: 0.freebsd.pool.ntp.org
Mar  2 21:58:28 freenas ntpd_initres[2412]: host name not found: 1.freebsd.pool.ntp.org
Mar  2 21:58:28 freenas ntpd_initres[2412]: host name not found: 2.freebsd.pool.ntp.org
Mar  2 21:58:28 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar  2 21:58:29 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar  2 21:58:30 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect() failed Socket:32 Err:-1 Errno:2 No such file or directory
Mar  2 21:58:32 freenas mDNSResponder: mDNSResponder (Engineering Build) (Mar  1 2014 18:12:24) starting
Mar  2 21:58:32 freenas mDNSResponder:  8: Listening for incoming Unix Domain Socket client requests
Mar  2 21:58:32 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Mar  2 21:58:32 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Mar  2 21:58:32 freenas mDNSResponder: mDNSPlatformSourceAddrForDest: connect 1.1.1.1 failed errno 51 (Network is unreachable)
Mar  2 21:58:33 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 freenas.local. (Addr) that's already in the list
Mar  2 21:58:33 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 1.0.0.127.in-addr.arpa. (PTR) that's already in the list
Mar  2 21:58:34 freenas kernel: bridge0: Ethernet address: 02:21:fe:30:a4:00
Mar  2 21:58:34 freenas kernel: epair0a: Ethernet address: 02:23:ce:00:07:0a
Mar  2 21:58:34 freenas kernel: epair0b: Ethernet address: 02:23:ce:00:08:0b
Mar  2 21:58:34 freenas kernel: epair0a: link state changed to UP
Mar  2 21:58:34 freenas kernel: epair0b: link state changed to UP
Mar  2 21:58:34 freenas kernel: epair0a: promiscuous mode enabled
Mar  2 21:58:34 freenas kernel: bridge0: link state changed to UP
Mar  2 21:58:40 freenas kernel: em0: link state changed to UP
Mar  2 21:58:40 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:40 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:41 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:41 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:42 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:46 freenas dhclient: New IP Address (em0): 192.168.1.10
Mar  2 21:58:46 freenas dhclient: New Subnet Mask (em0): 255.255.255.0
Mar  2 21:58:46 freenas dhclient: New Broadcast Address (em0): 192.168.1.255
Mar  2 21:58:46 freenas dhclient: New Routers (em0): 192.168.1.1
Mar  2 21:58:58 freenas ntpd[2405]: time reset -1.344673 s

 

[jkh]

Upgraded with the bad version of 9.2.1.2 yesterday and after light use throughout the day noticed in the evening that the smbd process was sitting pegged at 100% for one of my CPU cores. Looking at the reporting chart for cpu, this had been the case for most of the day, even when server totally idle. My server is xeon based with 16GB RAM and it is in a home environmen- so no extreme usage. I haven't seen this before. I have run the "reroll" update script and rebooted. All seems normal again. I will keep an eye out for this issue and post a bug if it happens again. Is there any information I should try to gather from the system in this state before rebooting if it happens again?

The smbd issue certainly has nothing to do with the "bad version" of 9.2.1.2 - that was just some bad python code in the middleware, completely separate and distinct from Samba. If you're seeing it run away, attaching to it with gdb and getting a backtrace (attaching it to a bug report) would be very helpful! We can symbolicate the backtrace using some debugging symbols we save for each build. Thanks!

 

[Yatti420]

Thanks,

 

[Savell Martin]

Ok so I just upgraded from 9.2.1.1.
Upgrade looked ok except I cannot navigate to my shares via \\freenas using \\ipaddress works.

I also now have this warning:

• 
  WARNING: The WebGUI Address could not bind to 192.168.1.10; using wildcard

Lastly I cannot access any of my plugins via the net, I just get page time out.



This is what I can see in the Console.

Code:

Mar  2 21:58:27 freenas winbindd[2652]: [2014/03/02 21:58:27.659313,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Mar  2 21:58:27 freenas winbindd[2652]:  initialize_winbindd_cache: clearing cache and re-creating with version number 2
Mar  2 21:58:27 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar  2 21:58:28 freenas ntpd_initres[2412]: host name not found: 0.freebsd.pool.ntp.org
Mar  2 21:58:28 freenas ntpd_initres[2412]: host name not found: 1.freebsd.pool.ntp.org
Mar  2 21:58:28 freenas ntpd_initres[2412]: host name not found: 2.freebsd.pool.ntp.org
Mar  2 21:58:28 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar  2 21:58:29 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar  2 21:58:30 freenas smbd[2649]: dnssd_clientstub ConnectToServer: connect() failed Socket:32 Err:-1 Errno:2 No such file or directory
Mar  2 21:58:32 freenas mDNSResponder: mDNSResponder (Engineering Build) (Mar  1 2014 18:12:24) starting
Mar  2 21:58:32 freenas mDNSResponder:  8: Listening for incoming Unix Domain Socket client requests
Mar  2 21:58:32 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Mar  2 21:58:32 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Mar  2 21:58:32 freenas mDNSResponder: mDNSPlatformSourceAddrForDest: connect 1.1.1.1 failed errno 51 (Network is unreachable)
Mar  2 21:58:33 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 freenas.local. (Addr) that's already in the list
Mar  2 21:58:33 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 1.0.0.127.in-addr.arpa. (PTR) that's already in the list
Mar  2 21:58:34 freenas kernel: bridge0: Ethernet address: 02:21:fe:30:a4:00
Mar  2 21:58:34 freenas kernel: epair0a: Ethernet address: 02:23:ce:00:07:0a
Mar  2 21:58:34 freenas kernel: epair0b: Ethernet address: 02:23:ce:00:08:0b
Mar  2 21:58:34 freenas kernel: epair0a: link state changed to UP
Mar  2 21:58:34 freenas kernel: epair0b: link state changed to UP
Mar  2 21:58:34 freenas kernel: epair0a: promiscuous mode enabled
Mar  2 21:58:34 freenas kernel: bridge0: link state changed to UP
Mar  2 21:58:40 freenas kernel: em0: link state changed to UP
Mar  2 21:58:40 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:40 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:41 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:41 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:42 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/em0/1
Mar  2 21:58:46 freenas dhclient: New IP Address (em0): 192.168.1.10
Mar  2 21:58:46 freenas dhclient: New Subnet Mask (em0): 255.255.255.0
Mar  2 21:58:46 freenas dhclient: New Broadcast Address (em0): 192.168.1.255
Mar  2 21:58:46 freenas dhclient: New Routers (em0): 192.168.1.1
Mar  2 21:58:58 freenas ntpd[2405]: time reset -1.344673 s

Can you help with this?

 

[Hi-Liter]

Upgraded with the bad version of 9.2.1.2 yesterday and after light use throughout the day noticed in the evening that the smbd process was sitting pegged at 100% for one of my CPU cores. Looking at the reporting chart for cpu, this had been the case for most of the day, even when server totally idle. My server is xeon based with 16GB RAM and it is in a home environmen- so no extreme usage. I haven't seen this before. I have run the "reroll" update script and rebooted. All seems normal again. I will keep an eye out for this issue and post a bug if it happens again. Is there any information I should try to gather from the system in this state before rebooting if it happens again?

Sounds like this bug: https://bugs.freenas.org/issues/4285 - I was hoping it was fixed in 9.2.1.2. Could you update the bug and tell them that it still occurs on your system?

 

[rjgould]

Another person who does not read the README file. :)

What does "If you see a release directory without a CHECKSUMS file, you have the old one." mean? exactly?

Is there a way to determine if a 9.2.1.2 version is the broken one, e.g. via the command line?

If not is it safe to apply the fix to both the broken version and the fixed version, i.e. when unsure of the version of 9.2.1.2 installed can the fix be applied anyway for certainty?

 

[Majik]

Well I took the plunge late last night......installed a fresh copy of 9.2.1.2 to see how it runs under the hood. I'm impressed! On my system it seems to go a lot smoother and much faster in both reactions and processes. I had a sharing issue with CIFS before that is no longer after importing my volumes. Good job guys! I hope it stays like this ;)

 

[unca_NAS]

Updated 9.2.1 > 9.2.1.2 via GUI upgrade.
Evrything seems to be in order, but the FTP-service is not starting:

Code:

freenas notifier: proftpd not running?
freenas notifier: Starting proftpd.
freenas notifier: freenas.local proftpd[16428]: Fatal: SyslogFacility: unable to open syslog: Operation not permitted on line 10 of '/usr/local/etc/proftpd.conf'
freenas root: /usr/local/etc/rc.d/proftpd: WARNING: failed to start proftpd
freenas notifier: /usr/local/etc/rc.d/proftpd: WARNING: failed to start proftpd

"Operation not permitted" seems to have something to do with file/folder rights.
Any advice how a n00b should proceed?

 

[John Hixson]

Updated 9.2.1 > 9.2.1.2 via GUI upgrade.
Evrything seems to be in order, but the FTP-service is not starting:

Code:

freenas notifier: proftpd not running?
freenas notifier: Starting proftpd.
freenas notifier: freenas.local proftpd[16428]: Fatal: SyslogFacility: unable to open syslog: Operation not permitted on line 10 of '/usr/local/etc/proftpd.conf'
freenas root: /usr/local/etc/rc.d/proftpd: WARNING: failed to start proftpd
freenas notifier: /usr/local/etc/rc.d/proftpd: WARNING: failed to start proftpd

"Operation not permitted" seems to have something to do with file/folder rights.
Any advice how a n00b should proceed?

Okay. I am able to reproduce this. The problem turns out to be a stale syslog socket. If you restart syslogd you should be able to start your ftp service up. I am currently working on a fix for this.

 

[imdos]

I'm still running on 9.1.1 for my primary box. Is it safe to upgrade directly to 9.2.1(.2) through the GUI, or should I do 9.2.0 first and then 9.2.1(.2)?

 

[Yatti420]

I'm still running on 9.1.1 for my primary box. Is it safe to upgrade directly to 9.2.1(.2) through the GUI, or should I do 9.2.0 first and then 9.2.1(.2)?

Should be fine.. Just save a copy of your config as instructed for upgrade..

 

[imdos]

Should be fine.. Just save a copy of your config as instructed for upgrade..

That shouldn't be a problem. I've got a back-up script running which saves all config files and modifications to a (at the moment of writing still USB) disk, which is back-upped to my pool weekly.

Only thing to figure out now is if all my modifications to the base system are still required and if they need some patching.

And if my hand made optimalizations will interfere with the autotuning

 

[Savell Martin]

I've upgraded from 9,2.0 do I need to update my zfs?
If so how should I do this?

 

[GaiusBaltar]

I've upgraded from 9,2.0 do I need to update my zfs?
If so how should I do this?

you don't necessarily need to. but know that if you do, you can not go back to 9.2.0 if you decide to do so (without destroying the pool, re installing 9.20, then recreating the ZFS pool)

that said, the command to upgrade the zpool is:

Code:

zpool upgrade [zpool name]

 

[Savell Martin]

Ok thanks :)

 

[kyleman7]

I previously upgraded to 9.2.1.1 where I had issues, then, I went back to 9.2. Upon returning to 9.2 I have a the new .system dataset showing up on my storage tab. I'm wondering if I should destroy the .system dataset created by 9.2.1.1 before upgrading to 9.2.1.2?