advanced options with 8.3, can't download any cores

[whocrazy]

Hi there.
I've come back after a brief hiatus, and I must say, I really like the v8.3 web interface. It's much less clunkier and more screen reader friendlier than the GTK GUI, so thank you.
Can I still use the advanced configuration commands? IE, I used to fold short work units using special command line options with the v7.x version. I could tell it that I only had x amount of memory, that I wanted small work units and tell it how many CPU cores to use.
Also, I can't download any work unit, because the dns fails to resolve. What's happening?
10:51:16:I1:WU1:Received WU P19228 R1323 C3 G2
10:51:16:I1:Downloading https://cores2.foldingathome.org/fahcor ... ar.bz2.crt
10:51:31:W :CON5:DNS lookup failed for cores2.foldingathome.org
I tried downloading the file in question with my browser and got a 2KB certificate file rather than the executable.

[toTOW]

Yes it's a certificate file.

You probably have a security solution that prevents the client from accessing the Internet.

[whocrazy]

No I don't have any security software or firewall turned on, I was able to get the work unit but not the core. This is really strange.

[Marcos FRM]

I'm occasionally experiencing some name resolution failures here too. It disappears for a while, sometimes comes back, but always ends up working after a few tries. If you can consistently reproduce the issue, it would be helpful to install the debug version, add the following to the configuration file /etc/fah-client/config.xml:

Code: Select all

<config>
  <log-domain-levels>
    Base:5
    Nameserver:5
  </log-domain-levels>
</config>

and report a bug at https://github.com/FoldingAtHome/fah-cl ... tet/issues with the log.

[BobWilliams757]

whocrazy,

The CPU core count is now set under machine settings/resource usage by means of a slider. I'm not sure if your screen reader will allow you to access that slider or not. I don't currently have any of the V8 versions on my machine, so I can't check for compatibility with your screen reader. I *think* it might be possible to alter the configuration file, but I'd have to double check on that, as well as nail down the usual location on your machine.

As for advanced commands, I think most of them are no longer in use regardless of which version you run. Most of those that limited work unit types and sizes have been gone for some time unless I've misunderstood some of the more informed and senior forum users.

[Joe_H]

Some of the advanced options can be set in the config.xml file. It is read when the fah-client process is stared at boot time or using a restart command. here may be added to the GUI in some later version. You can find what options are available by running fah-client --help from a command line. I have copied the output:

Code: Select all

fah-client --help
Usage: fah-client [[--config] <filename>] [OPTIONS]...

OPTIONS:


Configuration:
  --config <string=config.xml>
      Set configuration file.

  --print
      Print configuration and exit.

Informational:
  --help [string]
      Print help screen or help on a particular option and exit.

  --info
      Print application and system information and exit.

  --json-help
      Print help in JSON format and exit.

  --license
      License information and exit.

  -q|--quiet
      Set verbosity to zero.

  -v|--verbose
      Increase verbosity level.

  --version
      Print application version and exit.


Configuration options:
The following options can be specified in a configuration file or on the command
line using the following syntax:

    --<option> <value>

  or:

    --<option>=<value>

  or when marking boolean values true:

    --<option>

Account:
  account-token <string>
    Folding@home account token.

  machine-name <string>
    Name used to identify this machine.

Client:
  allowed-origins <string=https://beta.foldingathome.org/ http://localhost:7396>
    Web origins (URLs) allowed to access this client. Only trusted origins
    should be added. Web pages at added origins will be able to control the
    client.

  on-idle <boolean=false>
    Folding only when idle.

  open-web-control <boolean=false>
    Make an operating system specific call to open the Web Control in a browser
    once client is fully loaded

  web-root <string=fah-web-control/dist>
    Path to files to be served by the client's Web server

HTTP Server:
  http-addresses <string=127.0.0.1:7396>
    A space separated list of server address and port pairs to listen on in the
    form <ip | hostname>[:<port>]

  http-max-body-size <integer=2147483647>
    Maximum size of an HTTP request body.

  http-max-headers-size <integer=2147483647>
    Maximum size of the HTTP request headers.

