FreeNAS 9.2.0-BETA now available!

[jyavenard]

I upgraded to 9.2 beta earlier today.
played with the web interface, looking into system information, then settings, looked at AFP, then attempted to open CIFS.
When it tried to open the CIFS settings page, it just hanged. In the console (via ipmi), I see that python2.7 takes 100% cpu time. Can't seem to do anything.

And so I rebooted.
Tried to reproduce the problem but couldn't.

The new jails type are great!

One suggestion:
For the dynamic dns service, it would be great to have a "custom dyndns" option. Something that uses the dyndns but allowing you to set your own URL: there are plenty of dynamic dns services that uses the same API as dyndns but that aren't listed in the default list.
Another would be to simply allow to set a URL such as:
"http://username:password@blah.com/myip?ip=@" where "@" is your IP address.

that way I could use the system with hurricane electric IPv6 tunnel broker.

Otherwise, great so far... Haven't done much with it, but I like that the "CIFS shares blah" doesn't show on my mac anymore... served little purpose as freenas was showing under several different names there.

Edit: it has happened again, this time I did absolutely nothing. I suddenly heard the fan of my very noisy chassis suddenly started to become even louder. When to the GUI and it was unresponsive. Checked on the console, and once again python2.7 process was using 100% of CPU...

 

[Dusan]

Edit: it has happened again, this time I did absolutely nothing. I suddenly heard the fan of my very noisy chassis suddenly started to become even louder. When to the GUI and it was unresponsive. Checked on the console, and once again python2.7 process was using 100% of CPU...

That issue should already be taken care of: https://bugs.freenas.org/issues/3478

 

[jyavenard]

thanks... is there a place where you can download the latest image then (9.2-RC from the tag) ?

Edit: I wasn't browsing the rrd page at the time ... maybe it's a different issue?

I restarted the ngix service, now I get when trying to connect:

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 theerror log for details.
Faithfully yours, nginx.

 

[Dusan]

thanks... is there a place where you can download the latest image then (9.2-RC from the tag) ?

I don't see any at the moment. The RC is not out yet and the last night build on SourceForge is from November 20th.

I restarted the ngix service, now I get when trying to connect:

You also need to restart python/django. kill -9 the stuck process and run "service django restart".

 

[jyavenard]

thank you very much for those instructions... easier than rebooting!

I've been trying to compile from git, but compilation always fail when trying to compile libc...
Maybe I should open another thread on how to compile freenas...

 

[Fran Aquino]

I'm having the same issues other users are reporting with networking within Linux jails, Debian 7 template in my case.
ifconfig reports eth0 as present but I've been unable to assign it an IP address

# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 02:66:55:00:0a:0b
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:126 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
RX bytes:36190 (35.3 KiB) TX bytes:478 (478.0 B)

# ifconfig eth0 192.168.158.135 netmask 255.255.255.0
SIOCSIFADDR: Address family not supported by protocol
SIOCSIFFLAGS: Invalid argument
SIOCSIFNETMASK: Invalid argument

 

[hidden72]

I don't have an account (yet) on bugs.freenas.org. Was poking around the 9.2.0-beta and saw small GUI issue. Under Storage / ZFS Replication, I have a couple of replication tasks defined. The summary screen shows the "Remote Hostname" fields as blank. However, if I edit the replication, the Remote Hostname field is populated.

 

[jyavenard]

the HOME directory option in AFP sharing doesn't seem to work any longer... On the mac I can only see the shares I actively created in freenas.

trying to go to afp://freenas_ip/username gives me a "share doesn't exist" error.

Ended up compiling my own image from github; the 100% CPU time issue hasn't occurred since I upgraded earlier today.
I'm copying the images there if anyone is interested:
http://www.avenard.org/files/freenas/nightlies/

will take a few hours for the image to be uploaded...

 

[jkh]

thanks... is there a place where you can download the latest image then (9.2-RC from the tag) ?

I've just restarted the nightlies at http://iso.cdn.freenas.org/nightlies/ - 2013-11-28 is uploading now and should be there shortly.

I can't promise to do this every night, since in some cases there may be no point (very little change from previous night) but the python run-away problem is bad enough that I think it's worth releasing this one. FWIW, this one is running on all my own machines and so far so good!

