Linux IDS 7.30 Error in /var/log/messages (kernel: dupfd: fd 1875, max 1024)

Hi, when I shutdown IDS 7.30 with "onmonitor" I get the following messages in "/var/log/messages": ---------------------- cut --------------------- kernel: dupfd: fd 1875, max 1024 kernel: dupfd: fd 1874, max 1024 kernel: dupfd: fd 1873, max 1024 kernel: dupfd: fd 1872, max 1024 ---------------------- cut ---------------------- But when I shutdown the Server with "onmode" this error will not occur. -- Regards Robert Held ______________________________________________________ e-mail: rheld@prounix.de

Robert Held wrote: > > Hi, > > when I shutdown IDS 7.30 with "onmonitor" I get the following messages > in "/var/log/messages": > ---------------------- cut --------------------- > kernel: dupfd: fd 1875, max 1024 > kernel: dupfd: fd 1874, max 1024 > kernel: dupfd: fd 1873, max 1024 > kernel: dupfd: fd 1872, max 1024 > ---------------------- cut ---------------------- > But when I shutdown the Server with "onmode" this error will not occur. > > -- > Regards > > Robert Held > > ______________________________________________________ > e-mail: rheld@prounix.de -- I get the same messages and it means the number of File-Discriptors ist to small. For Informix fd should be greather 3000. In other UNIX Sytems with kernel-tune tools can increase this number and generate a new kernel. but I don't know how to do this under Linux. Perhaps it resolves the error "IDS 7.30 Linux Edition cancels Connection to a Client" I wrote this week in Informix-news-Group. Do you know how to increase the number of File-Discriptors? --Regards Torsten Achatz

Torsten Achatz wrote: > Robert Held wrote: > > > > Hi, > > > > when I shutdown IDS 7.30 with "onmonitor" I get the following messages > > in "/var/log/messages": > > ---------------------- cut --------------------- > > kernel: dupfd: fd 1875, max 1024 > > kernel: dupfd: fd 1874, max 1024 > > kernel: dupfd: fd 1873, max 1024 > > kernel: dupfd: fd 1872, max 1024 > > ---------------------- cut ---------------------- > > But when I shutdown the Server with "onmode" this error will not occur. > > > > -- > > Regards > > > > Robert Held > > > > ______________________________________________________ > > e-mail: rheld@prounix.de > > -- > > I get the same messages and it means the number of File-Discriptors ist > to small. > For Informix fd should be greather 3000. > In other UNIX Sytems with kernel-tune tools can increase this number and > generate a > new kernel. but I don't know how to do this under Linux. Perhaps it > resolves the error > "IDS 7.30 Linux Edition cancels Connection to a Client" I wrote this > week in Informix-news-Group. > Do you know how to increase the number of File-Discriptors? > > --Regards > > Torsten Achatz I have read a posting from David Williams who has made the following entry before he starts IDS: echo -n "Setting kernel parameters" echo "16384" > /proc/sys/fs/file-max echo "65536" > /proc/sys/fs/inode-max echo "5 128 64 256 15 3000 500 1884 2" > /proc/sys/vm/bdflush echo "0" > /proc/sys/vm/overcommit_memory echo "262144000" > /proc/sys/kernel/shmmax I do not test it jet -- Regards Robert Held

onmonitor is deleted off my hard drive. :-) I never ever ever use it, and don't recommend it for anyone to use it. Until it is rewritten into something more useful, and the screens don't look like they're falling, I won't use it. You don't need it to manage your server, all can be done from the command-line or the new web-based tools from Informix. If you want to change config parameters, that's what Vi is for. Onmonitor is just too risky of an app when your data matters. :-) Tim Robert Held wrote: > > Hi, > > when I shutdown IDS 7.30 with "onmonitor" I get the following messages > in "/var/log/messages": > ---------------------- cut --------------------- > kernel: dupfd: fd 1875, max 1024 > kernel: dupfd: fd 1874, max 1024 > kernel: dupfd: fd 1873, max 1024 > kernel: dupfd: fd 1872, max 1024 > ---------------------- cut ---------------------- > But when I shutdown the Server with "onmode" this error will not occur. > > -- > Regards > > Robert Held > > ______________________________________________________ > e-mail: rheld@prounix.de -- . .- .-- .--- .---- Tim Schaefer .----- tschaefe@bellsouth.net .---- http://www.inxutil.com .--- http://www.datad.com .-- .- .

There is ONE thing that you cannot do without onmonitor Tim. That being to change the value of any of the LTAPE* parameters and have the change take effect without having to bounce the engine. Onmonitor will change the ONCONFIG file but it will also change the value in shared memory. BTW I've never had a problem using onmonitor to modify the onconfig file. I do use it seldom in the last many years but once upon a time and once in a while now I still do. I dunno I don't use the pickax my father-in-law gave me (don't ask) often but it came in handy when I had to dig up a tree stump enough to cut it off below ground 2 years ago. I say don't throw any tool away. Art S. Kagel Tim Schaefer wrote: > > onmonitor is deleted off my hard drive. > > :-) > > I never ever ever use it, and don't recommend it for anyone to use it. > Until it is rewritten into something more useful, and the screens don't > look like they're falling, I won't use it. You don't need it to manage > your server, all can be done from the command-line or the new web-based > tools from Informix. If you want to change config parameters, that's what > Vi is for. Onmonitor is just too risky of an app when your data matters. > > :-) > > Tim > > Robert Held wrote: > > > > Hi, > > > > when I shutdown IDS 7.30 with "onmonitor" I get the following messages > > in "/var/log/messages": > > ---------------------- cut --------------------- > > kernel: dupfd: fd 1875, max 1024 > > kernel: dupfd: fd 1874, max 1024 > > kernel: dupfd: fd 1873, max 1024 > > kernel: dupfd: fd 1872, max 1024 > > ---------------------- cut ---------------------- > > But when I shutdown the Server with "onmode" this error will not occur. > > > > -- > > Regards > > > > Robert Held > > > > ______________________________________________________ > > e-mail: rheld@prounix.de > > -- > . > .- > .-- > .--- > .---- Tim Schaefer > .----- tschaefe@bellsouth.net > .---- http://www.inxutil.com > .--- http://www.datad.com > .-- > .- > .

