Kattare Internet Hosting Home | Home | Services | Contact Us | Order Online |   whitespace image
  Kattare I/S: View FAQ Answer | Webmail | News | FAQ | Members Login |   whitespace image
tail end of the Kattare logo Toll Free: (866) KATTARE -or- (877) KATTARE
Local: (541) 753-1079
keyboard image  whitespace image
You've got Q's? We've got A's.  whitespace image
greenspace image for php hosting, jsp hosting, servlet hosting, java hosting website

Home

Contribute Hosting!

Hosting Services

Java Hosting
  JBoss Hosting
  JSP Hosting
  GlassFish Hosting
  Servlet Hosting
  Tcat Hosting
  Tomcat Hosting

Standard Hosting
  Perl Hosting
  PHP 4 Hosting
  PHP 5 Hosting
  Ruby Hosting

Dedicated Servers
Server Co-Location

Domain Lookup
Join Us Today!

Members

Control Panel
  Ticketing
  Webmail
F.A.Q.
Recent News
Referral System
Spam Blocking

Company

About Us
  History
  Privacy Policy
  Sites We Host
  Strategic Partners
  Terms of Service
  Trademarks
Contact Us
  Phone / Fax
  Mail / Email
  SMS Text


Verify Kattare Internet Services

Documentation

Kattare is dedicated to making your hosting experience as painless as possible. That means making as much help and documentation available as possible. If you have a question that you think would be helpful to have here, please [Submit your Question].

Quick Links
 [Getting Started
 [JSP & Java
 [Ruby & Rails
 [Email & Webmail
Category
Administration
Question

Last Modified: Jan 07, 2008

Apache - File exists: unable to create scoreboard - name-based shared memory failure
Answer
Error: [crit] (17)File exists: unable to create scoreboard (name-based shared memory failure)

This occurs when apache has had an ungraceful shutdown (for one reason or another) and did not free up a shared memory segment.  When httpd is restarted it discovers that its shared memory segment already exists, thinks an instance is already running, and terminates because it cannot allocate the resources it needs.

To fix the problem without requiring a system restart you need to find the orphan shared memory segment.  To do this we need to use the ipcs command as root to list allocated segments.  Typically the shared memory usage would look like the following:
[root@ /]# ipcs -m -p
------ Shared Memory Creator/Last-op --------
shmid      owner      cpid       lpid
65536      root       15572      19626
98305      root       15572      19626

[root@ /]# ipcs -m

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x00000000 65536      root      600        524288     46         dest
0x0100e49f 98305      root      600        225304     46


You will notice 46 attached proceses (nattach) to the first shared memory segment (segment 0). These are the 46 httpd threads waiting for incoming http requests. If you see 0 attached processes, then you have a pretty good indicator of which chunk of memory to release.

You might do a ps process check to make sure the above listed pid's really are not running, Then you remove the shared memory associated with ID 0 using the ipcrm command.

[root@ /]# ipcrm -m 0

You should now be able to restart apache successfully.

[FAQ Main] [Submit a Question]

[Back to Category "Administration"]


whitespace image
green spacer

 [Getting Started]  [JSP & Java]  [Ruby & Rails]  [Email & Webmail]

Kattare Logo
whitespace image
 
whitespace image
whitespace image