I also applaud @jyavenard for doing his own nightlies - that's cool! Technically, anyone should be able to build FreeNAS from sources, and I'd like to hear more from folks who are trying and what sorts of issues they're running into, if any. The build process has already been much improved over the last few months (there wasn't even a Makefile 4 months ago!) but I'm sure it can get better!

- Jordan

 

[jkh]

the HOME directory option in AFP sharing doesn't seem to work any longer...

Can I get you to file a bug on bugs.freenas.org about this? It very likely won't get fixed if it's not tracked in the bug database. :(

Thanks!

 

[jyavenard]

I also applaud @jyavenard for doing his own nightlies - that's cool! Technically, anyone should be able to build FreeNAS from sources, and I'd like to hear more from folks who are trying and what sorts of issues they're running into, if any. The build process has already been much improved over the last few months (there wasn't even a Makefile 4 months ago!) but I'm sure it can get better!

Oh, I'm not sure this is going to be a regular thing !

it's currently a very manual process, I would love to automate it but I'm not having much luck so far... plus I build in a VM and it takes LOTS of time (6 hours or so)

Probably would be better to mention it elsewhere than this thread but...

issues I've encountered:
I built in a VM, using FreeBSD 9.2 on a zfs partition as required by the README (why is that BTW)?

So the notes:
- Must have more than 14GB of disk space available; or building will run out of space (that purely the space required for the freenas git clone)
- Must have at least 4GB of RAM minimum. 512MB, 1GB, 2GB caused the pxz compressor when building the GUI image to get killed otherwise.

I had to modify the build/nanobsd/nanobsd.sh: and modify umount with umount -f ; for some reasons, compilation would otherwise always fails when the scripts attempt to unmount os-base/_.mnt with "device busy" (or something to that extent)

More often than not; when the build failed half-way due to the errors above, I found no way of restarting the build short of deleting everything and restarting from scratch. I'm sure there's an easier way to do so, but when the build failed, it would usually leave some temporary files over and it would always exit early...

I've attempted to build on my freenas box directly ; not getting anywhere... compiling from zero fails when compiling libc
I then compiled world+kernel on the VM; copied the file over to the freenas box and restarted the build. After a while it get stuck while building the disk image.

it just doesn't progress; ps shows that the culprit is cpio getting stuck: here is ps axww of when it happens

6976 0 I+ 0:00.00 make release
6978 0 S+ 0:00.01 script -a release.build.log make do-release
6979 1 Is+ 0:00.00 make do-release
6987 1 I+ 0:00.00 /bin/sh build/build_release.sh
31581 1 I+ 0:00.00 sh build/do_build.sh -a
31612 1 I+ 0:00.06 sh /pool/freenas/build/nanobsd/nanobsd.sh -c /pool/freenas/nanobsd/os-base -b -j 9
58128 1 I+ 0:00.00 sh /pool/freenas/build/nanobsd/nanobsd.sh -c /pool/freenas/nanobsd/os-base -b -j 9
58145 1 I+ 0:00.00 sh /pool/freenas/build/nanobsd/nanobsd.sh -c /pool/freenas/nanobsd/os-base -b -j 9
58210 1 I+ 0:00.02 find .
58211 1 I+ 0:00.00 egrep -v (CVS|\\.git|\\.svn|.orig$|.rej$)
58212 1 I+ 0:00.00 sh /pool/freenas/build/nanobsd/nanobsd.sh -c /pool/freenas/nanobsd/os-base -b -j 9
58213 1 D+ 0:00.44 cpio -dumpv /pool/freenas/os-base/amd64/_.mnt (bsdcpio)
58214 1 I+ 0:00.00 grep -v ^./usr/workdir/
58215 1 I+ 0:00.00 grep -v ^./usr/obj/

been stuck like that for over an hour.

Edit: I should add that it's impossible then to interrupt the process other than using kill -9 on all processes listed above

 

[jyavenard]

