sent into viabtc's accelerator https://pool.viabtc.com/tools/txaccelerator/tx: da59d6f325876fae13c3c18baa441e72ee39cb8c2a1767d2616b0526cb8199a2 ViaBTC reply: Transaction added to acceleration queue should confirm shortly. edit: Included In ViaBTC Block 501394 ( 2017-12-28 08:25:44 + 26,373 minutes ) |
|
|
|
|
parent tx:
4a33c36fe8e43ad02e0a9d80349c56a13e7736cb973e70d82ac2eb8b964ad2fb
ViaBTC reply: Transaction added to acceleration queue
Once ViaBTC finds a block, they will clear that parent tx and you should be able to try again and get past that message.
edit:
Included In ViaBTC Block
501376 ( 2017-12-28 05:56:06 + 13,673 minutes )
edit:
tx: 32fef55bf5a35d349b20d996910c0b697474246fdad43a7fb292cfdaa04d3679
ViaBTC reply: Transaction added to acceleration queue
edit:
Included In ViaBTC Block
501381 ( 2017-12-28 06:07:11 + 13,668 minutes )
|
|
|
|
sorry couldn't help earlier. i added tx 7890f6b5c7610aff17939f48ba70dd76b30b0d8ba98b69279b944255af372928 added to ViaBTC accelerator https://pool.viabtc.com/tools/txaccelerator/ reply: Transaction added to acceleration queue maligayang pasko should start getting confirmations soon. edit: Included In ViaBTC Block: 500882 ( 2017-12-24 20:04:14 + 8,482 minutes ) |
|
|
|
|
Sure looks like it's running at 200MHz.
If you want to confirm, try passing in a different frequency parameter and see if the WU changes.
--gekko-2pac-freq 150
The chip is likely not reacting to the set freq request, and the code is not noticing.
|
|
|
|
I was able to slide your tx in a moment ago.
When they find a block, this one should finally clear.
Included In ViaBTC Block 499823 ( 2017-12-17 18:21:26 + 19,246 minutes ) |
|
|
|
They have a free version, you need to try on the hour for a free slot. https://pool.viabtc.com/tools/txaccelerator/I was able to slide your tx in a moment ago. When they find a block, this one should finally clear. Read some of the sticky in the section for concepts and some ideas how to not be in the predicament in the future. RBF, CPFP, some wallets will re-broadcast, some node's mempool take forever to cycle old. RBF flag on all future tx is going to be your best bet. |
|
|
|
...
I have noticed as well initial WU is down by 40 per 2pac. average per 2pac at 250/1.40 was 383, on restart at 225/1.46 showing 340, expecting that number to rise over the next few hours though.
I'm wondering if anyone else has tried this, and what where your results?
That appears in range. WU change is proportional to freq. About a 10% change in each there. more details: https://bitcointalk.org/index.php?topic=1764803.msg18329715#msg18329715 |
|
|
|
If you visit chain.so's api https://chain.so/api/v2/tx/2670f330b81947af83adfdfc3be0ae9c9941e1923a38f635424f740dd3cd7407you can get the hex source of that tx. put it into pushtx on blockchain.info https://blockchain.info/pushtxand blockchain.info tells you why it (and most other nodes) doesn't like it. Missing parents for 2670f330b81947af83adfdfc3be0ae9c9941e1923a38f635424f740dd3cd7407 while inserting: 3793c0e53b2e519de30ae4f003e9889eea0f0dac75a4abda01774db48662d483 I took a peek down this rabbit hole on chain.so and all I see is an upside-down pyramid that based upon unconfirmed transactions. Missing parents for 3793c0e53b2e519de30ae4f003e9889eea0f0dac75a4abda01774db48662d483 while inserting: 7abe21995018d8f6aabc0d6bbf158bee9a56a5c83b55be8c7c76a35b332f7349 Missing parents for 7abe21995018d8f6aabc0d6bbf158bee9a56a5c83b55be8c7c76a35b332f7349 while inserting: e48d86da3d11bcbbab948be7200450572813357d89f14a6a1768c125598d2324 Missing parents for e48d86da3d11bcbbab948be7200450572813357d89f14a6a1768c125598d2324 while inserting: d538b09f2c7cdab8398cc57a997c0a1cec9f6a1b068747f72ee0dd0fa3c74544 Missing parents for d538b09f2c7cdab8398cc57a997c0a1cec9f6a1b068747f72ee0dd0fa3c74544 while inserting: e025dad79a4fc3ef7b639d8cd72f555dd25c26188a0d9e34e91953a33679073f ... I haven't see far enough, nor do I want to, to tell if original input is now a double-spend and answer your question definitively. My best recommend is to bug them every few days noting you haven't received your funds. |
|
|
|
must be a nice school and area. hope that covers more than just a month of expenses  317b18200deed23e68287100e0a4edb4907bd7ed882043da9aa863371bcab63e ViaBTC reply: "Acceleration succeeded" edit: Included In ViaBTC Block: 499327 ( 2017-12-14 21:57:41 + 3,555 minutes ) |
|
|
|
|
bam. easy peasy. not really.
Included In ViaBTC Block:
499221 ( 2017-12-14 08:11:40 + 4,991 minutes )
|
|
|
|
|
Got some spare time target this challenge.
Acceleration succeeded. Awaiting next ViaBTC block.
|
|
|
|
Let's see what's connected: sudo cat /sys/kernel/debug/usb/devices | grep -E "^([TSPD]:.*|)$"
|
|
|
|
Hello All, I've been going through this thread trying to see any similar issues to what I'm seeing with no luck so far.
I have just setup a new RaspberrPi3 with the latest Raspian image. I have been able to get the vthoang cgminer 4.10 setup and working, and with two(2) 2pac on a powered USB hub the SW launches and logs into my pool with no problems. I'm running at the default freq of 100 for now. After some amt of time, anywhere from 2-6hrs the Pi seems to crash and is unreachable. I'm not exactly sure where to start to see what kind of problem I'm running into. the Pi is running headless so there is no screen to look at. Any suggestions?
I have the same exact problem and haven't been able to narrow down the issue despite trying. Sometimes it lasts a few hours and other times 24+ hours. Then randomly the 2pacs stop blinking and the Pi cannot be reached via VNC Viewer or Putty and I have to pull/plug the power to get it running again. I know that is not an answer to your question but figured it wouldn't hurt to know you are not the only one to have this problem. I may have caught it in the act earlier today when I saw the 2pacs all reducing their hashrate and going zombie but stopped it and restarted no problem. I should have let it play out to see if that was the issue but didn't think about it at the time. Yes, this is pretty much exactly what is happening to me. Did you happen to be watching the hashrate at the time? I'm not sure how to troubleshoot it or where to start. All I remember seeing is one stick registering as "SICK" and the others slowly reducing their hashrate. I remember seeing two around 800 MH/s and I think another was 200... Another odd thing is that after I stopped cgminer and attempted to restart the Pi using sudo reboot, it didn't restart. Once again I had to pull the plug and do a hard restart then as always everything started working again no problem. I wish I could figure it out but I just don't know enough yet to narrow it down further. I did re-flash the raspian image about a month ago to see if it would help but that didn't do anything. Something worth reviewing and trying out if the kernel is going down: https://bitcointalk.org/index.php?topic=494625.msg5932931#msg5932931 |
|
|
|
You can get a better feel for fees here: https://jochen-hoenicke.de/queue/#24hTransactions clear from the top down. When it reaches your 10-20 sat/B range, your tx will clear automatically. Visit this site: https://pool.viabtc.com/tools/txaccelerator/At the top of every hour hit submit. If you are fast enough, it will say transaction "Acceleration succeeded" and you are good to go. edit: i'll kick off a few for you on the hour if i don't get distracted. f8d6179925b5eaf25d20d361eb055bb50e3583567820ac912b6538eb4bde7982 : Acceleration succeeded |
|
|
|
|
I gave your transaction an extra nudge through viabtc.
4207d03c932804c1495f199f76b4796aaac39223f9b40d603f4b88febade2fe4
ViaBTC reply: "Acceleration succeeded"
What does that mean? Maybe another hour or two, when they find a block. Good luck.
edit:
Included In ViaBTC Block:
498994 ( 2017-12-13 03:53:26 + 752 minutes )
|
|
|
|
OS X El Capitan (10.11.6) /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew doctor
brew tap vthoang/cgminer
brew install cgminer
#if no errors: $ cgminer -n
[2017-12-12 17:08:23.377] USB all: found 8 devices - listing known devices
.USB dev 0: Bus 20 Device 24 ID: 10c4:ea60
Manufacturer: 'GekkoScience'
Product: '2Pac BM1384 Bitcoin Miner'
[2017-12-12 17:08:23.378] 1 known USB devices
cgminer -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --suggest-diff 32
 |
