[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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 Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux source package in Lucid: Confirmed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux source package in Precise: Confirmed Status in linux-lts-trusty source package in Precise: Confirmed Status in linux source package in Trusty: Confirmed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux source package in Utopic: Confirmed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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. https://bugs.launchpad.net/bugs/1335478 Title: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux source package in Lucid: Confirmed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux source package in Precise: Confirmed Status in linux-lts-trusty source package in Precise: Confirmed Status in linux source package in Trusty: Confirmed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux source package in Utopic: Confirmed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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/bugs/1335478 Title: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Committed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Confirmed Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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 subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1335478 Title: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Committed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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 <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Committed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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 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 <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Committed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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 goes. If this re-appears again in a new kernel line (and you've come here from a google search from the future in your DeLorean, complete with Flux Capacitor), I also want to share another workaround I've found: build & install the vanilla kernel. I've tried it and it works. Here's a tutorial: https://veithen.github.io/2013/12/19/ubuntu-vanilla-kernel.html -- 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 <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Committed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
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.launchpad.net/bugs/1269053
Title:
IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel
3.5.0-45.68
Status in linux package in Ubuntu:
Fix Released
Status in linux-armadaxp package in Ubuntu:
Invalid
Status in linux-ec2 package in Ubuntu:
Invalid
Status in linux-lts-quantal package in Ubuntu:
Invalid
Status in linux-lts-raring package in Ubuntu:
Invalid
Status in linux-lts-saucy package in Ubuntu:
Invalid
Status in linux-ti-omap4 package in Ubuntu:
Invalid
Status in linux source package in Lucid:
Invalid
Status in linux-armadaxp source package in Lucid:
Invalid
Status in linux-ec2 source package in Lucid:
Invalid
Status in linux-lts-quantal source package in Lucid:
Invalid
Status in linux-lts-raring source package in Lucid:
Invalid
Status in linux-lts-saucy source package in Lucid:
Invalid
Status in linux-ti-omap4 source package in Lucid:
Invalid
Status in linux source package in Precise:
Fix Released
Status in linux-armadaxp source package in Precise:
Fix Released
Status in linux-ec2 source package in Precise:
Invalid
Status in linux-lts-quantal source package in Precise:
Fix Released
Status in linux-lts-raring source package in Precise:
Fix Released
Status in linux-lts-saucy source package in Precise:
Fix Released
Status in linux-ti-omap4 source package in Precise:
Fix Released
Status in linux source package in Quantal:
Fix Released
Status in linux-armadaxp source package in Quantal:
Fix Released
Status in linux-ec2 source package in Quantal:
Invalid
Status in linux-lts-quantal source package in Quantal:
Invalid
Status in linux-lts-raring source package in Quantal:
Invalid
Status in linux-lts-saucy source package in Quantal:
Invalid
Status in linux-ti-omap4 source package in Quantal:
Fix Released
Status in linux source package in Saucy:
Fix Released
Status in linux-armadaxp source package in Saucy:
Invalid
Status in linux-ec2 source package in Saucy:
Invalid
Status in linux-lts-quantal source package in Saucy:
Invalid
Status in linux-lts-raring source package in Saucy:
Invalid
Status in linux-lts-saucy source package in Saucy:
Invalid
Status in linux-ti-omap4 source package in Saucy:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux-armadaxp source package in Trusty:
Invalid
Status in linux-ec2 source package in Trusty:
Invalid
Status in linux-lts-quantal source package in Trusty:
Invalid
Status in linux-lts-raring source package in Trusty:
Invalid
Status in linux-lts-saucy source package in Trusty:
Invalid
Status in linux-ti-omap4 source package in Trusty:
Invalid
Bug description:
Something has changed in Ubuntu's Kernel 3.5.0-45 32 & 64-bit Intel,
has prevented IBM Domino's
"/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root
(setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3,
and HTTP processes. The IBM Domino Application Server's parent process
"/opt/ibm/domino/notes/latest/linux/server" runs as a Service Account
or a normal non-admin user, that launches "bindsock"and others like
"http", "ldap"
In the Live Domino Console we're seeing the Application Server report:
"Listener failure: 'bindsock' is missing, not executable, not owned by
root, not setuid root or user needs net_privaddr privilege."
Another thing in the Live Domino Console, which is unusual is:
"Error_CmdToDo_INVAL"... might be an IBM thang.
A number of us have to hold back the kernel now and there's lots of
scratching going on.
http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=485F5F092833BCBE85257C33006AC7A3
It does seem to be limited to IBM Domino's "bindsock" binary and other
things are just fine, such as Nginx.
I have attached some files within the zip "ibm-domino-bindsock_strace.zip"
>>bindsock_binary_strace.txt
This is just running strace against the binary that isn't running in any
process.
>> domino-server-pid1052_strace-f.txt
The IBM Domino Application Server
("/opt/ibm/domino/notes/latest/linux/server") is running as PID 1052 so this is
what I applied "strace -f" to and towards the end, I told "server" to start the
"http" process ("l http") which would then try launch "bindsock" (I hope).
Hopeully this first attempt at strace provides some good info for you
kind folks :-)
Many thanks
MR
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-45-generic 3.5.0-45.68~precise1
ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26
Uname: Linux 3.5.0-45-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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 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/1335478 Title: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Released Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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/1335478 Title: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Released Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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 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 <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Committed Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335478] Re: A new instance of IBM Domino 'bindsock' cannot bind to ports <1024 Kernel 3.13.0-29 and above
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: "There is a known issue with SLES 12 where bindsock has issues. Before we can support SLES 12 and any other newer kernel with this issue, we will have to identify the issue and get it fixed - bindsock and it's code has never changed in this area so the issue is a change in behavior in the kernel". So, there is hope that there may be a future fixpack(s)(9.0.1 FP3?) where the issue may be addressed on the bindsock side. But, as one of my favorite quotes goes, "Hope? Let me tell you something, my friend. Hope is a dangerous thing. Hope can drive a man insane. It's got no use on the inside. You'd better get used to that idea." -Red, Shawshank Redemption -- 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 <1024 Kernel 3.13.0-29 and above Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Released Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Starting with kernels 3.2.0-64 and 3.13.0-29 Something has changed to once again that prevents IBM Domino's "/opt/ibm/domino/notes/latest/linux/bindsock" binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The Domino server reports the following: : "Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege." This is the same behaviour that was reported and subsequently corrected in Bug # 1269053 === break-fix: dbb490b96584d4e958533fb637f08b557f505657 6a2a2b3ae0759843b22c929881cc184b00cc63ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
