- **status**: assigned --> accepted
---
** [tickets:#2700] log: coredump when stop cluster**
**Status:** accepted
**Milestone:** 5.18.01
**Created:** Wed Nov 22, 2017 08:43 AM UTC by Canh Truong
**Last Updated:** Wed Nov 22, 2017 09:10 AM UTC
**Owner:** Canh Truong
**Attachments:**
- [bt.log](https://sourceforge.net/p/opensaf/tickets/2700/attachment/bt.log)
(5.9 kB; application/octet-stream)
-
[osaflogd1](https://sourceforge.net/p/opensaf/tickets/2700/attachment/osaflogd1)
(542.3 kB; application/octet-stream)
-
[osaflogd2](https://sourceforge.net/p/opensaf/tickets/2700/attachment/osaflogd2)
(967.0 kB; application/octet-stream)
- [syslog1](https://sourceforge.net/p/opensaf/tickets/2700/attachment/syslog1)
(31.2 kB; application/octet-stream)
- [syslog2](https://sourceforge.net/p/opensaf/tickets/2700/attachment/syslog2)
(90.2 kB; application/octet-stream)
Steps:
1/ Enable trace for log service on both SC node
2/ Start cluster
3/ Stop cluser
The coredump is generated during stop cluster
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets