Re: Hope your response AGAIN: How to modify the msgsys configuration in kernel on solaris 8

[xugang]

On 9月15日, 下午9时50分, 旭刚 宋 <xugangs...@gmail.com> wrote:
> confused, anyone else knows?
>
> On 9月15日, 上午9时14分, 旭刚 宋 <xugangs...@gmail.com> wrote:
>
>
>
> > Dear all:
>
> >     I have posted the title with the following link about the
> > modification of MSGMAX parameter
>
> > of msysys in solaris 8 and gotten the feedback from Jim and brandon
> > (Thanks all). I have tried but
>
> > still not working.
>
> > Group: comp.unix.solaris
> > Title: Can't modify the MSGMAX configuration successfully for IPC
> > Queue on solaris 8
> > link:http://groups.google.com/group/comp.unix.solaris/browse_thread/thread...
> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> >    In the previous days, we have tried the following method, all turns
> > out no working on the server,
>
> > what's the matter? We are in deep doubt!!! Could you give us some
> > suggestions?
>
> >    Thanks again !
>
> > Method 1:
>
> >   From Brandon:
>
> >   >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> >  ?? ? <xugangs...@gmail.com> wrote:
> >   >        forceload: sys/msgsys
>
> > >>>Don't put whitespace in front.  Not '      forceload: sys/msgsys', but just
> > >>>'forceload: sys/msgsys'.
> > >>>Did you reboot afterward?  You have to reboot to make changes in /etc/system
> > >>>take effect.
>
> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> > We remove the whitespace before modification line and restart the
> > server, no working.
>
> > ---------------------------------------------------------------------------­­-------------------------------------------------------------------
>
> > Method 2:
>
> > According to the article: SUMMARY: HELP tuning SEMAPHORES on solaris
> > on GROUP: info.sun-managers
>
> > >>I received several responses for this and most helped.
> > >>Finally here is what I did to solve the problem.
> > >>I added the following entries to the /etc/system file
> > >>(values obtained from Informix release notes):
> > >>forceload: sys/shmsys
> > >>forceload: sys/msgsys
> > >>forceload: sys/semsys
> > >>set enable_sm_wa = 1
> > >>set shmsys:shminfo_shmmax=268435456
> > >>set semsys:seminfo_semmap=64
> > >>set semsys:seminfo_semmni=4096
> > >>set semsys:seminfo_semmns=4096
> > >>set semsys:seminfo_semmnu=4096
> > >>set semsys:seminfo_semume=64
> > >>set shmsys:shminfo_shmmin=100
> > >>set shmsys:shminfo_shmmni=100
> > >>set shmsys:shminfo_shmseg=100
> > >>And *this is important*, I did a boot -r to make the system
> > >>understand the changes. Alternatively you can make a file
> > >>called /reconfigure and reboot.
>
> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> > We tried the reconfiguration boot on the server by typing the
> > following command on the prompt:
>
> > reboot -- -r  , no working again. And then we tried another
> > reconfiguration boot method: touch a file
>
> > named <reconfigure> on the root directory and reboot, no working again
> > again.
>
> > ---------------------------------------------------------------------------­­--------------------------------------------------------------
>
> > Method 3:
>
> > According to the feedback from our IT supporter, update the parameter
> > value we want to update from
>
> > 4096 to 65535, and reboot the server. No working.....
>
> > ---------------------------------------------------------------------------­­--------------------------------------------------------------
>
> > Method 4:
>
> > Copy the system file which on the other server which is working to our
> > server instead of modifying
>
> > our own and restart the server. No working....
>
> > ---------------------------------------------------------------------------­­----------------------------------------------------------------
>
> > Till now, We have tried the methods which posted on the internet, but
> > it still not working. we all
>
> > doubts what's the matter? And now we have no other thinking, but hope
> > you can give some
>
> > suggestions.
>
> > Thanks all!
>
> > BR.
> > xugang
>
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> > The following part is the /etc/system file we modified:
>
> > >> *ident "@(#)system        1.18    97/06/27 SMI" /* SVR4 1.5 */
> > >> *
> > >> * SYSTEM SPECIFICATION FILE
> > >> *
>
> > >> * moddir:
> > >> *
> > >> *      Set the search path for modules.  This has a format similar to the
> > >> *      csh path variable. If the module isn't found in the first directory
> > >> *      it tries the second and so on. The default is /kernel /usr/kernel
> > >> *
> > >> *      Example:
> > >> *              moddir: /kernel /usr/kernel /other/modules
>
> > >> * root device and root filesystem configuration:
> > >> *
> > >> *      The following may be used to override the defaults provided by
> > >> *      the boot program:
> > >> *
> > >> *      rootfs:         Set the filesystem type of the root.
> > >> *
> > >> *      rootdev:        Set the root device.  This should be a fully
> > >> *                      expanded physical pathname.  The default is the
> > >> *                      physical pathname of the device where the boot
> > >> *                      program resides.  The physical pathname is
> > >> *                      highly platform and configuration dependent.
> > >> *
> > >> *      Example:
> > >> *              rootfs:ufs
> > >> *              rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
> > >> *
> > >> *      (Swap device configuration should be specified in /etc/vfstab.)
>
> > >> * exclude:
> > >> *
> > >> *      Modules appearing in the moddir path which are NOT to be loaded,
> > >> *      even if referenced. Note that `exclude' accepts either a module name,
> > >> *      or a filename which includes the directory.
> > >> *
> > >> *      Examples:
> > >> *              exclude: win
> > >> *              exclude: sys/shmsys
>
> > >> *forceload:
> > >> *
> > >> *      Cause these modules to be loaded at boot time, (just before mounting
> > >> *      the root filesystem) rather than at first reference. Note that
> > >> *      forceloadexpects a filename which includes the directory. Also
> > >> *      note that loading a module does not necessarily imply that it will
> > >> *      be installed.
> > >> *
> > >> *      Example:
> > >> *              forceload: drv/foo
>
> > >> * set:
> > >> *
> > >> *      Set an integer variable in the kernel or a module to a new value.
> > >> *      This facility should be used with caution.  See system(4).
> > >> *
> > >> *      Examples:
> > >> *
> > >> *      To set variables in 'unix':
> > >> *
> > >> *              set nautopush=32
> > >> *              set maxusers=40
> > >> *
> > >> *      To set a variable named 'debug' in the module named 'test_module'
> > >> *
> > >> *              set test_module:debug = 0x13
>
> > >> * OUR MODIFICATION PART
> > >>forceload: sys/msgsys
>
> > >> * Maximum number of messages queues
> > >> set msgsys:msginfo_msgmap=800
>
> > >> *Maximum bytes on messages
> > >> set msgsys:msginfo_msgmax=4096
>
> > >> * Maximum bytes on queue
> > >> set msgsys:msginfo_msgmnb=32768
>
> > >> * Number of system message headers
> > >> set msgsys:msginfo_msgtql=200
>
> > >> * Number of message queue identifiers
> > >> set msgsys:msginfo_msgmni=200
>
> > >> * OUR MODIFICATION PART
>
> > >> *Begin MDD root info (do not edit)
> > >>forceload: misc/md_trans
> > >>forceload: misc/md_raid
> > >>forceload: misc/md_hotspares
> > >>forceload: misc/md_sp
> > >>forceload: misc/md_stripe
> > >>forceload: misc/md_mirror
> > >>forceload: drv/pcisch
> > >>forceload: drv/mpt
> > >>forceload: drv/sd
> > >>forceload: sys/msgsys
> > >> rootdev:/pseudo/md@0:0,0,blk
> > >> * End MDD root info (do not edit)
> > >> * Begin MDD database info (do not edit)
> > >> set md:mddb_bootlist1="sd:15:16 sd:15:1050 sd:15:2084 sd:23:16 sd:23:1050"
> > >> set md:mddb_bootlist2="sd:23:2084"
> > >> * End MDD database info (do not edit)
>
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~- 隐藏被引用文字 -
>
> > - 显示引用的文字 -- 隐藏被引用文字 -
>
> > - 显示引用的文字 -- 隐藏被引用文字 -
>
> - 显示引用的文字 -

For a conclusion, At last, we checked that it is a bug of solaris 8
server. Our server has not the patch for this bug,so we tried but
failed. Then we add the patch for server, and now it works.

Confused again, why SUN company gives no info for this problem?

[ohaya]

Hi,

Good for you!

Well, Solaris 8 is rather old...., so you should probably be thankful
that you could get a patch that fixed the problem :)...

Just out of curiousity, how did you happen to figure out that you needed
a/that patch?

Jim

[xugang]

> >>>------------------------------------------------------------------------­---­­-------------------------------------------------------------------

> >>>------------------------------------------------------------------------­---­­--------------------------------------------------------------

>
> >>>Method 3:
>
> >>>According to the feedback from our IT supporter, update the parameter
> >>>value we want to update from
>
> >>>4096 to 65535, and reboot the server. No working.....
>

> >>>------------------------------------------------------------------------­---­­--------------------------------------------------------------

>
> >>>Method 4:
>
> >>>Copy the system file which on the other server which is working to our
> >>>server instead of modifying
>
> >>>our own and restart the server. No working....
>

> >>>------------------------------------------------------------------------­---­­----------------------------------------------------------------

> Jim- 隐藏被引用文字 -
>
> - 显示引用的文字 -

The IT manager got the help from his best friend, the other details
i'm not sure. Now our application can run. This process is long but is
interesting. more needs to learn.

thanks for your attention!