Opened at 2010-06-03T18:19:29Z
Closed at 2020-10-26T16:12:29Z
#1064 closed defect (fixed)
Node._startService failed: got stderr: 'ifconfig: en6: no media types?\n'
Reported by: | guyzmo | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | soon |
Component: | code-network | Version: | 1.6.1 |
Keywords: | tahoe-start mac error iputil transparency review | Cc: | |
Launchpad Bug: |
Description (last modified by zooko)
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 :
- % tahoe create-client
- then ~/.tahoe got created
- % tahoe start
- then it outputs :
STARTING /Users/guyzmo/.tahoe /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/twisted/persisted/sob.py:12: DeprecationWarning: the md5 module is deprecated; use hashlib instead import os, md5, sys /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/twisted/python/filepath.py:12: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha Removing stale pidfile /Users/guyzmo/.tahoe/twistd.pid client node probably started
I'm running :
- allmydata-tahoe: 1.6.1-r4328, foolscap: 0.5.1, pycryptopp: 0.5.17-r683, zfec: 1.4.7, Twisted: 8.2.0, Nevow: 0.10.0, zope.interface: 3.5.1, python: 2.6.1, platform: Darwin-10.3.0-i386-64bit, sqlite: 3.6.12, simplejson: 2.1.1, argparse: 1.1, pyOpenSSL: 0.7, pyutil: 1.7.7, zbase32: 1.1.1, setuptools: 0.6c15dev, pysqlite: 2.4.1
- (Snow Leopard) Darwin myhost 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
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.
Attachments (1)
Change History (17)
Changed at 2010-06-03T18:20:16Z by guyzmo
comment:1 Changed at 2010-06-03T18:35:09Z by zooko
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!
comment:2 Changed at 2010-06-04T16:11:23Z by guyzmo
Just a hint : it fails with en6 in the error log, and en6 has been created by vmware-fusion to connect to virtual machines (but it's not running).
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)
comment:3 Changed at 2010-06-12T23:50:01Z by davidsarah
- Component changed from unknown to code-network
- Keywords tahoe-start mac error added
comment:4 Changed at 2010-08-02T14:30:23Z by zooko
Just so people don't have to click through to the twistd.log to see, here is the fatal error:
12 2010-05-31 17:15:34+0200 [-] Unhandled Error 13 Traceback (most recent call last): 14 Failure: twisted.internet.utils._UnexpectedErrorOutput: got stderr: 'ifconfig: en6: no media types?\n' 15 16 2010-05-31 17:15:34+0200 [-] Node._startService failed, aborting 17 2010-05-31 17:15:34+0200 [-] [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.utils._UnexpectedErrorOutput'>: got stderr: 'ifconfig: en6: no media types?\n' 18 2010-05-31 17:15:34+0200 [-] ] 19 2010-05-31 17:15:34+0200 [-] calling os.abort() 20 2010-05-31 17:15:34+0200 [-] calling os.abort()
comment:5 Changed at 2010-08-02T16:08:19Z by zooko
- Summary changed from error launching tahoe on mac osx to Node._startService failed: got stderr: 'ifconfig: en6: no media types?\n'
comment:6 Changed at 2010-08-02T16:09:19Z by zooko
- Milestone changed from undecided to soon
comment:7 follow-up: ↓ 8 Changed at 2010-08-02T16:39:43Z by guyzmo
- Description modified (diff)
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.
comment:8 in reply to: ↑ 7 Changed at 2010-08-02T17:17:56Z by zooko
Replying to guyzmo:
The only way I got around this bug is to launch PDAnet while lauching tahoe.
What do you mean? Launching PDAnet while launching Tahoe-LAFS causes this bug to occur? Or does it cause this bug to stop occurring?
If someone can tell me how can I get full tracebacks in the twistd.log when launching tahoe,
comment:10 Changed at 2013-05-27T17:36:29Z by zooko
- Keywords iputil transparency added
comment:11 Changed at 2013-05-27T21:00:10Z by daira
- Owner changed from nobody to guyzmo
guyzmo: on your system, in the configuration that previously failed, does the command ip addr appear to work?
comment:12 Changed at 2013-06-25T18:15:57Z by Daira Hopwood <david-sarah@…>
comment:13 Changed at 2013-06-27T02:16:26Z by daira
guyzmo, please try to reproduce this with current Tahoe-LAFS trunk.
comment:14 Changed at 2015-03-27T10:49:02Z by daira
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.
comment:15 Changed at 2020-10-23T20:01:36Z by exarkun
- Keywords review added
- Owner guyzmo deleted
https://github.com/tahoe-lafs/tahoe-lafs/pull/872 removed the use if ifconfig entirely
comment:16 Changed at 2020-10-26T16:12:29Z by exarkun
- Resolution set to fixed
- Status changed from new to closed
twistd log file