perfect meaning what ?
meaning that blocknotify HAS to be present on the B server, where the coin daemon is, so that it can access physically (by disk path) this compiled executable. Not on the A server where you said it is present.
So to summarize:
in server A ip: 1.1.1.1 yiimp is installed
in server B ip: 2.2.2.2 daemon is installed <- this is where blocknotify script must exist in order to work.
Topic: blocknotify - yiimp (Read 682 times)
Thanks perfect 
where is your blocknotify executable located?
try to use full path
try to use full path
Code:
blocknotify=/path/to/blocknotify 1.1.1.1:4233 307 %s
I'm trying to setup a pool on yiimp and having issue with blocknotify. Yiimp is in one server while daemon is in another server.
in server A ip: 1.1.1.1 yiimp is installed
in server B ip: 2.2.2.2 daemon is installed
Even though block is found however blocknotify doesn't seem to work, I doubt because bitcoin.conf file is in daemon's B server while actual pool script is on server A.
Here is the line I added to daemon's conf file at server B: 2.2.2.2
any idea why blocknotify isn't not working? Do I need to make any changes in above line to make blocknotify work from daemon's B server to intimate server A.
PS. I'm using Linux, Ubuntu 16.04.3
in server A ip: 1.1.1.1 yiimp is installed
in server B ip: 2.2.2.2 daemon is installed
Even though block is found however blocknotify doesn't seem to work, I doubt because bitcoin.conf file is in daemon's B server while actual pool script is on server A.
Here is the line I added to daemon's conf file at server B: 2.2.2.2
Code:
blocknotify=blocknotify 1.1.1.1:4233 307 %s
any idea why blocknotify isn't not working? Do I need to make any changes in above line to make blocknotify work from daemon's B server to intimate server A.
PS. I'm using Linux, Ubuntu 16.04.3
Jump to: