TypesConfig Error

Discussion in 'Apache Migration/Compatibility' started by DraCoola, Dec 6, 2009.

  1. DraCoola

    DraCoola Well-Known Member

    I have these error mesage on LSWS WHM Panel :

    Screenshot ---> http://img412.imageshack.us/img412/2572/typesconfig.jpg

    As I found on my httpd.conf (line 112) :

    <IfModule mime_module>
        TypesConfig conf/mime.types
        AddType application/x-compress .Z
        AddType application/x-gzip .gz .tgz
    Is that safe to just coment out those lines above in purpose to fix errors which LSWS said on screenshot above?

    Thank you.
  2. mistwang

    mistwang LiteSpeed Staff

    You can ignore this error for now, it does not hurt anything, will be addressed in next release.
  3. DraCoola

    DraCoola Well-Known Member

    Glad to know that :)
    Thank you for your explanation.
  4. Statskij

    Statskij Active Member

    I use 4.0.12 version and it has an error:
    2009-12-19 21:55:38.227 WARN /usr/local/apache/conf/httpd.conf:114: Directive 'TypesConfig' is not allowed in current context.
    As far as I understand this mistake will be corrected in 4.0.13 version?
  5. rlshosting

    rlshosting Member

    I have same issue too.
  6. anewday

    anewday Moderator

    Same here.

    When I tried to upgrade from 4.0.11 to 4.0.12 from web console, I see this in the error log:

    [66.x.x.x:51587-2#_AdminVHost] [STDERR] PHP Warning: file_get_contents(http://download.litespeedtech.com/packages/latest/lsws-4.0.12-ent-i386-linux.tar.gz) [<a href='function.file-get-contents'>function.file-get-contents</a>]: failed to open stream: no suitable wrapper could be found in /usr/local/lsws/admin/html.4.0.11/classes/ws/Service.php on line 534
  7. DanEZPZ

    DanEZPZ Well-Known Member

    I'm getting this too. Litespeed also seems to be restarting quite often which is worrying
  8. mistwang

    mistwang LiteSpeed Staff

    This is fixed with latest 4.0.12 build. please do a manual update from command line.
  9. DanEZPZ

    DanEZPZ Well-Known Member

    I am running 4.0.12, infact this is the only version im seeing this on, it doesnt come up with 4.0.11.

Share This Page