Kbase 15433: Error 2601 caused by not able to reset user limit, very progress file permissions
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
FACT(s) (Environment):
UNIX
SYMPTOM(s):
Problems starting Progress session due to ulimit size.
Unable to set ulimit to <number>, errno=<number>, ulimit remains at <number>. (2601)
Unable to set ulimit to 4194303, errno=1, ulimit remains at xxx (2601)
The ulimit numbers displayed in the message are in 512-bytes units.
CAUSE:
When a PROGRESS session is initiated, PROGRESS checks the user's ulimit (maximum UNIX file size). If the ulimit is less than 2 GigaBytes, PROGRESS will set the user's ulimit for the PROGRESS session to 2 Giga Bytes. If the ulimit is already at 2 Giga Bytes or higher, it will remain unchanged.
The reason for this is so that the user can access PROGRESS database files that are up to the maximum size for a database file which is 2 Gig.
If PROGRESS can not change the user's ulimit, the warning 2601 will be displayed.
FIX:
To resolve this error, make sure the permissions of the PROGRESS executables (i.e., _progres, _mprosrv, _dbutil, etc.) are set to include the "setuserid" bit and that the owner of the executables is root.
For example:
chown root _progres
chmod 4775 _progres
for V9:
chmod 755 _sqlsrv2
chmod 755 _waitfor
When doing an "ls -l", the permissions for the executables should
look like this:
-rwsrwxr-x 1 root 716160 Jan 30 07:03 _mprosrv
-rwsrwxr-x 1 root 749060 Jan 30 07:03 _mprshut
-rwsrwxr-x 1 root 3333189 Jan 30 07:02 _progres
-rwsrwxr-x 1 root 1018200 Jan 30 07:05 _proutil
-rwsrwxr-x 1 root 808826 Jan 30 07:05 _rfutil