In article <38345ED6.2872B0C9@bloomberg.net>, Art S. Kagel <kagel@bloomberg.net> writes >There is ONE thing that you cannot do without onmonitor Tim. That being >to change the value of any of the LTAPE* parameters and have the change >take effect without having to bounce the engine. Onmonitor will change ?? I've changing it to /dev/null and back an ontape noticed it fine??!! >the ONCONFIG file but it will also change the value in shared memory. BTW >I've never had a problem using onmonitor to modify the onconfig file. I >do use it seldom in the last many years but once upon a time and once in >a while now I still do. I dunno I don't use the pickax my father-in-law >gave me (don't ask) often but it came in handy when I had to dig up a tree >stump enough to cut it off below ground 2 years ago. I say don't throw >any tool away. > >Art S. Kagel > >Tim Schaefer wrote: >> >> onmonitor is deleted off my hard drive. >> >> :-) >> >> I never ever ever use it, and don't recommend it for anyone to use it. >> Until it is rewritten into something more useful, and the screens don't >> look like they're falling, I won't use it. You don't need it to manage >> your server, all can be done from the command-line or the new web-based >> tools from Informix. If you want to change config parameters, that's what >> Vi is for. Onmonitor is just too risky of an app when your data matters. >> >> :-) >> >> Tim >> >> Robert Held wrote: >> > >> > Hi, >> > >> > when I shutdown IDS 7.30 with "onmonitor" I get the following messages >> > in "/var/log/messages": >> > ---------------------- cut --------------------- >> > kernel: dupfd: fd 1875, max 1024 >> > kernel: dupfd: fd 1874, max 1024 >> > kernel: dupfd: fd 1873, max 1024 >> > kernel: dupfd: fd 1872, max 1024 >> > ---------------------- cut ---------------------- >> > But when I shutdown the Server with "onmode" this error will not occur. >> > >> > -- >> > Regards >> > >> > Robert Held >> > >> > ______________________________________________________ >> > e-mail: rheld@prounix.de >> >> -- >> . >> .- >> .-- >> .--- >> .---- Tim Schaefer >> .----- tschaefe@bellsouth.net >> .---- http://www.inxutil.com >> .--- http://www.datad.com >> .-- >> .- >> . -- David Williams

Sorry Art, I couldn't use onmonitor if my life depended on it. It's just too unclear what some of the options mean, and yes, I did use it a long time ago. To me, if you have to change the LTAPE parameters, schedule a bounce, and you're done. I'd rather do that anyway, as many systems seem to benefit from an occasional reboot now and then, despite the occasional system that can never go off-line. If your system is never allowed to go-offline, then perhaps you have a point. I rather think it makes you a better UNIX Sysadmin or DBA to know how to use vi without complaining, and to know how to edit the ONCONFIG by hand. It's not that big of a deal, is certainly faster than diddling with onmonitor, and I know for sure what I'm getting into. :-) Tim "Art S. Kagel" wrote: > > There is ONE thing that you cannot do without onmonitor Tim. That being > to change the value of any of the LTAPE* parameters and have the change > take effect without having to bounce the engine. Onmonitor will change > the ONCONFIG file but it will also change the value in shared memory. BTW > I've never had a problem using onmonitor to modify the onconfig file. I > do use it seldom in the last many years but once upon a time and once in > a while now I still do. I dunno I don't use the pickax my father-in-law > gave me (don't ask) often but it came in handy when I had to dig up a tree > stump enough to cut it off below ground 2 years ago. I say don't throw > any tool away. > > Art S. Kagel > > Tim Schaefer wrote: > > > > onmonitor is deleted off my hard drive. > > > > :-) > > > > I never ever ever use it, and don't recommend it for anyone to use it. > > Until it is rewritten into something more useful, and the screens don't > > look like they're falling, I won't use it. You don't need it to manage > > your server, all can be done from the command-line or the new web-based > > tools from Informix. If you want to change config parameters, that's what > > Vi is for. Onmonitor is just too risky of an app when your data matters. > > > > :-) > > > > Tim > > > > Robert Held wrote: > > > > > > Hi, > > > > > > when I shutdown IDS 7.30 with "onmonitor" I get the following messages > > > in "/var/log/messages": > > > ---------------------- cut --------------------- > > > kernel: dupfd: fd 1875, max 1024 > > > kernel: dupfd: fd 1874, max 1024 > > > kernel: dupfd: fd 1873, max 1024 > > > kernel: dupfd: fd 1872, max 1024 > > > ---------------------- cut ---------------------- > > > But when I shutdown the Server with "onmode" this error will not occur. > > > > > > -- > > > Regards > > > > > > Robert Held > > > > > > ______________________________________________________ > > > e-mail: rheld@prounix.de > > > > -- > > . > > .- > > .-- > > .--- > > .---- Tim Schaefer > > .----- tschaefe@bellsouth.net > > .---- http://www.inxutil.com > > .--- http://www.datad.com > > .-- > > .- > > . -- . .- .-- .--- .---- Tim Schaefer .----- tschaefe@bellsouth.net .---- http://www.inxutil.com .--- http://www.datad.com .-- .- .