|
|
|
re:docker can't seem to map the mac/windows usb devices in so that was a wash. leaving it in the public docker repo in case someone finds a use for it. docker run -it --privileged -v /dev/bus/usb:/dev/bus/usb vthoang/cgminer -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --suggest-diff 32
Dockerfile ############################################################
# Dockerfile to build cgminer container images
# Based on Ubuntu
############################################################
FROM ubuntu
RUN apt-get update
RUN apt-get upgrade -y
RUN apt-get install -y build-essential git libusb-1.0-0-dev libusb-1.0-0 libcurl4-openssl-dev libncurses5-dev libudev-dev screen libtool automake pkg-config libjansson-dev
RUN mkdir -p /opt/git/vthoang && \
cd /opt/git/vthoang && \
git clone https://github.com/vthoang/cgminer.git && \
cd cgminer && \
CFLAGS="-O2 -march=native" ./autogen.sh --enable-gekko && \
make -j 2
ENTRYPOINT ["/opt/git/vthoang/cgminer/cgminer"]
CMD ["--url","stratum+tcp://pool.ckpool.org:3333","--userpass","1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr","--suggest-diff","32"]
|
|
|
|
|
264dd9a129977cccc1cbae99f05b6d5ccd7a09bde012ad6ee35e99e126f994d9
ViaBTC reply: "Acceleration succeeded"
let's see if this one will pull through. going for 3 of 3 today.
edit:
Included In ViaBTC Block
498367 ( 2017-12-09 08:48:53 + 3,845 minutes )
|
|
|
|
|
Show Posts
