Node._startService failed: got stderr: 'ifconfig: en6: no media types?\n' #1064
Labels
No Label
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
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1064
Loading…
Reference in New Issue
Block a user
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?
Hi,
I configured successfully an introducer node on a debian box. Now I want to configure a client on my OSX box. So I've done :
I'm running :
And the log twistd.log is joined with the ticket.
Just a hint : it fails with en6 in the error log, and en6 has been created by PDAnet to do mobile network tethering.
Attachment twistd.log (11432 bytes) added
twistd log file
Thanks for the bug report. I don't recognize this and I'm just guessing, but could you try upgrading to the latest release of Twisted? It shows there that you are using Twisted 8.2.0. The current release is Twisted 10.0.0. Thanks!
well, after some investigations, it has not been created by vmware fusion, it's been created by PDAnet, a tool that does mobile phone tethering through USB... basically it's like a point-to-point tun interface, so I shall report the bug to them. Meanwhile, I'm gonna try to find out if I can't work out a patch to just catch that exception and make it ignore it (as that network interface is not meant to be used by tahoe-lafs)
Just so people don't have to click through to the twistd.log to see, here is the fatal error:
error launching tahoe on mac osxto Node._startService failed: got stderr: 'ifconfig: en6: no media types?\n'The only way I got around this bug is to launch PDAnet while lauching tahoe.
If someone can tell me how can I get full tracebacks in the twistd.log when launching tahoe, I may write a patch that ignores that kind of errors (as all is needed is to have at least one interface working, not all interfaces)... having it around may be useful for a future user that gets into the same kind of troubles I went into.
Replying to guyzmo:
What do you mean? Launching PDAnet while launching Tahoe-LAFS causes this bug to occur? Or does it cause this bug to stop occurring?
source:docs/logging.txt
See #1988
guyzmo: on your system, in the configuration that previously failed, does the command
ip addr
appear to work?In /tahoe-lafs/trac-2024-07-25/commit/a493ee0bb641175ecf918e28fce4d25df15994b6:
guyzmo, please try to reproduce this with current Tahoe-LAFS trunk.
Note that as a side-effect of the fix to #754 (which will be released in Tahoe-LAFS 1.10.1), setting
tub.location
without including "AUTO
" will skip the local IP auto-detection code entirely, thus allowing a workaround for this problem if the other changes on trunk didn't fix it.(https://github.com/tahoe-lafs/tahoe-lafs/pull/872) removed the use if ifconfig entirely
pull 872 merged in https://github.com/tahoe-lafs/tahoe-lafs/commit/25ee76104ad15e78b33a15643e330d2ec285dc89