stability between device #649
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#649
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Using the latest vikunja arm version when i'm connected on Vikunja using my IPhone navigator and trying to use Vikunja conected on my mac navigator at the same time i get at the first attempt (list clicking for exemple) an error 500. It does the same both ways. Here is an extact of the api logs showing the case:
As showed the first error is made by the Macintosh navigator whes i was successfully using the Iphone just before and the second error is made when using the Iphone just after the Macintoch browser was stable.
Sometimes being conected else where could create the same error while tryng to conect but it return a wrong username/password message instead of the error code 500 whitch could be missleading and make people retype their credential vene when they are good
This line
seems to indicate there's an issue with your database. What database are you using, can you verify it works correctly and is accessible from the server running vikunja?
I use the arm image of biarms/mysql:5.7.30-beta-travis. Since my database is located on a mounted nfs server with a ssd cache, network latency might cause this if i'm the only one having this trouble. Did you reproduce this issue in your usual configuration ?
I entered into the vikunja api container and called it without any trouble when i tried it yesterday.
I could not reproduce it, but my setup is a bit different. The only way I have seen this issue so far is when using this in a docker environment and the mysql container is starting and not yet ready to accept connections, but that is different from the case you're seeing.
Okey,seems like nfs + mysql is not the best combo... :
https://dev.mysql.com/doc/refman/5.6/en/disk-issues.html#disk-issues-nfs
You can close this issue, i will rethink my setup.