[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-quantal (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-quantal (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-quantal (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-saucy (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Released ** Changed in: linux-lts-quantal (Ubuntu Trusty) Importance: Medium => Undecided ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: In Progress => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Assignee: Andy Whitcroft (apw) => (unassigned) ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => In Progress ** Changed in: linux-lts-saucy (Ubuntu Precise) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => In Progress ** Also affects: linux-lts-raring (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Quantal) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => In Progress ** Changed in: linux-lts-raring (Ubuntu Precise) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-lts-quantal (Ubuntu Precise) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Saucy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Saucy) Status: New => In Progress ** Changed in: linux (Ubuntu Saucy) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Quantal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Quantal) Status: New => In Progress ** Changed in: linux (Ubuntu Quantal) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Precise) Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/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-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” source package in Precise: Fix Committed Status in “linux-lts-quantal” source package in Precise: In Progress Status in “linux-lts-raring” source package in Precise: In Progress Status in “linux-lts-saucy” source package in Precise: In Progress Status in “linux” source package in Quantal: In Progress 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” source package in Saucy: In Progress 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” source package in Trusty: Fix Released 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” sou
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
I have submitted the patch for this issue to kernel-team@ for review and
application.
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
In Progress
Status in “linux-lts-raring” source package in Precise:
In Progress
Status in “linux-lts-saucy” source package in Precise:
In Progress
Status in “linux” source package in Quantal:
In Progress
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” source package in Saucy:
In Progress
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” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-45-generic N/A
linux-backports-modules-3.5.0-45-generic N/A
linux-firmware
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
Ok this patch has hit all of our upstream stable trees and will hit the
various kernels in the next SRU cycle. Note that this is not the next
kernel which will hit the archive for all releases, for precise it is
included in that very next kernel, other releases it will be the
following kernel.
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
In Progress
Status in “linux-lts-raring” source package in Precise:
In Progress
Status in “linux-lts-saucy” source package in Precise:
In Progress
Status in “linux” source package in Quantal:
In Progress
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” source package in Saucy:
In Progress
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” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generi
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: Invalid => In Progress
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
In Progress
Status in “linux-lts-raring” source package in Precise:
In Progress
Status in “linux-lts-saucy” source package in Precise:
In Progress
Status in “linux” source package in Quantal:
In Progress
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” source package in Saucy:
In Progress
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:
In Progress
Status in “linux” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-45-generic N/A
linux-backports-modules-3.5.0-45-generic N/A
linux-firmware
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: In Progress => Invalid
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
In Progress
Status in “linux-lts-raring” source package in Precise:
In Progress
Status in “linux-lts-saucy” source package in Precise:
In Progress
Status in “linux” source package in Quantal:
In Progress
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” source package in Saucy:
In Progress
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” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-45-generic N/A
linux-backports-modules-3.5.0-45-generic N/A
linux-firmware
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux (Ubuntu Quantal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Saucy)
Status: In Progress => Fix Committed
** Changed in: linux-lts-raring (Ubuntu Precise)
Status: In Progress => Fix Committed
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: In Progress => Fix Committed
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: In Progress => Fix Committed
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
Fix Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux” source package in Quantal:
Fix Committed
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” source package in Saucy:
Fix Committed
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” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
T
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Description changed:
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."
+ "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.
+ "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
+
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
- Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
- SHELL=/bin/bash
- TERM=xterm
- PATH=(custom, no user)
- LANG=en_GB.UTF-8
- LANGUAGE=en_GB:en
+ SHELL=/bin/bash
+ TERM=xterm
+ PATH=(custom, no user)
+ LANG=en_GB.UTF-8
+ LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
RelatedPackageVersions:
- linux-restricted-modules-3.5.0-45-generic N/A
- linux-backports-modules-3.5.0-45-generic N/A
- linux-firmware1.79.9
+ linux-restricted-modules-3.5.0-45-generic N/A
+ linux-backports-modules-3.5.0-45-generic N/A
+ linux-firmware1.79.9
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux-lts-quantal
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
+
+
+ break-fix: - db31c55a6fb245fdbb752a2ca4aefec89afabb06
** Tags added: linux-break-fix
--
You received this bug notification because you are a member of Ke
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed => Confirmed
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux” source package in Quantal:
Fix Committed
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” source package in Saucy:
Fix Committed
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” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-45-generic N/A
linux-backports-modules-3.5.0-45-generic N/A
linux-firmware
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Tags removed: linux-break-fix
** Tags added: kernel-bug-break-fix
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux” source package in Quantal:
Fix Committed
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” source package in Saucy:
Fix Committed
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” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-45-generic N/A
linux-backports-modules-3.5.0-45-generic N/A
linux-firmware1
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Description changed:
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MarkForUpload: True
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-45-generic
root=UUID=a2842a37-9023-4e21-8460-a565465b7f67 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-45-generic N/A
linux-backports-modules-3.5.0-45-generic N/A
linux-firmware1.79.9
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux-lts-quantal
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
-
- break-fix: - db31c55a6fb245fdbb752a2ca4aefec89afabb06
+ break-fix: 1661bf364ae9c506bc8795fef70d1532931be1e8
+ db31c55a6fb245fdbb752a2ca4aefec89afabb06
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
F
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
quantal' to 'verification-done-quantal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-quantal
--
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 Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
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 Committed
Status in “linux-armadaxp” source package in Quantal:
Fix Committed
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:
Confirmed
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:
Confirmed
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
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux-ti-omap4 (Ubuntu Quantal)
Status: Confirmed => Fix Committed
** Changed in: linux-ti-omap4 (Ubuntu Saucy)
Status: Confirmed => Fix Committed
--
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 Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
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 Committed
Status in “linux-armadaxp” source package in Quantal:
Fix Committed
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 Committed
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 Committed
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
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
Confirm fix resolves issue in Quantal. Tested 3.5.0-47-generic
#71~precise1-Ubuntu SMP Wed Feb 19 22:02:52 UTC 2014 x86_64 x86_64
x86_64
Many thanks !
** Tags removed: verification-needed-quantal
** Tags added: verification-done-quantal
--
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 Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
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 Committed
Status in “linux-armadaxp” source package in Quantal:
Fix Committed
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 Committed
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 Committed
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~precis
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
I still see this problem in 3.8.0-35. Should I see the fix in this
release too or was it fixed in 3.5.0 codestream only?
--
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 Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
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 Committed
Status in “linux-armadaxp” source package in Quantal:
Fix Committed
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 Committed
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 Committed
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
AlsaVe
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux-lts-quantal -
3.5.0-47.71~precise1
---
linux-lts-quantal (3.5.0-47.71~precise1) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1281900
[ Upstream Kernel Changes ]
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disabling even without CONFIG_EXPERT
- LP: #1277722
* i2c: i801
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux-lts-quantal -
3.5.0-47.71~precise1
---
linux-lts-quantal (3.5.0-47.71~precise1) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1281900
[ Upstream Kernel Changes ]
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disabling even without CONFIG_EXPERT
- LP: #1277722
* i2c: i801
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux - 3.5.0-47.71
---
linux (3.5.0-47.71) quantal; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1281828
[ Upstream Kernel Changes ]
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disabling even without CONFIG_EXPERT
- LP: #1277722
* i2c: i801: SMBus patch for Intel Avoton DeviceIDs
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux - 3.5.0-47.71
---
linux (3.5.0-47.71) quantal; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1281828
[ Upstream Kernel Changes ]
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disabling even without CONFIG_EXPERT
- LP: #1277722
* i2c: i801: SMBus patch for Intel Avoton DeviceIDs
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux-ti-omap4 - 3.5.0-239.55
---
linux-ti-omap4 (3.5.0-239.55) quantal; urgency=low
* Release Tracking Bug
- LP: #1281895
[ Paolo Pisati ]
* rebased on Ubuntu-3.5.0-47.71
[ Ubuntu: 3.5.0-47.71 ]
* Release Tracking Bug
- LP: #1281828
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disabling eve
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux-ti-omap4 - 3.5.0-239.55
---
linux-ti-omap4 (3.5.0-239.55) quantal; urgency=low
* Release Tracking Bug
- LP: #1281895
[ Paolo Pisati ]
* rebased on Ubuntu-3.5.0-47.71
[ Ubuntu: 3.5.0-47.71 ]
* Release Tracking Bug
- LP: #1281828
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disabling eve
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux-armadaxp - 3.5.0-1628.37
---
linux-armadaxp (3.5.0-1628.37) quantal-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1281897
* Rebase onto Ubuntu-3.5.0-47.71
[ Ubuntu: 3.5.0-47.71 ]
* Release Tracking Bug
- LP: #1281828
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disab
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug was fixed in the package linux-ti-omap4 - 3.5.0-239.55
---
linux-ti-omap4 (3.5.0-239.55) quantal; urgency=low
* Release Tracking Bug
- LP: #1281895
[ Paolo Pisati ]
* rebased on Ubuntu-3.5.0-47.71
[ Ubuntu: 3.5.0-47.71 ]
* Release Tracking Bug
- LP: #1281828
* Revert "mm: ensure get_unmapped_area() returns higher address than
mmap_min_addr"
- LP: #1277722
* net: clamp ->msg_namelen instead of returning an error
- LP: #1269053
* netfilter: nf_conntrack: avoid large timeout for mid-stream pickup
- LP: #1270237
* SELinux: Fix kernel BUG on empty security contexts.
- CVE-2014-1874
* lirc_zilog: Don't use dynamic static allocation
- LP: #1277722
* net: Fix "ip rule delete table 256"
- LP: #1277722
* ipv6: use rt6_get_dflt_router to get default router in rt6_route_rcv
- LP: #1277722
* random32: fix off-by-one in seeding requirement
- LP: #1277722
* bonding: don't permit to use ARP monitoring in 802.3ad mode
- LP: #1277722
* 6lowpan: Uncompression of traffic class field was incorrect
- LP: #1277722
* bonding: fix two race conditions in bond_store_updelay/downdelay
- LP: #1277722
* isdnloop: use strlcpy() instead of strcpy()
- LP: #1277722
* connector: improved unaligned access error fix
- LP: #1277722
* ipv4: fix possible seqlock deadlock
- LP: #1277722
* inet: prevent leakage of uninitialized memory to user in recv syscalls
- LP: #1277722
* atm: idt77252: fix dev refcnt leak
- LP: #1277722
* net: core: Always propagate flag changes to interfaces
- LP: #1277722
* net: rework recvmsg handler msg_name and msg_namelen logic
- LP: #1277722
* net: add BUG_ON if kernel advertises msg_namelen > sizeof(struct
sockaddr_storage)
- LP: #1277722
* packet: fix use after free race in send path when dev is released
- LP: #1277722
* inet: fix addr_len/msg->msg_namelen assignment in recv_error and rxpmtu
functions
- LP: #1277722
* ipv6: fix leaking uninitialized port number of offender sockaddr
- LP: #1277722
* net: update consumers of MSG_MORE to recognize MSG_SENDPAGE_NOTLAST
- LP: #1277722
* inet: fix possible seqlock deadlocks
- LP: #1277722
* ipv6: fix possible seqlock deadlock in ip6_finish_output2
- LP: #1277722
* af_packet: block BH in prb_shutdown_retire_blk_timer()
- LP: #1277722
* {pktgen, xfrm} Update IPv4 header total len and checksum after
tranformation
- LP: #1277722
* bridge: flush br's address entry in fdb when remove the
- LP: #1277722
* mmc: block: fix a bug of error handling in MMC driver
- LP: #1277722
* NFSv4: Update list of irrecoverable errors on DELEGRETURN
- LP: #1277722
* Update of blkg_stat and blkg_rwstat may happen in bh context. While
u64_stats_fetch_retry is only preempt_disable on 32bit UP system. This
is not enough to avoid preemption by bh and may read strange 64 bit
value.
- LP: #1277722
* ASoC: wm8990: Mark the register map as dirty when powering down
- LP: #1277722
* irq: Enable all irqs unconditionally in irq_resume
- LP: #1277722
* xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
- LP: #1277722
* libsas: fix usage of ata_tf_to_fis
- LP: #1277722
* crypto: authenc - Find proper IV address in ablkcipher callback
- LP: #1277722
* s390/crypto: Don't panic after crypto instruction failures
- LP: #1277722
* crypto: s390 - Fix aes-xts parameter corruption
- LP: #1277722
* crypto: ccm - Fix handling of zero plaintext when computing mac
- LP: #1277722
* ALSA: hda - Fix silent output on ASUS W7J laptop
- LP: #1277722
* net: smc91: fix crash regression on the versatile
- LP: #1277722
* ARM: footbridge: fix VGA initialisation
- LP: #1277722
* hpsa: do not discard scsi status on aborted commands
- LP: #1277722
* hpsa: return 0 from driver probe function on success, not 1
- LP: #1277722
* ALSA: hda - Another fixup for ASUS laptop with ALC660 codec
- LP: #1277722
* enclosure: fix WARN_ON in dual path device removing
- LP: #1277722
* powerpc/gpio: Fix the wrong GPIO input data on MPC8572/MPC8536
- LP: #1277722
* ASoC: wm8731: fix dsp mode configuration
- LP: #1277722
* cpuidle: Check for dev before deregistering it.
- LP: #1277722
* iwlwifi: dvm: don't override mac80211's queue setting
- LP: #1277722
* um: add missing declaration of 'getrlimit()' and friends
- LP: #1277722
* dm: fix truncated status strings
- LP: #1277722
* elevator: acquire q->sysfs_lock in elevator_change()
- LP: #1277722
* iommu/vt-d: Fixed interaction of VFIO_IOMMU_MAP_DMA with IOMMU address
limits
- LP: #1277722
* video: kyro: fix incorrect sizes when copying to userspace
- LP: #1277722
* Input: allow deselecting serio drivers even without CONFIG_EXPERT
- LP: #1277722
* Input: mousedev - allow disabling eve
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Tags removed: kernel-bug-break-fix
** Tags added: kernel-bug-break-fix-complete
--
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 Dr
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-saucy
--
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/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-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” source package in Precise:
Fix Committed
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux” source package in Quantal:
Fix Committed
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” source package in Saucy:
Fix Committed
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” source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Jan 14 15:33:47 2014
HibernationDevice: RESUME=UUID=474adefd-59c4-4582-8d03-3c570137809d
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType:
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-quantal (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-raring (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Quantal) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Saucy) Status: New => Invalid -- 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/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 Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Confirmed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Confirmed 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: Confirmed Status in “linux” source package in Saucy: Fix Committed 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: Confirmed 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 missi
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux (Ubuntu Lucid)
Status: New => Invalid
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: New => Invalid
** Changed in: linux-ti-omap4 (Ubuntu Precise)
Status: New => Fix Committed
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New => Fix Committed
** Changed in: linux-ti-omap4 (Ubuntu Quantal)
Status: New => Confirmed
** Changed in: linux-ti-omap4 (Ubuntu Saucy)
Status: New => Confirmed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: New => Confirmed
--
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 Committed
Status in “linux-armadaxp” source package in Precise:
Fix Committed
Status in “linux-ec2” source package in Precise:
Invalid
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux-ti-omap4” source package in Precise:
Fix Committed
Status in “linux” source package in Quantal:
Fix Committed
Status in “linux-armadaxp” source package in Quantal:
Confirmed
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:
Confirmed
Status in “linux” source package in Saucy:
Fix Committed
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:
Confirmed
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
"
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
IBM Domino is able to bind to ports lower than 1024. This is fixed in
"saucy-proposed"
Enabled "saucy-proposed"
Installed linux-image-server/saucy-proposed linux-headers-server/saucy-
proposed linux-headers-generic/saucy-proposed linux-image-generic/saucy-
proposed
Rebooted with new kernel: Linux mru64dom64-1 3.11.0-17-generic
#31-Ubuntu SMP Mon Feb 3 21:52:43 UTC 2014 x86_64 x86_64 x86_64
GNU/Linux
Thanks folks !!!
MR
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
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 Committed
Status in “linux-armadaxp” source package in Precise:
Fix Committed
Status in “linux-ec2” source package in Precise:
Invalid
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux-ti-omap4” source package in Precise:
Fix Committed
Status in “linux” source package in Quantal:
Fix Committed
Status in “linux-armadaxp” source package in Quantal:
Confirmed
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:
Confirmed
Status in “linux” source package in Saucy:
Fix Committed
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:
Confirmed
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 wo
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux (Ubuntu Precise)
Status: Fix Committed => Fix Released
** Changed in: linux-ti-omap4 (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
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 Committed
Status in “linux-ec2” source package in Precise:
Invalid
Status in “linux-lts-quantal” source package in Precise:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
Status in “linux-lts-saucy” source package in Precise:
Fix Committed
Status in “linux-ti-omap4” source package in Precise:
Fix Released
Status in “linux” source package in Quantal:
Fix Committed
Status in “linux-armadaxp” source package in Quantal:
Confirmed
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:
Confirmed
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:
Confirmed
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
Unam
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
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:
Confirmed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
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 Committed
Status in “linux-armadaxp” source package in Quantal:
Confirmed
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:
Confirmed
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:
Confirmed
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 Driv
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Confirmed => Fix Committed
--
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 Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
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 Committed
Status in “linux-armadaxp” source package in Quantal:
Confirmed
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:
Confirmed
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:
Confirmed
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
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Confirmed => Fix Committed
--
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 Committed
Status in “linux-lts-raring” source package in Precise:
Fix Committed
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 Committed
Status in “linux-armadaxp” source package in Quantal:
Fix Committed
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:
Confirmed
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:
Confirmed
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
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
Seems the bug reappeared in precise with 3.2.0-64-generic-pae.
3.2.0-61-generic-pae works.
I do not know which of the kernels in between work.
--
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
[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 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
I reported this as a new bug back almost a month ago - but to date,
while the status has been changed to confirmed, the bug remains
unassigned. I have tested 3.13.0-32 and the bug remains in this new
version as well.
--
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:
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
The bug now shows up in Trusty as of 3.13.0-30I know it was working
in 3.13.0-24
--
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
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
The bug is also present in 3.13.0-29 as well.
--
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.
AplayDevices: E
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
@Kit / @Sebastian -- ok the fix for the original bug appears to be
correctly applied. I believe this is a new form of this bug triggered
by the commit below:
commit dbb490b96584d4e958533fb637f08b557f505657
Author: Matthew Leach
Date: Tue Mar 11 11:58:27 2014 +
net: socket: error on a negative msg_namelen
As this is essentially a new bug, could one of you file a new bug
against the 'linux' package for me, and reference it here. I'll see
about some debugging to confirm this on that bug.
--
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") w
[Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
Reported as bug #1335478
Thanks
--
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.
AplayDevices: Error: [Errno
Re: [Kernel-packages] [Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to ports <1024 since recent kernel 3.5.0-45.68
I had to revert to Ubuntu server 13.04 that did not have the bug in order
to keep my business running on IBM Domino. Will this kernel fix work on
13.04? If not, I will not be able to test the fix.
73 & Cheers,
Ken Behrens
IBM Certified Advanced Application Developer Lotus Notes & Domino 7
MicroBlue Software, LLC
KB0YLN
E-mail: khbehr...@microbluesoftware.com
Web site: http://www.MicroBlueSoftware.com
From: Brad Figg
To: khbehr...@microbluesoftware.com
Date: 02/06/2014 11:50 AM
Subject:[Bug 1269053] Re: IBM Domino 'bindsock' cannot bind to
ports <1024 since recent kernel 3.5.0-45.68
Sent by:boun...@canonical.com
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-saucy
--
You received this bug notification because you are subscribed to the bug
report.
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-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? source package in Precise:
Fix Committed
Status in ?linux-lts-quantal? source package in Precise:
Confirmed
Status in ?linux-lts-raring? source package in Precise:
Fix Committed
Status in ?linux-lts-saucy? source package in Precise:
Fix Committed
Status in ?linux? source package in Quantal:
Fix Committed
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? source package in Saucy:
Fix Committed
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? source package in Trusty:
Fix Released
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
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.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No
