Skip to content
This repository has been archived by the owner on Nov 2, 2018. It is now read-only.

WAL file is still present after clean shutdown/ causes WARN messages in log #3197

Open
2-Watts opened this issue Aug 9, 2018 · 0 comments
Open

Comments

@2-Watts
Copy link

2-Watts commented Aug 9, 2018

BUG REPORT

Stack Trace or error message
contractmanager.log

2018/08/07 18:54:08.157988 dependencies.go:247: STARTUP: Logging has started. Siad Version 1.3.3
2018/08/07 18:59:19.572545 writeaheadlog.go:287: WARN: WAL file detected, performing recovery after unclean shutdown.
2018/08/09 14:51:18.106770 dependencies.go:247: STARTUP: Logging has started. Siad Version 1.3.3
2018/08/09 14:56:48.817046 writeaheadlog.go:287: WARN: WAL file detected, performing recovery after unclean shutdown.

Expected Behavior
WAL file should be programmatically erased after correctly being processed.

How to reproduce it (as minimally and precisely as possible)

  1. cause to exist after shutdown: ~/Sia/host/contractmanager/contractmanager.wal
    Per my casual and amateur examination; writeaheadlog.go seems to indicate that both the tmp and old .wal files should be deleted automagically after being successfully processed and upon clean shutdown.
    (I am shutting down via './siac stop' and starting via './siad -M cghtw')

Possibly a separate issue, or non-issue at all, is that also 'contractmanager.wal_temp' file remains, after clean shutdown.

Environment

  • Sia version: 1.3.3
  • OS: Linux Ubuntu 16.04
huetsch pushed a commit to HyperspaceApp/Sia that referenced this issue Oct 23, 2018
Checkforipviolations step 2

Closes NebulousLabs#3197

See merge request NebulousLabs/Sia!3236
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant