Calibre plugin trying to "chown" for non-existent directory

    • OMV 2.x
    • Resolved
    • Calibre plugin trying to "chown" for non-existent directory

      Running into a problem here. I tried activating Calibre recently (it'd been installed a while, but I wasn't using it) and ran into an error. As you can see below, it's trying to "chown" /media/ad1d56f8-7de7-4da9-9e8e-add98be1d615/Books. Problem is, that drive UUID doesn't exist, and it's not the UUID I selected for the data drive. It's also not the drive in OMV's config.xml, nor is it the one in /etc/calibre-server.conf. I've tried removing and reinstalling the plugin, no change. Running 'apt-get -f install' throws the same chown error for openmediavault-calibre. I even tried 'apt-get purge openmediavault-calibre' and then reinstalling, same error.

      I'm pretty sure that UUID is for a drive that failed long, long ago, and I'm not sure how I can get rid of it. I suppose I could create a symlink to the proper directory, but I'd really rather avoid that. Anyone have suggestions? The error is below.


      Source Code

      1. ​Error #4000:
      2. exception 'OMVException' with message 'Failed to execute command 'omv-mkconf calibre 2>&1': chown: cannot access `/media/ad1d56f8-7de7-4da9-9e8e-add98be1d615/Books/': No such file or directory' in /usr/share/openmediavault/engined/module/calibre.inc:83
      3. Stack trace:
      4. #0 /usr/share/openmediavault/engined/rpc/config.inc(180): OMVModuleCalibre->applyConfig()
      5. #1 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      6. #2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      7. #3 /usr/share/php/openmediavault/rpcservice.inc(158): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
      8. #4 /usr/share/openmediavault/engined/rpc/config.inc(224): OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
      9. #5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
      12. #8 /usr/sbin/omv-engined(500): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1)
      13. #9 {main}
      Display All
    • Try purging the plugin: apt-get purge openmediavault-calibre

      If that doesn't work, you may have to manually edit the config.xml file.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Purged it, still threw the error on reinstall, still getting the error on re-apply.

      When I go into the config.xml file (it is the one in /etc/openmediavault/ yes?) and do a search for 'ad1', I get no result, and the calibre section lists the correct UUID (3414ab35-295e-4d67-9fa7-a1e6e711c7f5).

      I did just try and manually start Calibre, and I got the following:

      Source Code

      1. ​root@moonhawk:/etc/openmediavault# service calibre start
      2. Starting Calibre
      3. root@moonhawk:/etc/openmediavault# No write acces to /media/ad1d56f8-7de7-4da9-9e8e-add98be1d615/Books/.config/calibre using a temporary dir instead


      At that point it hangs. So it looks like something with Calibre itself, but it was removed I thought when I removed the plugin.
    • Calibre doesn't remove anything from the data directory when purging. So, make sure to use a new shared folder. An existing one can cause problems. It should also only be used by calibre. Why did you manually start it? If the plugin doesn't work when applying settings, then it won't work manually starting it.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

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