Israel Fruchter
Israel Fruchter
> Please report the bug to systemd so it can be fixed at the origin, in addition to working around it. systemd specificly state that `on-abnormal` includes coredumps https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#Restart= and...
> @fruch Continuing from [scylladb/scylla-enterprise#4246 (comment)](https://github.com/scylladb/scylla-enterprise/issues/4246#issuecomment-2147245586): > > > > > other than that I don't I have any fix for this situation. > > > > > > >...
> how about prioritizing [scylladb/scylladb#18854](https://github.com/scylladb/scylladb/pull/18854) and see if we still hit problems with it? It should improve timings and maybe help us avoid corruptions? I said exactly that in https://github.com/scylladb/scylla-enterprise/issues/4246#issuecomment-2146545425...
put the trial to use hardlink into a PR: https://github.com/scylladb/scylla-cluster-tests/pull/7689
1) I think we should ignore those errors by default 2) we might want to skip this code completely in non-perf test, it's wasting time generating snapshot we never look...
> I done some investigations several months before: #6827 but something is off here, it shouldn't happen, it should pick a random port, i.e. use 0, and then check it....
looking into those, seems like we are aborting on of the repair sessions ``` < t:2024-03-03 03:48:04,350 f:base.py l:228 c:RemoteLibSSH2CmdRunner p:DEBUG > [2024-03-03 03:45:50,906] Starting repair command #1570, repairing 1...
> > I suspect that the new `scylla nodetool` is now being used, and behave a bit differently then the original nodetool command. > > Yes, the repair command was...
If there are not enough logs, one needs to run it with keep and take a look