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


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • 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

Cloudron Forum

Apps | Demo | Docs | Install

Healtheck error and logs broken

Scheduled Pinned Locked Moved Solved LibreTranslate
15 Posts 3 Posters 91 Views
    • 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.
  • W Offline
    W Offline
    warg
    wrote on last edited by
    #1

    Hello,

    LibreTranslate is running for some time without issues. In the logs I see that the HealthChecks died for unknown reasons:

    7af587ab-3d18-4436-8f13-def3af59fdfc-grafik.png

    Furthermore clicking "Download Full Logs" downloads a text file with the exact same (very few) log entries but throws an error that the log file wasn't found.

    Looks like Cloudron v7.5.0 broke it or it's unstable.

    Best Regards,

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #2

    Not seeing this in both our instances. I tired a test install and that doesn't have this error either. Anyone else seeing this?

    Do you see this error even after app restart?

    1 Reply Last reply
    0
  • W Offline
    W Offline
    warg
    wrote on last edited by
    #3

    Restarting the app did help to get the log logging again but downloading the full log file is still broken.

    Looks like there's an error in the browser console of Firefox:

    grafik.png

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #4

    Do you get the logs error with other apps as well? Just wondering if this is a general log viewer issue in 7.5.0 . Maybe we introduced a regression.

    1 Reply Last reply
    0
  • W Offline
    W Offline
    warg
    wrote on last edited by warg
    #5

    Health Checks just died again so looks like a reoccuring issue without any user-related activity.

    Downloading full logs (error "Log file(s) not found") is broken for other apps as well, e. g. NextCloud. So we have 1 app-specific issue and 1 app-unrelated issue (regression).

    1 Reply Last reply
    1
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by
    #6

    for the log file issue, can you enable remote SSH support for us and send a mail to support@cloudron.io with your dashboard domain so we can debug this directly?

    1 Reply Last reply
    1
  • W Offline
    W Offline
    warg
    wrote on last edited by
    #7

    I have sent an email (actually 2 because I forgot details in the first one). Thank you.

    1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by
    #8

    Thanks for providing this. The issue with downloading full logs is indeed a regression in 7.5 and is fixe in the upcoming release then.

    For Libretranslate, it seems the app as such is running, but still shows those timeouts in the logs for the healthcheck. Not sure yet what the root cause for this is.

    W 1 Reply Last reply
    0
  • W Offline
    W Offline
    warg
    replied to nebulon on last edited by
    #9

    @nebulon said in Healtheck error and logs broken:

    For Libretranslate, it seems the app as such is running, but still shows those timeouts in the logs for the healthcheck. Not sure yet what the root cause for this is.

    Looks like a regression too because it didn't happen with previous Cloudron version and there was no app update.

    1 Reply Last reply
    1
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by
    #10

    Actually the timeouts for the healthcheck are quite infrequent (about faililng twice per hour, while we perform the check every 10 seconds!) and seem to be due to temporary server load. I don't think there is anything to be fixed as such besides adding more hardware resources. So in the end there is likely nothing to be concerned as long as the app itself is working.

    1 Reply Last reply
    0
  • W Offline
    W Offline
    warg
    wrote on last edited by warg
    #11

    How comes that you think the hardware resources is an issue? This sounds very unlikely to me (stats for last 24h):

    • RAM is 3 of 16 GB used
    • CPU is <= 20 % exhausted
    • disk is nearly not even half full + high read/write rates

    If it's a performance issue, this is caused on Cloudron's side somewhere. Furthermore there is zero user activity on my the machine nor does the timeouts happen at times where something is done, e. g. when I'm not even connected to the machine and no updates run.

    Also it looks like a bug that the app is reported as online/running when healthcheck fails.

    1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by
    #12

    As said, the healthcheck succeeds nearly all the time, so besides the log line there is nothing to worry about.

    1 Reply Last reply
    0
  • W Offline
    W Offline
    warg
    wrote on last edited by warg
    #13

    I see. So basically the healtcheck logging in the LibreTranslate app is different to the other apps and thus I wasn't aware the healthcheck does succeed most of the time because in the log you see no information about successful healthchecks, only failed ones it looks like while other apps show both.

    1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by nebulon
    #14

    Correct, the logging of the upstream apps as such is app specific, so in this case only failed requests are show.

    I guess we can close this thread then as resolved?

    1 Reply Last reply
    2
  • W Offline
    W Offline
    warg
    wrote on last edited by
    #15

    Sounds good, let's close it. Thank you.

    1 Reply Last reply
    0
  • W warg marked this topic as a question on
  • W warg has marked this topic as solved on

  • Login

  • Don't have an account? Register

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

  • Don't have an account? Register

  • Login or register to search.