"lotus-storage-miner info" segfaults

Hello everyone,

Does anyone know why ‘lotus-storage-miner info’ might be segfaulting?

A new miner has just been initialized and the lotus-storage-miner has started running.

console message:

2020-06-27T14:58:59.884-0700 INFO build go-paramfetch@v0.0.2-0.20200605171344-fcac609550ca/paramfetch.go:128 Parameter file /var/tmp/filecoin-proof-parameters/v27-proof-of-spacetime-fallback-merkletree-poseidon_hasher-8-8-0-559e581f022bb4e4ec6e719e563bf0e026ad6de42e56c18714a2c692b1b88d7e.params is ok
2020-06-27T14:59:02.485-0700 INFO basichost basic/natmgr.go:96 DiscoverNAT error:no NAT found
2020-06-27T15:05:14.659-0700 INFO build go-paramfetch@v0.0.2-0.20200605171344-fcac609550ca/paramfetch.go:128 Parameter file /var/tmp/filecoin-proof-parameters/v27-stacked-proof-of-replication-merkletree-poseidon_hasher-8-8-0-sha256_hasher-82a357d2f2ca81dc61bb45f4a762807aedee1b0a53fd6c4e77b46a01bfef7820.params is ok
2020-06-27T15:05:45.535-0700 INFO build go-paramfetch@v0.0.2-0.20200605171344-fcac609550ca/paramfetch.go:128 Parameter file /var/tmp/filecoin-proof-parameters/v27-proof-of-spacetime-fallback-merkletree-poseidon_hasher-8-8-0-0377ded656c6f524f1618760bffe4e0a1c51d5a70c4509eedae8a27555733edc.params is ok
2020-06-27T15:05:45.540-0700 INFO build go-paramfetch@v0.0.2-0.20200605171344-fcac609550ca/paramfetch.go:147 parameter and key-fetching complete
2020-06-27T15:05:45.569-0700 WARN modules modules/core.go:47 Generating new API secret
2020-06-27T15:05:45.583-0700 INFO stores stores/index.go:137 New sector storage: 64794b35-9528-4d2f-bf83-64d7091eea23
2020-06-27T15:05:47.057-0700 WARN storedask storedask/storedask.go:121 no previous ask found, miner will not accept deals until a price is set
2020-06-27T15:05:47.126-0700 INFO storageminer storage/miner.go:130 starting up miner t0117915, worker addr t3wovvjse37tn6kwge6vuvjcpejpndoj2dttdgxnx7nlqntvvax4zq4cnxwspc6mzbdccijjhswdlnjfmumnfa
2020-06-27T15:05:47.149-0700 INFO main lotus-storage-miner/run.go:137 Remote version 0.4.0+git.fbfe57cd+api0.5.0

When running “lotus-storage-miner info”, it fails with the following output:

# lotus-storage-miner info

Miner: t0117915
Sector Size: 32 GiB
Byte Power: 0 B / 10.27 PiB (0.0000%)
Actual Power: 0 / 10 Pi (0.0000%)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1568c77]

goroutine 1 [running]:
main.glob…func2(0xc000154880, 0x0, 0x0)
/root/lotus/cmd/lotus-storage-miner/info.go:104 +0xc37
github.com/urfave/cli/v2.(*Command).Run(0x4d1b2a0, 0xc0001546c0, 0x0, 0x0)
/root/go.codes/pkg/mod/github.com/urfave/cli/v2@v2.2.0/command.go:164 +0x4e0
github.com/urfave/cli/v2.(*App).RunContext(0xc000001980, 0x2b6fe60, 0xc000130030, 0xc000126020, 0x2, 0x2, 0x0, 0x0)
/root/go.codes/pkg/mod/github.com/urfave/cli/v2@v2.2.0/app.go:306 +0x814
github.com/urfave/cli/v2.(*App).Run(…)
/root/go.codes/pkg/mod/github.com/urfave/cli/v2@v2.2.0/app.go:215
main.main()
/root/lotus/cmd/lotus-storage-miner/main.go:83 +0x6e6

Current system’s ‘top’ output:

top - 15:17:13 up 15:29,  2 users,  load average: 0.34, 0.51, 0.96
Tasks: 151 total,   1 running, 150 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1.0 us,  0.5 sy,  0.0 ni, 98.3 id,  0.0 wa,  0.0 hi,  0.2 si,  0.0 st
MiB Mem :  64195.8 total,    408.7 free,  48311.6 used,  15475.5 buff/cache
MiB Swap:  66560.0 total,  41628.0 free,  24932.0 used.  16354.4 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   7924 root      20   0   78.8g  48.6g   1.9g S   8.6  77.6   1097:32 lotus daemon
1871869 root      20   0 6936124  93064  37120 S   0.7   0.1   6:11.68 lotus-storage-miner run
1875644 root      20   0    8036   3764   3204 R   0.7   0.0   0:00.03 top
....snip....

Unresolved, but this issue can be ignored.
I am moving on to trying the next version of Lotus as there seems to be updates today.