HTTP request failed: Protocol stratum+tcp not supported or disabled in libcurl

[WolfEdge]

Hey,

I got a bit of a problem after the 0.3.6 update. For some reason, my first pool won't show up as alive. After a bit of pinging from my PC and from the Pi itself and some others stuff, it is clear the pool is fine. After some looking in the logs, I've figured out it can't connect because of the error in the title.

Here is a bit from the log:

[2014-10-09 22:43:06] Testing pool stratum+tcp://ca.simplemulti.com:3364

 [2014-10-09 22:43:06] HTTP request failed: Protocol stratum+tcp not supported or disabled in libcurl

I'm not too sure how to fix this problem. Could I get some help?

Thanks

[michelem09]

You need to recompile your miner, I think you are using BFGminer, so you need to run this command in your minera system:

cd /var/www/minera ./build_miner.sh bfgminer

On Thu, Oct 9, 2014 at 9:46 PM, IrshadAM notifications@github.com wrote:

Hey,

I got a bit of a problem after the 0.3.6 update. For some reason, my first pool won't show up as alive. After a bit of pinging from my PC and from the Pi itself and some others stuff, it is clear the pool is fine. After some looking in the logs, I've figured out it can't connect because of the error in the title.

Here is a bit from the log:

[2014-10-09 22:43:06] Testing pool stratum+tcp://ca.simplemulti.com:3364

[2014-10-09 22:43:06] HTTP request failed: Protocol stratum+tcp not supported or disabled in libcurl

I'm not too sure how to fix this problem. Could I get some help?

Thanks

— Reply to this email directly or view it on GitHub https://github.com/michelem09/minera/issues/108.

[WolfEdge]

Hi!

Thanks for your response. Thing is, you helped me the other day and told me to recompile my BFGMiner, which I did and it fixed the problem. Here is the thread: https://github.com/michelem09/minera/issues/107

I will try to recompile it again and report back.

Thanks

[michelem09]

Are you installing Minera with a "manual" install, right? The problem is, Minera can't install additional libraries via install script, so if you installed Minera manually you always need to recompile and build bfgminer (this is not needed for cpuminer).

[WolfEdge]

When I installed Minera I did it by getting the Minera image and putting it on my SD card and making it bootable. It has worked fine since then, until these problems came up.

[michelem09]

What image file version do you put in the SD Card initially? You need at least 0.3.6. Upgrading from 0.3.5 can give you this kind of problem.

[WolfEdge]

Oh. I believe it was 0.3.4. It could have been 0.3.5 though. I'm not sure. Shall I just download my config settings, wipe my SD card, and put the latest image on?

[michelem09]

Yes for sure. Hope everything works but it should. (If you want you could take a sd-card backup before putting the latest image).

[WolfEdge]

Alright, thanks for the help man! I'll send a little something your way in a bit!

[WolfEdge]

Hey.

It looks like it still isn't working. I can't seem to find the http error this time but I did catch it saying that the connection to pool 0 (simple multi) timed out? I can't get it to connect either when I click this 'select this' button next to the pools. :/

[michelem09]

Best try it's change pool to see if it works with another one.

[WolfEdge]

I've tried with the Canadian Simple Multi Pool and the other one they have. Doesn't work. Any commands I should try in the terminal?

[michelem09]

Look at the miner log in /var/log/minera

[WolfEdge]

Okay, I think I got a lead! You see, I think the problem (in the title) only happens to Pool 0. You see, I changed the top pool to Clevermining, and of course, it can't connect to that! Any ideas?

[PartTimeLegend]

Got the same issue after upgrading here. Just knocked 300MHs offline on multiple installs.

[jimmsta]

I rebuilt all the miners, and I'm also experiencing the same issue. I updated to the latest version first through the web gui, then through git. It doesn't seem to matter which way I go to update it, I still end up with the libcurl error. I also have an issue with my gridseeds being detected at all - lsusb shows them, but none of the mining apps seem to see them. Any ideas?

[WolfEdge]

Hmm. So it looks looks like a possible Minera issue in the way it provides the pool 0 details to the miner, maybe? I can't remember what it's called but it's in the settings. Its like JSON or something.

Just to confirm, are you other guys having problems with Pool 0 only?

[michelem09]

Guys, please take the command Minera uses to start the miner and try running it from a terminal. Then please we need to look at the miner logs, I think it's a BFGminer/Pool issue, so we need to investigate that. You could also take a look at system log in /var/log/syslog (use sudo) or with: sudo dmesg

[michelem09]

Try also to enable option on Minera settings "Miner superuser (root)" or try run the terminal command with "sudo" in front of it

[WolfEdge]

Do you know how I can go about getting the miner + systems logs onto pastebin or able to download?

[WolfEdge]

Hey I think I caught something. I saw it disabling then re-enabling one of my pools (Pool 1) after it started behaving again. Is there a BFGMiner flag to stop that?

[michelem09]

How is going here? Did you find the problem?

[WolfEdge]

Nope.. It's been getting worse and worse really. Like now I'm getting a lot of that issue where it can't use the ASIC because something is using ttyUSB0 (probably a miner that wasn't killed properly) and now I'm getting problems with connecting to the interface because I get this:

Could not connect to Redis at localhost:6379

Also no matter what I do to rearrange my failover list so that the pool I don't want to use is Pool 0 (because Pool 0 always has the problem in the title) it never saves properly. Also, sometimes trying to reconfigure things can be very difficult because the interface becomes slow to load stuff.

It's a wreck. I love Minera but I might just have to use BFGMiner on Raspbian or something like that and miss out on the charts and all that. I don't want to but this problem is an absolute mystery haha. I'm out of ideas.

[michelem09]

Please update to 0.3.8 I found a big bug https://github.com/michelem09/minera/issues/111

[WolfEdge]

Haha I updated and rebuilt BFGminer right after I wrote my last reply! I believe this will fix the USB issue now, right? That's pretty cool. I can now at least mine on a pool that isn't bad properly haha.

As for the HTTP issue, do you have any ideas whatsoever? Iirc I did try running the command Minera uses to run BFGminer in the terminal and I still had the same issue. As for getting the logs (system and miner) I don't know what to do because I'm not too good with Linux. I will try and look for a way to get them on pastebin or somewhere else.

Thanks for the fix btw. :D

[WolfEdge]

Huh.. It seems that after some more testing on my end the problem doesn't only apply to Pool 0 like I thought before. It only applies to my SimpleMulti pool (stratum+tcp://ca.simplemulti.com:3364). However I suspect that this is actually a problem with BFGMiner. It must be. Minera is doing everything right (JSON pool list, miner execution, etc..). I think I should ask @luke-jr about this but before I do I just wanna make sure that I got some solid proof/evidence that its a BFGMiner problem. So firstly, to the other participants in this thread (@PartTimeLegend & @jimmsta), would you like to aid me in reporting the issue? Secondly, Mike, can you perhaps test for a few minutes on your own controller the SimpleMulti pool? The address is stratum+tcp://ca.simplemulti.com:3364 (can't find any others), the username is . and the pass can just be x.

EDIT: Oh my god sorry I think I'm I just really stupid.. You see, the whole time I was certain that something else was the problem because I could ping SimpleMulti just fine. Just now I got curious and ran my batch script that I use to mine on my PC. And what do you know? It can't connect! I don't know why. But I feel really stupid.

[michelem09]

Trying a completely different pool, when the problem is on a pool, it's always the best try you can do.

[michelem09]

Feel free to re-open