Search found 17 matches
- Thu Apr 11, 2024 9:29 pm
- Forum: V8.3.xx Open Beta
- Topic: Unit.runtime = 0 when running a GPU project.
- Replies: 3
- Views: 597
Re: Unit.runtime = 0 when running a GPU project.
So only GPU projects will exhibit this behavoir?
- Tue Apr 09, 2024 6:20 pm
- Forum: V8.3.xx Open Beta
- Topic: Unit.runtime = 0 when running a GPU project.
- Replies: 3
- Views: 597
Unit.runtime = 0 when running a GPU project.
I have observed that the unit.runtime= 0 ( when connected via WebSocket ) when running a GPU Project. This does not occur if I am running a non GPU client.
- Sun Mar 31, 2024 5:09 pm
- Forum: V8.3.xx Open Beta
- Topic: FahCore_a8.exe application crash.
- Replies: 2
- Views: 600
FahCore_a8.exe application crash.
I occasionally get the following exception when running FahCore_a8.exe https://boincspy.ddns.net/images/fah-application-crash.png This only occurs on Windows boxes. I checked the log files for warnings and errors and this what was logged: 01:50:24:W :CON115535:DNS lookup failed for fah1.innovatr.ca:...
- Sat Mar 02, 2024 9:16 pm
- Forum: V8.3.xx Open Beta
- Topic: Mac OS getting HTTP_BAD_REQUST
- Replies: 18
- Views: 1770
- Sat Mar 02, 2024 6:33 pm
- Forum: V8.3.xx Open Beta
- Topic: Mac OS getting HTTP_BAD_REQUST
- Replies: 18
- Views: 1770
Re: Mac OS getting HTTP_BAD_REQUST
Clarification I can change it in FAH client, cant easily change it from OS.
Once it was a valid name, I was able to link the machine name to the account and everything worked.
So it was the .local suffix causing this issue.
Thanks your for your help.
Once it was a valid name, I was able to link the machine name to the account and everything worked.
So it was the .local suffix causing this issue.
Thanks your for your help.
- Sat Mar 02, 2024 6:19 pm
- Forum: V8.3.xx Open Beta
- Topic: Mac OS getting HTTP_BAD_REQUST
- Replies: 18
- Views: 1770
Re: Mac OS getting HTTP_BAD_REQUST
The mac os hostname is wks-mac-mini-007.local and that was assigned by the os and appears I cannot remove the .local suffix.
- Sat Mar 02, 2024 6:44 am
- Forum: V8.3.xx Open Beta
- Topic: Mac OS getting HTTP_BAD_REQUST
- Replies: 18
- Views: 1770
Re: Mac OS getting HTTP_BAD_REQUST
Mac OS - Sonoma 14.3.1
I have tried chrome and MS Edge - same results.
Using safari does not connect to local fah client.
Yes I have python3 installed and comfortable using command line interface.
I have tried chrome and MS Edge - same results.
Using safari does not connect to local fah client.
Yes I have python3 installed and comfortable using command line interface.
- Sat Mar 02, 2024 12:31 am
- Forum: V8.3.xx Open Beta
- Topic: Mac OS getting HTTP_BAD_REQUST
- Replies: 18
- Views: 1770
Re: Mac OS getting HTTP_BAD_REQUST
I tried restarting and logging out and logging back in again with no luck.
I cannot unlink machine from account as the link is greyed out. Its a local machine and not remote. Also the machine text label has a red border around it.
I cannot unlink machine from account as the link is greyed out. Its a local machine and not remote. Also the machine text label has a red border around it.
- Fri Mar 01, 2024 8:31 pm
- Forum: V8.3.xx Open Beta
- Topic: Mac OS fails to resolve api.foldingathome.org:443
- Replies: 23
- Views: 2177
Re: Mac OS fails to resolve api.foldingathome.org:443
Reposting new issue in a new topic.
05:20:11:I1:OUT7:< HTTP/1.1 400 HTTP_BAD_REQUEST
05:20:11:I1:OUT7:< HTTP/1.1 400 HTTP_BAD_REQUEST
- Fri Mar 01, 2024 8:30 pm
- Forum: V8.3.xx Open Beta
- Topic: Mac OS getting HTTP_BAD_REQUST
- Replies: 18
- Views: 1770
Mac OS getting HTTP_BAD_REQUST
05:20:11:I3:Connecting to api.foldingathome.org:443
05:20:11:I1:OUT7:> PUT https://api.foldingathome.org/machine/(largeestring HTTP/1.1
05:20:11:I1:OUT7:< HTTP/1.1 400 HTTP_BAD_REQUEST
05:20:11:E :OUT7:HTTP_BAD_REQUEST:
05:20:11:I1:OUT7:> PUT https://api.foldingathome.org/machine/(largeestring HTTP/1.1
05:20:11:I1:OUT7:< HTTP/1.1 400 HTTP_BAD_REQUEST
05:20:11:E :OUT7:HTTP_BAD_REQUEST:
- Mon Feb 26, 2024 5:23 am
- Forum: V8.3.xx Open Beta
- Topic: Mac OS fails to resolve api.foldingathome.org:443
- Replies: 23
- Views: 2177
Re: Mac OS fails to resolve api.foldingathome.org:443
it now resolves however now getting the following error:
05:20:11:I3:Connecting to api.foldingathome.org:443
05:20:11:I1:OUT7:> PUT https://api.foldingathome.org/machine/( ... argestring HTTP/1.1
05:20:11:I1:OUT7:< HTTP/1.1 400 HTTP_BAD_REQUEST
05:20:11:E :OUT7:HTTP_BAD_REQUEST:
05:20:11:I3:Connecting to api.foldingathome.org:443
05:20:11:I1:OUT7:> PUT https://api.foldingathome.org/machine/( ... argestring HTTP/1.1
05:20:11:I1:OUT7:< HTTP/1.1 400 HTTP_BAD_REQUEST
05:20:11:E :OUT7:HTTP_BAD_REQUEST:
- Sun Feb 25, 2024 6:32 pm
- Forum: V8.3.xx Open Beta
- Topic: Mac OS fails to resolve api.foldingathome.org:443
- Replies: 23
- Views: 2177
Mac OS fails to resolve api.foldingathome.org:443
I have updated to 8.3.5 and on a MAC M2 Sonoma 14.3.1 I am getting the following error in the log file: 8:13:22:W :CON3:DNS lookup failed for api.foldingathome.org:443 18:13:22:E :OUT3:Failed response: CONNECT I can ping to api.foldingathome.org without issues. If I goto into account settings there ...
- Tue Oct 17, 2023 4:45 am
- Forum: V8.1.xx Open Beta
- Topic: FAH 8.18 Not downloading any work for Raspberry Pi
- Replies: 5
- Views: 15362
Re: FAH 8.18 Not downloading any work for Raspberry Pi
Darn I dont have old cores lying around. I have a M1/M2 and it still crunching away.. To bad there isnt a core for the GPU..
- Sat Oct 14, 2023 10:32 pm
- Forum: V8.1.xx Open Beta
- Topic: FAH 8.18 Not downloading any work for Raspberry Pi
- Replies: 5
- Views: 15362
FAH 8.18 Not downloading any work for Raspberry Pi
Installed Fah 8.1.18 on Raspberry pi 4 and getting the following error messages. 22:18:28:I1::WU3:Requesting WU assignment for user BoincSpy team 54196 22:18:28:I1:OUT3:> POST https://assign1.foldingathome.org/api/assign HTTP/1.1 22:18:28:I3:Connecting to assign1.foldingathome.org:443 22:18:29:I1:OU...
- Tue Oct 10, 2023 10:29 pm
- Forum: V8.1.xx Open Beta
- Topic: FAH 8.18 Ubuntu Client not retrieving work.
- Replies: 1
- Views: 11737
Re: FAH 8.18 Ubuntu Client not retrieving work.
Found out the issue. I had to toggle the Fold Anonymously button on and off to down load the workunit, I noticed the Json for the config.fold_anon was initiall set to 1 instead of a false or true. Once I toggled the button it is now its all working now.. So I suspect the exception in the log was cau...