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

Vikunja instance running into variety of errors

Scheduled Pinned Locked Moved Solved Vikunja
10 Posts 3 Posters 212 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.
  • S Offline
    S Offline
    shrey
    wrote on last edited by shrey
    #1

    My Vikunja has sort of stopped functioning.

    When i try to login, i either get 405 error, or 502.
    Have ensured that login credentials are working, network connection from local to cloudron is ok and that the Vikunja app is up and running with enough resources.

    Also, i keep seeing this error in the console:

    Feb 25 09:56:10 172.18.0.1 - - [25/Feb/2023:04:26:10 +0000] "GET /api/v1/info HTTP/1.1" 502 166 "-" "Mozilla (CloudronHealth)"
    Feb 25 09:56:10 2023/02/25 04:26:10 [error] 130#130: *574 no live upstreams while connecting to upstream, client: 172.18.0.1, server: default_server, request: "GET /api/v1/info HTTP/1.1", upstream: "http://localhost/api/v1/info", host: "my-vikunja-domain"
    
    

    What could be the issue here and how do i go about diagnosing it?

    Thanks.

    fbartelsF 1 Reply Last reply
    1
  • fbartelsF Offline
    fbartelsF Offline
    fbartels App Dev
    replied to shrey on last edited by
    #2

    @shrey the vikunja app has some frontend files and then a separate backend server (all part of the same app). The error 502 indicates that the backend has stopped for some reason.

    I would restart the Cloudron app and have a look at the logging during startup if login still does not work afterwards.

    What makes me wonder however is that ad far as I remember the Cloudron app pings the health endpoint of the backend for the health check. So if the backend does not respond, the app should be marked as non responsive in the dashboard.

    S 1 Reply Last reply
    1
  • S Offline
    S Offline
    shrey
    replied to fbartels on last edited by
    #3

    Hi @fbartels

    Restarting the app is not resolving the issue.

    0f482210-d72e-4233-8494-4a554f2b05ae-image.png

    Here's the log file starting from the moment the app is restarted:
    https://www.dropbox.com/s/w1nyoo3mfq2i4ns/vikunja-logs.txt?raw=1

    fbartelsF 1 Reply Last reply
    0
  • fbartelsF Offline
    fbartelsF Offline
    fbartels App Dev
    replied to shrey on last edited by
    #4

    @shrey the relevant error seems to be:

    on_find.go:161 +0x9ff
    Feb 25 18:55:00 xorm.io/xorm.(*Session).Find(0xc000412480?, {0x1233a40?, 0xc0004504b0?}, {0x0?, 0x0?, 0x0?})
    Feb 25 18:55:00 /srv/app/pkg/mod/xorm.io/xorm@v1.3.2/session_find.go:31 +0x7b
    Feb 25 18:55:00 code.vikunja.io/api/pkg/models.getUndoneOverdueTasks(0xc0004ccb60, {0x100000101c056?, 0xc000489640?, 0x22210e0?})
    Feb 25 18:55:00 /source/pkg/models/task_overdue_reminder.go:44 +0x245
    Feb 25 18:55:00 code.vikunja.io/api/pkg/models.RegisterOverdueReminderCron.func1()
    Feb 25 18:55:00 /source/pkg/models/task_overdue_reminder.go:128 +0x9c
    Feb 25 18:55:00 github.com/robfig/cron/v3.FuncJob.Run(0xc0004a07d0?)
    Feb 25 18:55:00 /srv/app/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:136 +0x1a
    Feb 25 18:55:00 github.com/robfig/cron/v3.(*Cron).startJob.func1()
    Feb 25 18:55:00 /srv/app/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:312 +0x6a
    Feb 25 18:55:00 created by github.com/robfig/cron/v3.(*Cron).startJob
    Feb 25 18:55:00 /srv/app/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:310 +0xad
    Feb 25 18:55:00 2023-02-25 13:25:00,030 INFO exited: vikunja-api (exit status 2; not expected)
    

    So the server throws an error during startup (and then gets restarted). I had a short look on the vikunja forum, but could not find a similar report. I recommend to post the above error message along with version information at https://community.vikunja.io/

    S 1 Reply Last reply
    4
  • S Offline
    S Offline
    shrey
    replied to fbartels on last edited by
    #5

    @fbartels Thanks for the triage!

    Will raise a ticket there.

    1 Reply Last reply
    2
  • S Offline
    S Offline
    shrey
    wrote on last edited by
    #6

    Hi @fbartels

    So, i did hear back from them (https://community.vikunja.io/t/vikunja-self-host-cloudron-not-working/1187/4)

    The recommendation is to disable redis, as it's currently buggy, and will be removed in a future release.

    But, i'm unable to do so at my end, because even though i set cache & redis to disabled, in the config.yaml, the config gets reset to true once the app has been restarted.

    fbartelsF 1 Reply Last reply
    0
  • fbartelsF Offline
    fbartelsF Offline
    fbartels App Dev
    replied to shrey on last edited by fbartels
    #7

    @shrey ah yes, the two points in the app that use redis are indeed hardcoded in the startup script. Let me make a pr so that @staff only needs to merge and do their normal release procedure.

    edit: https://git.cloudron.io/cloudron/vikunja-app/-/merge_requests/9

    girishG 1 Reply Last reply
    3
  • girishG Offline
    girishG Offline
    girish Staff
    replied to fbartels on last edited by
    #8

    @fbartels thanks, I will make a new package.

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

    Done. I have published a new package.

    S 1 Reply Last reply
    2
  • S Offline
    S Offline
    shrey
    replied to girish on last edited by
    #10

    @girish Thanks for the quick update!

    The app is finally working again.

    1 Reply Last reply
    1
  • nebulonN nebulon marked this topic as a question on
  • nebulonN nebulon 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.