MMonit segmentation fault

[Hussain Mohammed]

Dears,

Kindly note that we have observed an issue of segmentation fault of our PROD MMonit which caused MMonit to restart. There is no change performed on the MMonit server. Kindly advise whether it is a bug and/or about the root cause of this issue.

Regards.

[Tildeslash]

Please can you provide more details? Do you have coredump?

Is it Monit or M/Monit? The version field is set to 5.33.0 (which is Monit), but the text describes M/Monit. If it is M/Monit - which version it is?

[Hussain Mohammed]

Dears,

It is M/Monit version 3.7.14. The core dump seems does not exist.

           PID: 1781908 (mmonit)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Mon 2023-09-11 13:46:58 +03 (6 days ago)
  Command Line: /app/mmonit/mmonit-3.7.14/bin/mmonit -i
    Executable: /app/mmonit/mmonit-3.7.14/bin/mmonit
 Control Group: /
         Slice: -.slice
       Storage: /var/lib/systemd/coredump/core.mmonit.0.e09f699b84684986a30f63a5e34f6823.1781908.1694429218000000.lz4 (inaccessible)
       Message: Process 1781908 (mmonit) of user 0 dumped core.

                Stack trace of thread 3436319:
                #0  0x00007f2e1ccc5b20 n/a (n/a)

‌

[Tildeslash]

Thank you dor data.

If the /var/lib/systemd/coredump/core.mmonit.0.e09f699b84684986a30f63a5e34f6823.1781908.1694429218000000.lz4 exists, please send it to [e-mail] along with error.log and mmonit.log from M/Monit’s “logs” directory.

If the coredump doesn’t exist, please send at least the error.log and mmonit.log.

‌