panic: runtime error: invalid memory address or nil pointer dereference .

Panic on the BSD version:

[UZP5V] 10:43:40 INFO: syncthing v0.14.2 "Dysprosium Dragonfly" (go1.6.3 freebsd-amd64) unknown-user@
lx-buildslave.syncthing.net 2016-07-26 11:55:25 UTC
...
[UZP5V] 10:44:32 INFO: Joined relay relay://163.172.210.93:22067
[UZP5V] 10:50:21 INFO: Established secure connection to YGUGY[snip] at 192.168.1.11:22000-192.168.1.155:65511 (TCP (Server))
[UZP5V] 10:50:21 INFO: Device YGUGYH[snip] client is "syncthing v0.14.0" named "surface"
[UZP5V] 12:35:08 INFO: Device KI3N7U[snip] folder "foldername" is delta index compatible (mlv=151823)
Panic at 2016-07-27T12:35:08+01:00
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x38 pc=0x783ee9]

goroutine 31834 [running]:
panic(0xbded80, 0xc82000e110)
        /usr/local/go/src/runtime/panic.go:481 +0x3e6
github.com/syncthing/syncthing/lib/connections.(*Connection).ID(0xc82279f6b0, 0x0, 0x0, 0x0, 0x0)
        <autogenerated>:95 +0x59
github.com/syncthing/syncthing/lib/model.sendIndexes(0x8014e9b68, 0xc82279f6b0, 0xc8218fb590, 0xe, 0x
c8203cfc00, 0xc821c3d040, 0x2510f)
        /home/buildslave/workspace/syncthing-release/src/github.com/syncthing/syncthing/lib/model/model.go:1207 +0x3c
created by github.com/syncthing/syncthing/lib/model.(*Model).ClusterConfig
        /home/buildslave/workspace/syncthing-release/src/github.com/syncthing/syncthing/lib/model/model.go:733 +0x2073

The Surface (0.14.0) machine is now upgraded, but thought I’d log the panic anyway in case it’s something else causing it.

Thanks for reporting this. This has already been reported and we have a issue open on github. You can potentially add a comment with your FULL log there.

Aha, yes, I see that now.

Happy to add comments, but the full log discloses information (folder names etc) - if there was a supported way to salt & hash anything like that then happy to send.

Sadly there isn’t.

Is that the actual log sequence of have you doctored it? I’m asking because I would expect there to be several log lines referring to KI3N7U connecting prior to the “delta index” line.

Here you go, with tin foil hat firmly attached:

