Search found 10 matches
- Mon May 25, 2020 1:31 am
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: Can't bind socket port in use
- Replies: 9
- Views: 2260
Re: Can't bind socket port in use
In my case...I somehow managed to have a process called FAHclient (caps for FAH) running and could not be killed with the mac's Activity Monitor. This process was not working with web control or the advanced control and was using the default ports of 36330 and 7396. After killing the bad process wit...
- Sun May 24, 2020 7:35 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: Can't bind socket port in use
- Replies: 9
- Views: 2260
Re: Can't bind socket port in use
I was running fahclient from the command line. You are correct. I finally was able to kill the FAHClient process that kept restarting itself. I used this command: sudo launchctl unload /Library/LaunchDaemons/org.foldingathome.fahclient.plist It killed the extra process and now fahclient works with t...
- Sun May 24, 2020 7:14 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: Can't bind socket port in use
- Replies: 9
- Views: 2260
Re: Can't bind socket port in use
I use Activity Monitor....Task Manager I believe is Windows. FAHClient runs as an activity and restarts itself even if I force quit it.
- Sun May 24, 2020 6:51 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: Can't bind socket port in use
- Replies: 9
- Views: 2260
Re: Can't bind socket port in use
I have turned off my mac firewall and router firewall...no luck with the socket binding issue. No anti-malware running. Ran the normal install from the pkg file.
Even un-installed the client and reinstalled. Still won't bind the sockets...saying the default ports of 36330 and 7396 are in use.
Even un-installed the client and reinstalled. Still won't bind the sockets...saying the default ports of 36330 and 7396 are in use.
- Sun May 24, 2020 6:03 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: Can't bind socket port in use
- Replies: 9
- Views: 2260
Can't bind socket port in use
I am running a Macbook Pro with High Sierra. When I run FAHclient....it can't bind the socket saying the port is in use In this case the ports are 36330 for the advanced control and port 7396 for the web control. The client does run and process WU's....but I can't use the advanced control or web con...
- Sun Jun 02, 2013 9:12 pm
- Forum: Issues with a specific server
- Topic: 171.67.108.11 work server issue
- Replies: 8
- Views: 1771
Re: 171.67.108.11 work server issue
I found the logfile regarding the "dumped" issue. Looks like missing work files associated with the WU on my laptop. Thanks for the help on this problem. 21:06:20:WU00:FS00:0x11:Folding@home Core Shutdown: MISSING_WORK_FILES 21:06:20:WARNING:WU00:FS00:FahCore returned: MISSING_WORK_FILES (...
- Sun Jun 02, 2013 6:24 pm
- Forum: Issues with a specific server
- Topic: 171.67.108.11 work server issue
- Replies: 8
- Views: 1771
Re: 171.67.108.11 work server issue
Seems the problem is with the WU on my computer not the connection to the server. I ended up deleting the WU.
- Sun Jun 02, 2013 5:35 pm
- Forum: Issues with a specific server
- Topic: 171.67.108.11 work server issue
- Replies: 8
- Views: 1771
Re: 171.67.108.11 work server issue
Paused both active WU's and restarted my client. It did retry sending the stuck WU right away but failed again with this log entry: 17:33:07:WU00:FS00:Sending unit results: id:00 state:SEND error:DUMPED project:5767 run:10 clone:83 gen:3391 core:0x11 unit:0x4a150d1f51a78ea00d3f0053000a1687 17:33:07:...
- Sun Jun 02, 2013 3:33 pm
- Forum: Issues with a specific server
- Topic: 171.67.108.11 work server issue
- Replies: 8
- Views: 1771
Re: 171.67.108.11 work server issue
I did read the "Do This First" topic. :-) Nothing has changed on my connection. I do get the OK page from 171.67.108.11:8080 and 171.67.108.11:80. The WU send function has fallen back to the bad collection server at 171.67.108.25...I do realize this is a known issue. How do I make the WU s...
- Sun Jun 02, 2013 3:01 am
- Forum: Issues with a specific server
- Topic: 171.67.108.11 work server issue
- Replies: 8
- Views: 1771
171.67.108.11 work server issue
Not having any luck uploading a WU that came from this work server...fell back to the collection server 171.67.108.25 and has failed 13 attempts to upload the results. 02:27:27:WU00:FS00:Uploading 6.75KiB to 171.67.108.11 02:27:27:WU00:FS00:Connecting to 171.67.108.11:8080 02:27:28:WARNING:WU00:FS00...