RE: shmget: [EEXIST][17]: key 52564801: shared memory already exists
Posted in 2004
Topics: Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration, Platform-Specific Issues
Hi Sergey.
This error messages means can not create shared memory.
Make sure output of ipcs command.
Probably shared memory key exists.
Try onmod -ky and oninit again.
OR
Reboot your machine.
Regards.
--
Tsutomu Ogiwara from Tokyo Japan.
ICQ#:168106592
>From: sshumilov@yahoo.com (Sergey)
>Reply-To: sshumilov@yahoo.com (Sergey)
>To: informix-list@iiug.org
>Subject: shmget: [EEXIST][17]: key 52564801: shared memory already exists
>Date: 30 Nov 2004 23:19:39 -0800
>
>Hi guys!
>Need some help with informix...
>
>here is what happens.
>on our Linux Red Hat 7 machine we have 3 versions of informix(7.3,
>9.2, 9.4)
>7.3 and 9.2 work fine after initialization, but 9.4 doesn't want to
>initialize.
>I also checked onconfig(s) and found that 7.3 and 9.2 use the same
>SHMBASE 0x10000000L and 9.4 use 0x44000000L... don't know if it can
>help you.
>
>here is part of online.log
>
>ue Nov 30 15:20:02 2004
>
>15:20:02 Event alarms enabled. ALARMPROG =
>'/iif94/etc/alarmprogram.sh'
>15:20:02 Booting Language <c> from module <>
>15:20:02 Loading Module <CNULL>
>15:20:02 Booting Language <builtin> from module <>
>15:20:02 Loading Module <BUILTINNULL>
>15:20:16 IBM Informix Dynamic Server Started.
>15:20:16 shmget: [EEXIST][17]: key 52564801: shared memory already>exists
>15:20:16 mt_shm_init: can't create resident segment>
>
>and part of onconfig file
>
># Physical Log Configuration
>
>PHYSDBS rootdbs # 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
>
>MSGPATH /iif94/online.log # System message log file path
>CONSOLE /dev/console # System console message path>
># To automatically backup logical logs, edit alarmprogram.sh and set
># BACKUPLOGS=Y
>ALARMPROGRAM /iif94/etc/alarmprogram.sh # Alarm program path
>TBLSPACE_STATS 1 # Maintain tblspace statistics>
># System Archive Tape Device
>
>TAPEDEV /dev/nul # Tape device path
>TAPEBLK 32 # Tape block size (Kbytes)
>TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes)>
># Log Archive Tape Device
>
>LTAPEDEV /dev/nul # Log tape device path
>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
>
>SERVERNUM 2 # Unique id corresponding to a OnLine instance
>DBSERVERNAME tester94 # Name of default database server
>DBSERVERALIASES # 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 0 # 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
>
>SHMBASE 0x44000000L # Shared memory base address>
>Please help... this machine must become our new production.
sending to informix-list
Related threads
- the longer you surf, the MORE $$$ you earn !!
- Store procedure
- emulation for Vt100
- extent size questions again ...