Latest posts of: OoIGR

Show Posts
Pages: [1]

Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] T-Rex miner for Nvidia GPU (Windows & Linux)

on: July 18, 2018, 06:45:56 AM

Quote from: trexminer on July 18, 2018, 06:32:20 AM We use a logging library and the error you're getting is a mystery for us, never seen anything like that. What you could try is to turn off the file logging. It is off by default, unless you use a config file example from the archive, where it's set to "log-path": "t-rex.log", (simply delete this entry). API documentation is only relevant for monitoring software developers I believe, and what you said about accessing 127.0.0.1:4067 is correct. Currently the only supported method is "summary". You can see the response by going to http://127.0.0.1:4067/summary in your browser. We'll add that info to a readme/help file or to "t-rex -h" output, thanks. Ok, I will try, new API allows to monitor the state of miner without file logging.

Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] T-Rex 0.5.1 Nvidia GPU miner (Windows & Linux)

on: July 18, 2018, 06:14:10 AM

Quote It would appear the API does not work for AwesomeMiner, which is probably the biggest farm management tool out there.. I've tried setting both --api-bind-telnet and --api-bind-http and neither give me data Try to start miner without -b, --api-bind-telnet and, --api-bind-http arguments. Then in browser on the same rig open 127.0.0.1:4067 and you will see that API is working. After that setup your network and firewall to access rigs API remotely. In addition, we need the documentation about available methods. With examples of requests

Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] T-Rex miner for Nvidia GPU (Windows & Linux)

on: July 18, 2018, 06:05:40 AM

Quote We are going to release a new version in a few hours, hopefully your problem is resolved in 0.5.1 (we fixed a lot of bugs in 0.5x) I am using t-rex miner for windows version 0.5.1 on 8 rigs with lyra2z algo on f2pool.com. The same problem happening repeatedly on all my rigs in same situations. Quite often all rigs in same time fails with the same error like "Cuda error the launch timed out and was terminated" or something else - it does not matter. In this case special software closing miner, deleting all log files in t-rex folder and then starting t-rex miner again. Nevertheless, "failed to remove file 'C'" error occurs 2-3 restarts in a row. Due to this error T-rex miner restarts unnecessary times. Code: 20180718 11:37:27 WARN: Logger: failed to remove file 'C': Процесс не может получить доступ к файлу, так как этот файл занят другим процессом What is the file 'C'? Where is its location - in what folder? Why is it happens? All log files deleted before start miner. What else files do miner use outside of its folder?

Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] T-Rex miner for Nvidia GPU (Windows & Linux)

on: July 17, 2018, 11:02:54 AM

Now I am deleting all *.log files in the folder of T-Rex miner before start it after any error but this error happening again.

What is the file 'C'??
Where is its location?

Code:

20180717 14:58:27 WARNING: Logger: failed to remove file 'C': Процесс не может получить доступ к файлу, так как этот файл занят другим процессом

Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] T-Rex miner for Nvidia GPU (Windows & Linux)

on: July 17, 2018, 10:18:12 AM

I'am using windows version 0.4c.
Sometimes after restart miner it is do not start mining with only one row in log file.

Code:

20180717 14:58:27 WARNING: Logger: failed to remove file 'C': Процесс не может получить доступ к файлу, так как этот файл занят другим процессом

Sometimes after this error "failed to remove file" miner continue mining, but do not write in log file first rows with version of miner, count of gpu devices and name of the pool:

Code:

20180717 12:05:20 T-Rex NVIDIA GPU miner v0.4c
20180717 12:05:20 
20180717 12:05:20 CUDA devices available: 8
20180717 12:05:20 Starting on: xzc.f2pool.com:5740

Example #1

Code:

