Out of Memory Problems


Recommended Posts

Hiya,

 

Unfortunately I have had some reoccurring "out of memory" problems with my server over the past few weeks. This time I was actually able to get some diagnostics output which I have attached.

I had to run `diagnostics` from the command line which also gave errors.
 

Starting diagnostics collection... 
Warning: file_put_contents(): Only 0 of 5 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 80

Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 12 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 665 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 13 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 599 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 1034 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 14 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85

Warning: file_put_contents(): Only 0 of 82 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 101

Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120

Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device

Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160

Warning: file_put_contents(): Only 0 of 25 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160

 

EDIT: Currently running a MEMTEST. First pass completed without an error.

tower-diagnostics-20200710-1912.zip

Edited by ZipsServer
Link to comment

Could it possibly be a disk problem?

 

I have three external hard drives running in a btrfs pool through Unassigned Devices. My system just froze again and I was unable to run diagnostics. I also noticed that my dockers using the Unassigned Devices btrfs pool were not working properly and the Unassigned Devices plugin UI was not displaying any info.

I hard disconnected the external hard drives and everything returned to normal. Unsure if this was the cause of previous problems. Attached is the diags i just ran.

mastertower-diagnostics-20200719-1509.zip

 

EDIT: I want to clarify that I have run these external disks through a preclear without any errors and SMART seemed to be ok. This leads me to believe there may be a problem with using a manually created btrfs pool (no raid) with external disks. Any thoughts here?

Edited by ZipsServer
Link to comment
13 hours ago, ZipsServer said:

but it really only shows rcpbind messages from my NFS shares.

Those messages end up filling the syslog.

 

12 hours ago, ZipsServer said:

This leads me to believe there may be a problem with using a manually created btrfs pool (no raid) with external disks.

If by external you mean USB disks we don't recommend those used for pools/array devices, but it's not necessarily a problem, impossible to say if there are issues with this without the diags, ones posted just have the NFS spam.

Link to comment

The rcpbind log spamming with NFS shares has been brought up in other posts such as this

 

Unfortunately, there is no way to stop these log messages that I know of currently. I have sent a message to the support email but have not heard back.

I really don't understand why more people don't complain about the rcpbind spamming.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.