[UZP5V] 10:43:40 INFO: syncthing v0.14.2 "Dysprosium Dragonfly" (go1.6.3 freebsd-amd64) unknown-user@lx-buildslave.syncthing.net 2016-07-26 11:55:25 UTC
[UZP5V] 10:43:40 INFO: My ID: UZP5VJ
[UZP5V] 10:43:40 INFO: Single thread hash performance is ~172 MB/s
[UZP5V] 10:43:40 INFO: Ready to synchronize mp (readwrite)
[UZP5V] 10:43:40 INFO: Ready to synchronize pk (readwrite)
[UZP5V] 10:43:40 INFO: Ready to synchronize sp (readwrite)
[UZP5V] 10:43:41 INFO: Ready to synchronize Sy (readwrite)
[UZP5V] 10:43:43 INFO: Ready to synchronize is (readwrite)
[UZP5V] 10:43:43 INFO: Ready to synchronize dt (readwrite)
[UZP5V] 10:43:45 INFO: Ready to synchronize oy (readwrite)
...
[UZP5V] 10:43:45 INFO: Ready to synchronize pl (readwrite)
[UZP5V] 10:43:46 INFO: Ready to synchronize t0 (readwrite)
[UZP5V] 10:43:46 INFO: Ready to synchronize ad (readwrite)
[UZP5V] 10:43:46 INFO: Ready to synchronize as (readwrite)
[UZP5V] 10:43:46 INFO: Using discovery server https://discovery-v4-1.syncthing.net/v2/?id=SR7AAR
[UZP5V] 10:43:46 INFO: Using discovery server https://discovery-v4-2.syncthing.net/v2/?id=DVU36W
[UZP5V] 10:43:46 INFO: Using discovery server https://discovery-v4-3.syncthing.net/v2/?id=VK6HNJ
[UZP5V] 10:43:46 INFO: Using discovery server https://discovery-v6-1.syncthing.net/v2/?id=SR7AAR
[UZP5V] 10:43:46 INFO: Using discovery server https://discovery-v6-2.syncthing.net/v2/?id=DVU36W
[UZP5V] 10:43:46 INFO: Using discovery server https://discovery-v6-3.syncthing.net/v2/?id=VK6HNJ
[UZP5V] 10:43:46 INFO: TCP listener ([::]:22000) starting
[UZP5V] 10:43:46 INFO: Device D75YGL is "or" at [dynamic]
[UZP5V] 10:43:46 INFO: Device KI3N7U is "Pk" at [dynamic]
[UZP5V] 10:43:46 INFO: Device Q2NR77 is "Ey" at [dynamic]
[UZP5V] 10:43:46 INFO: Device UZP5VJ is "sd" at [dynamic]
[UZP5V] 10:43:46 INFO: Device YGUGYH is "se" at [dynamic]
[UZP5V] 10:43:47 INFO: Completed initial scan (rw) of folder pk
[UZP5V] 10:43:47 INFO: Completed initial scan (rw) of folder sp
[UZP5V] 10:43:47 INFO: GUI and API listening on [::]:8384
[UZP5V] 10:43:47 INFO: Access the GUI via the following URL: https://127.0.0.1:8384/
[UZP5V] 10:43:48 INFO: Completed initial scan (rw) of folder ad
[UZP5V] 10:43:48 INFO: Completed initial scan (rw) of folder pl
[UZP5V] 10:43:48 INFO: Completed initial scan (rw) of folder as
[UZP5V] 10:43:48 INFO: Completed initial scan (rw) of folder dt
[UZP5V] 10:43:53 INFO: New NAT port mapping: external TCP address 109.***.***.40:51212 to local address 0.0.0.0:22000.
[UZP5V] 10:43:56 INFO: Completed initial scan (rw) of folder Sy
[UZP5V] 10:43:58 INFO: New NAT port mapping: external TCP address 109.***.***.40:57755 to local address 0.0.0.0:22000.
[UZP5V] 10:43:58 INFO: Detected 2 NAT devices
[UZP5V] 10:44:00 INFO: Completed initial scan (rw) of folder mp
[UZP5V] 10:44:01 INFO: Established secure connection to KI3N7U at 192.168.1.11:22000-192.168.1.254:50697 (TCP (Server))
[UZP5V] 10:44:01 INFO: Device KI3N7U client is "syncthing v0.14.2" named "Pk"
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "Sy" is delta index compatible (mlv=151484)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "ad" is delta index compatible (mlv=1833)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "dt" is delta index compatible (mlv=11477)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "is" is delta index compatible (mlv=147332)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "oy" is delta index compatible (mlv=151662)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "pl" is delta index compatible (mlv=22292)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "sp" is delta index compatible (mlv=151131)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "mp" is delta index compatible (mlv=147496)
[UZP5V] 10:44:01 INFO: Device KI3N7U folder "pk" is delta index compatible (mlv=141759)
[UZP5V] 10:44:09 INFO: Established secure connection to D75YGL at 192.168.1.11:12965-109.***.***.40:21204 (TCP (Client))
[UZP5V] 10:44:09 INFO: Device D75YGL client is "syncthing v0.14.2" named "or"
[UZP5V] 10:44:09 INFO: Device D75YGL folder "pk" is delta index compatible (mlv=141759)
[UZP5V] 10:44:17 INFO: Completed initial scan (rw) of folder oy
[UZP5V] 10:44:21 INFO: Completed initial scan (rw) of folder is
[UZP5V] 10:44:27 INFO: Completed initial scan (rw) of folder t0
[UZP5V] 10:44:32 INFO: Joined relay relay://163.172.210.93:22067
[UZP5V] 10:50:21 INFO: Established secure connection to YGUGYH at 192.168.1.11:22000-192.168.1.155:65511 (TCP (Server))
[UZP5V] 10:50:21 INFO: Device YGUGYH client is "syncthing v0.14.0" named "se"
[UZP5V] 12:35:08 INFO: Device KI3N7U folder "oy" is delta index compatible (mlv=151823)
Panic at 2016-07-27T12:35:08+01:00
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x38 pc=0x783ee9]

