Packages scheduled

classic Classic list List threaded Threaded
40 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Packages scheduled

Mathias Radtke
Hi

I ecountered a problem on our local OBS instance.
I made an upload to the remote instance.

The local instance is linked to our official projects.
It seems the local instace has downloaded the remote changes.

But now all packages are just scheduled on the local instance.

All current build workers are idling.

What can I do to start the build process?
Which logs should I check?

The dispatcher says  for example
badhost event: ....

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Packages scheduled

Stefan Botter-2
On Fri, 16 Jun 2017 11:18:08 +0200
Mathias Radtke <[hidden email]> wrote:

> Hi
>
> I ecountered a problem on our local OBS instance.
> I made an upload to the remote instance.
>
> The local instance is linked to our official projects.
> It seems the local instace has downloaded the remote changes.
>
> But now all packages are just scheduled on the local instance.
>
> All current build workers are idling.
>
> What can I do to start the build process?
> Which logs should I check?
>
> The dispatcher says  for example
> badhost event: ....
I had exactly the same situation on my own build server and on
Packman's PMBS - which share some of the workers.

I updated my own build server to the latest 2.7 package several days
ago, and noticed, that some workers then were unable to build their
assigned packages. I did not dig in deep, but it seemed to me, as if
all build failures were logged for PMBS build request, which had not
been on the latest 2.7.

Yesterday I updated PMBS to the latest obs 2.7.4-1.19, and since then
the badhost events have reduced to some workers exclusive to PMBS.

I suggest you try updating your server and have a look at any
improvements...

Greetings,

Stefan
--
Stefan Botter zu Hause
Bremen

