MultiversX Tracker is Live!

blocknotify ignores > /dev/null 2>&1 and fills up my debug log

Bitcoin Stack Exchange

Bitcoin News / Bitcoin Stack Exchange 103 Views

I have this code in my bitcoin.conf

blocknotify=/root/.nvm/versions/node/v11.15.0/bin/node /home/BTC/block.js %s > /dev/null 2>&1

I see the error

runCommand error: system(/root/.nvm/versions/node/v11.15.0/bin/node /home/BTC/block.js ea31b10db3554ba03a81166c27aa94ba27c335769 7cdd834509731c8946d6fde > /dev/null 2>&1) returned 256

As whenever I'm not running an additional script /home/BTC/block.js is automatically deleted.

Why does bitcoin debug ignore /dev/null 2>&1 and how do I stop it?

@m1xolyd1an, sorry if I am not clear:

The %s gives the block hash to the block.js nodejs script if the script exists (and when it does block.js accepts the hash fine and does what it needs to do). The problem is that the instruction to ignore all errors in the conf is not upheld by bitcoind, thus, my debug.log looks terrible when blocks.js does not exist. blocks.js only exists when it is created by another script and when that script terminates it deletes blocks.js


Get BONUS $200 for FREE!

You can get bonuses upto $100 FREE BONUS when you:
πŸ’° Install these recommended apps:
πŸ’² SocialGood - 100% Crypto Back on Everyday Shopping
πŸ’² xPortal - The DeFi For The Next Billion
πŸ’² CryptoTab Browser - Lightweight, fast, and ready to mine!
πŸ’° Register on these recommended exchanges:
🟑 Binance🟑 Bitfinex🟑 Bitmart🟑 Bittrex🟑 Bitget
🟑 CoinEx🟑 Crypto.com🟑 Gate.io🟑 Huobi🟑 Kucoin.



Comments