I have installed bitcoind daemon into my server and create address for individual users. An User A sends 0.005 BTC into my Bitcoind daemon server, yet it will not appears into my server. I have checked using the following commands:
getreceivedbyaddress()
listaccounts()
listreceivedbyaddress()
Following Link will generate acknowledgement from user transaction.It will show transaction history, yet it will not receive coin into my bitcoind daemon server.
Please kindly advice me. How do I resolve this issue?
When you are sending the commands to Bitcoind make sure you are sending in the minimum confirmations count of 0, this should show your Bitcoins. Change the number passed in to return the balance based on how many confirmations are required. I'm not sure which language your using but the call may look something like this, where 0 is the minimum confirmations required.
client.getReceivedByAddress('1HB5XMLmzFVj8ALj6mfBsbifRoD4miY36v',0);
Related
I am writing several systemd user units and some of them need to depend on the system unit wpa_supplicant#INT.service. These units need to be started when the wpa_supplicant#INT.service starts and stop when it stops.
I have seen that user units can not depend on system units. So, how can I do that ?
Do I have to rewrite all my user units at system units ? Seems very disgraceful and not the way to go.
I would like to avoid creating a service that will check the state of the wpa_supplicant#INT.service and would like to be alerted directly by an instance of systemd.
Any advice will be very appreciated,
Thanks for your time.
I finally found two ways to do that.
We can use systemctl from the system to talk to the user systemctl instance with the --user --machine=user#.host argument.
For example, in a systemd system unit we can start a process like this:
/bin/sh -c "systemctl --user --machine=$${USER}#.host stop wpa_service.target"
Another way is to use a socket to talk to a service running at the user level. Then it will perform any actions at the user session level without any problem.
I've recently started using Monit to monitor some production machines. And it does this well. But the annoying issue I have is that part of the routine is to restart the servers once a day on a rotating basis and each of those restarts generates a unmonitor and monitor message.
I can't find a specific alert setting to turn this off and consequently I'm bombarded by correct but unnecessary messages. There does not seem to be a specific event related to this.
Does anyone know of a way to do this? To be clear, I want to tell monit to unmonitor a server/task, restart or do something, then restart the server/task, then monitor it again. But I don't want to know about the unmonitor or monitor, only failure situations.
You can disable alerts for user actions in general, like the monitrc states:
## Do not alert when Monit starts, stops or performs a user initiated action.
## This filter is recommended to avoid getting alerts for trivial cases.
#
# set alert your-name#your.domain not on { instance, action }
Documentation: https://mmonit.com/monit/documentation/monit.html#Setting-an-event-filter
Hi all (especially Twilio evangelists out there)
I've connected my EMR app to Twilio in order to send faxes, and it works reasonably well, however there's one big problem I'm running into. Some faxes fail to send, and I can't find the reason for it. If the line is busy, or if there's no answer, Twilio marks the fax instances accordingly, and I can attempt a retry or whatever. But in some circumstances I do not understand, a sent fax immediately comes back as Failed through the webHook. So it gets "queued", but the first message I receive from the webHook is FAILED - no additional data whatsoever.
I've tried checking the developer tools Debugger, but there nothing there - it's 100% blank (checked last 30 days). I know from my test account that I should find the failure reason there, if there's something wrong with my implementation (e.g., if Twilio can't fetch my PDF, or I don't provide the "from" number, etc). But on production account, it's empty.
Faxes that I send to myself (Toshiba multifunction) work just fine, report busy when busy, etc. But the faxes sent to other companies fail, though I'm quite sure the numbers are OK. I was wondering if anybody can make a list of the possible reasons for a fax to fail? And I was also wondering why Twilio doesn't send more details on Failed faxes, it would be very helpful to know what happened from my logs...
Thanks,
Vic
Here's a trick that works well, at least when you're just figuring it out. Instead of taking the time to set up a statusCallback URL to handle the error, use an invalid url. This will cause an "Error - 11200 HTTP retrieval failure" in the Twilio debugger, which will include the POST request parameters, including any ErrorMessage.
Twilio evangelist here.
The statusCallback parameter makes as request to a URL when the status of the fax changes and includes parameters like Status, ErrorCode and ErrorReason.
curl 'https://fax.twilio.com/v1/Faxes' \
-X POST \
-d 'To=%2B15558675309' \
-d 'From=%2B15017250604' \
-d 'MediaUrl=https://www.twilio.com/docs/documents/25/justthefaxmaam.pdf' \
-d 'StatusCallback=https://example.com/statusUpdates' \
-u ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:your_auth_token
Twilio Fax is still in beta but I know that adding the ability to display fax logs in the Twilio Console is planned.
Hope that helps.
I am using Twitter4J to retrieve user timelines, but it stopped working. The number of accepted requests is fine, but I get a autentication problem, probably related to clock sync?
INFO: Error while querying Twitter: 401:Authentication credentials (https://dev.twitter.com/pages/auth) were missing or incorrect. Ensure that you have set valid consumer key/secret, access token/secret, and the system clock is in sync.
{"request":"/1.1/statuses/user_timeline.json","error":"Not authorized."}
401:Authentication credentials (https://dev.twitter.com/pages/auth) were missing or incorrect. Ensure that you have set valid consumer key/secret, access token/secret, and the system clock is in sync.
{"request":"/1.1/statuses/user_timeline.json","error":"Not authorized."}
rateLimitStatus=RateLimitStatusJSONImpl{remaining=178, limit=180, resetTimeInSeconds=1432305852, secondsUntilReset=899}, version=3.0.5}
Not sure what to do then. ive tried already to sync my server with ntpdate ntp.ubuntu.com with no luck.
I think you are using SandBox(Build-in VM) of Cloudera/Hortonworks etc
I was also getting the same problem and was trying to sync my clock with 'time.windows.com' clock but I was failed to do. So I moved to 4 nodes cluster which was already existing in my case and there my clock was in sync and I could run my request to Twitter successfully.
Conclusion: Move from Cloudera/Hortonworks VM to own installed OS and make the clock sync.
Hope this help!!!
I am running 340 concurrent users to load test on server using jmeter.
But on most of the cases jmeter hangs up and won' t return, even if I try to close the connection it just hangs up. and eventually I have to close the application.
Any idea how to check what is holding the requests and how to check the requests sent by jmeter and find the bottleneck.
Got the following message on closing the thread
Shutting down thread please be patient message
I've hit this several times over the past few years. In each of my cases (may not be in your's) the issue was with the Load Balance (F5) I was sending my traffic through. Basically a property called OneConnect was holding the connections in a time-wait state and never killing the connection.
Run a pack tool like wireshark and see what's happening with the requests.
Try distributed testing, 340 concurrent users is not a big deal, but still you can try if that decreases your pain. Also take a look at the following link:
http://jmeter.apache.org/usermanual/best-practices.html#lean_mean
First check you script is ok with one user.
Ensure you use assertions.
Then run you test following jmeter best practices:
no gui
no costly listeners
You should then be able to see in csv output the longest request and be able to fix your issue.
I also encountered this problem before when I run my JMeter on my laptop(Core 2 Duo 1.5Ghz) it always hang-up in the middle of the processing. I tried to run on another pc which is more powerful than my laptop and its works now smoothly. Therefore, JMeter will run effectively if your pc or laptop has a better specs.
Note: It is also advisable to run your JMeter in non-gui mode.
Example to run JMeter in Linux box:
$ ./jmeter -t test.jmx -n -l /Users/home/test.jtl
I had the
one or more test threads won't exit
because of a firewall blocking some requests. So I had to leap in the firewalls timeout for all blocked request... then it returned.
You are getting this error probably because JVM is not capable of running so many threads. If you take a look at your terminal, you will see the exception you get:
Uncaught Exception java.lang.OutOfMemoryError: unable to create new native thread. See log file for details.
You can solve this by doing Remote Testing and have multiple clusters running, instead of one.