Error: "Failed to read file '/tmp/bgstatusfs2WVj' (size=0)."

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • tornadox wrote:

      This makes OMV unusable at all, I can't save settings, nor install packages via UI
      If it's the flashmemory plugin simply disable it and you're done. If you want others being able to get a clue what's going on you might want to provide 'armbianmonitor -u' output too first :)
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • tornadox wrote:

      in my case it seems to be related to flashmemory plugin which is installed by default on ARM systems afaik.
      I've never had an issue with the flashmemory plugin causing this. Does removing the plugin fix your problem?
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      I've never had an issue with the flashmemory plugin causing this. Does removing the plugin fix your problem?
      It was just an assumption, anyway I've scrapped the A10 board for several reasons and moved to PCDuino3Nano. The problem does not appear there, however it sometimes appears on my main OMV x86 server with the system installed to an SSD drive. not sure what causes the issue, but it appeared only once. I suppose it can be caused by OMV running from a slow storage drive like microSD.
      24/7 OpenVPN server: PCDuino3 Nano, OMV 3, ARM V7 Alwinner A20, 1GB DDR3, 1x500GB HGST (2.5"), 1000mbps lan. 300GB +160 GB old IDE Seagate Drives, running over wifi.
      used with WOL by demand: OMV 3, Cooler Master Elite 120, Asrock E350M1, 84GB DDR3, 6432GB SSD(kingfast) for OS, 2x4TB + 2x2TB - Seagate(3.5"). 1x500GB HGST, 1x500GB WD.
    • in my case it seems the issue is related to OMV 4. installing and setting up OMV 3.0.89 did not invoke the issue. so it seems like this:

      1) HP N40L - OMV 4.0.6 failed to read file error appears after installing & setting up plugins, reproduced 3 times
      2) HP N40L - OMV 3.0.89 - everything OK, cannot reproduce
      3) Virtualbox - OMV 4.0.6 - everything OK, cannot reproduce

      Now i cannot gurantee that i performed exactly the same steps in every case. In case of virtualbox i did not set up an additional partition on the system disk and did not change the default webui password.
      HP N40L, 4 GB ECC RAM, 3x WD RED 3TB + OCZ Vertex3 128 GB SSD
    • I have also the same problem.
      I upgraded my backup server from omv 3 to omv4 and the problem appeared.
      In omv3 there was no problem.

      Source Code

      1. Error #0:
      2. OMV\Exception: Failed to read file '/tmp/bgstatusCG8Qsw' (size=0). in /usr/share/php/openmediavault/json/file.inc:199
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()
      5. #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(306): OMV\Json\File->read()
      6. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(536): OMV\Rpc\ServiceAbstract->finalizeBgProcStatus('/tmp/bgstatusCG...', '', Object(OMV\Exception))
      7. #3 /usr/share/openmediavault/engined/rpc/rsync.inc(265): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      8. #4 [internal function]: OMVRpcServiceRsync->execute(Array, Array)
      9. #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('execute', Array, Array)
      11. #7 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Rsync', 'execute', Array, Array, 1)
      12. #8 {main}
      Display All
    • maybe this is the same?! I get this error when trying to apply settings from email notification service.

      Source Code

      1. Fehler #0:
      2. OMV\Exception: Failed to read file '/tmp/bgstatusCDVTKA' (size=0). in /usr/share/php/openmediavault/json/file.inc:199
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()
      5. #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(306): OMV\Json\File->read()
      6. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(536): OMV\Rpc\ServiceAbstract->finalizeBgProcStatus('/tmp/bgstatusCD...', '', Object(OMV\Exception))
      7. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      8. #4 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      9. #5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      12. #8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      13. #9 {main}
      Display All
      Intel Pentium G3460T @ 3GHz
      Debian GNU/Linux 9.2 (stretch)
      Release: 4.0.10-1 Arrakis

      Post by godfuture ().

      This post was deleted by votdev ().
    • Same issue for me as well, Brand few fresh install of 4.0.13-1 installed from a USB stick to SATA drive. After install I was able to install updates, load omv extras and install a bunch of plugins without any issues. It started happening after I tried enabling the SMART Plugin. At first I was able to disable that plugin, reboot and then it let me apply. however after trying again it wont let me apply any settings what so ever, even after apt-clean, and multiple reboots.

      Error #0:OMV\Exception: Failed to read file '/tmp/bgstatusj07kHO' (size=0). in /usr/share/php/openmediavault/json/file.inc:199Stack trace:#0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()#1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(306): OMV\Json\File->read()#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(536): OMV\Rpc\ServiceAbstract->finalizeBgProcStatus('/tmp/bgstatusj0...', '', Object(OMV\Exception))#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))#4 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)#5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)#8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)#9 {main}

      x86 - AMD A8-5545 here (Biostar A68N-5545), boot drive is a Maxtor 300G sata drive, I initially tried installing to a USB Stick and had nothing but issues so I did a complete fresh reinstall on this drive. Things were much better until this occurred.

      The post was edited 2 times, last by iamchocho: Additional details ().

    • It is a known issue. We are trying to find what is causing it. The code hasn't changed in over a year. So, it is likely a php7 issue.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Hello,

      SO i have the same problems i have installed Fresh copy with no plugins and flash plugin just vanilla OMV 4
      As you can see on this video useloom.com/share/a323a5bcacc14ba5ac50a0553e3b13fc

      I will get the error randomly no matter what i do in most case i get the error on first try and second try is fine.

      But if i run apt clean if seams to clear the error when it happens over and over but it will come back.

      The post was edited 1 time, last by gibbc: added temp fix ().