Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

History is not syncing between all servers #208

Open
yoplait2 opened this issue Apr 24, 2024 · 1 comment
Open

History is not syncing between all servers #208

yoplait2 opened this issue Apr 24, 2024 · 1 comment

Comments

@yoplait2
Copy link

Since the beginning I have installed hishtory logs are not syncing between them :

I think it might be related to this entry log :

info msg="github.com/ddworken/hishtory/client/lib/lib.go:599 database is locked"
time="2024-04-24T17:32:19Z" level=info msg="github.com/ddworken/hishtory/client/hctx/hctx.go:105 database is locked (261)\n[0.018ms] [rows:0] PRAGMA journal_mode = WAL" fromSQL=true
time="2024-04-24T17:32:19Z" level=info msg="github.com/ddworken/hishtory/client/hctx/hctx.go:106 database is locked (261)\n[0.017ms] [rows:0] CREATE INDEX IF NOT EXISTS start_time_index ON history_entries(start_time)" fromSQL=true
time="2024-04-24T17:32:19Z" level=info msg="github.com/ddworken/hishtory/client/hctx/hctx.go:107 database is locked (261)\n[0.023ms] [rows:0] CREATE INDEX IF NOT EXISTS end_time_index ON history_entries(end_time)" fromSQL=true
time="2024-04-24T17:32:19Z" level=info msg="github.com/ddworken/hishtory/client/hctx/hctx.go:108 database is locked (261)\n[0.019ms] [rows:0] CREATE INDEX IF NOT EXISTS entry_id_index ON history_entries(entry_id)" fromSQL=true

I have updated to the latest version and init to the same secret key

The other logs are POST api requests that seems to go through my internet is ok on both server
Server1
hiSHtory: v0.292
Enabled: true
Secret Key: xxxx
Commit Hash: efb9b87

Server2
hiSHtory: v0.292
Enabled: true
Secret Key: xxxx
Commit Hash: efb9b87

@ddworken
Copy link
Owner

Hmm, I don't think it is related to that log message. Can you run try running hishtory status -v on both computers since that has some useful information about sync state. The other thing you can try is running hishtory reupload on both computers which should fix this issue by having each machine re-upload their entire history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants