Page 2 of 3
Re: Current Start-Up Issues
Posted: Fri Mar 20, 2020 1:38 pm
by aka_daryl
im experiancing exactly the same issue on 2 machines, one a Windows desktop and the other a Linux VM
Re: Current Start-Up Issues
Posted: Fri Mar 20, 2020 5:02 pm
by Joe_H
Both look like the download of the core to process the WU's they were able to get assigned was either disconnected from heavy network traffic or blocked. Without the core which does the actual calculations, the client can't start up the WU and that is why the usage is at 0%.
Basically the download is a package that is opened by the FAHClient process and installs the executable core in the right location. There are other reports of the core downloads failing, so I don't know if it is a problem with the server or network, or something blocking the executable being installed on your PC. For the second, if you have some anti-malware software running, you could try suspending it temporarily or exclude the directory where F@h is installed from scans. Someone is supposed to be looking into the issue on the server and network side.
Re: Current Start-Up Issues
Posted: Fri Mar 20, 2020 7:19 pm
by aka_daryl
Hi Joe, I have already ruled out network and AV issues my end as I have 2 identical devices with the same image on them and only one of them is having the issue, we are getting ready to push a domain-wide deployment but dont want to hit the go button until we determine the issue with the core download.
Re: Current Start-Up Issues
Posted: Fri Mar 20, 2020 11:36 pm
by Skatman
Hi Joe,
Sorry for the late response.
I've added exclusion rules to my AV tools and still no joy. Does it need a port adding manually to the Windows firewall? I doubt it as I can already see the traffic leaving my network via the firewall logs.
Any ideas?
Best,
Re: Current Start-Up Issues
Posted: Sat Mar 21, 2020 12:24 am
by Joe_H
Not familiar with that firewall, so it depends. Some firewalls have blocks for any HTTP or HTTPS traffic not from a known browser such as Chrome, IE, Firefox and so on. For those you may have to explicitly allow HTTP and HTTPS over ports 8080 and 80 for the FAHClient process so it is treated like a browser.
About the only other thing is some firewalls also block HTTP and HTTPS connections to "raw" IP addresses like what the client uses for WU downloads and uploads, but that would not apply to the core download which uses an URL. At some point you also received the WUs, so that also is a another thing against this being the issue.
But to be honest, it is looking more like a problem on the server side or the network between there and your systems.
Re: Current Start-Up Issues
Posted: Sat Mar 21, 2020 4:16 pm
by Skatman
I've looked at everything on my network firewall and there's nothing I can see blocking it. Can you let me know all IP addresses and ports that are used for communication and I'll put in explicit allow rules just in case.
My core firewall is an NGFW and it was blocking the initial traffic as it was detecting it as a manual proxy attempt, but I've changed the rules to allow that.
How do I contact the FatH server team? Or is that you that will do that, Joe?
Best,
Re: Current Start-Up Issues
Posted: Sat Mar 21, 2020 6:43 pm
by Joe_H
The server IP addresses I know of are listed on the Server Status page -
https://apps.foldingathome.org/serverstats. The one for "assign2" is a bit more work as the IP address shown there is a redirect or something, the actual IP shows up in your log when the client connect to it. Assign2 is hosted on an AWS server, IP 18.something.
As far as the server side, I put in a message about the core download issue, hopefully now that some of the big fires have been put out they get to this problem.
Re: Current Start-Up Issues
Posted: Sat Mar 21, 2020 7:36 pm
by Skatman
Great,
Thanks Joe. Keep me updated on the progress and if you would like me to try anything.
Best,
Re: Current Start-Up Issues
Posted: Mon Mar 23, 2020 1:26 pm
by Skatman
Hi, latest logs and I received a new one. HTTP Bad Gateway...
Code: Select all
13:19:42:FS01:Converted slot from GPU to 01: PAUSED cpu:4 (by user)
13:19:42:Removing old file 'configs/config-20200316-192209.xml'
13:19:42:Saving configuration to config.xml
13:19:42:<config>
13:19:42: <!-- Folding Core -->
13:19:42: <core-priority v='low'/>
13:19:42:
13:19:42: <!-- Network -->
13:19:42: <proxy v=':8080'/>
13:19:42:
13:19:42: <!-- Slot Control -->
13:19:42: <power v='full'/>
13:19:42:
13:19:42: <!-- User Information -->
13:19:42: <team v='237039'/>
13:19:42: <user v='Skatman'/>
13:19:42:
13:19:42: <!-- Folding Slots -->
13:19:42: <slot id='0' type='CPU'>
13:19:42: <paused v='true'/>
13:19:42: </slot>
13:19:42: <slot id='1' type='CPU'>
13:19:42: <paused v='true'/>
13:19:42: </slot>
13:19:42:</config>
13:19:42:WARNING:WU01:FS01:No longer matches Slot 1's configuration and there are no other matching slots, dumping
13:19:42:WU01:FS01:Sending unit results: id:01 state:SEND error:DUMPED project:11757 run:0 clone:2942 gen:0 core:0x22 unit:0x000000009bf7a4d55e6d77085a350c83
13:19:42:WU01:FS01:Connecting to 155.247.164.213:8080
13:19:43:WU01:FS01:Server responded WORK_ACK (400)
13:19:43:WU01:FS01:Cleaning up
13:19:46:FS00:Unpaused
13:19:46:FS01:Unpaused
13:19:52:WU01:FS01:Connecting to 65.254.110.245:8080
13:19:53:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
13:19:53:WU01:FS01:Connecting to 18.218.241.186:80
13:19:54:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
13:19:55:ERROR:WU01:FS01:Exception: Could not get an assignment
13:19:55:WU01:FS01:Connecting to 65.254.110.245:8080
13:19:55:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
13:19:55:WU01:FS01:Connecting to 18.218.241.186:80
13:19:56:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
13:19:56:ERROR:WU01:FS01:Exception: Could not get an assignment
13:20:32:Removing old file 'configs/config-20200316-192310.xml'
13:20:32:Saving configuration to config.xml
13:20:32:<config>
13:20:32: <!-- Folding Core -->
13:20:32: <core-priority v='low'/>
13:20:32:
13:20:32: <!-- Network -->
13:20:32: <proxy v=':8080'/>
13:20:32:
13:20:32: <!-- Slot Control -->
13:20:32: <power v='full'/>
13:20:32:
13:20:32: <!-- User Information -->
13:20:32: <team v='237039'/>
13:20:32: <user v='Skatman'/>
13:20:32:
13:20:32: <!-- Folding Slots -->
13:20:32: <slot id='0' type='CPU'/>
13:20:32: <slot id='1' type='CPU'/>
13:20:32:</config>
13:20:50:FS00:Paused
13:20:50:FS01:Paused
13:21:13:FS00:Unpaused
13:21:13:FS01:Unpaused
13:21:13:WU01:FS01:Connecting to 65.254.110.245:8080
13:21:14:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
13:21:14:WU01:FS01:Connecting to 18.218.241.186:80
13:21:14:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
13:21:14:ERROR:WU01:FS01:Exception: Could not get an assignment
13:22:51:WU01:FS01:Connecting to 65.254.110.245:8080
13:22:51:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
13:22:51:WU01:FS01:Connecting to 18.218.241.186:80
13:22:51:WU01:FS01:Assigned to work server 40.114.52.201
13:22:51:WU01:FS01:Requesting new work unit for slot 01: READY cpu:4 from 40.114.52.201
13:22:51:WU01:FS01:Connecting to 40.114.52.201:8080
13:23:12:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
13:23:12:WU01:FS01:Connecting to 40.114.52.201:80
13:23:27:ERROR:WU01:FS01:Exception: 10001: Server responded: HTTP_BAD_GATEWAY
13:25:28:WU01:FS01:Connecting to 65.254.110.245:8080
13:25:28:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
13:25:28:WU01:FS01:Connecting to 18.218.241.186:80
13:25:29:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
13:25:29:ERROR:WU01:FS01:Exception: Could not get an assignment
Re: Current Start-Up Issues
Posted: Mon Mar 23, 2020 1:45 pm
by Skatman
Also got this message: HTTP_SERVICE_UNAVAILABLE
Are you guys being DDoS'd?
Code: Select all
13:36:34:WU01:FS01:Assigned to work server 155.247.166.219
13:36:34:WU01:FS01:Requesting new work unit for slot 01: READY cpu:4 from 155.247.166.219
13:36:34:WU01:FS01:Connecting to 155.247.166.219:8080
13:36:35:ERROR:WU01:FS01:Exception: 10001: Server responded: HTTP_SERVICE_UNAVAILABLE
Re: Current Start-Up Issues
Posted: Mon Mar 23, 2020 1:57 pm
by aka_daryl
they are but not in a bad way, there are just so many new users
Re: Current Start-Up Issues
Posted: Mon Mar 23, 2020 2:17 pm
by Skatman
That's what I thought.
Guys, let me know if you want any help server-side. More than happy to help where I can.
Re: Current Start-Up Issues
Posted: Mon Mar 23, 2020 2:20 pm
by aka_daryl
ditto here, we are on project halt at the moment so more than willing to help out where we can
Re: Current Start-Up Issues
Posted: Thu Mar 26, 2020 9:36 am
by Skatman
Any updates?
Re: Current Start-Up Issues
Posted: Tue Apr 07, 2020 9:50 am
by Skatman
So my gaming laptop CPU is now churning and burning, which is cool. However, it has a dGPU (970M) which is still not being utilised. I also have another server that isn't linking up. Are you still being DDoS'd with requests?
As before, let me know if you need any help. Happy to where I can.