Console Messages missing in pop-up window

[maurertodd]

9.2.1.2.

I have console messages appearing in the footer. When I click that box in the footer I get the pop-up window for the console messages, but the pop-up window is empty. The footer box shows messages.

Is there something I need to change or fix to be able to view the messages i the pop-up window?

 

[cyberjock]

Can you post server specs?

 

[maurertodd]

Build FreeNAS-9.2.1.2-RELEASE-x64 (002022c)
Platform AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Memory 2986MB

 

[cyberjock]

Are you running ZFS?

 

[maurertodd]

yes

 

[cyberjock]

Well, I'd start with meeting the minimum hardware requirements for FreeNAS...

I didn't put 8GB of RAM for FreeNAS with ZFS because of boredom.. it's a fact that if you don't have 8GB of RAM weird unexplained things happen to FreeNAS. Guess what my first guess is to your problem?

 

[maurertodd]

So a system showing 2.1 GB of free memory is memory starved. That's an interesting theory.

Now if I were running ZFS with dedup and read ahead in a production environment and pounding the daylights out of the arc, then having 8GB makes sense to me. But in this test box case adding another 5GB (and buying the motherboard to support it) would most likely reseult in 7.1 GB free.

I'd asked about the recommended minimums before. The response I got was that for a small non-production server the memory should be fine. That the recommendation was aimed at production NAS servers and performance issues that not having enough cache can cause.

But theories are meant to be explored no matter how much sarcasm and contempt they are delivered with.

So I detached my two ZFS volumes and rebooted.

Now the console messages popped up. Imported the larger of the two and they didn't. Detached and they did. Then I added the smaller volume and they still did. Imported larger volume and they still did...? So I rebooted again. And I still see the console messages in the popups. The only difference is the the order of the ZFS volumes in the volume list or in a zpool status for that matter.

So is there validity to the argument that 3GB is the issue and it is causing strange behaviors, or is something more subtle going on?

I was sure cyberjock was on to something and was somewhat stunned when after adding the larger volume back in that things still worked. Of course that is the nature of flaky.

 

[cyberjock]

Really? How about the message from the manual?

The best way to get the most out of your FreeNAS® system is to install as much RAM as possible. If your RAM is limited, consider using UFS until you can afford better hardware. FreeNAS® with ZFS typically requires a minimum of 8 GB of RAM in order to provide good performance and stability.

If you don't have at least 8GB of RAM with ZFS or 2GB of RAM with UFS, you should consider getting more powerful hardware before using FreeNAS® to store your data. Otherwise, data loss may result. Plenty of users expect FreeNAS to function with less than these requirements, just at reduced performance. The bottom line is that these minimums are the minimums based on many users' feedback in the forums for FreeNAS® to work, regardless of performance. Do not ask for help on systems that do not meet these requirements in the forums or IRC. They will likely be ignored because of the abundance of information that FreeNAS may not behave properly with <8GB of RAM.

I don't think I need to say anymore... the validity is already in the manual. I wrote that in the manual.. because of the abundant data. To be blunt, I got tired of having to continually explain over and over to every 3rd person that shows up that you need enough RAM for the system to be stable. So now I paste the manual and let them deal with their issues accordingly.

I didn't see anyone in the forum that every validated that 3GB of RAM is enough, but we've told plenty of people with twice your RAM to go to 8GB or GTFO. ;)

Free memory isn't free for most definitions of "free". It's a lot to explain, but the bottom line is that the manual speaks for itself.

 

[maurertodd]

What the second paragraph of you quote is saying is that essentially anyone with less than 8GB with ZFS should stay away from the forums.

I don't come to the forums expecting that code will be changed. I come because I assume I'm doing something wrong. Granted I have only 3GB of memory, but I've been running v8+ for years that way. If a new behavior shows up, I'm going to be sure I didn't do something wrong procedurally before I invest a couple hundred dollars and a week of time in hardware. Also it is possible that someone with more memory has seen a similar problem.

Yes "free memory" is more than just empty space. The bulk of UFS cache resides there. Deallocated pages end up here too. Too small can incure paging.

Not disputing the validity of what you are saying, in fact I ran an experiment that seems to support it. However you do realize you are making circular argument: I'm right because the manual backs me up...the manual is right because I wrote it. Just saying.

 

[Yatti420]

Use UFS.. System wayyy underspecd.. Is this a non-ecc box aswell?

I'm glad you understand you are doing something wrong. .Step one would be to use UFS until you are capable of using ZFS.. The only other thing this could really be is browser caching..

Granted I have only 3GB of memory, but I've been running v8+ for years that way.

What is V8? Is this FreeNAS? How does it have anything to do with running FreeBSD?

You ran your own experiment so you know running ZFS with less the 8gb of ram is a bad idea.. It doesn't take long to figure out..

Read the docs / search the forums.. X86/UFS is finished in FreeNAS anyways so hopefully guard dog wont have to reply to many more of these..

 

[Michael Mendoza]

I am having a similar issue. Both the console and the pop up window are empty. It occurs when Plex is updating. It will remain in this state for hour after Plex completes the updates. Then it goes back to normal. Very frustrating and I can't figure out why.

FreeNAS-9.3-STABLE-201412090314
E3-1270 V3
8 Seagate SEST4000VN00 4TB NAS Internal HDD
1 Intel Xeon E3-1270 v3
4 Samsung 8GB DDR3-1600 MHz PC3-12800 M391B1G73QH0-YK0
1 Fractal Design FD-CA-NODE-804
1 SeaSonic G Series 550-Watt 80 PLUS GOLD
1 Supermicro Motherboard MBD-X10SL7-F-O
1 SanDisk Cruzer Fit 8GB USB 2.0

 

[pschatz100]

What the second paragraph of you quote is saying is that essentially anyone with less than 8GB with ZFS should stay away from the forums.

I don't come to the forums expecting that code will be changed. I come because I assume I'm doing something wrong. Granted I have only 3GB of memory, but I've been running v8+ for years that way. If a new behavior shows up, I'm going to be sure I didn't do something wrong procedurally before I invest a couple hundred dollars and a week of time in hardware. Also it is possible that someone with more memory has seen a similar problem.

Yes "free memory" is more than just empty space. The bulk of UFS cache resides there. Deallocated pages end up here too. Too small can incure paging.

Not disputing the validity of what you are saying, in fact I ran an experiment that seems to support it. However you do realize you are making circular argument: I'm right because the manual backs me up...the manual is right because I wrote it. Just saying.

@maurertodd
No reason for the snarky post. You came to the forum because you assumed that you were doing something wrong... You are. And when told what it is, you get upset - even though you subsequently confirmed that what you were told is correct.

If you had taken a little time to understand the differences between FreeNAS 8 and 9.2, particularly with respect to the resource needs of UFS versus ZFS, then you might have answered your own question before coming to the forum. You may not always like the tone of the forum regulars, but at least show a little respect.