Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7994595
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T14:10:42+00:00 2026-06-04T14:10:42+00:00

I am moving from Apache 1.3 to Apache 2.063 and am having trouble getting

  • 0

I am moving from Apache 1.3 to Apache 2.063 and am having trouble getting Apache::VMonitor working.

I tried a setup like this, similar to how I had it setup in my old Apache:

<Perl>
  use Apache::VMonitor();
  $Apache::VMonitor::Config{BLINKING} = 1;
  $Apache::VMonitor::Config{refresh}  = 0;
  $Apache::VMonitor::Config{verbose}  = 1;
  $Apache::VMonitor::Config{system}   = 1;
  $Apache::VMonitor::Config{apache}   = 1;
  $Apache::VMonitor::Config{procs}    = 1;
  $Apache::VMonitor::Config{mount}    = 1;
  $Apache::VMonitor::Config{fs_usage} = 1;
  $Apache::VMonitor::Config{apache_sort_by}  = 'vsize';
  $Apache::VMonitor::PROC_REGEX = join "\|", qw(.*)
</Perl>

<Location /vmonitor>
  SetHandler perl-script
  PerlHandler Apache::VMonitor
  Order deny,allow
  Deny from all
  Allow from 127.0.0.1
  Allow from X.X.X.X ## really a valid IP
</Location>

When I try to start my server I get this error:

ap_scoreboard_image doesn’t exist at …

I found a note in the Apache::VMonitor documentation that says:

NOTE For Apache versions later than 2.0.53 (veriied on 2.0.54, 2.0.55, and 2.0.58), loading Apache::VMonitor in sections and/or PostConfigRequire files does not work due to a change in when Apache initialises the scoreboard object.

The problem is that it doesn’t say when I can initialize the scoreboard object in later versions of Apache. I tried to omit the “use” statement and get this error:

panic: del_backref during global destruction.

* Error code 255

Does anyone have any idea how to get this working? I am not stuck on using Apache::VMonitor, I am open to suggestions if anyone can suggest an alternate way to parse and display data from Apache’s scoreboard.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T14:10:44+00:00Added an answer on June 4, 2026 at 2:10 pm

    I’ve pushed V2.07 to CPAN which should fix the issue (and also removed the dependency on GTop if you don’t need the information it provides, or are running on Windows).

    Using the previous release (V2.06), you should be able to initialise it in your script/application. Basically anywhere after the start-up phase as, if I remember correctly, there’s no scoreboard until the child threads/processes are created.

    The source is on github ( http://github.com/mjharwood/Apache–VMonitor-2.0 ) should you want it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am moving from jQuery to MooTools (for the fun..) and I have this
I've encountered a problem when moving a Wordpress installation from a Linux Apache server
I'm considering moving from Apache to Lighttpd for an internal web application, written with
I'm currently moving from my development server to an Apache web production server. I've
Moving my website to a new webhost, I'm having an issue with apache /
I'm having a strange problem here. I'm moving a (working) site to a new
Afrter moving site from RedHAT/CloudLinux/ Apache 2.2 to to Windows 2008 R* / IIS7
We're looking at moving our repository access from svnserve to apache/Subversion Edge to enable
I am moving my site from a tomcat only instance to an apache httd/
Im moving from django to pylons, is there an admin app?

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.