[sr-dev] [kamailio/kamailio] Unexpected log_systemd behavior when daemon is forked (#799)

Anthony Messina notifications at github.com
Fri Nov 22 07:15:23 CET 2019


> If found if kamailio started from command line like `kamailio -DD -E` and present `log_engine_type="systemd"`, then i can see messages from `sd_journal_print` and `xlog` functions.
> 
> When I start kamailio with same config as systemd service then I not see messages from `sd_journal_print` and `xlog` functions.
> 
> When I disable `log_engine_type="systemd"` then i can see output of `sd_journal_print` and `xlog` functions again.
> Think some issue exist here.

That is exactly what I find as well.  I'm re-researching this as well as the new `systemdops.so` module to support `sd_notify()` in 0c48e1621c88bf1d390e4cfb82e52b2d6339b837.  Both of them seem to suffer from the same issue -- the way Kamailio is forking interferes with the core using certain modules, as they relate to sending messages to systemd.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/799#issuecomment-557405557
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20191121/a83b3413/attachment.html>


More information about the sr-dev mailing list