Completely at a loss of how to fix this. json_decode() is corrupting the data, and it's a built-in feature of PHP (5.2 in my case). Googling around, I'm not seeing anyone else with the same problem.
absolutely stumped :/
Does miner.php work OK? Nope, it's php issue. I''ll see if I can upgrade php.
|
|
|
That means the problem is the code you are using to read the API, not the API. e.g. a php, json,python or whatever you are using update issue?
Yeah, seems to be the php json_decode() function has stopped working. Bizzare. Completely at a loss of how to fix this. json_decode() is corrupting the data, and it's a built-in feature of PHP (5.2 in my case). Googling around, I'm not seeing anyone else with the same problem. absolutely stumped :/
|
|
|
Upped to 3.6.3 https://www.dropbox.com/s/h3hsknaf1fdw2rk/cgminer_3.6.3_mipsel.ipkAll working with my 6 BFL SC singles CPU usage on the RT-N16 is around 10% for everything (cgminer + OS + whatever else is running). Total power consumption of that lot is about 1560W (Remember: Hot-plugging does not work. Have to restart cgminer to find new units.)
|
|
|
3.6.2 won't even run on Win7: [2013-10-16 07:08:27] BAS 1 usb write err:(-5) LIBUSB_ERROR_NOT_FOUND [2013-10-16 07:08:27] BAS1: RequestQueJob failed (err=-5 amt=0)
Works for me.
|
|
|
Why's my API output garbled??? (3.6.1 windows binary)
...
Does java API summary get the same result? Edit: or to see the JSON version: java API "{\"command\":\"summary\"}"comes out fine both formats there. That means the problem is the code you are using to read the API, not the API. e.g. a php, json,python or whatever you are using update issue? Yeah, seems to be the php json_decode() function has stopped working. Bizzare.
|
|
|
With a swap drive it might, but you'd be pushing it some.
|
|
|
Why's my API output garbled??? (3.6.1 windows binary)
...
Does java API summary get the same result? Edit: or to see the JSON version: java API "{\"command\":\"summary\"}"comes out fine both formats there.
|
|
|
Won't really help. The debug version only does something if it crashes.
Oh. Thought you have some other trickery in there :/ I wish. The debug builds in there are based on 3.6.1 currently so they will likely have the memory leak bug inherent in the included libusb. That said, sometimes strangely issues go away on debug builds due to a bug showing up only with optimisations enabled (debug builds have no compiler optimisations). yeah, stopped working with a stream of mem errors again. actually -11, not -7 giving 3.5.1 another bash now.
|
|
|
Won't really help. The debug version only does something if it crashes.
Oh. Thought you have some other trickery in there :/
|
|
|
I replaced cgminer-nogpu.exe with the one in the above temp folder. I get ever increasing lines of: AMU 0 usb write err:(-7) LIBUSB_ERROR_TIMEOUT Odd. What hardware are you using? I got this after a couple of hours too. Win cgminer-nogpu 3.6.1, with 1 BFL SC 60GHz Now trying the debug version you put up.
|
|
|
Why's my API output garbled??? (3.6.1 windows binary)
"SUMMARY": [ { "Elapsed": 8429, "MHS av": 6, +43.+1, "Found Blocks": 0, "Getworks": 196, "Accepted": 2399, "Rejected": 17, "Hardware Errors": 553, "Utility": 2-.1., "Discarded": 374, "Stale": 0, "Get Failures": 0, "Local Work": 309488, "Remote Failures": 0, "Network Blocks": 27, "Total MH": 5-.2, 4320.2-, 1, "Work Utility": 8-0./3, "Difficulty Accepted": 11/4, ., "Difficulty Rejected": 8-4, "Difficulty Stale": 0, "Best Share": 246339597, "Device Hardware%": 0.51/-, "Device Rejected%": 0.72, , , "Pool Rejected%": 0.703., "Pool Stale%": 0 } ],
|
|
|
I won't be mining 3 months from now.
|
|
|
you had a dream? Seriously? Seems legit. I'm convinced.
|
|
|
Yeah, I should add the caveat... no hot-plugging! the OS/kernel just doesn't support it.
|
|
|
Just realized something... My problem with libusb, I had assumed that it was libusb itself to segfault, but it's actually cgminer not handling the error properly and segfaulting.
libusb_init() failed err -99 [2013-10-11 14:02:49] libusb_init() failed
Program received signal SIGSEGV, Segmentation fault. 0x00455dcc in libusb_exit () (gdb) bt #0 0x00455dcc in libusb_exit () #1 0x004175f0 in clean_up () #2 0x0040a180 in _quit () #3 0x00404064 in main ()
So the call to libusb_exit() shouldn't be made if the init didn't work.
|
|
|
Out of curiosity, what mining hardware do you use?
|
|
|
"service cgminer on" nor "service cgminer start" doesn't work, I edited the cgminer.conf beforehand. I can't even get the services command to list anything. I think that's the DD-WRT only feature. I have no clue how it's handled in the ASUSWRT-Merlin firmware.
Edit:Got CGminer running at least, GETRESULTS TIME OUT ERRORS. FFFFFFF- I GIVE UP.
I guess I'll just have to live with 5-7$ higher power bills for another month at least.
Ah yeah, service is a optware the right way thing. Probably best give up. Not a lot I can do about that error.
|
|
|
|