On May 17, 2018 3:58:43 PM GMT+02:00, Mattia Milani <mattia.mil...@studenti.unitn.it> wrote: >> They may also have crashed (which would be bad). Try running the >Birds in >> debug mode (don't remember the flag, see bird --help) and collecting >their >> exit value. >> > >I used the command bird -c *confFile* -s *socketFile* -D *debugFile* >in the conf file I inserted: > >debug protocols all; >debug commands 2; > >but i didn't see anything in the debug file i setted, (i need to >recompile >bird with some option?)
Yes, it is needed to reconfigure BIRD with --enable-debug. But it is probably an overkill. Maybe my previous hint was misleading. Try running BIRD in no-fork mode and collect its exit value. It will tell you how it stopped. You can also enable coredumps to see whether there is some corpse left after unexpected death of BIRD. Maria
