3. Error on Siad

Error on Siad

  • C

    I got this on Siad, any ideas why?

    A lock was held for too long, id '755415'. Call stack:
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:101'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:98'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/gat
    eway.go:121'
    A lock was held for too long, id '755554'. Call stack:
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:101'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:98'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/gat
    eway.go:121'
    A lock was held until deadlock, subsequent call to unlock failed. id '755415'. C
    all stack:
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:107'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:98'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/gat
    eway.go:121'
    A lock was held until deadlock, subsequent call to unlock failed. id '755554'. C
    all stack:
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:109'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/nod
    es.go:98'
    File: '/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/gat
    eway.go:121'

    0
  • admins

    It indicates a deadlock happening in the gateway. Do you know what version you were running?

    0
  • C

    Version 6.0. It still seems to be running ok though and picking up contracts.

    0
  • V

    I had similar logs and I suppose this to be linked with high disk i/o activity on the same drive where sia blockchain resides. May be coincidence as well, but I saw these logs when running deduplication job. Now it's finished and the errors no longer appear. Though I also restarted siad, so might be just an unstable bug.

    0
  • J

    Thanks for the crashlog.

    Veber is right, this is caused by the gateway saving the node list to disk in the RelayNode RPC. This error was more likely to occur during high i/o ativity. The RelayNode RPC has been removed for other reasons, so this particular error cannot occur in newer versions. I'll look into reducing the gateway's i/o as a similar error could occur if you try to connect to many peers at once.

    0
Log in to reply