tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

startup failures non-obvious #2802

New issue
Closed
opened 2016-08-08 21:41:32 +00:00 by meejah · 2 comments
meejah commented 2016-08-08 21:41:32 +00:00
Owner
Copy link

If you start up a node with a magic-folder and for some reason the shared-folder can't be accessed you'll get a long exception in logs/twistd.log ending with allmydata.mutable.common.UnrecoverableFileError: no recoverable versions.

However, the node keeps running but will not do any magic-folder "stuff" any more. No matter what, the error printed to the log should be something suitable for a user (e.g. "can't access magic-folder directory X" or so).

We should either:

  • kill the entire node if this happens
  • keep re-trying (and re-logging the error)

I have seen this occasionally when running check_magicfolder_smoke.py tests but am unsure how to reliably repeat it. The obvious thing of turning off all the storage servers and re-starting the Alice (or Bob) client doesn't appear to be sufficient.

If you start up a node with a magic-folder and for some reason the shared-folder can't be accessed you'll get a long exception in `logs/twistd.log` ending with `allmydata.mutable.common.UnrecoverableFileError: no recoverable versions`. However, the node keeps running but will not do any magic-folder "stuff" any more. No matter what, the error printed to the log should be something suitable for a user (e.g. "can't access magic-folder directory X" or so). We should either: - kill the entire node if this happens - keep re-trying (and re-logging the error) I have seen this occasionally when running `check_magicfolder_smoke.py` tests but am unsure how to reliably repeat it. The obvious thing of turning off all the storage servers and re-starting the Alice (or Bob) client doesn't appear to be sufficient.
tahoe-lafs added the
code-frontend-magic-folder
normal
defect
1.11.0
 labels 2016-08-08 21:41:32 +00:00
tahoe-lafs added this to the undecided milestone 2016-08-08 21:41:32 +00:00
meejah commented 2016-08-08 22:30:35 +00:00
Author
Owner
Copy link

Okay there's a way to repeat: run check_magicfolder_smoke.py, then run it with kill argv, then start just one of the storage nodes, then start Alice.

Alice will be when_connected_enough because there will be 2 storage servers connected (alice, plus the one storage node) so MagicFolder.ready is called, but this fails because the DMD can't be retrieved...

Okay there's a way to repeat: run `check_magicfolder_smoke.py`, then run it with `kill` argv, then start just one of the storage nodes, then start Alice. Alice will be `when_connected_enough` because there will be 2 storage servers connected (alice, plus the one storage node) so `MagicFolder.ready` is called, but this fails because the DMD can't be retrieved...
exarkun commented 2020-06-30 13:45:05 +00:00
Author
Owner
Copy link

magic-folder has been split out into a separate project - https://github.com/leastauthority/magic-folder

magic-folder has been split out into a separate project - <https://github.com/leastauthority/magic-folder>
tahoe-lafs added the
somebody else's problem
 label 2020-06-30 13:45:05 +00:00
exarkun closed this issue 2020-06-30 13:45:05 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No milestone
undecided
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2802
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?