18.218.241.186: NOT listed on Server Stats [Known as assign2

Moderators: Site Moderators, FAHC Science Team

Locked
Manfred.Knick
Posts: 36
Joined: Wed Mar 25, 2020 10:21 am
Hardware configuration: Multiple XEON + GTX
Location: Germany

18.218.241.186: NOT listed on Server Stats [Known as assign2

Post by Manfred.Knick »

{ iterated }
13:49:21:WU00:FS01:Connecting to 65.254.110.245:8080
13:49:22:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
13:49:22:WU00:FS01:Connecting to 18.218.241.186:80 <----- <----- <----- <----- <----- <----- <----- <----- <----- <----- <----- <----- <-----
13:49:22:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
13:49:22:ERROR:WU00:FS01:Exception: Could not get an assignment
{ iterated }

$ whois 18.218.241.186 :

- - CIDR: 18.128.0.0/9
- - Organization: Amazon Technologies Inc. (AT-88-Z)

$ grep "18.218.241.186" /opt/foldingathome/log.txt

07:43:15:WU00:FS00:Connecting to 18.218.241.186:80
07:43:55:WU01:FS01:Connecting to 18.218.241.186:80
07:45:49:WU01:FS01:Connecting to 18.218.241.186:80
09:42:30:WU02:FS00:Connecting to 18.218.241.186:80
09:42:31:WARNING:WU02:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
09:42:32:WU02:FS00:Connecting to 18.218.241.186:80
09:42:32:WARNING:WU02:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:47:57:WU00:FS01:Connecting to 18.218.241.186:80
11:47:57:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:47:58:WU00:FS01:Connecting to 18.218.241.186:80
11:47:58:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:48:58:WU00:FS01:Connecting to 18.218.241.186:80
11:48:58:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:50:35:WU00:FS01:Connecting to 18.218.241.186:80
11:50:36:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:53:12:WU00:FS01:Connecting to 18.218.241.186:80
11:53:13:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:57:27:WU00:FS01:Connecting to 18.218.241.186:80
11:57:27:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:04:18:WU00:FS01:Connecting to 18.218.241.186:80
12:04:19:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:15:24:WU00:FS01:Connecting to 18.218.241.186:80
12:15:24:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:33:20:WU00:FS01:Connecting to 18.218.241.186:80
12:33:21:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:40:41:WU01:FS00:Connecting to 18.218.241.186:80
12:40:42:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:40:43:WU01:FS00:Connecting to 18.218.241.186:80
12:40:43:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:41:43:WU01:FS00:Connecting to 18.218.241.186:80
12:41:43:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
12:43:20:WU01:FS00:Connecting to 18.218.241.186:80
13:02:23:WU00:FS01:Connecting to 18.218.241.186:80
13:02:23:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
13:49:22:WU00:FS01:Connecting to 18.218.241.186:80
13:49:22:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
15:05:22:WU00:FS01:Connecting to 18.218.241.186:80
15:07:33:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': Failed to connect to 18.218.241.186:80: Connection timed out <-----
Last edited by Manfred.Knick on Sat Apr 11, 2020 6:27 pm, edited 1 time in total.
Knish
Posts: 222
Joined: Tue Mar 17, 2020 5:20 am

Re: 18.218.241.186: unknown: not enlisted on Server Stats

Post by Knish »

it's assign2.foldingathome if u enter it in the url it takes u to the page that displays "Assignment Server"
it's just that somebody forgot to update that on the serverstats webpage to replace the IP that starts with 172 with this new one
Manfred.Knick
Posts: 36
Joined: Wed Mar 25, 2020 10:21 am
Hardware configuration: Multiple XEON + GTX
Location: Germany

Re: 18.218.241.186: unknown: not enlisted on Server Stats

Post by Manfred.Knick »

Knish wrote: it's just that somebody forgot
... "Just" ... "Only" ... ???

Have you ever been concerned about security ?

This project is responsible for the resources
as well as even more for the security of its clients
who donate their trust!

Who are you?! I don't know you -
and I doubt you being authorized to change my title without asking !!!

More and more, I am less than 1/4 of an inch away
from recommending all my clients and friends
to retract from this project behaving like a "children play-ground" !

This is not living up to sound and valid OpenSource !
Joe_H
Site Admin
Posts: 7937
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: 18.218.241.186: NOT listed on Server Stats [Known as ass

Post by Joe_H »

This question has been asked, and answered multiple times. There is a glitch in how the Server Status page displays the IP number for assign2, it shows the local net address in one of the private IP ranges. The actual IP points to the AWS server it is on.

Locking this topic
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Locked