Bug #11889

Bitcoin wallet backup cronjob fails

Added by intrigeri 2016-10-26 15:44:46 . Updated 2017-01-24 14:05:04 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Infrastructure
Target version:
Tails 2.10
Start date:
2016-10-26
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

It’s been failing every day during last sysadmin shift, so assigning to bertagaz who was on duty.

Subtasks

History

#1 Updated by anonym 2016-12-14 20:11:28

  • Target version changed from Tails_2.9.1 to Tails 2.10

#2 Updated by intrigeri 2016-12-18 09:55:58

  • Assignee changed from bertagaz to intrigeri

#3 Updated by intrigeri 2016-12-26 13:38:12

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100

I’ve not seen it happen for weeks, and the last backup we have is current.

#4 Updated by intrigeri 2017-01-08 08:46:33

  • Status changed from Resolved to In Progress
  • Assignee set to intrigeri
  • % Done changed from 100 to 20

Apparently, whatever fix was applied (apparently, it was a mere service bitcoind restart) does not survive a reboot.

On startup, bitcoind binds its RPC interface to ::1:8332 only, no IPv4, so of course bitcoin-cli can’t connect to it as we set it up to connect to 127.0.0.1. In the logs I see:

2017-01-07 15:08:39 libevent: getaddrinfo: address family for nodename not supported
2017-01-07 15:08:39 Binding RPC on address 127.0.0.1 port 8332 failed.

… while it binds to both IPv4 and IPv6 for its other port:

2017-01-07 15:08:39 Bound to [::]:8333
2017-01-07 15:08:39 Bound to 0.0.0.0:8333

Both confirmed with ss -tlpn.

Restarting bitcoind manually fixes that.

#5 Updated by intrigeri 2017-01-24 14:05:04

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 20 to 100

Seems that the obvious, trivial solution (adding After=networking.service) was enough to fix it.