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

  • Hi,
    I just installed a fresh OMV 3.16.0 and I'm getting the following error in the web interface:


    It appears most of the time when I try to save and apply my changes but sometimes I'm lucky and the error doesn't show up.
    Logging out/rebooting seems to fix it for "one saving".


    I hope you can help me :)


    Best regards,
    Daniel

  • Oh sorry, I made a careless mistake. When looking up the version number I got into the kernel line.


    OMV version is 3.0.36
    Kernel 3.16.0-4-amd64


    I updated everything from the Update Manager Tab and my new OMV Version is 3.0.52.


    That did not solve my issue. For instance I got the same error for checking for new updates and trying to upload the extras deb to the plugins.

  • It is installed on a SD Card. I made sure to use a new, high quality one with wear leveling. Also it has a capacity of 32 GB so that should be enough space for the wear leveling to get through the installation without destroying the card.
    I've got similar errors when I installed it to a ssd but I didn't keep this installation due to problems with the network.
    So I guess it must be some configuration problem.


    I couldn't find anything interesting in the logs. I looked into syslog, daemon.log and messages.

  • I assumed that there might be some sort of a bug in the code. I was able to get it working again with some changes that I will explain now:


    In the file /usr/share/php/openmediavault/json/file.inc I changed the getContens() method to use php's file_get_contents()



    Then I got an invalid JSON Error in line 217 (original file)


    I checked the returned json string for validity and it was ok.
    Then I went to usr/share/php/openmediavault/functions.inc to check the is_json method and found that the
    regex in line 363 is responsible (but I absolutly don't know why because the regex looks fine to me).
    I commented it out and my is_json method looks like this now:



    Now I don't get any "Failed to read file '/tmp/...'" errors any more and it seems to work great.


    As I'm not very familiar with the project I'm unsure if my changes will break something in another place or what some sideeffects might be.




    Also I found that there is a misleading error message in the read method:


    In line 7 (source code from this post) json_last_error_msg() is called but as far as I can see if the $contents is empty the validate method will return false before json_decode can be called so json_last_error_msg() will return No Error, which is kind of confusing for the end user.

  • I installed using iso to bootable usb (used unetbootin-windows-625.exe to create bootable usb)


    output for ls -al /


    output for ls -al /tmp

  • output for mount


    output for cat /etc/fstab

  • did you ever resolve this?


    I am having the same problem after an update from stonerburner to erasmus.


    Everytime I try to make some configuration changes or update/install plugins I get "Failed to read file '/tmp/bgstatus80tySW' (size=0)."


    Also transmission seems to be broken, cant do any configuration changes and I cant get it enabled from the GUI because this error pops up all the time:
    "The property 'pexenabled' does not exist in the model 'conf.service.transmissionbt'."


    Also this is "stuck":
    The configuration has been changed. You must apply the changes in order for them to take effect.
    And it wont go away when I click Apply or Revert changes.


    I am totally out of ideas here and I think these are odd errors to have after an update... Any help ?

  • Clear your browser cache to start. Then omv-aptclean Then try removing: rm /var/lib/openmediavault/dirtymodules.json

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • i am also having similar error, with stuck "configuration has been changed" banner. omv-aptclean and removing dirtymodules.json did not help


    HP Proliant Microserver Gen8, E3-1265Lv2, 16 GB ECC RAM, 3x WD RED 3TB + 1x WD RED 4TB + Crucial MX300 525 GB SSD.

    Powered by Proxmox VE

  • Fresh install of ArmBian -> Update packages -> Install OMV



    Board is an ARM Alwinner A10, installed on a microSD card. Reinstalled several times, this happens all the time. OMV 3.0.89

    24/7 PCDuino3 Nano OMV 4 (custom built armbian with debian 9), 1drive
    OMV 4, AMD A8-5600k + 16gb, 8 drives, 26TB of storage, zalman r1 with custom hdd bracing

    test OMV 5, AMD e350 + 4gb, 1 drive , DIY enclosure from Nokia D-Box 2 case.

  • i did a fresh reinstall, upgraded to arrakis, installed a bunch of plugins and the Failed to read file '/tmp/bgstatusybb9l8' (size=0). error reappeared.


    the issue started with this plugin installation (pasted only the errored parts):






    I suspect it's virtualbox causing the issue in my case, as it was plugin i installed in the previous run as well.

    HP Proliant Microserver Gen8, E3-1265Lv2, 16 GB ECC RAM, 3x WD RED 3TB + 1x WD RED 4TB + Crucial MX300 525 GB SSD.

    Powered by Proxmox VE

  • I suspect it's virtualbox causing the issue in my case, as it was plugin i installed in the previous run as well.

    in my case it seems to be related to flashmemory plugin which is installed by default on ARM systems afaik.


    This makes OMV unusable at all, I can't save settings, nor install packages via UI

    24/7 PCDuino3 Nano OMV 4 (custom built armbian with debian 9), 1drive
    OMV 4, AMD A8-5600k + 16gb, 8 drives, 26TB of storage, zalman r1 with custom hdd bracing

    test OMV 5, AMD e350 + 4gb, 1 drive , DIY enclosure from Nokia D-Box 2 case.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!