Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xmr-stak rejects and connection errors! #242

Open
siphon00 opened this issue Feb 17, 2021 · 0 comments
Open

xmr-stak rejects and connection errors! #242

siphon00 opened this issue Feb 17, 2021 · 0 comments

Comments

@siphon00
Copy link

I'm not sure what I've done wrong here, it's been a few years since I've set up a miner! Hopefully someone here knows more than me. I'm using an older PC: AMD fx-6200, 12GB DDR3, r9 280X gpu. trying to use xmr-stak to mine monero. Using Radeon Crimson Driver Packaging Version
17.30.1029-170808a2-317304E-CrimsonReLive

Attaching the config below along with the miner progress:

/*

  • Number of GPUs that you have in your system. Each GPU will get its own CPU thread.
    */
    "gpu_thread_num" : 1,

/*

  • GPU configuration. You should play around with intensity and worksize as the fastest settings will vary.
  •  index    - GPU index number usually starts from 0
    
  • intensity - Number of parallel GPU threads (nothing to do with CPU threads)
  • worksize - Number of local GPU threads (nothing to do with CPU threads)
  • affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
    */
    "gpu_threads_conf" : [
    { "index" : 0, "intensity" : 1000, "worksize" : 8, "affine_to_cpu" : false },

],

/*

  • Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel.
    */
    "platform_index" : 0,

/*

  • TLS Settings
  • If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
  • to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
  • use_tls - This option will make us connect using Transport Layer Security.
  • tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
  • tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
    */
    "use_tls" : false,
    "tls_secure_algo" : true,
    "tls_fingerprint" : "",

/*

  • pool_address - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
  • wallet_address - Your wallet, or pool login.
  • pool_password - Can be empty in most cases or "x".
    */
    "pool_address" : "pool.supportxmr.com:3333",
    "wallet_address" : "48AetnsfAix9nCPfYHAFzsaU9vGv3FjZs7SJ5Gcd8pwVXc6ujaQVtP8VE5Px8uj9YyZN3v9aZffrXRD8phz6Wter71HQosg",
    "pool_password" : "x",

/*

  • Network timeouts.
  • Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
  • sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
  • nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
  • long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
  • server usually takes to process our calls.
  • call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
  • retry_time - How long should we wait before another connection attempt.
  •            Both values are in seconds.
    
  • giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
  •            don't mine while the connection is lost, so your computer's power usage goes down to idle.
    

*/
"call_timeout" : 10,
"retry_time" : 10,
"giveup_limit" : 0,

/*

  • Output control.
  • Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
  • really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
  • performance monitors, there is very little reason to spew out pages of text instead of concise reports.
  • Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
  • verbose_level - 0 - Don't print anything.
  •             1 - Print intro, connection event, disconnect event
    
  •             2 - All of level 1, and new job (block) event if the difficulty is different from the last job
    
  •             3 - All of level 1, and new job (block) event in all cases, result submission event.
    
  •             4 - All of level 3, and automatic hashrate report printing 
    

*/
"verbose_level" : 3,

/*

  • Automatic hashrate report
  • h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
  •            This option has no effect if verbose_level is not 4.
    

*/
"h_print_time" : 60,

/*

  • Daemon mode
  • If you are running the process in the background and you don't need the keyboard reports, set this to true.
  • This should solve the hashrate problems on some emulated terminals.
    */
    "daemon_mode" : false,

/*

  • Output file
  • output_file - This option will log all output to a file.

*/
"output_file" : "",

/*

  • Built-in web server
  • I like checking my hashrate on my phone. Don't you?
  • Keep in mind that you will need to set up port forwarding on your router if you want to access it from
  • outside of your home network. Ports lower than 1024 on Linux systems will require root.
  • httpd_port - Port we should listen on. Default, 0, will switch off the server.
    */
    "httpd_port" : 0,

/*

  • prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
  •           This setting will only be needed in 2020's. No need to worry about it now.
    

*/
"prefer_ipv4" : true,

You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection

[2021-02-17 17:21:39] : Starting GPU thread, no affinity.
[2021-02-17 17:21:39] : Connecting to pool pool.supportxmr.com:3333 ...
[2021-02-17 17:21:39] : Connected. Logging in...
[2021-02-17 17:21:39] : Difficulty changed. Now: 50000.
[2021-02-17 17:21:39] : New block detected.
[2021-02-17 17:21:42] : Result rejected by the pool.
[2021-02-17 17:24:56] : Result rejected by the pool.
[2021-02-17 17:24:56] : SOCKET ERROR - PARSE error: Unexpected call response
[2021-02-17 17:24:56] : Pool connection lost. Waiting 10 s before retry (attempt 1).
[2021-02-17 17:25:06] : Connecting to pool pool.supportxmr.com:3333 ...
[2021-02-17 17:25:06] : Connected. Logging in...
[2021-02-17 17:25:06] : Difficulty changed. Now: 50000.
[2021-02-17 17:25:06] : New block detected.
[2021-02-17 17:25:25] : Difficulty changed. Now: 70313.
[2021-02-17 17:25:25] : New block detected.
[2021-02-17 17:26:25] : Difficulty changed. Now: 50000.
[2021-02-17 17:26:25] : New block detected.
[2021-02-17 17:26:30] : New block detected.
[2021-02-17 17:30:37] : Result rejected by the pool.
[2021-02-17 17:36:09] : Result rejected by the pool.
[2021-02-17 17:36:09] : Difficulty changed. Now: 50001.
[2021-02-17 17:36:09] : New block detected.
[2021-02-17 17:36:25] : Difficulty changed. Now: 50000.
[2021-02-17 17:36:25] : New block detected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant