obsworker connecting to localhost:5352
Hi, since a couple of days we have a problem with our obs workers. We start the service Mär 15 10:39:52 obsworker1 obsworker[2158]: Fetching initial worker code fromhttp://obs.uib.local:5252/getworkercode Mär 15 10:39:52 obsworker1 systemd[1]: Finished OBS worker. Mär 15 10:40:56 obsworker1 systemd[1]: Stopping OBS worker... Mär 15 10:40:56 obsworker1 obsworker[2215]: Shutting down obsworker Mär 15 10:40:56 obsworker1 obsworker[2224]: Name "BSConfig::reposervers" used only once: possible typo at ./bs_worker line 695. Mär 15 10:40:56 obsworker1 obsworker[2226]: Name "BSConfig::reposervers" used only once: possible typo at ./bs_worker line 695. Mär 15 10:40:56 obsworker1 obsworker[2225]: Name "BSConfig::reposervers" used only once: possible typo at ./bs_worker line 695. Mär 15 10:41:14 obsworker1 obsworker[2215]: ..done Mär 15 10:41:14 obsworker1 systemd[1]: obsworker.service: Succeeded. But when I check the screen session I get Name "BSConfig::reposervers" used only once: possible typo at ./bs_worker line 695. worker started on port 33567 code ? build ? Name "BSConfig::reposervers" used only once: possible typo at ./bs_worker line 695. activating new worker code 390facb63336a0fa14d6dd84e2e15883 192.168.109.101 [2400]: rebooting... Name "BSConfig::reposervers" used only once: possible typo at ./bs_worker line 695. worker started on port 37155 code 390facb63336a0fa14d6dd84e2e15883 build d41d8cd98f00b204e9800998ecf8427e fetching new buildcode f434116c0f239d7ec7be232d1928223a, mine was d41d8cd98f00b204e9800998ecf8427e got job, run build... 2022-03-15 11:10:39: building 'zsync-curl' for project 'home:uibmz:opsi:4.2:stable' repository 'RHEL_8' arch 'x86_64' fetching sources, getsources: connect to localhost:5352: Connection refused build failed, marked as bad build host... rpc failed: connect to localhost:5252: Connection refused Here are the obs-server entries in syconfig OBS_SRC_SERVER="192.168.109.101:5352" OBS_REPO_SERVERS="192.168.109.101:5252" Why does it try to connect to localhost? obsworker1:/etc # rpm -qa | grep obs obs-common-2.10.12-lp153.80.2.noarch system-user-obsservicerun-2.10.12-lp153.80.2.noarch system-user-obsrun-2.10.12-lp153.80.2.noarch obs-worker-2.10.12-lp153.80.2.noarch Regards Mathias -- opsi - Open PC-Server-Integration das Open Source Client-Management-System von uib gmbh Mathias Radtke Entwicklung eMail: m.radtke@uib.de Tel. +49 6131 / 27561-0 Fax +49 6131 / 27561-22 uib gmbh Bonifaziusplatz 1B 55118 Mainz Internet: https://uib.de https://opsi.org Geschftsfhrer: Dr. Detlef Oertel, Erol Ülükmen Handelsregister: Amtsgericht Mainz HRB 6942
On Tue, Mar 15, 2022 at 10:15:21AM +0000, Mathias Radtke wrote:
OBS_SRC_SERVER="192.168.109.101:5352"
OBS_REPO_SERVERS="192.168.109.101:5252"
Why does it try to connect to localhost?
The source server to use is part of the job data. So the question is why the scheduler has put localhost into the job data. If your BSConfig.pm looks like the template we have, it looks like: my $hostname = Net::Domain::hostfqdn() || 'localhost'; our $srcserver = "http://$hostname:5352"; Thus it seems like the DNS lookup did not work when the scheduler was started. Simply restarting the schedulers should fix this. Cheers, Michael. -- Michael Schroeder SUSE Software Solutions Germany GmbH mls@suse.de GF: Felix Imendoerffer HRB 36809, AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
On Mär 15 2022, Michael Schroeder wrote:
Thus it seems like the DNS lookup did not work when the scheduler was started. Simply restarting the schedulers should fix this.
The existing (broken) scheduled jobs also need to be removed. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
On Mär 15 2022, Michael Schroeder wrote:
Thus it seems like the DNS lookup did not work when the scheduler was started. Simply restarting the schedulers should fix this.
The existing (broken) scheduled jobs also need to be removed. What is the command to remove these schedules jobs? Regards Mathias
Thus it seems like the DNS lookup did not work when the scheduler was started. Simply restarting the schedulers should fix this.
The existing (broken) scheduled jobs also need to be removed. Which command removes the broken scheduled jobs? Regards Mathias
On Tue, Mar 15, 2022 at 02:25:23PM +0000, Mathias Radtke wrote:
Thus it seems like the DNS lookup did not work when the scheduler was started. Simply restarting the schedulers should fix this.
The existing (broken) scheduled jobs also need to be removed.
Which command removes the broken scheduled jobs?
They are files in the /srv/obs/jobs/<arch> directories, just delete them with 'rm'. Cheers, Michael. -- Michael Schroeder SUSE Software Solutions Germany GmbH mls@suse.de GF: Felix Imendoerffer HRB 36809, AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
participants (3)
-
Andreas Schwab -
Mathias Radtke -
Michael Schroeder