Re: oninit dies without error on RedHat 9

Your configuration looks OK. Try running the Redhad version of Solaris' "truss" command on the oninit process to see why it is failing at "Bringing up ADM VP...". One thought: there might be some kernel parameters that are necessary to bing up the instance listed in the release notes ($INFORMIXDIR/release/en_us/0333/IDS2000_9.4?). Good luck. Brice Avila Minneapolis, Minnesota marc@solarmetric.com (Marc Prud'hommeaux) wrote in message news:<ac498549.0306042352.6c627122@posting.google.com>... > A clean Informix 9.40 install on RedHat 9 (with glibc 2.3.2) seems to > have gone fine. I configured the INFORMIXDIR/etc/sqlhosts file > correctly (as per an installation I had on a previous release of > RedHat). I have a problem where "oninit" silently dies after "Bringing > up ADM VP..." with no error message. > > I have read various problems people have had with RH 9's version of > glibc. Is there any workaround I can use to get Informix working > (aside from installing a previous RH version, which isn't possible for > us to do), or should I just give up? > > > When running "oninit -ivy", I get: > > > Checking group membership to determine server run modesucceeded > Reading configuration file > '/opt/informix/etc/onconfig.ifxtest'...succeeded > Creating /INFORMIXTMP/.infxdirs ... succeeded > Creating infos file "/opt/informix/etc/.infos.ifxtest" ... > "/opt/informix/etc/.conf.ifxtest" ... succeeded > Writing to infos file ... succeeded > Checking config parameters...succeeded > Allocating and attaching to shared memory...succeeded > Creating resident pool 1382 kbytes...succeeded > Creating buffer pool 10002 kbytes...succeeded > Initializing rhead structure...succeeded > Initializing ASF ...succeeded > Initializing Dictionary Cache and SPL Routine Cache...succeeded > Bringing up ADM VP... > > ... and then it dies silently. The online.log is not very helpful; > this is all that is written to it: > > 03:39:08 Informix Dynamic Server Started. > > Thu Jun 5 03:39:08 2003 > > 03:39:08 Event alarms enabled. ALARMPROG = > '/opt/informix/etc/alarmprogram.sh' > 03:39:08 Booting Language <c> from module <> > 03:39:08 Loading Module <CNULL> > 03:39:08 Booting Language <builtin> from module <> > 03:39:08 Loading Module <BUILTINNULL> > > > > My configuration files follow. Any help at all would be greatly > appreciated. > > > INFORMIXDIR/etc/sqlhosts: > > ifxtest onipcshm calypso ifxtest_shm > ifxtest_net onsoctcp calypso ifxtest_net> > > > INFORMIXDIR/etc/onconfig.ifxtest: > > #************************************************************************** > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.std > # Description: Informix Dynamic Server Configuration Parameters > # > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME ifxtestdbs # Root dbspace name > ROOTOFFSET 0 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 30000 # Size of root dbspace (Kbytes)> > # Disk Mirroring Configuration Parameters > > MIRROR 0 # Mirroring flag (Yes = 1, No = 0) > MIRRORPATH # Path for device containing mirrored> root > MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> > # Physical Log Configuration > > PHYSDBS ifxtestdbs # Location (dbspace) of physical log > PHYSFILE 2000 # Physical log file size (Kbytes)> > # Logical Log Configuration > > LOGFILES 6 # Number of logical log files > LOGSIZE 2000 # Logical log size (Kbytes)> > # Diagnostics > > CONSOLE /dev/console # System console message path> > # To automatically backup logical logs, edit alarmprogram.sh and set > # BACKUPLOGS=Y > ALARMPROGRAM /opt/informix/etc/alarmprogram.sh # Alarm program path > TBLSPACE_STATS 1 # Maintain tblspace statistics> > # System Archive Tape Device > > TAPEBLK 32 # Tape block size (Kbytes) > TAPESIZE 10240 # Maximum amount of data to put on > tape (Kbytes)> > # Log Archive Tape Device > > LTAPEBLK 32 # Log tape block size (Kbytes) > LTAPESIZE 10240 # Max amount of data to put on log > tape (Kbytes)> > # Optical > > STAGEBLOB # Informix Dynamic Server staging area > > # System Configuration > > DBSERVERALIASES ifxtest # List of alternate dbservernames> #NETTYPE # Configure poll thread(s) for > nettype > DEADLOCK_TIMEOUT 60 # Max time to wait of lock in> distributed env. > RESIDENT 0 # Forced residency flag (Yes = 1, No = > 0)> > > MULTIPROCESSOR 0 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 1 # Number of user (cpu) vps > SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps> to one > > NOAGE 0 # Process aging > AFF_SPROC 0 # Affinity start processor > AFF_NPROCS 0 # Affinity number of processors> > # Shared Memory Parameters > > LOCKS 2000 # Maximum number of locks > BUFFERS 5000 # Maximum number of shared buffers > NUMAIOVPS # Number of IO vps > PHYSBUFF 32 # Physical log buffer size (Kbytes) > LOGBUFF 32 # Logical log buffer size (Kbytes) > CLEANERS 1 # Number of buffer cleaner processes > SHMVIRTSIZE 8000 # initial virtual shared memory> segment size > SHMADD 8192 # Size of new shared memory segments > (Kbytes) > SHMTOTAL 0 # Total shared memory (Kbytes). > 0=>unlimited > CKPTINTVL 300 # Check point interval (in sec) > LRUS 8 # Number of LRU queues > LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning> limit > LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit > TXTIMEOUT 300 # Transaction timeout (in sec) > STACKSIZE 32 # Stack size (Kbytes)> > # Dynamic Logging > # DYNAMIC_LOGS: > # 2 : server automatically add a new logical log when necessary. > (ON) > # 1 : notify DBA to add new logical logs when necessary. (ON) > # 0 : cannot add logical log on the fly. (OFF) > # > # When dynamic logging is on, we can have higher values for > LTXHWM/LTXEHWM, > # because the server can add new logical logs during long transaction > rollback. > # However, to limit the number of new logical logs being added, > LTXHWM/LTXEHWM > # can be set to smaller values. > # > # If dynamic logging is off,

