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

Checkpointing does not work if .local dir is symlinked #27

Open
drirmbda opened this issue May 22, 2024 · 1 comment
Open

Checkpointing does not work if .local dir is symlinked #27

drirmbda opened this issue May 22, 2024 · 1 comment

Comments

@drirmbda
Copy link

drirmbda commented May 22, 2024

On Rocky Linux 9, starting nodes with safenode command (PunchBowl of May 9 2024), and using vdash 0.17.6:

I have two servers with a symbolic link to move ~/.local to a different drive, for example using the command ln -s /media/WD5T1/safe ~/.local

I noticed that only on those two systems using symbolic links, when I start new nodes as usual, and use vdash as usual, vdash is not creating safenode.vdash checkpointing files. When I re-start vdash, no checkpoints are read either. On systems without symlinks all works as expected.

(In both cases had about 40 nodes running. These are running behind NAT with port forwarding.)

An additional observation: In case of a symlinked .local directory, after pressing ‘r’ (which does not seem to work) and waiting, and then pressing ‘space’, most nodes appear INACTIVE except a few that are/were Shunned.

And I just realized that the overview display is not updating; at startup, vdash processes the logs but does not process any new log records after that. Pressing space bar results in all but a few Shunned nodes as INACTIVE.

@drirmbda
Copy link
Author

Workaround: vdash $(realpath ~/.local/share/safe/node/*/logs/safenode.log)

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

1 participant