mynodebtc/mynode

Mempool gives 502 bad gateway because of error: invalid subnet 172.26.0.1/24: it should be 172.26.0.0/24

Closed this issue · 1 comments

Mempool gives 502 Bad gateway. I believe this is the reason:

Jan 22 08:54:17 mynode mempool[699085]: invalid subnet 172.26.0.1/24: it should be 172.26.0.0/24

I am running on amd64 and custom bitcoin config. Why is Mempool expecting different subnet?

I have both those lines in bitcoin config:

rpcallowip=172.16.0.0/12
whitelist=172.16.0.0/12

This is full error log:

Jan 22 08:54:26 mynode mempool[699086]: + sleep 10s
Jan 22 08:54:26 mynode mempool[699086]: Waiting to initialize mempool DB...
Jan 22 08:54:26 mynode mempool[699086]: + echo 'Waiting to initialize mempool DB...'
Jan 22 08:54:26 mynode mempool[699086]: + '[' '' == true ']'
Jan 22 08:54:26 mynode mempool[699086]: + isRunning=
Jan 22 08:54:26 mynode mempool[699315]: Error: No such object: mempool_db_1
Jan 22 08:54:26 mynode mempool[699315]: ++ docker inspect '--format={{.State.Running}}' mempool_db_1
Jan 22 08:54:26 mynode mempool[699086]: + '[' 1 ']'
Jan 22 08:54:26 mynode mempool[699086]: + isRunning=
Jan 22 08:54:17 mynode systemd[1]: mempool.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 08:54:17 mynode mempool[699085]: invalid subnet 172.26.0.1/24: it should be 172.26.0.0/24
Jan 22 08:54:17 mynode mempool[699085]: invalid network config:
Jan 22 08:54:17 mynode mempool[699085]: Creating network "mempool_default" with driver "bridge"
Jan 22 08:54:16 mynode mempool[699086]: + sleep 10s
Jan 22 08:54:16 mynode mempool[699086]: ++ source /usr/share/mynode/mynode_config_debian.sh
Jan 22 08:54:16 mynode mempool[699086]: ++ '[' -f /usr/share/mynode/mynode_config_debian.sh ']'
Jan 22 08:54:16 mynode mempool[699086]: ++ '[' -f /usr/share/mynode/mynode_config_raspi.sh ']'

Upgrade to 0.3.26 has resolved the problem.

I am closing this issue.