Can I get you to file a bug on bugs.freenas.org about this? It very likely won't get fixed if it's not tracked in the bug database. :(

Thanks!

done:
https://bugs.freenas.org/issues/3534

 

[Yatti420]

Thanks for the nightly.. Seems that the WebGUI stays up now as of RC-2651b1b-x64.. I still see high system load.. Or I think it's high compared to what I was getting in 9.1.1..

 

[jkh]

Can you ssh into the box and run top(1)? Sort by CPU and see what's using the most, then maybe paste in the top 10 lines. Thanks!

 

[Yatti420]

Can you ssh into the box and run top(1)? Sort by CPU and see what's using the most, then maybe paste in the top 10 lines. Thanks!

It seems alot better.. Maybe i'm just misreading the load averages but I thought it didn't get this high on Freenas 9.1.1 ..

Code:

last pid: 32336;  load averages:  0.97,  0.96,  0.98    up 0+08:19:37  09:55:10
67 processes:  1 running, 66 sleeping
CPU 0:  0.0% user,  0.0% nice,  0.0% system,  0.8% interrupt, 99.2% idle
CPU 1:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
Mem: 124M Active, 138M Inact, 2959M Wired, 1168K Cache, 88M Buf, 4656M Free
ARC: 2305M Total, 1152M MFU, 930M MRU, 48K Anon, 14M Header, 210M Other
Swap:
 
  PID USERNAME    THR PRI NICE  SIZE    RES STATE  C  TIME  WCPU COMMAND
32213 root          1  20    0 16556K  2608K CPU0    0  0:01  0.20% top
7234 root        12  20    0  138M 20644K uwait  0  4:51  0.10% collectd
4496    921        2  20    0 50836K 10696K kqread  0  0:41  0.00% transmissi
3048 root          1  20    0 12040K  1688K select  0  0:38  0.00% powerd
5886 root          1  20    0  9916K  1668K select  0  0:05  0.00% minirsyslo
3903 root          1  20    0 91312K 17404K select  0  0:05  0.00% python2.7
2486 root          1 -52  r0 12044K  8024K nanslp  0  0:05  0.00% watchdogd
4763 root          6  52    0  102M 18440K usem    0  0:04  0.00% python2.7
6498 root          6  52    0  164M 46996K usem    1  0:04  0.00% python2.7
2605 root          1  20    0 22216K  4160K select  1  0:03  0.00% ntpd
5502 root          1  20    0  188M 17244K kqread  0  0:01  0.00% php-fpm
2729 root          1  20    0 73724K  7804K select  1  0:01  0.00% nmbd
3176 root          1  20    0 36488K  5424K select  0  0:01  0.00% proftpd
7322 root          1  52    0 14136K  1920K nanslp  0  0:01  0.00% cron
2476 root          1  20    0 12036K  1736K select  1  0:01  0.00% syslogd

 

[Dusan]

It seems alot better.. Maybe i'm just misreading the load averages but I thought it didn't get this high on Freenas 9.1.1 ..

If you mean the CPU Usage graph on the Reporting screen then in 9.1.1 it only displayed data for one core. In 9.2.0 it aggregates data for all cores. The System Load graph should be the same.

 

[jkh]

It seems alot better.. Maybe i'm just misreading the load averages but I thought it didn't get this high on Freenas 9.1.1 ..

Well, based on your top(1) numbers, I don't know how the load could drop much *lower*. :) There's nothing really eating CPU time in that particular sample, at least. The box is, for all intents and purposes, completely idle.

 

[jyavenard]

.8% CPU usage, that is indeed very high :)

I've set a cron job to build nightlies (where does that name come from btw?), all available there: http://www.avenard.org/files/freenas/nightlies/

I did so because I wanted the fix for the AFP home share.... (thanks btw for fixing it so quickly)

 

[amires]

.8% CPU usage, that is indeed very high :)

I've set a cron job to build nightlies (where does that name come from btw?), all available there: http://www.avenard.org/files/freenas/nightlies/

I did so because I wanted the fix for the AFP home share.... (thanks btw for fixing it so quickly)

What is the difference between your nightlies and the ones here : http://iso.cdn.freenas.org/nightlies/ ?

 

[cyberjock]

What is the difference between your nightlies and the ones here : http://iso.cdn.freenas.org/nightlies/ ?

You should be using the official nightlies only. It adds alot of complexity if you aren't using the official builds as you may have problems we don't have.

One of the other mods emailed me asking if we should delete that link as we shouldn't be confusing people with multiple sources for nightlies.

What this forum doesn't need is a bunch of non-standard unofficial builds floating around trying to be supported here.