Comment 3 for bug 2057576

I think I've found what causes the SIGSEGV, see line 59 in sapi/fpm/fpm/fpm_status.c: It uses scoreboard_p after it checks it for NULL

57 scoreboard_p = fpm_scoreboard_acquire(NULL, 1);
58 if (!scoreboard_p) {
59 zlog(ZLOG_NOTICE, "[pool %s] status: scoreboard already in use.", scoreboard_p->pool); // scoreboard_p is NULL here
60 return -1;
61 }

Hope this helps.