dmesg (bis)

[bouguera]

hi stefan
hi robin

i give you another informations

i saw with sam that my
nfile = 790
nproc = 276
maxusers=32
npty=60
nstrpty=60
everything works ok since 1998 with the same parameters.

i just change an IP adr of host and printers.

when i use informix , there are errors :
. cannot open system catalog
. unable to create pipes


in syslog i have

vmunix: file: table is full

after few minutes all it's work ok

could you confirm me if i increase nfile
i will resolve my problem.

regards

[linuxfan]

Hi,

Looks like you are hitting the nfile limit only when starting the database.

I would increase the nfile to about 1200 and see the usage, if you are still getting the error then increase it to 1600

To increase nfile parameter, you can use SAM and increase nfile to 1200 and reboot the system or if you want to do it manually

1. cd /stand/build
2. /usr/lbin/system_prep -s /stand/build/system
3. Edit the system file and increase nfile (1200)
4. mk_kernel
5. cd /stand
6. mv system system.prev
7. mv vmunix vmunix.prev
8. mv build/system .
9. mv build/vmunix .
10. shutdown -ry now

-HTH
Ramesh

[Santosh Nair_1]

The error in /var/adm/syslog/syslog.log indicates that the nfiles kernel parameter limit has been hit. Increase this parameter (requires a reboot).

-Santosh

[Joseph Chakkery]

Hello,

I think informix keeps the information of host when it initializing. Like Sqlhosts file in $INFORMIXHOME/etc. Since u have changed the IP of host machine, Informix engine may not be liking it and spawning proceses.

Can u check the onling log and find out any errors in that. Also check the /etc/rc.log for any errors.

Regards
Joe.

[Wodisch]

Hello,

since you will have to create a new kernel
anyway, why not do it right and modify more
parameters? You are using an installation
default kernel, after all - no good idea...

Candidates to be increased are:
max_thread_proc
maxdsiz
maxfiles
maxfiles_lim
maxswapchunks
maxuprc
nclist
nfile
ninode
nkthread
nproc
npty
nstrpty
nstrtel
semmns
semmni
shmmax

candidates to be decreased:
dbc_max_pct


most are increased by increasing "maxusers",
even if I do not like that approach for myself,
but if you do not know the details it is ok.

Read the output of tools like
dmesg
vmstat
sar -b
sar -v
glance or gpm

to get an idea how "full" your tables are,
and how much resources you are using. Then
increase alll of them by at least 25%

This NOT optimal but certainly better than what
you have got ;-)

HTH,
Wodisch