crt0: ERROR couldn't open /usr/lib/dld.sl

[Pradeep Saxena_1]

Hi
I have D-class server ruuning HPUX11.00, having 256MB RAM only, ruuning 3 oracle instances. Intermittently I am getting error even with the ls command also, which gets resolved automatically after certain time, I hope this may be related to resource crunch, can some one please let me know the possible solution of this problem. #ls
crt0: ERROR couldn't open /usr/lib/dld.sl errno:000000023

[Shahul]

Hi

I think this is a patch related problem. Please load recent patch available for dld.sl and try.

Best of luck
Shahul

[Pradeep Saxena_1]

Sahul
Thanx for reply, do you have idea of any specific patch required for above problem.

[KapilRaj]

Hi Mr. Saxena,

You can try loading Software Critical patch bundle came with the OS.

At the same time please try one more thing mv /dev/rct* to a diff name. and do a reboot. These files are recreated by ioinitrc so no issues. These files should hv a permission 444 and owner & group should be bin:bin

Good luck,

kaps

[eran maor]

Hi

this error is happen because dld.sl can't load
any more files into memory.

do this menual for fixing the problem
Per the dld man page:

dld.sl - dynamic loader

DESCRIPTION
The /usr/lib/dld.sl program is the dynamic loader. In programs
that use shared libraries, /usr/lib/dld.sl is automatically
invoked at startup time by the startup file crt0.o. Identical
copies of crt0.o are kept in both /opt/langtools/lib/ and
/usr/ccs/lib/ directories. The dynamic loader is, itself, a
shared library, although it defines no symbols for use by user
programs.

The file table overflow error means that the system file table
is full. The system has reached the maximum amount of files that the
table can hold. This table keeps track of all open files. You can
increase this table by increasing the value of the 'nfile' kernel
parameter.

Per the nfile man page:

nfile

DESCRIPTION
nfile defines the maximum number of files that can be open
simultaneously, system-wide, at any given time.

Using SAM (System Administration Manager) to increase the nfile
value:

Note: This information applies to HP-UX 10.X and 11.X.

1. Start SAM.
2. Select the 'Kernel Configuration' subsystem.
3. Select the 'Configurable Parameters' subsystem.
4. Select the 'maxusers' kernel parameter.
5. Increase the 'maxusers' value.

Note: You usually double the 'maxusers' value. Increase this
value to meet your system needs.

6. Click 'OK'.
7. Verify that the nproc and nfile values were increased.
8. Select 'Action'.
9. Click 'Create New Kernel', and follow the instructions.

Warning: The system will reboot after you successfully rebuild
the kernel. You also have the option to defer the reboot.
Make sure that you stop all applications, such as Oracle,
that need to be stopped before the system reboots.

If you cannot use SAM to modify and build a new kernel, you can use
the command line to accomplish the same results:

Note: This procedure applies to HP-UX 10.X:

1. cd /stand/build

2. Create a new system file:

/usr/lbin/sysadm/system_prep -v -s ./system

3. Modify the new system file by increasing the maxusers parameter:

maxusers

4. Build a new kernel:

mk_kernel -s ./system

5. Backup your old kernel and system files:

mv /stand/vmunix /stand/vmunix.prev
mv /stand/system /stand/system.prev

6. Move the new kernel and system files to the proper place:

mv /stand/build/vmunix_test /stand/vmunix
mv /stand/build/system /stand/system

7. Reboot the system:

shutdown -r -y 0 or reboot -r


Note: This procedure applies to HP-UX 11.X:

1. cd /stand/build

2. Create a new system file:

/usr/lbin/sysadm/system_prep -v -s ./system

3. Use kmtune to view and modify kernel parameter:

A. Display the current value:

kmtune -q maxuser

B. Increment maxusers:

kmtune -s maxuser+

4. Build a new kernel:

mk_kernel -s ./system

5. Use kmupdate to schedule the re-location and shutdown-reboot
of the new kernel.

6. Reboot the system:

shutdown -r -y 0 or reboot -r

For your information:

maxusers

DESCRIPTION
maxusers allocates system resources according to the expected
number of simultaneous users on the system.

Why only increase maxusers? Increasing maxusers creates a domino
effect on other kernel parameters involved with this same type of
limited resources. Some of the parameters affected are nfile,
nflocks, nproc, unlocable_mem, and bufpages.

[Pradeep Saxena_1]

hi Kapil:
I do not have /dev/rct* file , rebuilding the kernel and reboot even does not creating the same...what next..
Hi Eran: As suggested by , I have increased the parameter values, and waiting if we face the error again. meanwhile if you could also lit something on the /dev/rct* file which I don't have here.

[Pradeep Saxena_1]

problem didn't appear again after increasing maxuser , thanks to all