Fork me on GitHub

Haunted WebPage!?  Bottom

  • Hi:

    Well this is difficult to believe at least in my experience dealing with Apache, PostNuke and Web pages. I have a directory that I erased from the web server. I stops the server and restart it and when I try to access the web dir it shows something (with error) but it should show a 404!

    My _mayor_ problem is the index page of my web site is loading twice. You will see the large white space after the page ends:

    http://www.politicaboricua.com

    However when you access a 'channel' it shows properly...
    http://www.politicab….com/Politica.phtml

    The haunted part is this:
    The directory named /usr/local/apache2/htdocs2/testbed WAS erased and it is reported as such by bash. But if I try to access:
    http://www.politicab…/testbed/News.phtml

    It SHOWS something... (when it should show a 404) I have stop and restarted the web server twice (I think I even rebooted) and it continues to show...

    My setup is Apache 2.2.2, PHP 5.1.4, PostNUke .762, MySQL 4.1.19.

    I **HAVE** erased all PostNuke related caches (pnRender_compile, AutoTheme _compile, pzLib) have stop and restart the server and this continues. Unless it is 'cache' installed by my ISP.

    Could someone confirm
    http://www.politicaboricua.com/testbed/News.phtml show a 404???

    Otherwise Apache 2.2.2 *might* have a cache thats is producing this..

    Please advise or comment... I really don't believe this is happennng... particulary for the 'double page' loading at index page. It is nasty.

    Later

    icon_confused icon_rolleyes icon_frown

    p.d.
    I am running PostNuke since august 2003, I am used to configure Apache, PHP and MySQL so please note that I am not a newbie regarding Web Technologies altough aI am not a programmer perse..




    edited by: edfel, May 30, 2006 - 05:50 PM
  • Hi:

    Further researching shows this:

    Summary: mod_mem_cache crashes after requesting the same object
    twice
    Product: Apache httpd-2
    Version: 2.2.2
    Platform: PC
    OS/Version: Linux
    Status: NEW
    Severity: critical
    Priority: P2
    Component: mod_cache
    AssignedTo: bugs[at]httpd.apache.org
    ReportedBy: croller[at]generali.fr


    When requesting the same object twice (a cachable object that respond to the mem
    cache parameters), a segmentation fault is generated (ie. [Tue May 23 12:59:31
    2006] [notice] child pid 960 exit signal Segmentation fault (11)) with Apache
    2.2.2 on RHEL ES 3 (Linux apache 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST)
    acting as a reverse proxy, with both mem cache and disk cache enabled for
    several virtual hosts.

    Several things were tried, but it makes no difference:
    - reload or restart Apache
    - reboot
    - disabling disk cache
    - changing mem cache parameters
    - request with "deflatable" and "not deflatable" objects
    - request with different browser (Firefox 1.5.0.3, IE 6.0SP2, telnet...)
    - requesting different objects (but still 2 times following) on different
    virtual hosts

    But disabling mem cache always makes it work perfectly without crashes.

    This is an exemple of telnet request (extracted from tcpdump):
    GET /fichiers/1417/00000012.htm HTTP/1.1
    Accept: */*
    Referer: http://www.my-site.com/synergies/Pages/index_FS.asp?res=1024&
    Accept-Language: en-us
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
    Host: www.my-site.com
    Connection: Keep-Alive

    This is the cache configuration:
    CacheDefaultExpire 60
    CacheLastModifiedFactor 0.1
    CacheMaxExpire 86400

    CacheEnable mem /
    MCacheMaxObjectCount 10000
    MCacheMaxObjectSize 32768
    MCacheMaxStreamingBuffer 16384
    MCacheMinObjectSize 0
    MCacheRemovalAlgorithm GDSF
    MCacheSize 32768


    CacheEnable disk /
    CacheDirLength 2
    CacheDirLevels 3
    CacheMaxFileSize 1000000
    CacheMinFileSize 64
    CacheRoot /var/cache/apache

    This *might* be also related:
    http://issues.apache…ow_bug.cgi?id=39647

    This was posted on may 23, 206. So I guess it is related with my problem. Problem is Apache release builds at 3-4 months intervals... Unless I risk trying cvs code once a fix is applied to the three...

    Later

    :(



    edited by: edfel, May 30, 2006 - 07:26 PM
  • Hi:

    Well, I think that the problem with the erased dir and the web page showing is related with _short urls_ since any word I wrote besides htdocs produces a similar output. So the web page is NOT haunted!

    BUT.......... still have to fix the double index page loading.

    Later

    :)



    edited by: edfel, May 30, 2006 - 10:29 PM

This list is based on users active over the last 60 minutes.