Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

New Server Install PHP Fatal error: PCRE is not compiled with UTF-8 support

Discussion in 'EasyApache' started by Killers2, Feb 23, 2013.

  1. Killers2

    Killers2 Registered

    Joined:
    Jan 21, 2009
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    51
    Hey,

    Just setup a new server and getting some issues with this PHP error. PCRE is indeed compiled with UTF-8 and Unicode support.

    PHP Warning: preg_match(): Compilation failed: unknown option bit(s) set at offset 0
    PHP Fatal error: PCRE is not compiled with UTF-8 support

    pcretest -C
    PCRE version 7.8 2008-09-05
    Compiled with
    UTF-8 support
    Unicode properties support
    Newline sequence is LF
    \R matches all Unicode newlines
    Internal link size = 2
    POSIX malloc threshold = 10
    Default match limit = 10000000
    Default recursion depth limit = 10000000
    Match recursion uses stack

    opt/pcre/bin/pcretest -C
    PCRE version 8.21 2011-12-12
    Compiled with
    UTF-8 support
    Unicode properties support
    No just-in-time compiler support
    Newline sequence is LF
    \R matches all Unicode newlines
    Internal link size = 2
    POSIX malloc threshold = 10
    Default match limit = 10000000
    Default recursion depth limit = 10000000
    Match recursion uses stack


    Using PHP 5.4.11, CentOS 6 x64 and Apache 2.4. Was using the same on another server except on a 32 bit OS and it was fine.
     
  2. NovemberRain

    NovemberRain Well-Known Member

    Joined:
    Sep 24, 2003
    Messages:
    110
    Likes Received:
    3
    Trophy Points:
    168
    Location:
    İstanbul
    cPanel Access Level:
    Root Administrator
  3. Killers2

    Killers2 Registered

    Joined:
    Jan 21, 2009
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    51
    Yes going back to 2.2 resolved this issue. Did not have the issue on a 32 bit CentOS 5 system.
     
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice