Page 2 of 8
Re: server 192.0.2.1 status
Posted: Sat Aug 01, 2020 9:28 pm
by Joe_H
192.0.2.1 is not a routable address, it is in one of the reserved IP ranges for documentation. It was added to the server code to redirect WU requests when they could not be filled due to a few reasons. One of them is unsupported hardware, another is no possiblw WUs available for a configuration, and the last one I know is an unsupported OS in the case of GPU WU requests from OS X clients.
Possibly an updated client could take those redirects and use them to issue a message as to the reason. But that would be something in the future.
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 1:43 am
by foldingfanmucde
An update on my previous activities / posts:
Unfortunately, I have been unable to restore the functionality regardless of how often, or in which order, I reinstall the Nvidia drivers (to get the apparently missing OpenCL drivers) and/or reinstall F@H. And also regardless of the value used for opencl-index. To me it seems to be a fundamental issue, because the error message is very early on when starting F@H. I've run out of ideas for now. And it doesn't look like it is going to disappear on its own, in the same way as it arose out of the blue. Any inspiration on what to further follow up on would be appreciated. It's quite dissapointing, because my workhorse system is now just standing there and unusable for folding. Most puzzling is that this came up amidst normal folding activity over night.
bruce wrote:
We have added some entries to GPUs.txt for Intel iGPUs. (They are currently not supported except for a little back-room testing.) I hdon't remember any comments from Linux folks, but the addition of the entries has caused some problems in Windows where the index values changed.
@bruce: Do you have a hint for what I would need to look for regarding the GPUs.txt you mentioned?
Many thanks!
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 2:47 am
by Endgame124
Same issue here on fedora 30. System was running fine until 3am central time 8/1 per EoC stats. System is dual GPU, 1080ti and 1660 Super, with no recent changes for at least a month. It may be several days until I can money with the host again, so here is hoping it’s something on the F@H side of things.
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 3:03 am
by JimboPalmer
Has any checked the date on their GPUs.txt file to see if it changed near then?
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 5:21 am
by bruce
On the previous page, I extracted some information from FAH's log (posted a bit earlier by foldingfanmucde) and noticed that OpenCL was not functional. EVERYBODY who still has the problem needs to post that segment of their log.
There are a number of different things that might have gone wrong but the rest of you are simply not giving us enough information to help you. (See below) It's not a change to GPUs.txt.
Re: server 192.0.2.1 status
Posted: Sun Aug 02, 2020 6:58 am
by bruce
goodyca wrote:Is the subject server currently on-line and working?
No. There is no such FAH server.
The on-line Assignment Server code is being enhanced to take advantage of some planned enhancements. This entire sequence essentially means i CAN'T PROVIDE YOU WITH A WU FOR YOUR CONFIGURATION. STOP AND FIX WHATEVER THE PROBLEM IS. but
it doesn't give a clue what's wrong.
It's a replacement for the old message we used to get:
Failed to get assignment from ['assign...]: No WUs available for this configuration
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 12:16 pm
by DocJonz
JimboPalmer wrote:Has any checked the date on their GPUs.txt file to see if it changed near then?
My copies of GPUs.txt seem to have updated on Wednesday - that is several days before this incident.
You can clearly see the evolution of the issue in the first post, second code box.
There were absolutely no changes to the system during this time (no automatic updates, and everyone tucked up in bed ...).
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 12:30 pm
by foldingfanmucde
JimboPalmer wrote:Has any checked the date on their GPUs.txt file to see if it changed near then?
@JimboPalmer:
Well unfortunately due to all the re-installations that I did yesterday, including F@H, the date of the current GPUs.txt file on the affected system has no relevance. Sorry. Maybe someone else could check that on a completely untouched system?
[Probably not relevant here, but on another system (which is not affected) the file has a last change date 25th July 2020 09:06 UTC.]
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 1:17 pm
by TurboAsterix
Hello,
I have exactly the same problem relative to
"Failed to connect to 192.0.2.1:80: Network is unreachable".
The client is running Linux Mint 19.3 with a Nvidia GT 1030 with Nvidia 440.100 and runs exclusively only Folding at Home and folded since months without issues.
Summary
First occurrence of the issue was on 1st August 14:35:11 CET. No changes were applied to the client before.
Code: Select all
******************************* Date: 2020-08-01 *******************************
14:35:07:WU01:FS01:Connecting to assign1.foldingathome.org:80
14:35:08:WU01:FS01:Assigned to work server 192.0.2.1
14:35:08:WU01:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:GP108 [GeForce GT 1030] from 192.0.2.1
14:35:08:WU01:FS01:Connecting to 192.0.2.1:8080
[93m14:35:11:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80[0m
14:35:11:WU01:FS01:Connecting to 192.0.2.1:80
[91m14:35:11:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Network is unreachable[0m
I see the issue, too, with libOpenCL.so. Checking old log files, this seems to be present since ever.
But now something suddenly changes that it matters.
Code: Select all
*********************** Log Started 2020-08-01T19:31:43Z ***********************
19:31:45: GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:5 GP108 [GeForce GT 1030]
19:31:45:CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:10.2
19:31:45: OpenCL: Not detected: Failed to open dynamic library 'libOpenCL.so':
19:31:45: libOpenCL.so: cannot open shared object file: No such file or
19:31:45: directory
I did as suggest by ZePompom in this thread, and installing package ocl-icd-opencl-dev and FAHClient restart fixed the issue.
Code: Select all
sudo apt update
sudo apt install ocl-icd-opencl-dev
Code: Select all
System: Host: LINUX-NODE1 Kernel: 5.3.0-61-generic x86_64 bits: 64 compiler: gcc v: 7.5.0
Desktop: Xfce 4.14.1 tk: Gtk 3.22.30 wm: xfwm4 dm: LightDM
Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic
Machine: Type: Desktop Mobo: Acer model: Aspire XC-214 serial: <filter>
UEFI: American Megatrends v: P11-B3 date: 11/06/2015
CPU: Topology: Quad Core model: AMD A4-5000 APU with Radeon HD Graphics bits: 64 type: MCP
arch: Jaguar rev: 1 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 11978
Speed: 1497 MHz min/max: N/A Core speeds (MHz): 1: 1497 2: 1497 3: 1497 4: 1497
Graphics: Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ZOTAC driver: nvidia v: 440.100
bus ID: 01:00.0 chip ID: 10de:1d01
Display: x11 server: X.Org 1.20.8 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 1280x800~60Hz
OpenGL: renderer: GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes
Audio: Device-1: AMD FCH Azalia vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Device-2: NVIDIA GP108 High Definition Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:0fb8
Sound Server: ALSA v: k5.3.0-61-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel port: d000 bus ID: 02:00.0
chip ID: 10ec:8168
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 931.51 GiB used: 23.01 GiB (2.5%)
ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-21M2NA0 size: 931.51 GiB
speed: 6.0 Gb/s serial: <filter>
Partition: ID-1: / size: 914.46 GiB used: 23.00 GiB (2.5%) fs: ext4 dev: /dev/dm-0
ID-2: swap-1 size: 976.0 MiB used: 524 KiB (0.1%) fs: swap dev: /dev/dm-1
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002
Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002
Device-1: 2-3:2 info: Realtek Mass Storage Device type: Mass Storage
driver: ums-realtek rev: 2.0 chip ID: 0bda:0153
Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 1.1 chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 1.1 chip ID: 1d6b:0001
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 chip ID: 1d6b:0003
Sensors: System Temperatures: cpu: 66.0 C mobo: N/A gpu: nvidia temp: 81 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 59%
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //mirrors.evowise.com/linuxmint/packages tricia main upstream import backport
2: deb http: //de.archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
3: deb http: //de.archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
4: deb http: //de.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ bionic partner
Info: Processes: 196 Uptime: 16h 42m Memory: 3.79 GiB used: 2.07 GiB (54.6%) Init: systemd
v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Client: Unknown python3.6 client
inxi: 3.0.32
Here are the links to the complete log files:
Link to log file 1
Link to log file 2
Best regards,
TurboAsterix
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 2:24 pm
by ajm
I have had that same problem today on a Win 10 folding rig with a 1080ti and a 5700XT. I had shut down that machine for a few days as it was too hot here. When I started it up again, this afternoon, everything was working well. Then I decided to update the display drivers as there were new versions available from Nvidia and AMD. After that, FAH knew only to try to reach that 192... server and OpenCL was not found. I tried a lot of obvious things, uninstall and reinstall FAH (with and without data) and both the new drivers (after dduing them). No luck.
To finally make it work, I had to ddu the
AMD drivers (win10-radeon-software-adrenalin-2020-edition-20.7.2-july14) and
install the former version (win10-radeon-software-adrenalin-2020-edition-20.5.1-june10).
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 2:27 pm
by TurboAsterix
Hello,
but the problem occurs independently of the drivers and platform as I had exactly the same issue on Linux with Nvidia.
The behavior relative to OpenCL just suddenly changed, I bet there is a related backend change and what we see here now is a side effect ...
Best regards,
TurboAsterix
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 2:32 pm
by ajm
On Linux, OpenCL is always something of a problem. You must install the OpenCL dev package, for example, and chose carefully where you get the Nvidia drivers.
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 2:34 pm
by TurboAsterix
Which doesn't explain why we see this issue suddenly across multiple machines and platforms.
The prior setup here and other posters on this thread WAS perfectly working and FAILS for all since a certain point in time.
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 2:43 pm
by banjackal
ajm wrote:On Linux, OpenCL is always something of a problem. You must install the OpenCL dev package, for example, and chose carefully where you get the Nvidia drivers.
+1 about choosing wisely on the nvidia drivers, just in general. I've found myself playing "why doesn't this work" whack-a-mole with bad driver installations
Also chiming in to remind the people who don't read that 192.0.2.1 is NOT a WU server! I just installed the opencl dev package after my Pop! machine decided it didn't want to fold anymore after no updates (auto updates are for windows blegh)
Reading the pertinent posts on this thread, followed by installing the ocl dev package and restarting my client was ALL I needed to do!
Re: Waiting for work on 192.0.2.1 ?
Posted: Sun Aug 02, 2020 2:50 pm
by bruce
I can guess who might be to blame for this problem but I'm not in the business of finding who to blame; I'm in the support business, and if we can fix your computer(s) we can move on.
Where is the information about FAH's hardware detection process? It looks like this:
(I don't see it in the log segments you posted)
Code: Select all
00:29:37:******************************* System ********************************
...
00:29:37: OS Arch: AMD64
00:29:37: GPUs: 1
00:29:37: GPU 0: Bus:4 Slot:0 Func:0 NVIDIA:5 GM206 [GeForce GTX 960]
00:29:37: CUDA Device 0: Platform:0 Device:0 Bus:4 Slot:0 Compute:5.2 Driver:10.2
00:29:37:OpenCL Device 0: Platform:0 Device:0 Bus:4 Slot:0 Compute:1.2 Driver:442.19
00:29:37:******************************...