error message could be more detailed: "client node probably not started" #602

Closed
opened 2009-02-02 19:10:34 +00:00 by zooko · 3 comments

I just ran bin/tahoe start on Windows, and it said this:

STARTING c:\playground\allmydata\tahoe\.tahoe
client node probably not started

Looking in logs/twistd.log shows that it ends with:

2009-02-02 12:07:23-0700 [-]   File "c:\python25\lib\site-packages\twisted-8.1.0-py2.5-win32.egg\twisted\internet\posixbase.py", line 328, in listenTCP
2009-02-02 12:07:23-0700 [-]     p.startListening()
2009-02-02 12:07:23-0700 [-]   File "c:\python25\lib\site-packages\twisted-8.1.0-py2.5-win32.egg\twisted\internet\tcp.py", line 739, in startListening
2009-02-02 12:07:23-0700 [-]     raise CannotListenError, (self.interface, self.port, le)
2009-02-02 12:07:23-0700 [-] twisted.internet.error.CannotListenError: Couldn't listen on any:4070: (10048, 'Address already in use').
I just ran `bin/tahoe start` on Windows, and it said this: ``` STARTING c:\playground\allmydata\tahoe\.tahoe client node probably not started ``` Looking in `logs/twistd.log` shows that it ends with: ``` 2009-02-02 12:07:23-0700 [-] File "c:\python25\lib\site-packages\twisted-8.1.0-py2.5-win32.egg\twisted\internet\posixbase.py", line 328, in listenTCP 2009-02-02 12:07:23-0700 [-] p.startListening() 2009-02-02 12:07:23-0700 [-] File "c:\python25\lib\site-packages\twisted-8.1.0-py2.5-win32.egg\twisted\internet\tcp.py", line 739, in startListening 2009-02-02 12:07:23-0700 [-] raise CannotListenError, (self.interface, self.port, le) 2009-02-02 12:07:23-0700 [-] twisted.internet.error.CannotListenError: Couldn't listen on any:4070: (10048, 'Address already in use'). ```
zooko added the
code-frontend-cli
major
defect
1.2.0
labels 2009-02-02 19:10:34 +00:00
zooko added this to the undecided milestone 2009-02-02 19:10:34 +00:00

See also #71, which is about the "probably not started" being unreassuring, and #529, which is about difficult-to-detect breakage.

See also #71, which is about the "probably not started" being unreassuring, and #529, which is about difficult-to-detect breakage.

I think this is fixed by changeset:ac3b26ecf29c08cb .. anyone want to confirm?

I think this is fixed by changeset:ac3b26ecf29c08cb .. anyone want to confirm?
Author

This ticket was split into #71 and #529, as Brian wrote in comment:69270.

This ticket was split into #71 and #529, as Brian wrote in [comment:69270](/tahoe-lafs/trac-2024-07-25/issues/602#issuecomment-69270).
zooko added the
duplicate
label 2010-11-20 06:29:26 +00:00
zooko closed this issue 2010-11-20 06:29:26 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#602
No description provided.