domenkozar
commented
11 years ago That's a known issue, it's probably due to the way forking happens for bconsole communication. This is a serious problem and should have the highest priority for the fix.
Open cedottotecnica opened 11 years ago
domenkozar
commented
11 years ago That's a known issue, it's probably due to the way forking happens for bconsole communication. This is a serious problem and should have the highest priority for the fix.
domenkozar
commented
11 years ago It's also relevant to #41
domenkozar
commented
11 years ago @cedottotecnica can you send logs to domen@dev.si?
cedottotecnica
commented
11 years ago Il 24/03/2013 19:59, Domen Kožar ha scritto:
@cedottotecnica https://github.com/cedottotecnica can you send logs to domen@dev.si mailto:domen@dev.si?
— Reply to this email directly or view it on GitHub https://github.com/iElectric/almir/issues/46#issuecomment-15366027.
I'll send them in a minute.
Marcello Romani Ottotecnica s.r.l. Responsabile IT http://www.ottotecnica.it
domenkozar
commented
11 years ago So, steps to reproduce:
What's going on: seems like subprocess fork for bconsole blocks almir to start
Temporary solution:
Almir process stops working. The web browser tells me it can't connect to server... supervisorctl shows almir process is in FATAL state:
serverlinux:/var/www/almir# python bin/supervisorctl HttpOk RUNNING pid 6073, uptime 27 days, 18:31:10 Memmon RUNNING pid 6074, uptime 27 days, 18:31:10 almir FATAL Exited too quickly (process log may have details)
A restart all solves the problem: supervisor> restart all HttpOk: stopped Memmon: stopped HttpOk: started Memmon: started almir: started
(Too bad github issues doesn't have attachments...)
http://89.119.66.34/almir-log.tgz