Wrong owner on symlinks make IBM DB2's administrative server fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
db2exc (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
On db2exc 9.7.4-0lucid3, the init script tries to start the administration instance by:
- su-ing to the admin instance user
- calling "db2admin", which is in ~/das/bin/db2admin, which is in the PATH
This fails with the message "-su: das/bin/db2admin: Permission denied".
Calling /opt/ibm/
The kernel log reports "non-matching-uid symlink following attempted in sticky world-writable directory".
I think it's because:
- ~/das/bin is a symbolic link owned by root
- but ~/das has the sticky bit, so only root can follow the symbolic link
The same problem exists for several other symbolic links in ~/das/: conv function java lib msg
So maybe the whole administration instance is not installed using the right UID ?
Lionel Sausin
summary: |
- Wrong owner on symlink make administrative instance fail to start + Wrong owner on symlink make IBM DB2's administrative instance fail to + start |
summary: |
- Wrong owner on symlink make IBM DB2's administrative instance fail to - start + Wrong owner on symlinks make IBM DB2's administrative fail |
description: | updated |
summary: |
- Wrong owner on symlinks make IBM DB2's administrative fail + Wrong owner on symlinks make IBM DB2's administrative server fail |
Status changed to 'Confirmed' because the bug affects multiple users.