attachment0 (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Packages scheduled

Mathias Radtke

On 16.06.2017 11:37, Stefan Botter wrote:

> On Fri, 16 Jun 2017 11:18:08 +0200
> Mathias Radtke <[hidden email]> wrote:
>
>> Hi
>>
>> I ecountered a problem on our local OBS instance.
>> I made an upload to the remote instance.
>>
>> The local instance is linked to our official projects.
>> It seems the local instace has downloaded the remote changes.
>>
>> But now all packages are just scheduled on the local instance.
>>
>> All current build workers are idling.
>>
>> What can I do to start the build process?
>> Which logs should I check?
>>
>> The dispatcher says  for example
>> badhost event: ....
> I updated my own build server to the latest 2.7 package several days
> ago, and noticed, that some workers then were unable to build their
> assigned packages. I did not dig in deep, but it seemed to me, as if
> all build failures were logged for PMBS build request, which had not
> been on the latest 2.7.
My obs server contains my workers.
The only external workers are the ARM ones.

Currently the OBS server hat the following obs packages installed

rpm -qa | grep obs
obs-server-2.8.1-2.1.noarch
obs-service-download_url-0.1-6.1.noarch
obs-service-recompress-0.3.1+git20160217.7897d3f-8.1.noarch
obs-service-obs_scm-common-0.7.0.1492101301.747de50-6.3.1.noarch
obs-service-set_version-0.5.6-5.3.1.noarch
obs-service-obs_scm-0.7.0.1492101301.747de50-6.3.1.noarch
obs-service-extract_file-0.3-6.1.noarch
obs-productconverter-2.8.1-2.1.noarch
obs-utils-2.8.1-2.1.noarch
obs-worker-2.8.1-2.1.noarch
obs-service-verify_file-0.1.1-21.1.noarch
obs-service-download_src_package-0.2-3.1.noarch
obs-common-2.8.1-2.1.noarch
obs-service-snapcraft-0.7.0.1492101301.747de50-6.3.1.noarch
obs-service-format_spec_file-20170204-2.3.1.noarch
obs-api-2.8.1-2.1.noarch
obs-service-tar_scm-0.7.0.1492101301.747de50-6.3.1.noarch
obs-service-source_validator-0.6+git20170111.82ea590-13.3.1.noarch
obs-service-tar-0.7.0.1492101301.747de50-6.3.1.noarch
obs-signd-2.3.0-2.1.x86_64
obs-source_service-2.8.1-2.1.noarch
obs-service-download_files-0.5.1.git.1455712026.9c0a4a0-7.1.noarch

After the last update it did even build some packages.
As for today it doesn't

--
Mathias Radtke


---
http://uib.de/de/support-schulung/schulung/

---
uib gmbh
Bonifaziusplatz 1B
55118 Mainz

Tel. 06131 / 27561-16 <phone:061312756116>
Fax  06131 / 27561-22 <phone:061312756122>

E-Mail: [hidden email]
Internet: www.uib.de

Geschäftsführer: dr. detlef oertel & erol ueluekmen
Handelsregister: Amtsgericht Mainz HRB 6942

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Packages scheduled

Mathias Radtke


On 16.06.2017 11:48, Mathias Radtke wrote:

>
> On 16.06.2017 11:37, Stefan Botter wrote:
>> On Fri, 16 Jun 2017 11:18:08 +0200
>> Mathias Radtke <[hidden email]> wrote:
>>
>>> Hi
>>>
>>> I ecountered a problem on our local OBS instance.
>>> I made an upload to the remote instance.
>>>
>>> The local instance is linked to our official projects.
>>> It seems the local instace has downloaded the remote changes.
>>>
>>> But now all packages are just scheduled on the local instance.
>>>
>>> All current build workers are idling.
>>>
>>> What can I do to start the build process?
>>> Which logs should I check?
>>>
>>> The dispatcher says  for example
>>> badhost event: ....
>> I updated my own build server to the latest 2.7 package several days
>> ago, and noticed, that some workers then were unable to build their
>> assigned packages. I did not dig in deep, but it seemed to me, as if
>> all build failures were logged for PMBS build request, which had not
>> been on the latest 2.7.
> My obs server contains my workers.
> The only external workers are the ARM ones.
>
> Currently the OBS server hat the following obs packages installed
>
> rpm -qa | grep obs
> obs-server-2.8.1-2.1.noarch
> obs-service-download_url-0.1-6.1.noarch
> obs-service-recompress-0.3.1+git20160217.7897d3f-8.1.noarch
> obs-service-obs_scm-common-0.7.0.1492101301.747de50-6.3.1.noarch
> obs-service-set_version-0.5.6-5.3.1.noarch
> obs-service-obs_scm-0.7.0.1492101301.747de50-6.3.1.noarch
> obs-service-extract_file-0.3-6.1.noarch
> obs-productconverter-2.8.1-2.1.noarch
> obs-utils-2.8.1-2.1.noarch
> obs-worker-2.8.1-2.1.noarch
> obs-service-verify_file-0.1.1-21.1.noarch
> obs-service-download_src_package-0.2-3.1.noarch
> obs-common-2.8.1-2.1.noarch
> obs-service-snapcraft-0.7.0.1492101301.747de50-6.3.1.noarch
> obs-service-format_spec_file-20170204-2.3.1.noarch
> obs-api-2.8.1-2.1.noarch
> obs-service-tar_scm-0.7.0.1492101301.747de50-6.3.1.noarch
> obs-service-source_validator-0.6+git20170111.82ea590-13.3.1.noarch
> obs-service-tar-0.7.0.1492101301.747de50-6.3.1.noarch
> obs-signd-2.3.0-2.1.x86_64
> obs-source_service-2.8.1-2.1.noarch
> obs-service-download_files-0.5.1.git.1455712026.9c0a4a0-7.1.noarch
>
> After the last update it did even build some packages.
> As for today it doesn't
>
Additional Information

The ARM builds on the external worker are running fine.
Only the internal worker are affected

--
Mathias Radtke


---
http://uib.de/de/support-schulung/schulung/

---
uib gmbh
Bonifaziusplatz 1B
55118 Mainz

Tel. 06131 / 27561-16 <phone:061312756116>
Fax  06131 / 27561-22 <phone:061312756122>

E-Mail: [hidden email]
Internet: www.uib.de

Geschäftsführer: dr. detlef oertel & erol ueluekmen
Handelsregister: Amtsgericht Mainz HRB 6942

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Stefan Botter-2
On Fri, 16 Jun 2017 12:30:52 +0200
Mathias Radtke <[hidden email]> wrote:

> On 16.06.2017 11:48, Mathias Radtke wrote:
> >
> > On 16.06.2017 11:37, Stefan Botter wrote:  
> >> On Fri, 16 Jun 2017 11:18:08 +0200
> >> Mathias Radtke <[hidden email]> wrote:
> > My obs server contains my workers.
> > The only external workers are the ARM ones.
> >
> > Currently the OBS server hat the following obs packages installed
> >
> > rpm -qa | grep obs
> > obs-server-2.8.1-2.1.noarch
:
> > After the last update it did even build some packages.
> > As for today it doesn't
> >  
> Additional Information
>
> The ARM builds on the external worker are running fine.
> Only the internal worker are affected

I have an update on my situation:
Builds for Tumbleweed are building fine, whereas builds for - at
least - openSUSE 12.3, openSUSE 13.1, openSUSE 13.2 are not building.

Setup of the kvm machine seems to be not working correctly:

======
Ä   12sÜ ### WATCHDOG MARKER START ###
Ä   12sÜ booting kvm...
Ä   12sÜ linux64 /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic
-vga none -object rng-random,filename=/dev/random,id=rng0 -device
virtio-rng-pci,rng=rng0 -runas qemu -cpu host -mem-prealloc -mem-path /dev/hugetlbfs -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append root=/dev/disk/by-id/virtio-0 rootfstype=ext3 rootflags=data=writeback,nobarrier,commit=150,noatime panic=1 quiet no-kvmclock nmi_watchdog=0 rw rd.driver.pre=binfmt_misc elevator=noop console=ttyS0 init=/.build/build -m 1994 -drive file=/var/cache/obs/worker/root_2/root,format=raw,if=none,id=disk,serial=0,cache=unsafe -device virtio-blk-pci,drive=disk -drive file=/var/cache/obs/worker/root_2/swap,format=raw,if=none,id=swap,serial=1,cache=unsafe -device virtio-blk-pci,drive=swap -serial stdio -smp 2
Ä   23sÜ ÄFAILEDÜ Failed to start Setup Virtual Console.
Ä   23sÜ See 'systemctl status systemd-vconsole-setup.service' for
details.
Ä   23sÜ Ä  OK  Ü Started dracut cmdline hook.
Ä   23sÜ          Starting dracut pre-udev hook...
Ä   24sÜ Ä  OK  Ü Started dracut pre-udev hook.
Ä   24sÜ          Starting udev Kernel Device Manager...
Ä   24sÜ Ä  OK  Ü Started udev Kernel Device Manager.
Ä   24sÜ          Starting dracut pre-trigger hook...
Ä   24sÜ Ä  OK  Ü Started dracut pre-trigger hook.
Ä   24sÜ          Starting udev Coldplug all Devices...
Ä   24sÜ Ä  OK  Ü Started udev Coldplug all Devices.
Ä   24sÜ          Starting Show Plymouth Boot Screen...
Ä   24sÜ          Starting dracut initqueue hook...
Ä   24sÜ Ä  OK  Ü Reached target System Initialization.
Ä   24sÜ Ä  OK  Ü Started Show Plymouth Boot Screen.
Ä   24sÜ Ä  OK  Ü Started Forward Password Requests to Plymouth
Directory Watch.
Ä   24sÜ Ä  OK  Ü Reached target Paths.
Ä   24sÜ Ä  OK  Ü Reached target Basic System.
Ä   25sÜ Ä  OK  Ü Found device /dev/disk/by-id/virtio-0.
======

There it stops, until after approx. 120s
dracut-initqueue timeout - starting timeout scripts
start and the build aborts.


There seems to be an incompatible change in the last published worker
code, which prohibits correct setup of the vm setup in the worker
instance for older build targets.

I do not know where to report this other than here, perhaps in github,
but my track record of reporting things there is rather poor.


Greetings,

Stefan
--
Stefan Botter zu Hause
Bremen

attachment0 (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Stefan Botter-2
On Fri, 16 Jun 2017 14:59:15 +0200
Stefan Botter <[hidden email]> wrote:
> There seems to be an incompatible change in the last published worker
> code, which prohibits correct setup of the vm setup in the worker
> instance for older build targets.

As there has been no change in worker code for the past weeks (at least
for obs-server 2.7.4), not the worker code is at fault, but most
probably the initrd generation with the past plymouth update from
approx Jun 12th, as this is the only other change since Jun 9th,  when
kernel 4.4.70 was rolled out.
I went back to 4.4.62 (which was running with my workers built fine),
but not still no build is happening for older targets like oS 13.1 and
older.

> I do not know where to report this other than here, perhaps in github,
> but my track record of reporting things there is rather poor.

Greetings,

Stefan
--
Stefan Botter zu Hause
Bremen

attachment0 (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Mathias Radtke


On 18.06.2017 09:44, Stefan Botter wrote:

> On Fri, 16 Jun 2017 14:59:15 +0200
> Stefan Botter <[hidden email]> wrote:
>> There seems to be an incompatible change in the last published worker
>> code, which prohibits correct setup of the vm setup in the worker
>> instance for older build targets.
> As there has been no change in worker code for the past weeks (at least
> for obs-server 2.7.4), not the worker code is at fault, but most
> probably the initrd generation with the past plymouth update from
> approx Jun 12th, as this is the only other change since Jun 9th,  when
> kernel 4.4.70 was rolled out.
> I went back to 4.4.62 (which was running with my workers built fine),
> but not still no build is happening for older targets like oS 13.1 and
> older.
I did this too today.
One packages did build, the other ones staying on scheduled don't.
I don't get why.
Oh an here's some strange line in /var/log/mesages

Shutting down obsworkerName "Build::Kiwi::urlmapper" used only once:
possible typo at ./bs_worker line 2574.
>> I do not know where to report this other than here, perhaps in github,
>> but my track record of reporting things there is rather poor.
> Greetings,
>
> Stefan

--
Mathias Radtke


---
http://uib.de/de/support-schulung/schulung/

---
uib gmbh
Bonifaziusplatz 1B
55118 Mainz

Tel. 06131 / 27561-16 <phone:061312756116>
Fax  06131 / 27561-22 <phone:061312756122>

E-Mail: [hidden email]
Internet: www.uib.de

Geschäftsführer: dr. detlef oertel & erol ueluekmen
Handelsregister: Amtsgericht Mainz HRB 6942

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Frank Schreiner-2
> Shutting down obsworkerName "Build::Kiwi::urlmapper" used only once:
> possible typo at ./bs_worker line 2574.

This is only a perl warning and has IMO nothing to do with your problem.

You could login on the one of the badhost workers. A screen session should be
running there (because of an bug, there might be multiple screen session, find
the active one, "ps faux" might be helpful). Attach to the screen -
"screen -x ..." for more debugging info (use <CRTL>-a-n to switch between
workers and <CTRL>-a-d to detach from screen again).

the complete "badhost event:" from the dispatcher log might be useful too.

cheers
M0ses

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Mathias Radtke


On 19.06.2017 08:46, Frank Schreiner wrote:

>> Shutting down obsworkerName "Build::Kiwi::urlmapper" used only once:
>> possible typo at ./bs_worker line 2574.
> This is only a perl warning and has IMO nothing to do with your problem.
>
> You could login on the one of the badhost workers. A screen session should be
> running there (because of an bug, there might be multiple screen session, find
> the active one, "ps faux" might be helpful). Attach to the screen -
> "screen -x ..." for more debugging info (use <CRTL>-a-n to switch between
> workers and <CTRL>-a-d to detach from screen again).
>
> the complete "badhost event:" from the dispatcher log might be useful too.
>
> cheers
> M0ses
M0ses
Thank you for the hint. Now I get a better error message
2017-06-19 06:06:24: building 'opsi-linux-bootimage' for project
'home:uibmz:opsi:opsi40-experimental' repository 'RedHat_RHEL-6' arch
'x86_64'
fetching sources, source verification fails:
713990b4462e712af44a658004e11f72 != f58ce6478db93749199604c958a7c9b8
build failed, marked as bad build host...
sent, all done...

Where are those hashsums comming from?

Cheers

--
Mathias Radtke


---
http://uib.de/de/support-schulung/schulung/

---
uib gmbh
Bonifaziusplatz 1B
55118 Mainz

Tel. 06131 / 27561-16 <phone:061312756116>
Fax  06131 / 27561-22 <phone:061312756122>

E-Mail: [hidden email]
Internet: www.uib.de

Geschäftsführer: dr. detlef oertel & erol ueluekmen
Handelsregister: Amtsgericht Mainz HRB 6942

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Adrian Schröter
On Montag, 19. Juni 2017, 08:50:13 CEST wrote Mathias Radtke:

>
> On 19.06.2017 08:46, Frank Schreiner wrote:
> >> Shutting down obsworkerName "Build::Kiwi::urlmapper" used only once:
> >> possible typo at ./bs_worker line 2574.
> > This is only a perl warning and has IMO nothing to do with your problem.
> >
> > You could login on the one of the badhost workers. A screen session should be
> > running there (because of an bug, there might be multiple screen session, find
> > the active one, "ps faux" might be helpful). Attach to the screen -
> > "screen -x ..." for more debugging info (use <CRTL>-a-n to switch between
> > workers and <CTRL>-a-d to detach from screen again).
> >
> > the complete "badhost event:" from the dispatcher log might be useful too.
> >
> > cheers
> > M0ses
> M0ses
> Thank you for the hint. Now I get a better error message
> 2017-06-19 06:06:24: building 'opsi-linux-bootimage' for project
> 'home:uibmz:opsi:opsi40-experimental' repository 'RedHat_RHEL-6' arch
> 'x86_64'
> fetching sources, source verification fails:
> 713990b4462e712af44a658004e11f72 != f58ce6478db93749199604c958a7c9b8
> build failed, marked as bad build host...
> sent, all done...
>
> Where are those hashsums comming from?

They are calculated from the worker sources, basically a sum over the
content of /usr/lib/obs/server/worker/ (on the server side).

What are you running(how did you deploy)?

--

Adrian Schroeter
email: [hidden email]

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
 
Maxfeldstraße 5                        
90409 Nürnberg
Germany


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Frank Schreiner-2
In reply to this post by Mathias Radtke
> M0ses

> Thank you for the hint. Now I get a better error message
> 2017-06-19 06:06:24: building 'opsi-linux-bootimage' for project
> 'home:uibmz:opsi:opsi40-experimental' repository 'RedHat_RHEL-6' arch
> 'x86_64'
> fetching sources, source verification fails:
> 713990b4462e712af44a658004e11f72 != f58ce6478db93749199604c958a7c9b8
> build failed, marked as bad build host...
> sent, all done...
>
> Where are those hashsums comming from?
The first one is generated on the worker for the received sources.
The second one is sent from the dispatcher to the worker as part
of the buildinfo (verifymd5).

You could check the verifymd5:

curl "http://<SOURCESERVER>:5352/getprojpack?withsrcmd5&project=<PROJECTNAME>&package=<PACKAGENAME>"

This is how the scheduler gets the current source information.

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: Packages scheduled

Andreas Schwab-2
In reply to this post by Frank Schreiner-2
On Jun 19 2017, Frank Schreiner <[hidden email]> wrote:

> (because of an bug, there might be multiple screen session, find
> the active one, "ps faux" might be helpful).

screen -ls

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Stefan Botter-2
In reply to this post by Stefan Botter-2
On Sun, 18 Jun 2017 09:44:14 +0200
Stefan Botter <[hidden email]> wrote:

> On Fri, 16 Jun 2017 14:59:15 +0200
> Stefan Botter <[hidden email]> wrote:
> > There seems to be an incompatible change in the last published
> > worker code, which prohibits correct setup of the vm setup in the
> > worker instance for older build targets.  
>
> As there has been no change in worker code for the past weeks (at
> least for obs-server 2.7.4), not the worker code is at fault, but most
> probably the initrd generation with the past plymouth update from
> approx Jun 12th, as this is the only other change since Jun 9th,  when
> kernel 4.4.70 was rolled out.
> I went back to 4.4.62 (which was running with my workers built fine),
> but not still no build is happening for older targets like oS 13.1 and
> older.
I have another addition: it is entirely possible, that the kvm workers
do not set up correctly for quite a while, not just since a few days.
I stopped my chroot-workers last week due to the build errors with
openSUSE_Tumbleweed (where the rpmlint packages now probably needs
access to some hardware RNGs, which are not availabe in chroot), and
ran into the problem of the failing kvm workers with older targets.

chroot-workers build oS 13.1 and older fine.

All my kvm-workers are running openSUSE_Leap_42.2.


Greetings,

Stefan
--
Stefan Botter zu Hause
Bremen

attachment0 (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Mathias Radtke
In reply to this post by Frank Schreiner-2


On 19.06.2017 09:23, Frank Schreiner wrote:

>> M0ses
>> Thank you for the hint. Now I get a better error message
>> 2017-06-19 06:06:24: building 'opsi-linux-bootimage' for project
>> 'home:uibmz:opsi:opsi40-experimental' repository 'RedHat_RHEL-6' arch
>> 'x86_64'
>> fetching sources, source verification fails:
>> 713990b4462e712af44a658004e11f72 != f58ce6478db93749199604c958a7c9b8
>> build failed, marked as bad build host...
>> sent, all done...
>>
>> Where are those hashsums comming from?
> The first one is generated on the worker for the received sources.
> The second one is sent from the dispatcher to the worker as part
> of the buildinfo (verifymd5).
>
> You could check the verifymd5:
>
> curl "http://<SOURCESERVER>:5352/getprojpack?withsrcmd5&project=<PROJECTNAME>&package=<PACKAGENAME>"
>
> This is how the scheduler gets the current source information.
Well this gives me a completely different md5sum
  curl
"http://localhost:5352/getprojpack?withsrcmd5&project=home:uibmz:opsi:opsi40-experimental&package=opsi-linux-bootimage"
<projpack repoid="944824085">
   <project name="home:uibmz:opsi:opsi40-experimental">
     <title>remote experimental repo</title>
     <description></description>
     <package name="opsi-linux-bootimage" rev="6"
srcmd5="bbe298527bf9e593ec2dc6233228c5cf" revtime="1497853486" />
   </project>
</projpack>

Any reason why this happens on exactly this package?

--
Mathias Radtke


---
http://uib.de/de/support-schulung/schulung/

---
uib gmbh
Bonifaziusplatz 1B
55118 Mainz

Tel. 06131 / 27561-16 <phone:061312756116>
Fax  06131 / 27561-22 <phone:061312756122>

E-Mail: [hidden email]
Internet: www.uib.de

Geschäftsführer: dr. detlef oertel & erol ueluekmen
Handelsregister: Amtsgericht Mainz HRB 6942

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Frank Schreiner-2
In reply to this post by Stefan Botter-2
> I have another addition: it is entirely possible, that the kvm workers
> do not set up correctly for quite a while, not just since a few days.
> I stopped my chroot-workers last week due to the build errors with
> openSUSE_Tumbleweed (where the rpmlint packages now probably needs
> access to some hardware RNGs, which are not availabe in chroot), and
> ran into the problem of the failing kvm workers with older targets.

Please check if haveged is installed

rpm -q haveged

and make sure that rng-tools are not installed

rpm -e rng-tools

on the worker host of course.

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Mathias Radtke


On 19.06.2017 09:57, Frank Schreiner wrote:

>> I have another addition: it is entirely possible, that the kvm workers
>> do not set up correctly for quite a while, not just since a few days.
>> I stopped my chroot-workers last week due to the build errors with
>> openSUSE_Tumbleweed (where the rpmlint packages now probably needs
>> access to some hardware RNGs, which are not availabe in chroot), and
>> ran into the problem of the failing kvm workers with older targets.
> Please check if haveged is installed
>
> rpm -q haveged
>
> and make sure that rng-tools are not installed
>
> rpm -e rng-tools
>
> on the worker host of course.
obs:/srv/obs/log # rpm -q haveged
haveged-1.9.1-12.2.x86_64
obs:/srv/obs/log # rpm -e rng-tools
obs:/srv/obs/log # rpm -e rng-tools
error: package rng-tools is not installed

Seems it was installed.
Do I need to restart any services?

--
Mathias Radtke


---
http://uib.de/de/support-schulung/schulung/

---
uib gmbh
Bonifaziusplatz 1B
55118 Mainz

Tel. 06131 / 27561-16 <phone:061312756116>
Fax  06131 / 27561-22 <phone:061312756122>

E-Mail: [hidden email]
Internet: www.uib.de

Geschäftsführer: dr. detlef oertel & erol ueluekmen
Handelsregister: Amtsgericht Mainz HRB 6942

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Frank Schreiner-2
On Montag, 19. Juni 2017 10:03:42 CEST Mathias Radtke wrote:

> On 19.06.2017 09:57, Frank Schreiner wrote:
> >> I have another addition: it is entirely possible, that the kvm workers
> >> do not set up correctly for quite a while, not just since a few days.
> >> I stopped my chroot-workers last week due to the build errors with
> >> openSUSE_Tumbleweed (where the rpmlint packages now probably needs
> >> access to some hardware RNGs, which are not availabe in chroot), and
> >> ran into the problem of the failing kvm workers with older targets.
> >
> > Please check if haveged is installed
> >
> > rpm -q haveged
> >
> > and make sure that rng-tools are not installed
> >
> > rpm -e rng-tools
> >
> > on the worker host of course.
>
> obs:/srv/obs/log # rpm -q haveged
> haveged-1.9.1-12.2.x86_64
> obs:/srv/obs/log # rpm -e rng-tools
> obs:/srv/obs/log # rpm -e rng-tools
> error: package rng-tools is not installed
>
> Seems it was installed.
> Do I need to restart any services?
Hmm, maybe haveged, to be sure - but you could also try "journalctl" before if
haveged already has been started by systemd.

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: Packages scheduled

Andreas Schwab-2
In reply to this post by Stefan Botter-2
On Jun 16 2017, Stefan Botter <[hidden email]> wrote:

> Setup of the kvm machine seems to be not working correctly:
>
> ======
> Ä   12sÜ ### WATCHDOG MARKER START ###
> Ä   12sÜ booting kvm...
> Ä   12sÜ linux64 /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic
> -vga none -object rng-random,filename=/dev/random,id=rng0 -device
> virtio-rng-pci,rng=rng0 -runas qemu -cpu host -mem-prealloc -mem-path /dev/hugetlbfs -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append root=/dev/disk/by-id/virtio-0 rootfstype=ext3 rootflags=data=writeback,nobarrier,commit=150,noatime panic=1 quiet no-kvmclock nmi_watchdog=0 rw rd.driver.pre=binfmt_misc elevator=noop console=ttyS0 init=/.build/build -m 1994 -drive file=/var/cache/obs/worker/root_2/root,format=raw,if=none,id=disk,serial=0,cache=unsafe -device virtio-blk-pci,drive=disk -drive file=/var/cache/obs/worker/root_2/swap,format=raw,if=none,id=swap,serial=1,cache=unsafe -device virtio-blk-pci,drive=swap -serial stdio -smp 2

What do you get if you remove `quiet' from the kernel command line?

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Frank Schreiner-2
In reply to this post by Mathias Radtke
> Well this gives me a completely different md5sum

>   curl
> "http://localhost:5352/getprojpack?withsrcmd5&project=home:uibmz:opsi:opsi40
> -experimental&package=opsi-linux-bootimage" <projpack repoid="944824085">
>    <project name="home:uibmz:opsi:opsi40-experimental">
>      <title>remote experimental repo</title>
>      <description></description>
>      <package name="opsi-linux-bootimage" rev="6"
> srcmd5="bbe298527bf9e593ec2dc6233228c5cf" revtime="1497853486" />
>    </project>
> </projpack>
>
> Any reason why this happens on exactly this package?
hmm, whats in /srv/obs/events/<arch>  ?


signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled

Mathias Radtke

On 19.06.2017 10:12, Frank Schreiner wrote:

>> Well this gives me a completely different md5sum
>>    curl
>> "http://localhost:5352/getprojpack?withsrcmd5&project=home:uibmz:opsi:opsi40
>> -experimental&package=opsi-linux-bootimage" <projpack repoid="944824085">
>>     <project name="home:uibmz:opsi:opsi40-experimental">
>>       <title>remote experimental repo</title>
>>       <description></description>
>>       <package name="opsi-linux-bootimage" rev="6"
>> srcmd5="bbe298527bf9e593ec2dc6233228c5cf" revtime="1497853486" />
>>     </project>
>> </projpack>
>>
>> Any reason why this happens on exactly this package?
> hmm, whats in /srv/obs/events/<arch>  ?
>
obs:/srv/obs/events/x86_64 # ls
.ping
obs:/srv/obs/events/x86_64 # file .ping
.ping: fifo (named pipe)
obs:/srv/obs/events/x86_64 # cd ..
obs:/srv/obs/events # cd i586/
obs:/srv/obs/events/i586 # ls
.ping
obs:/srv/obs/events/i586 # file .ping
.ping: fifo (named pipe)
obs:/srv/obs/events/i586 #

--
Mathias Radtke


---
http://uib.de/de/support-schulung/schulung/

---
uib gmbh
Bonifaziusplatz 1B
55118 Mainz

Tel. 06131 / 27561-16 <phone:061312756116>
Fax  06131 / 27561-22 <phone:061312756122>

E-Mail: [hidden email]
Internet: www.uib.de

Geschäftsführer: dr. detlef oertel & erol ueluekmen
Handelsregister: Amtsgericht Mainz HRB 6942

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

12
Loading...