goroutine 31834 [running]:
panic(0xbded80, 0xc82000e110)
    /usr/local/go/src/runtime/panic.go:481 +0x3e6
github.com/syncthing/syncthing/lib/connections.(*Connection).ID(0xc82279f6b0, 0x0, 0x0, 0x0, 0x0)
    <autogenerated>:95 +0x59
github.com/syncthing/syncthing/lib/model.sendIndexes(0x8014e9b68, 0xc82279f6b0, 0xc8218fb590, 0xe, 0xc8203cfc00, 0xc821c3d040, 0x2510f)
    /home/buildslave/workspace/syncthing-release/src/github.com/syncthing/syncthing/lib/model/model.go:1207 +0x3c
created by github.com/syncthing/syncthing/lib/model.(*Model).ClusterConfig
    /home/buildslave/workspace/syncthing-release/src/github.com/syncthing/syncthing/lib/model/model.go:733 +0x2073

(the … log entry appears in all the panics so I assume it’s part of the output format, it’s not me)

Thanks. That’s fairly mysterious. I’ll need to ponder that for a while.

Do you by any chance have the logs from KI3N7U for the same event? I’m curious if it saw some connect/disconnect events this side didn’t log.

I had the issue 7889 on another machine (QNAP) and likely this one on my raspberry. Surprisingly, solving the tmp dir on the qnap seemed to have reliefed the issue on the raspberry. Here is the raspberry panic log.

panic-20160727-185140.log (5.5 KB)

I can’t be sure it’s connected, it’s just a “feeling”.

Happened on my other laptop today as well (0.14.2). I added a new device this morning. After messing up the folder setup, I deleted the folder and started the sync from scratch (effectively a download from other 2 devices).

I don’t have that device with me ATM, but let me know if you still need the logs and I can send them by tonight.

Behavior: the sync got stuck around 25% - local computer said Out of date, and other computers just said Syncing (25%) but 0bytes/sec.

I started monitoring logs and debugging but it fixed itself after a couple restarts and eventually synced completely (~30gb).

KI3N7.log (71.9 KB)

Hope that helps. Too big to paste in.

[HHO6K] 12:18:44 INFO: Starting usage reporting [HHO6K] 12:18:44 INFO: GUI and API listening on [::]:8880 [HHO6K] 12:18:44 INFO: Access the GUI via the following URL: http://127.0.0.1:8880/ [HHO6K] 12:18:45 INFO: Joined relay relay://192.168.21.2:22067 [HHO6K] 12:18:45 INFO: Completed initial scan (rw) of folder Khb_ScanDoc2 [HHO6K] 12:19:05 INFO: Device HBHOT6T-ZDP42HF-E55QV5A-NRH3TXB-LGNXFZR-VFICF62-SB2KDAN-4KMHLAW folder “Khb_ScanDoc” is delta index compatible (mlv=3800) Panic at 2016-07-28T12:19:05+10:00 panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x38 pc=0x784279]

goroutine 654 [running]: panic(0xbe00e0, 0xc82000e150) /usr/local/go/src/runtime/panic.go:481 +0x3e6 github.com/syncthing/syncthing/lib/connections.(*Connection).ID(0xc8205c0420, 0x0, 0x0, 0x0, 0x0) :95 +0x59 github.com/syncthing/syncthing/lib/model.sendIndexes(0x7f668031bce8, 0xc8205c0420, 0xc8220156b4, 0xb, 0xc821348300, 0xc8212ed360, 0xed8) /home/buildslave/workspace/syncthing-release/src/github.com/syncthing/syncthing/lib/model/model.go:1207 +0x3c created by github.com/syncthing/syncthing/lib/model.(*Model).ClusterConfig /home/buildslave/workspace/syncthing-release/src/github.com/syncthing/syncthing/lib/model/model.go:733 +0x2073

This has been solved in development build linked at the top of the page. We’ll make a new release with the fix soon.

Great, thanks for your (and the rest of the teams) tireless efforts!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.