1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

FAHClient not talking to FAHControl on Linux!

Discussion in 'bit-tech Folding Team' started by Scorpuk, 19 Aug 2012.

  1. Scorpuk

    Scorpuk Minimodder

    Joined:
    10 Jan 2012
    Posts:
    725
    Likes Received:
    10
    At the moment when I run FAHControl it just sits there saying connecting, but there is an FAHClient running.

    See top below:

    Code:
    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
     6518 fahclien  39  19  492m  68m 2960 S  696  0.4  35:40.94 FahCore_a4    

    If I then click on start within FAHControl I will end up with two FAHClients running at the same time. The newly started one by my user and the one that is running from boot up by user fahclien.

    Code:
    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
     6518 fahclien  39  19  492m  68m 2960 S  562  0.4  43:44.44 FahCore_a4         
     6673 john      39  19  434m  57m 2948 S  213  0.4   0:31.85 FahCore_a4   

    If I run sudo kill 6518 it just keeps on restarting itself.


    I did try and uninstall FAHClient and reinstall it, but it still does the same.



    Any suggestions?
     
  2. debs3759

    debs3759 Was that a warranty I just broke?

    Joined:
    10 Oct 2011
    Posts:
    1,769
    Likes Received:
    92
    Which Linux are you using? I think it makes a difference to what you have to do...

    In Ubuntu 12.04, I installed FAHClient first, then FAHControl, and everything worked perfectly out of the box. That's how Stanford and others say to do it. I don't know what the effect is if you installed FAHControl first, but that may cause the same sort of problem as you are seeing.

    Certainly uninstalling FAHClient then reinstalling would be the same as installing it after FAHControl.
     
  3. Scorpuk

    Scorpuk Minimodder

    Joined:
    10 Jan 2012
    Posts:
    725
    Likes Received:
    10
    Strange thing is its been working perfectly until this weekend. :(


    Only change is a new router and a new IP address range. I wouldnt have thought that would have affected it.
     

Share This Page