Bruce- Unfortunately, strace (which, in my understanding, is the Linux equivalent of Solaris' "truss") doesn't like setuid binaries (such as oninit). I was able to get around this by un-setuiding oninit and then running oninit within strace turned on. Unfortunately, the last thing I see is that oninit forks, and then it just silently dies. Does anyone have any hints on how to successfully run oninit with strace? briceavila@hotmail.com (Brice Avila) wrote in message news:<c46e3ec5.0306050652.3433ac67@posting.google.com>... > Your configuration looks OK. > > Try running the Redhad version of Solaris' "truss" command on the > oninit process to see why it is failing at "Bringing up ADM VP...". > > One thought: there might be some kernel parameters that are necessary > to bing up the instance listed in the release notes > ($INFORMIXDIR/release/en_us/0333/IDS2000_9.4?). > > Good luck. > > Brice Avila > Minneapolis, Minnesota

marc@solarmetric.com (Marc Prud'hommeaux) writes: > Bruce- > > Unfortunately, strace (which, in my understanding, is the Linux > equivalent of Solaris' "truss") doesn't like setuid binaries (such as > oninit). I was able to get around this by un-setuiding oninit and then > running oninit within strace turned on. Unfortunately, the last thing > I see is that oninit forks, and then it just silently dies. You can attempt to get strace to follow forks with -f, or maybe even -F if they are doing vfork. Don't know whether -F works with RH9, though. You can use -u informix as argument to strace ot get it ot run as user informix. You have to be root. -- 'yvind Gjerstad Systems dept Tollpost-Globe AS N-6301 'ndalsnes/Norway E-mail: ogj@tollpost.no Phone: +47 7122 6663 Fax: +47 7122 6694