www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy, Rakesh \(CAP, FLEET\)" <Rakesh....@fleet.gecapital.com>
Subject RE: os-sunos/8811: Unable to start the Apache web server
Date Tue, 20 Nov 2001 17:00:01 GMT
The following reply was made to PR os-sunos/8811; it has been noted by GNATS.

From: "Roy, Rakesh (CAP, FLEET)" <Rakesh.Roy@fleet.gecapital.com>
To: Ian Holsman <ianh@cnet.com>
Cc: apbugs@Apache.Org
Subject: RE: os-sunos/8811: Unable to start the Apache web server
Date: Tue, 20 Nov 2001 16:52:48 -0000

 This message is in MIME format. Since your mail reader does not understand
 this format, some or all of this message may not be legible.
 
 ------_=_NextPart_000_01C171E3.C89C83E0
 Content-Type: text/plain;
 	charset="iso-8859-1"
 
 The IPCS status
 
 IPC status from <running system> as of Tue Nov 20 16:43:18 GMT 2001
 
 T         ID      KEY        MODE        OWNER    GROUP
 
 Message Queues:
 
 Shared Memory:
 
 m          0   0x50000bba --rw-r--r--     root     root
 
 Semaphores:
 
 s     196608   0x3b006c10 --ra-ra-ra-   oracle      dba
 
 s          1   0x3b000002 --ra-ra-ra-   oracle      dba
 
 s          2   0x3b006412 --ra-ra-ra-   oracle      dba
 
 Attached here is the copy of the /etc/system file.
 
 Thanks 
 Rakesh
 
 -----Original Message-----
 From: Ian Holsman [mailto:ianh@cnet.com]
 Sent: 20 November 2001 16:49
 To: rakesh.roy@fleet.gecapital.com
 Cc: submit@bugz.apache.org
 Subject: Re: os-sunos/8811: Unable to start the Apache web server
 
 
 On Tue, 2001-11-20 at 07:52, Rakesh Roy wrote:
 > 
 > >Number:         8811
 > >Category:       os-sunos
 > >Synopsis:       Unable to start the Apache web server
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       medium
 > >Responsible:    apache
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          support
 > >Submitter-Id:   apache
 > >Arrival-Date:   Tue Nov 20 08:00:00 PST 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     rakesh.roy@fleet.gecapital.com
 > >Release:        1.3.17
 > >Organization:
 > apache
 > >Environment:
 > Soloris 2.8
 > >Description:
 > Getting the following error message in error_log:
 > 
 > Init Resource Cache and key store
 
 > shmget failed. You may be trying to make a cache that is too large or be
 doing a
 > pachectl restart.
 can you attach a copy of your /etc/system file
 and the output of ipcs
 
 > >How-To-Repeat:
 > 
 > >Fix:
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 >  [In order for any reply to be added to the PR database, you need]
 >  [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 >  [subject line starts with the report component and number, with ]
 >  [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 >  ["Re: general/1098:").  If the subject doesn't match this       ]
 >  [pattern, your message will be misfiled and ignored.  The       ]
 >  ["apbugs" address is not added to the Cc line of messages from  ]
 >  [the database automatically because of the potential for mail   ]
 >  [loops.  If you do not include this Cc, your reply may be ig-   ]
 >  [nored unless you are responding to an explicit request from a  ]
 >  [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 >  
 >  
 -- 
 Ian Holsman          IanH@cnet.com
 Performance Measurement & Analysis
 CNET Networks   -   (415) 344-2608
 
 
 ------_=_NextPart_000_01C171E3.C89C83E0
 Content-Type: application/octet-stream;
 	name="system"
 Content-Disposition: attachment;
 	filename="system"
 
 *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
 * 	forceload expects 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
 
 * Begin MDD root info (do not edit)
 forceload: misc/md_trans
 forceload: misc/md_raid
 forceload: misc/md_hotspares
 forceload: misc/md_stripe
 forceload: misc/md_mirror
 forceload: drv/pcisch
 forceload: drv/qlc
 forceload: drv/fp
 forceload: drv/ssd
 rootdev:/pseudo/md@0:0,0,blk
 * End MDD root info (do not edit)
 *
 * Network settings start.
 * Network full duplex 100m
 set hme:hme_adv_autoneg_cap=0
 set hme:hme_adv_100T4_cap=0
 set hme:hme_adv_100fdx_cap=1
 set hme:hme_adv_100hdx_cap=0
 set hme:hme_adv_10fdx_cap=0
 set hme:hme_adv_10hdx_cap=0
 * Network settings end.
 * To protect against possible buffer overflow or stack smashing
 set noexec_user_stack=1
 set noexec_user_stack_log=1
 * Begin MDD database info (do not edit)
 set md:mddb_bootlist1="ssd:7:16 ssd:23:16"
 * End MDD database info (do not edit)
 *
 * Start settings for Patrol
 set semsys:seminfo_semmap=200
 set semsys:seminfo_semmni=100
 set semsys:seminfo_semmns=200
 set semsys:seminfo_semmnu=30
 set shmsys:shminfo_shmmni=200
 set shmsys:shminfo_shmseg=50
 * End Patrol settings.
 
 ------_=_NextPart_000_01C171E3.C89C83E0--

Mime
View raw message