Regular connect-sync crash
jamesloosli opened this issue · 6 comments
Your environment
Operator Version: 1.4.1
Connect Server Version: 1.5.1
Kubernetes Version: 1.22
What happened?
Without warning, the onepassword connect-sync pod will fail to start.
What did you expect to happen?
I'd like the pod to run without crashing?
Steps to reproduce
- Install onepassword-connect on a kubernetes cluster, with a valid token.
- Wait
- ???
Notes & Logs
{"log_message":"(I) disabling bus peer auto-discovery","timestamp":"2022-05-26T22:55:17.751628353Z","level":3}
{"log_message":"(I) connected to bus peer at localhost:11220","timestamp":"2022-05-26T22:55:17.75261625Z","level":3}
{"log_message":"(W) configured to use HTTP with no TLS","timestamp":"2022-05-26T22:55:17.752676703Z","level":2}
{"log_message":"(I) starting 1Password Connect Sync ...","timestamp":"2022-05-26T22:55:17.752867812Z","level":3}
{"log_message":"(I) serving on :8081","timestamp":"2022-05-26T22:55:17.752917666Z","level":3}
{"log_message":"(I) database initialization complete","timestamp":"2022-05-26T22:55:17.753478884Z","level":3}
Error: checking integrity of file : reading file: read /home/opuser/.op/data/files: is a directory
Usage:
connect-sync [flags]
Flags:
-h, --help help for connect-sync
-v, --version version for connect-sync
This has been a serious issue for some time that we have to constantly work around.
Hi there!
Sorry to hear you are running into this frustrating issue. Let me clarify things first so I can help debug; are you able to get connect working at all, ie is it failing at every startup, during some startups, or can you get the sync to run for some time before crashing?
Hi there!
Sorry to hear you are running into this frustrating issue. Let me clarify things first so I can help debug; are you able to get connect working at all, ie is it failing at every startup, during some startups, or can you get the sync to run for some time before crashing?
I know for my part things get running, but over time the sync will fail until the pod is restarted.
Hey @wise0wl,
I have been able to reproduce a problem that looks very similar to what you are describing. We're working on a fix. I'll report back when the fix has been released.
We have released v1.5.4 of Connect which contains a fix for a similar problem. Could you let me know if updating resolves the issue?
I've updated connect-api and connect-sync to 1.5.6 with connect-operator 1.5.0, and that error seems to have been resolved.
Cheers