You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: