dashed-slug.net

Hello,

Have you set up a -walletnotify mechanism to notify the plugin on all incoming deposits? Or are you relying on the cron mechanism for transaction discovery?

The cron mechanism is OK in most cases, but as you have a large number of transactions on your site it is possible that some deposits get lost. The cron mechanism relies on calls such as listtransactions and these calls only return the last few transactions. If you set up the -walletnotify mechanism then no transaction will be lost.

Can you please do the following for me?

1. Find the TXID for a transaction that is missing.

2. Do the following call, either from your browser or from curl:

https://www.eotwallet.com/wallets/api2/notify/EOT/wallet/TXID

The above assumes that your coin symbol is EOT and you should replace TXID with the actual ID.

This will force the wallet to look at this transaction, and if its destination includes a user deposit address it will write a deposit transaction in the database.

Hit this URL and let me know what you got back as a result and if the deposit was discovered.

For this to happen automatically for every transaction, you should enter the following in your wallet’s .conf file, as initially instructed by the adapter:

walletnotify=curl -s https://www.eotwallet.com/wallets/api2/notify/EOT/wallet/%s >/dev/null

You will need to restart your wallet after adding this to your .conf file.

Hello Arne,

This is not possible because the selected coin does not correspond 1-to-1 with any particular shortcode or UI. The selected coin is a setting that applies throughout the entire page and all its UIs.

What you can do however, is to set the currently selected coin with JavaScript. For example, to set the selected coin to be Litecoin (assuming Litecoin is enabled on your site) you would call:

wp.wallets.viewModels.wallets.selectedCoin('LTC')

Unfortunately if you attach this to the document ready event it might not work, as the coin data might not have been loaded yet. I will add some kind of callback mechanism in the next release so that things like this will be possible. Something like a “wallets ready” event that you can attach JavaScript to.

I will let you know here once this is done.

kind regards

Thanks for providing this info.

The logs that you report are actually normal, see my earlier post here: https://ww.wp.xz.cn/support/topic/wordpress-database-error-125/page/2/#post-10339171

The problem you report might actually be caused by a bug in the code that occurs only in rare situations, but since you have high traffic you observed this.

There were no changes in 3.4.1 that are related to this. I am still testing and will hopefully release a patch later today if my suspicions are confirmed.

kind regards

Thank you for noticing this bug.

It is now fixed in version 3.4.1.

kind regards

Hello,

Since you were unable to uninstall the plugin and had to delete the files to regain control, it is to be expected that all of the settings remain. I have never attempted installation on a Windows machine, but you should start by checking the troubleshooting section of the manual under “When I activate the plugin, my WordPress becomes extremely slow and is unusable.”. Most likely this is due to some firewall. Firewalls are notorious for causing timeouts rather than errors and therefore can cause the site to become unusable. If you get some other error on the screen then please report it here.

To delete all of the plugin’s settings manually you could first backup your database and then hit the following on your MySQL console:

DELETE FROM wp_options WHERE option_name LIKE 'wallets%';

Make sure to replace wp_ with your actual DB prefix if it is different.

You can then reinstall the plugin and give it another go.

Do let me know if you see any errors on your screen or logs. By the way, you should be able to check your log file, even if your WordPress installation is unresponsive.

kind regards
Alex

OK thanks for keeping me in the loop.

Increasing the connections sounds like a good idea even if it did not solve your problem on its own. In fact this whole problem sounds like a matter of scaling your infrastructure, and is a DBA task. If you can point to some error that the plugin produces as you did before, then I can help you with that.

If I were you I would very carefully read the server logs, including the mysql logs, the webserver logs and the wordpress logs around the time when the site start failing.

If you need to exclude some lines from your logs you can use grep -v and pipes to remove some patterns that repeat frequently. Hopefully the real error will stand out and you will be able to know what to do to scale the services.

For example to remove lines that have foo or bar in them I would do the following on my setup:

tail -f /var/log/nginx/access.log /var/log/mysql/{mysql,error}.log /var/www/wordpress/wp-content/debug.log | fgrep -v foo | fgrep -v bar

This would let me observe all the services for any errors in real time but without having the screen cluttered with irrelevant messages. Your log paths may vary.

Keep in mind that the plugin’s frontend hits the webserver (and therefore the database) pretty hard due to the polling feature. One idea would be to disable polling. This would cause the frontend to not update automatically. See Admin → Wallets → Frontend settings → Live polling settings. Set the two polling intervals to 0 (disable) and also disable loading when page becomes visible. That should reduce the load on your server by a lot.

If you do find any other error in the logs, please share it with me.

best of luck!

kind regards

Hello Andy,

If you lose the transactions then the balance will still be on the site’s wallet but will not belong to any users.

You can protect yourself from this by backing up your database regularly. There is also a feature that lets you export the transactions to csv files, you can test it before disaster strikes.

The coin adapters are designed to re-discover the latest few deposit transactions even if they are lost in the database, but you cannot rely on this to rediscover all the transactions from the beginning of time, and internal transactions cannot be re-discovered. Hence the need to keep backups.

Think about it this way: Blockchains are the distributed, fault tolerant solution to centralized databases. Whenever you perform transactions in the plugin,
you record transactions in a centralized database and therefore you lose the benefits of blockchains, i.e. fault-tolerance, decentralization, etc. But you gain control on your website. You are therefore responsible to maintain that database until the funds are again withdrawn from your site. It’s a trade-off.

Hope this answers your question.

kind regards
Alex