20180717 14:16:39 WARNING: Logger: failed to remove file 'C': Процесс не может получить доступ к файлу, так как этот файл занят другим процессом
20180717 14:16:56 WARNING: stratum_authorize: extranonce subscribe timed out
20180717 14:16:56 WARNING: New difficulty: 0.499992 (0.00195)
20180717 14:16:56 WARNING: GPU #7: Intensity set to 22, 4194304 cuda threads
20180717 14:16:56 WARNING: GPU #0: Intensity set to 22, 4194304 cuda threads
20180717 14:16:56 WARNING: GPU #4: Intensity set to 22, 4194304 cuda threads
20180717 14:16:56 WARNING: GPU #2: Intensity set to 22, 4194304 cuda threads
20180717 14:16:56 WARNING: GPU #3: Intensity set to 22, 4194304 cuda threads
20180717 14:16:56 WARNING: GPU #5: Intensity set to 22, 4194304 cuda threads
20180717 14:16:56 WARNING: GPU #1: Intensity set to 22, 4194304 cuda threads
20180717 14:16:56 WARNING: GPU #6: Intensity set to 22, 4194304 cuda threads
20180717 14:17:00 [ OK ] 1/1 - 4308.81 kH/s
20180717 14:17:02 [ OK ] 2/2 - 16.75 MH/s
20180717 14:17:02 [ OK ] 3/3 - 16.75 MH/s
20180717 14:17:02 [ OK ] 4/4 - 16.75 MH/s
20180717 14:17:03 [ OK ] 5/5 - 16.75 MH/s
20180717 14:17:03 GPU #0: 4172.13 kH/s
20180717 14:17:03 GPU #1: 4329.03 kH/s
20180717 14:17:03 GPU #2: 4260.80 kH/s

Example #2

Code:


20180717 14:18:33 WARNING: Logger: failed to remove file 'C': Процесс не может получить доступ к файлу, так как этот файл занят другим процессом
20180717 14:18:45 WARNING: stratum_authorize: extranonce subscribe timed out
20180717 14:18:45 WARNING: New difficulty: 0.499992 (0.00195)
20180717 14:18:45 WARNING: GPU #5: Intensity set to 22, 4194304 cuda threads
20180717 14:18:45 WARNING: GPU #4: Intensity set to 22, 4194304 cuda threads
20180717 14:18:45 WARNING: GPU #0: Intensity set to 22, 4194304 cuda threads
20180717 14:18:45 WARNING: GPU #2: Intensity set to 22, 4194304 cuda threads
20180717 14:18:45 WARNING: GPU #7: Intensity set to 22, 4194304 cuda threads
20180717 14:18:45 WARNING: GPU #1: Intensity set to 22, 4194304 cuda threads
20180717 14:18:45 WARNING: GPU #6: Intensity set to 22, 4194304 cuda threads
20180717 14:18:45 WARNING: GPU #3: Intensity set to 22, 4194304 cuda threads
20180717 14:18:49 [ OK ] 1/1 - 0.00H/s 
20180717 14:18:49 [ OK ] 2/2 - 0.00H/s 
20180717 14:18:50 [FAIL] 2/3 - duplicate
20180717 14:18:50 [ OK ] 3/4 - 0.00H/s 
20180717 14:18:50 [ OK ] 4/5 - 25.67 MH/s
20180717 14:18:50 GPU #0: 149.78 kH/s
20180717 14:18:50 GPU #1: 4260.09 kH/s
20180717 14:18:50 GPU #2: 4193.95 kH/s
20180717 14:18:50 GPU #3: 150.45 kH/s

I am using additional software to control miner and need the count of gpu's to check that it is correct. May these rows about count of gpu devices and name of the pool to be in log file all the time miner start to avoid restarts of miner when gpu count check do not proceeds?

Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] zFastminer - Fastest Zcoin XZC miner (on poolside) for nVidia Pascal GPUs

on: April 16, 2018, 05:35:50 AM

I have the same errors on all my 8*1080ti rigs once a day. zFastminer-V2.2.8

Code:

[2018-04-16 08:34:12][31m stratum_recv_line timed out[0m
[2018-04-16 08:34:12][31m ...retry after 5 seconds[0m
[2018-04-16 08:34:15] GPU #4: GeForce GTX 1080 Ti, 4132.83 kH/s[0m
[2018-04-16 08:34:15][31m ...retry after 5 seconds[0m
[2018-04-16 08:34:16] GPU #7: GeForce GTX 1080 Ti, 4282.59 kH/s[0m
[2018-04-16 08:34:20][33m Stratum subscribe answer id is not correct![0m
[2018-04-16 08:34:21][33m Stratum subscribe answer id is not correct![0m
[2018-04-16 08:34:21][31m JSON-RPC call failed: [
   24,
   "unauthorized worker",
   null
][0m
[2018-04-16 08:34:21][31m ...retry after 5 seconds[0m

Alternate cryptocurrencies / Pools (Altcoins) / Re: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin.

on: December 13, 2017, 10:54:42 AM

Profit values in API https://miningpoolhub.com/index.php?page=api&action=getminingandprofitsstatistics are not equal to profit information on web site. So in API request the most profitable coin is one but on the web site is another. Why and where is real profit values - in API requests or on the web site?

Pages: [1]