Bug 474712

Summary:	dev-util/buildbot master init script needs to be improved in order to shutdown sqlite properly
Product:	Gentoo Linux	Reporter:	Markos Chandras (RETIRED) <hwoarang>
Component:	New packages	Assignee:	Markos Chandras (RETIRED) <hwoarang>
Status:	RESOLVED NEEDINFO
Severity:	enhancement	CC:	matsl
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://trac.buildbot.net/ticket/2005
Whiteboard:
Package list:		Runtime testing required:	---

Description Markos Chandras (RETIRED) gentoo-dev

2013-06-25 10:47:18 UTC

On a busy buildbot master, the simple stop() function in the init script can leave the sqlite locked and master will fail to start again due to sqlite operational errors. See

http://trac.buildbot.net/ticket/2005

buildbot can't deal with this problem effectively so the init script has to be improved to make sure the sqlite transactions have finished before we shutdown the buildbot master process.

Comment 1 Dirkjan Ochtman (RETIRED) gentoo-dev

2013-06-25 11:46:33 UTC

Do you have a proposed solution in mind?

Comment 2 Markos Chandras (RETIRED) gentoo-dev

2013-06-25 11:47:14 UTC

No not yet. I just opened this bug to track the problem before I forget.

Comment 3 Brian Dolbec (RETIRED) gentoo-dev

2018-03-13 20:52:44 UTC

Is this still relavent with the latest buildbot releases.  At my work we have moved to using a postgresql db backend for our buildbot installs.

Before that, I had not noticed any problems with that in out buildbot-0.9 installs.

If this is found to be still relevant, then please re-open.