[opensuse-buildservice] Local BS after build is succeeded, it is scheduled again.
Hello all, Yesterday, I updated my local installation from 0.1.1 to 0.5. I am building the packages in a chroot envroiment. The packages succeeded, but the scheduler wouldn't get it. I got the following error after the build: rpc failed: socket write: Connection reset by peer I saw this message in the screen session from the worker. If I interpreted it correct, then the worker cannot send the package to the server, because there is no rpc socket. kind regards -- Oliver Bengs Key fingerprint = 8F45 91CA 4038 41D3 2FF7 8A65 D3A3 3358 A16E A024 http://jacklab.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello Oliver, On Tue, Jan 08, 2008 at 02:18:24PM +0100, Oliver Bengs wrote:
Yesterday, I updated my local installation from 0.1.1 to 0.5. I am building the packages in a chroot envroiment. The packages succeeded, but the scheduler wouldn't get it. I got the following error after the build: rpc failed: socket write: Connection reset by peer I saw this message in the screen session from the worker. If I interpreted it correct, then the worker cannot send the package to the server, because there is no rpc socket.
kind regards
Interesting, when I submit stuff to the openSUSE buildservice instance, I often see that stuff builds, succeeds, and is scheduled for build again. Maybe we have a similar problem with our buildservice instance. Can you create a bug report? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hello Peter,
Am Fri, 11 Jan 2008 13:18:41 +0100
schrieb "Dr. Peter Poeml"
Hello Oliver,
On Tue, Jan 08, 2008 at 02:18:24PM +0100, Oliver Bengs wrote:
Yesterday, I updated my local installation from 0.1.1 to 0.5. I am building the packages in a chroot envroiment. The packages succeeded, but the scheduler wouldn't get it. I got the following error after the build: rpc failed: socket write: Connection reset by peer I saw this message in the screen session from the worker. If I interpreted it correct, then the worker cannot send the package to the server, because there is no rpc socket.
kind regards
Interesting, when I submit stuff to the openSUSE buildservice instance, I often see that stuff builds, succeeds, and is scheduled for build again.
It gets the status of suceeds in the frontend?
Maybe we have a similar problem with our buildservice instance.
Maybe, but for me no package get published.
Can you create a bug report?
I did https://bugzilla.novell.com/show_bug.cgi?id=353521
Peter
Thank you -- Oliver Bengs Key fingerprint = 8F45 91CA 4038 41D3 2FF7 8A65 D3A3 3358 A16E A024 http://jacklab.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Jan 08, 2008 at 02:18:24PM +0100, Oliver Bengs wrote:
Hello all,
Yesterday, I updated my local installation from 0.1.1 to 0.5. I am building the packages in a chroot envroiment. The packages succeeded, but the scheduler wouldn't get it. I got the following error after the build: rpc failed: socket write: Connection reset by peer I saw this message in the screen session from the worker. If I interpreted it correct, then the worker cannot send the package to the server, because there is no rpc socket.
This is probably caused some some outdated jobs in the job queue.
I.e. try
rm -rf
participants (3)
-
Dr. Peter Poeml -
Michael Schroeder -
Oliver Bengs