[opensuse-buildservice] signer problems
Hi, we recently upgraded our installation to buildserver 2.x, and are now experiencing problems with the signing daemon(s). webui reports "signer" as "dead", however signd and signer are up and running. Packages themselves seem to get signed, but the package repositories are no longer signed. Any ideas where to look for the problem? Some more info about our setup: We're running a split setup on 2 machines: Repo-Server/Signer/Scheduler: obs-utils-2.0.4-3.1 obs-signd-2.1.2-1.1 obs-server-2.0.4-3.1 Frontend/API/Webui: obs-common-2.0.1-1.1 obs-api-2.0.4-3.1 Bye, Marcel -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Jul 29, 2010 at 10:39:35AM +0200, Marcel Ritter wrote:
we recently upgraded our installation to buildserver 2.x, and are now experiencing problems with the signing daemon(s).
webui reports "signer" as "dead", however signd and signer are up and running.
You see a "bs_signer" in the preocess list and still the UI reports that the signer is dead? How about curl localhost:5352/build/_workerstatus\?scheduleronly Does it also say "dead" for the signer? Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am 29.07.2010 11:02, schrieb Michael Schroeder:
On Thu, Jul 29, 2010 at 10:39:35AM +0200, Marcel Ritter wrote:
we recently upgraded our installation to buildserver 2.x, and are now experiencing problems with the signing daemon(s).
webui reports "signer" as "dead", however signd and signer are up and running.
You see a "bs_signer" in the preocess list and still the UI reports that the signer is dead? How about
curl localhost:5352/build/_workerstatus\?scheduleronly
Does it also say "dead" for the signer?
No - it reports running. Taking a closer look: I tried to stop lighttpd on the API machine, and there were still several ruby processes running ... killed them ... started lighttpd again : signer goes "green" - somtimes it can be that easy :-) I tried "lighttpd restart" several times before, but I didn't check for left over processes - my fault :-( Thanks for the fast and helpful reply! Now let's build some packages and see if the repos get signed again :-)
Cheers, Michael.
Bye, Marcel -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Marcel Ritter
-
Michael Schroeder