[tahoe-lafs-trac-stream] [tahoe-lafs] #1377: "tahoe start" claims to have started when it didn't (due to port number conflict)
tahoe-lafs
trac at tahoe-lafs.org
Wed Jul 11 23:26:46 UTC 2012
#1377: "tahoe start" claims to have started when it didn't (due to port number
conflict)
-----------------------------+---------------------------------------------
Reporter: zooko | Owner: davidsarah
Type: defect | Status: assigned
Priority: major | Milestone: 1.11.0
Component: code- | Version: 1.8.2
nodeadmin | Keywords: cli tahoe-start error usability
Resolution: |
Launchpad Bug: |
-----------------------------+---------------------------------------------
Changes (by davidsarah):
* owner: nobody => davidsarah
* status: new => assigned
* component: unknown => code-nodeadmin
* milestone: undecided => 1.11.0
Comment:
stercor had this problem after accidentally configuring Apache to listen
on port 3456, and I've also had it once or twice. Putting it into
milestone 1.11.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1377#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list