Professional Web Applications Themes

apache error after 5.0.7 updates - SCO

The system logs indicate an apache error when running the apache rc2.d script ?apacheP90 or whichever startup script is in that directory. The error is "^W:number error" or similar; running the command line apache script such as apache start|stop|etc. gives the same error. DocView seems to bring up the online doentation for browsing; I haven't run indexing yet to allow searches. The default home page for apache doesn't load from mozilla, with url of the server's IP address, as it did before. The system is 5.0.7 with both the free maintenance updates and the paid updates applied. They were obtained ...

  1. #1

    Default apache error after 5.0.7 updates

    The system logs indicate an apache error when running the apache rc2.d
    script ?apacheP90 or whichever startup script is in that directory.

    The error is "^W:number error" or similar; running the command line apache
    script such as apache start|stop|etc. gives the same error.

    DocView seems to bring up the online doentation for browsing; I haven't
    run indexing yet to allow searches.

    The default home page for apache doesn't load from mozilla, with url of the
    server's IP address, as it did before.

    The system is 5.0.7 with both the free maintenance updates and the paid
    updates applied. They were obtained via ftp as I was reluctant to disable
    our firewall for ftp access to allow sco update within software manager to
    be used.

    This didn't occur prior to the updates; I forgot to ps -ef | grep apache
    before booting the system back to a SCSI disk running 5.0.6 for production
    use, but will do so when next feasible. I didn't note any obvious
    abnormality in the apache startup script, such as abnormal characters from
    file corruption.

    5.0.7 is on an IDE disk; I am configuring it before moving our apps and data
    currently running 5.0.6 on SCSI; only the SCSI tape and CDROM are currently
    enabled in 5.0.7. The IDE channels are disabled in BIOS when the system is
    being used in production during the day with 5.0.6.

    Thanks,

    David P. Lurie


    David Guest

  2. #2

    Default Re: apache error after 5.0.7 updates

    On Fri, Sep 12, 2003 at 02:21:38PM +0000, David P. Lurie wrote: 

    there is a known issue with 5.07 maintenance pack (1) that affects apache,
    among other programs - a new libary (libmm) causes kernel to run out
    of semaphores. need to increase kernel tunable parameter SEMMNI (to at
    least 100) relink & reboot if have not done so already - read release
    notes from mp1 for more details (2 sentences way at bottom). i don't
    recognize your error message, but if you haven't increased this parameter,
    may as well start with that as the docs mention it affects apache, docview
    at the very least (we found it with backupedge failures). i don't know why
    in their wisdom sco didn't see fit for the install process to do this
    for you.

    --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
    -Joe Chasan- Magnatech Business Systems, Inc.
    com Hicksville, NY - USA
    http://www.MagnatechOnline.com Tel.(516) 931-4444/Fax.(516) 931-1264
    Joe Guest

  3. #3

    Default Re: apache error after 5.0.7 updates

    Joe Chasan wrote:
     

    Because the problem was discovered the day _after_ the supplement was
    posted on the web site. We debated recutting the supplement, but that's
    always a big mess with different systems claiming to have the same thing
    on them, but they don't really. Or we could have recut it with a new
    version number, but then there would be an implied need for users who
    already had the original version to re-download and reinstall the "new"
    version, which would be a huge waste of their effort when all they
    needed to do was change a parameter.
     
    Bela Guest

  4. #4

    Default Re: apache error after 5.0.7 updates


    "Bela Lubkin" <com> wrote in message
    news:com...
     [/ref]

    Thanks for everyone's help - it seems to have worked.

    The updates also seem to have corrected a USB recognition problem; my system
    didn't hang on boot without disabling the USB subsystem in BIOS, as it would
    in the past.

    David P. Lurie


    David Guest

Similar Threads

  1. starting apache with mod_perl, error on Apache.pm
    By Selmar in forum PERL Modules
    Replies: 0
    Last Post: July 21st, 02:34 PM
  2. Error while installing Devices Updates 4.0
    By Filip Heens in forum ASP Components
    Replies: 0
    Last Post: February 19th, 12:31 PM
  3. Replies: 0
    Last Post: October 15th, 02:49 PM
  4. error in apache log
    By Peter Berglund in forum PHP Development
    Replies: 3
    Last Post: August 20th, 12:40 PM
  5. Apache starting error
    By Rikunj in forum PHP Development
    Replies: 2
    Last Post: August 20th, 09:34 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139