On 11/21/14 14:11, Philippe Makowski wrote: > Le 20/11/14 14:54, Alex Peshkoff a écrit : >> I.e. we need to know why does server not start. >> > It started all new results are in http://ci.ibphoenix.com/ > > results.log is firebird.log > and results.syslog is /var/log/syslog or journalctl --no-pager result > > Classic : > http://ci.ibphoenix.com/job/Firebird_trunk_on_Mageia_64/262/ > > Superserver : > http://ci.ibphoenix.com/job/Firebird30_Ubuntu_Linux/417/ > > in both cases we have > > fbt_run: segfault at 0 ip
That's very useful. Now I can say for sure - that's not firebird server that caused problems. The only place where we read that /opt/firebird/bin/firebird terminated is when changing mode from super to classic, and here superserver process must be terminated, i.e. this message is OK. Actual reason is in: fbt_run[20774]: segfault at 0 ip (null) sp 00007fff0b52ba48 error 14 in python2.7[400000+1000] I.e. python related and therefore we can guess that the reason are changes in python part. Actual segfault happens inside kernel, in open() system call - sooner of all due to bad data, passed to it. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
