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 reaching BMC dump max cap, these errors are thrown,
Aug 23 06:58:18 witherspoon systemd[1]: Started Phosphor Dump core monitor..
Aug 23 06:58:19 witherspoon phosphor-dump-manager[1096]: Dump not captured due to a cap.
Aug 23 06:58:19 witherspoon phosphor-dump-monitor[4540]: terminate called after throwing an instance of 'sdbusplus::exception::SdBusError'
Aug 23 06:58:19 witherspoon phosphor-dump-monitor[4540]: what(): sd_bus_call noreply: xyz.openbmc_project.Dump.Create.Error.QuotaExceeded: Dump not captured due to a cap.
Aug 23 06:58:19 witherspoon systemd[1]: Started Process Core Dump (PID 4541/UID 0).
Aug 23 06:58:19 witherspoon systemd[4542]: [email protected]: PrivateNetwork=yes is configured, but the kernel does not support network namespaces, ignoring.
Aug 23 06:58:19 witherspoon systemd-coredump[4528]: Process 1017 (phosphor-dump-m) of user 0 dumped core.
Aug 23 06:58:22 witherspoon systemd[1]: obmc-dump-monitor.service: Main process exited, code=dumped, status=6/ABRT
Aug 23 06:58:22 witherspoon systemd[1]: obmc-dump-monitor.service: Failed with result 'core-dump'.
On reaching BMC dump max cap, these errors are thrown,
Can be seen on latest Master build. @ojayanth
The text was updated successfully, but these errors were encountered: