Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminate called after throwing an instance of 'sdbusplus::exception::SdBusError' #3

Open
gkeishin opened this issue Aug 23, 2018 · 0 comments

Comments

@gkeishin
Copy link
Member

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'.

Can be seen on latest Master build. @ojayanth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant