Open
Bug 541392
Opened 14 years ago
Updated 2 years ago
ssltunnel should have more detailed errors
Categories
(Testing :: Mochitest, enhancement)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: sgautherie, Unassigned)
References
()
Details
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.8pre) Gecko/20100122 SeaMonkey/2.0.3pre] (comm-1.9.1-win32-unittest/1264165841) (W2Ksp4) { INFO | automation.py | SSL tunnel pid: 852 ... failed to bind socket Shutting down... } (I'm not sure why I'm getting this atm, but:) It would be very helpful if the error reported: server_addr, listen_port, the result code, etc.
Comment 1•14 years ago
|
||
See also bug 541117.
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #0) > (I'm not sure why I'm getting this atm, but:) (Ftr, my SeaMonkey (maybe ChatZilla related?) connections were interfering... It works again: "Server listening on port 4443 with cert pgo server certificate".)
Comment 3•14 years ago
|
||
Serge, didn't it happen that you had been running another instance of ssltunnel? However, I'll add more detailed logging. I have added some new recently just to investigate an intermittent bug, but I plane to keep it, just clean that up and some more with it.
Assignee: nobody → honzab.moz
Status: NEW → ASSIGNED
Reporter | ||
Comment 4•14 years ago
|
||
(In reply to comment #3) > Serge, didn't it happen that you had been running another instance of > ssltunnel? That happened with some other bug(s) in the past. But not this time: I checked and eventually found that going offline with my SeaMonkey v1.5a "fixed" it. (That's why the socket details would (have) make finding the "culprit" application much easier ;->) Thanks for taking this bug :-)
Reporter | ||
Comment 5•14 years ago
|
||
(In reply to comment #1) > See also bug 541117. I'm not sure which code that bug wants "fixed". But a comment there references bug 541000 which relates to nsServerSocket.cpp which has the same need for details: http://mxr.mozilla.org/mozilla-central/search?string=failed+to+bind&case=on&find=%5C.c
Comment 6•12 years ago
|
||
Another vote for more detailed error messages. I just struck the same problem and it took alot of spelunking to determine that VMWare version 8 has a service related to "shared VMs" that by default grabs a couple of the same ports. If the error message clearly said that it failed to bind a specific port (and even suggested I look for other processes which are bound to the port) I think I would have guessed the root cause of the problem much quicker and not have annoyed the guys in #ateam about failure of my mochi tests to work with SLL enabled sites :)
Updated•10 years ago
|
Assignee: honzab.moz → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•