Yes, working for me too. Ubuntu 14.04 LTS x86. Thanks! I hope this gets
into the mainline kernel soon!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1335478
Title:
A new instance of IBM
Attaching dmesg... thanks again.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1335478/+attachment/4281221/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Andy, is there any way to try to prevent this from happening again like
some comments in the code? As mentioned by OP, this has happened before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
I will try to open a service request based on this information. Is there
anything more specific information about which of the fields is passing
on the junk?
Perhaps this could actually get fixed!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Thanks, Andy- I've provided all this info in PMR 41425,227,000.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1335478
Title:
A new instance of IBM Domino 'bindsock' cannot bind to ports
I have also tested kernel 3.13.0-44 on Trusty-Proposed and it solves the
bug. I have modified the tag verification-needed-trusty to verification-
done-trusty.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are
I'm working with IBM on this, trying to convince them to debug their
bindsock binary. The initial hurdle, which I may or may not be able to
overcome, is the boilerplate "Ubuntu is not a supported OS." I've
offered to send them a virtual machine with the problem already present,
we'll see how this g
I have also commented on the new bug #1335478. Thanks to this bug being
fixed, I have a workaround- which is to install one of these FIXED
kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.laun
SPR YXYX9RA56Z "HTTP server can't be started with "Error - Unable to
Bind port 443 or 80" on SUSE12" has been resolved in 9.01 FP3 IF1 which
includes a fixed bindock! Just tested on Ubuntu with 3.13 kernel, SMTP
is binding and working properly there as well (unofficially, of course.)
;-)
--
You r
Clarification: I tested 9.0.1 FP3 IF1 on a pre-fixed kernel: 3.13.0-43
and SMTP binds properly with the new bindsock binary.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/133547
Ok, the PMR with IBM went about as expected.
"Unfortunately our level 3 support team will not pursue this issue
seeing how it is not seen on current supported platforms of Unix."
So much for bindsock itself getting fixed.
--
You received this bug notification because you are a member of Kernel
I pushed a little harder with IBM and found out that an SPR (Software
Problem Report) has been opened for the issue on SUSE 12, which also
exhibits the same behavior:
SPR # YXYX9RA56Z "Error - Unable to Bind port 443 or 80" on SUSE12.
My representative quoted one of the developers as saying:
"Th
12 matches
Mail list logo