Logging:
  log <string=log.txt>
    Set log file.

  log-color <boolean=true>
    Print log messages with ANSI color coding.

  log-crlf <boolean=false>
    Print carriage return and line feed at end of log lines.

  log-date <boolean=false>
    Print date information with log entries.

  log-date-periodically <integer=0>
    Print date to log before new log entries if so many seconds have passed
    since the last date was printed.

  log-domain <boolean=false>
    Print domain information with log entries.

  log-domain-levels <string ...>
    Set log levels by domain. Format is:
      <domain>[:i|d|t]:<level> ...
    Entries are separated by white-space and or commas.
      i - info
    For example: server:i:3 module:6
    Set 'server' domain info messages to level 3 and 'module' info messages to
    level 6. All other domains will follow the system wide log verbosity level.
    If <level> is negative it is relative to the system wide verbosity.

  log-header <boolean=true>
    Enable log message headers.

  log-level <boolean=true>
    Print level information with log entries.

  log-no-info-header <boolean=true>
    Don't print 'INFO(#):' in header.

  log-rotate <boolean=true>
    Rotate log files on each run.

  log-rotate-compression <integer=0>
    The type of compression to use when rotating log files.

  log-rotate-dir <string=logs>
    Put rotated logs in this directory.

  log-rotate-max <integer=90>
    Maximum number of rotated logs to keep.

  log-rotate-period <integer=86400>
    Rotate log once every so many seconds. No periodic rotation is performed if
    zero.

  log-short-level <boolean=true>
    Print shortened level information with log entries.

  log-simple-domains <boolean=true>
    Remove any leading directories and trailing file extensions from domains so
    that source code file names can be easily used as log domains.

  log-thread-id <boolean=false>
    Print id with log entries.

  log-thread-prefix <boolean=true>
    Print thread prefixes, if set, with log entries.

  log-time <boolean=true>
    Print time information with log entries.

  log-to-screen <boolean=true>
    Log to screen.

  log-truncate <boolean=false>
    Truncate log file.

  verbosity <integer=3>
    Set logging level for INFO messages.

Project Settings:
  beta <boolean=false>
    Accept beta projects.

  cause <string=any>
    The cause you prefer to support.

  project-key <integer=0>
    Key for access to restricted testing projects.

Resource Settings:
  cpus <integer=8>
    Number of cpus FAH client will use.

Server:
  allow <string=127.0.0.1>
    Client addresses which are allowed to connect to this server. This option
    overrides addresses which are denied in the deny option. The pattern 0/0
    matches all addresses.

  connection-backlog <integer=128>
    Size of the connection backlog queue. Once this is full connections are
    rejected.

  connection-timeout <string>
    Maximum time in seconds before a client connection times out. Zero indicates
    no timeout.

  deny <string=0/0>
    Client address which are not allowed to connect to this server.

  max-connections <integer=4294967295>
    Maximum simultaneous client connections per port

  max-ttl <integer=0>
    Maximum client connection time in seconds

User Information:
  passkey <string=>
    Your passkey.

  team <integer=0>
    Your team number.

  user <string=Anonymous>
    Your user name.

The Help output includes the type of value the options take and the default values used.

[bsod.exe]

I had the same problem too on the 8.3 client. It ended up working if I switched my network to my iphones hotspot, however only while on the hotspot did it work. I determined it was a DNS issue like you had. I have no AV other than windows defender and it wasnt flagging F@H. I decided to go back to the v7.6.21 client as it works just fine. Good luck finding a fix, or better yet if the devs can name a fix/workaround.

[Greg_BE]

I have similar but different issue.
V7 started acting up on me after the last MS update.
So I downloaded V8.
I could not download any cores, so I did a reinstall.
Then I could download 2 cores and tasks and I let it be overnight.
I just came back and only 1 GPU had a task running the other was stuck trying to download a core.
I switched back to V7 and I have both GPU's running again.

What's going on? Is there something in Windows that got changed that is messing with the software here or the settings?

[yoshineko]

I have also "DNS lookup failed" issue.
There was proxy tag in the config.xml even though I had not configured it.
<proxy v=':8080'/>

I've removed this tag and restarted FAH. I believe the warning has now disappeared.

[Joe_H]

I have also "DNS lookup failed" issue.
There was proxy tag in the config.xml even though I had not configured it.
<proxy v=':8080'/>

I've removed this tag and restarted FAH. I believe the warning has now disappeared.

The proxy tag you saw is part of the default configuration for v7, I don't know whether v8.3 uses it at all. The v8 client stores its settings in the client.db file and just reads config.xml at installation time and when the client is restarted. Currently that is the only way to bring in some of the advanced options which can not be configured through the v8 web interface.

[calxalot]

Basic http proxy support was recently added to v8, and exclusively uses OS specific proxy settings from the system. I don’t know how much testing it has received.

As I recall, the server that provides core downloads changed, and some people have been experiencing extremely slow downloads and some timeouts. Not helping is the size of some cores (some over 200MB).