[syslog-ng] SYSLOG-NG 3.4 exiting with error code 2

[Gergely Nagy]

"Deepak Gaur" <dgaur at cdotd.ernet.in> writes:

>  Hello,
>
>  I have cross-compiled syslog-ng for ARM target but it is exiting without showing any 
>  error code (on target). I am attaching strace output (syslog.txt). If anyone can help
> me out
>
> clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
> child_tidptr=0x404f9048) = 578 
> close(4)                                = 0 
> read(3, "2\n", 6)                       = 2 
> close(3)                                = 0 
> exit_group(2)                           = ? 
> +++ exited with 2 +++

Here, syslog-ng is forking into the background, and the child appears to
exit. I'd suggest running either strace -f, to see what happens in the
child, or running syslog-ng in the foreground, with -F. That should tell
us more about what happens.

Judging by this strace, the child ends up finishing here:

  if (!main_loop_initialize_state(current_configuration, persist_file))
    {
      return 2;
    }

(main_loop_init, in lib/mainloop.c)

Which suggests it could not initialise the configuration. Run it in the
foreground, with all kinds of verbose knobs turned on:

syslog-ng -Fvde

That should tell you more, I believe. Also, running syslog-ng -s for
checking the syntax of the config file may also be beneficial.

-- 
|8]