[SOLVED] Out of free space where ?

[dunnno]

I've been facing a weird problem when trynig to refresh the Docker application list :

Warning: file_put_contents(): Only 0 of 1666 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 179 Fatal error: Uncaught exception 'UnexpectedValueException' with message 'RecursiveDirectoryIterator::__construct(/var/lib/docker/unraid/templates-community-apps/templates): failed to open dir: No such file or directory' in /usr/local/emhttp/plugins/community.applications/include/exec.php:61 Stack trace: #0 /usr/local/emhttp/plugins/community.applications/include/exec.php(61): RecursiveDirectoryIterator->__construct('/var/lib/docker...', 4096) #1 /usr/local/emhttp/plugins/community.applications/include/exec.php(138): Community->listDir('/var/lib/docker...', 'xml') #2 /usr/local/emhttp/plugins/community.applications/include/exec.php(180): Community->downloadTemplates('/var/lib/docker...', '/tmp/tmp-186204...') #3 /usr/local/emhttp/plugins/community.applications/include/exec.php(440): Community->DownloadCommunityTemplates() #4 /usr/local/src/wrap_post.php(17): include('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 61

 

I face a same (?) problem when i try to update my 6.0.1 tower to the new 6.1-RC2:

plugin: installing: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg ... done

plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/beta/unRAIDServer-6.1-rc2-x86_64.zip ... done

plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/beta/unRAIDServer-6.1-rc2-x86_64.md5 ... done

Archive: /tmp/unRAIDServer.zip

inflating: /tmp/unRAIDServer/bzimage

 

/tmp/unRAIDServer/bzroot: write error (disk full?). Continue? (y/n/^C)

warning: /tmp/unRAIDServer/bzroot is probably truncated

unzip error 0

inflating: /tmp/unRAIDServer/bzroot plugin: run failed: /bin/bash retval: 1

 

I can read here and there that there's a lack of free space somewhere but i don't understand it because my flash drive has around 3.8GB avalaible and any of my disks have 300GB at least of free space.

 

Any clue to resolve this ?

[trurl]

See here

[dunnno]

Thanks!

 

From what BRiT said, i have to write this:

# resize log partition

mount -o remount,size=384m /var/log

somewhere, so that's a new question. Where do i have to write this ?

[trurl]

Thanks!

 

From what BRiT said, i have to write this:

# resize log partition

mount -o remount,size=384m /var/log

somewhere, so that's a new question. Where do i have to write this ?

You can run it at the command line. If you put it in config/go unRAID will run it when it boots.

[dunnno]

Thanks again, ran it. Restarted the server (in case it was needed), the errors reappeared.

Isn't there a way to purge those logs? (if that's what cause those probs)

 

[trurl]

Thanks again, ran it. Restarted the server (in case it was needed), the errors reappeared.

Isn't there a way to purge those logs? (if that's what cause those probs)

Did you put it in the go file so it will run on boot? Running it from the command line will only work until the next boot, which apparently you did immediately after running it.

 

The unRAID OS unpacks fresh from the flash drive each boot and runs completely in RAM, including the default code that initializes the size of /var/log. In fact, /var/log itself is in RAM which means these logs are gone after boot as well.

 

Putting the code in config/go will run it after unRAID has booted so it will change the default size that unRAID set when it booted.

 

[dunnno]

I wrote that tiny piece of code into the go file and restarted the server, I guess there's no errors anymore. Hope it's gonna stay that way, or is it just gonna delay the problem?

[bonienl]

I wrote that tiny piece of code into the go file and restarted the server, I guess there's no errors anymore. Hope it's gonna stay that way, or is it just gonna delay the problem?

 

If you are continuously running out of space then you need to check your logs and see what's going on, it is not normal that logs are hogging your system.

 

[dunnno]

Okay guys, the server has been running smooth for a few days now and I'm not bothered by the errors I faced.

I guess my case is solved and clear! Thanks to all