this can happen in older installations, where Vern...
# umh-support
j
this can happen in older installations, where VerneMQ takes too long to load the buffered data after restart, so that Kubernetes thinks the startup failed.