Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
unfortunately that didn't help either, the same error:
Nov 28 18:26:35 k1-dev k1-dev[27366]: INFO: nats [nats_mod.c:439]: nats_init_connection(): adding server [nats://127.0.0.1:4222] [1]
Nov 28 18:26:35 k1-dev k1-dev[27366]: ERROR: nats [nats_mod.c:458]: nats_init_connection(): could not create nats options [System Error]
Nov 28 18:26:35 k1-dev k1-dev[27366]: ERROR: nats [nats_mod.c:232]: init_worker(): failed to init nat connections
Nov 28 18:26:35 k1-dev k1-dev[27366]: ERROR: nats [nats_mod.c:348]: mod_child_init(): failed to init struct for worker [0]
Nov 28 18:26:35 k1-dev k1-dev[27366]: ERROR: <core> [core/sr_module.c:903]: init_mod_child(): error while initializing module nats (/usr/local/lib64/kamailio/modules/nats.so) (idx: 0 rank: -127 desc: [main])
Nov 28 18:26:35 k1-dev k1-dev[27366]: ERROR: <core> [main.c:1665]: main_loop(): error in init_child(PROC_INT) -- exiting
Nov 28 18:26:35 k1-dev kamailio: ERROR: <core> [core/daemonize.c:303]: daemonize(): Main process exited before writing to pipe
in the kernel logs I do see also some error related to the libuv, not sure that this can cause nats module to panic
Nov 28 18:26:35 k1-dev kernel: kamailio[27366]: segfault at 70 ip 00007f42e55f0888 sp 00007ffcce36f970 error 4 in libuv.so.1.0.0[7f42e55e0000+2c000]
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.