That behavior looks like what I'd expect if restic is run with the --quiet flag. Does setting TERM=dumb or RESTIC_PROGRESS_FPS=1 show some output? A stacktrace while the backup is running might also be useful. Please start a backup, then send a SIGQUIT to restic (e.g. via Ctrl+/). This will cause restic to print a stacktrace and exit immediately. This will leave a stale lock file behind which you can remove using restic unlock.