#3048 nuxwdog systemd - memory error when starting subCA
Closed: duplicate 5 years ago Opened 5 years ago by dmoluguw.

When subCA is installed and nuxwdog is enabled for that instance, the server fails to start. It seems some kind of unintended memory free operation is being performed causing the following error:

Aug 13 15:15:12 <hostname> nuxwdog[23862]: *** Error in `/bin/nuxwdog': free(): invalid next size (fast): 0x00000000021c2e70 ***
Aug 13 15:15:12 <hostname> nuxwdog[23862]: ======= Backtrace: =========
Aug 13 15:15:12 <hostname> nuxwdog[23862]: /lib64/libc.so.6(+0x81429)[0x7fd515447429]
Aug 13 15:15:12 <hostname> nuxwdog[23862]: /bin/nuxwdog[0x405698]
Aug 13 15:15:12 <hostname> nuxwdog[23862]: /bin/nuxwdog[0x4044ac]
Aug 13 15:15:12 <hostname> nuxwdog[23862]: /bin/nuxwdog[0x402d9d]
Aug 13 15:15:12 <hostname> nuxwdog[23862]: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fd5153e83d5]
Aug 13 15:15:12 <hostname> nuxwdog[23862]: /bin/nuxwdog[0x40323f]
Aug 13 15:15:12 <hostname> nuxwdog[23862]: ======= Memory map: ========
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 00400000-0040a000 r-xp 00000000 fd:00 3309616                            /usr/bin/nuxwdog
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 00609000-0060a000 r--p 00009000 fd:00 3309616                            /usr/bin/nuxwdog
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 0060a000-0060b000 rw-p 0000a000 fd:00 3309616                            /usr/bin/nuxwdog
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 0060b000-0060c000 rw-p 00000000 00:00 0
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 021bd000-021de000 rw-p 00000000 00:00 0                                  [heap]
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 7fd510000000-7fd510021000 rw-p 00000000 00:00 0
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 7fd510021000-7fd514000000 ---p 00000000 00:00 0
Aug 13 15:15:12 <hostname> nuxwdog[23862]: 7fd514929000-7fd514935000 r-xp 00000000 fd:00 33612770                   /usr/lib64/libnss_files-2.17.so

Further investigating, when nuxwdog is started from commandline by following the guidelines from here: http://www.dogtagpki.org/wiki/Nuxwdog/HOWTO#Running_nuxwdog the server starts successfully.

Root Cause of the Issue: The nuxwdog and systemd communication might be broken which causes this issue


Metadata Update from @dmoluguw:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.12
- Issue status updated to: Open (was: Closed)

5 years ago

Metadata Update from @mharmsen:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

5 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3166

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata