Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Grafana
  3. Plugins auto update fail

Plugins auto update fail

Scheduled Pinned Locked Moved Grafana
2 Posts 2 Posters 73 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • O
    O
    OskarArdolo
    wrote last edited by
    #1

    Hi, I have experienced an issue today with my Grafana instance.

    I have a datasource configured on InfluxDB, and today it was entirely bugged in the Grafana app (somehow missing, and somehow still there, Schrodinger's datasource)

    After looking at logs, I found the root cause: an update on the influx's grafana plugin.
    The application tries to update its plugins on start-up which seems to be located in /app/code/data/plugins-bundled/, which is read-only. Therefore it could not finish the update and never loads the plugin.

    Updating plugin  pluginId=influxdb from=13.1.3 to=13.1.6
    Failed to install plugin  pluginId=influxdb error="unlinkat /app/code/data/plugins-bundled/influxdb: read-only file system"
    plugin process exited  logger=plugin.influxdb
    

    This only happened now because there was an update published yesterday on the Cloudron package, which made the container restart.

    Adding this to /app/data/custom.ini "solves" the problem:

    [plugins]
    preinstall_auto_update = false
    

    But correct fixing would be putting plugins somewhere in /app/data or make their directory writable by the update process.

    1 Reply Last reply
    2
    • J
      J
      joseph
      Staff
      wrote last edited by
      #2

      @oskarardolo Is it a good idea to make code writable?

      The package should probably set preinstall_auto_update = false by default though . cc @james

      1 Reply Last reply
      1

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Bookmarks
      • Search