"tahoe start" claims to have started when it didn't #1377
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
4 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1377
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
The problem that I reported in #1376 was caused by the gateway failing to start due to the port number already being taken. From its
twistd.log
:Looking back through my screen buffer, I see that it misled me into thinking that it had started:
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.
Zancas just had this problem, and I've had it several times since the last comment. I'm increasingly annoyed by it.
We're at a hack fest in Berlin and a new user is also having this problem. Now I'm annoyed enough to fix it :-)
See also #2147: web.port can conflict
Hey, does http://twistedmatrix.com/trac/ticket/823 fix this?? Or at least help?
"tahoe start" claims to have started when it didn't (due to port number conflict)to "tahoe start" claims to have started when it didn't(http://twistedmatrix.com/trac/ticket/823) has been fixed, so if it fixes this ticket, or at least makes it easier for us to fix this ticket, then someone should revisit this ticket.
(http://twistedmatrix.com/trac/ticket/823) makes twistd wait by default, so there is nothing we need to do in Tahoe-LAFS to enable it. We should test whether it actually helps in cases such as #2147.
Milestone renamed
moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders
In 04b34b6/trunk:
"tahoe start" is now deprecated