Want to subscribe to topics you're interested in?
Become a Member

MariaDB MariaDB 10.1.16 now available

Discussion in 'MariaDB & General MySQL news & discussions' started by eva2000, Jul 19, 2016.

  1. eva2000

    eva2000 Administrator Staff Member

    29,702
    6,707
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,009
    Local Time:
    8:57 PM
    Nginx 1.13.x
    MariaDB 5.5
    The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.16. See the release notes and changelog for details on this release. Download MariaDB 10.1.16 Release Notes Changelog What is MariaDB 10.1? MariaDB APT and YUM Repository Configuration Generator Thanks, and enjoy MariaDB!

    The post MariaDB 10.1.16 now available appeared first on MariaDB.org.

    Continue reading...
     
    • Like Like x 2
  2. eva2000

    eva2000 Administrator Staff Member

    29,702
    6,707
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,009
    Local Time:
    8:57 PM
    Nginx 1.13.x
    MariaDB 5.5
     
  3. eva2000

    eva2000 Administrator Staff Member

    29,702
    6,707
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,009
    Local Time:
    8:57 PM
    Nginx 1.13.x
    MariaDB 5.5
    • Agree Agree x 1
    • Informative Informative x 1
  4. Revenge

    Revenge Active Member

    287
    64
    28
    Feb 21, 2016
    Portugal
    Ratings:
    +227
    Local Time:
    11:57 AM
    1.9.x
    10.1.x
    • Agree Agree x 2
  5. pamamolf

    pamamolf Well-Known Member

    2,659
    240
    63
    May 31, 2014
    Ratings:
    +422
    Local Time:
    1:57 PM
    Nginx-1.13.x
    MariaDB 10.1.x
    Not yet on yum update :(
     
  6. RoldanLT

    RoldanLT Well-Known Member

    3,868
    945
    113
    May 25, 2014
    Phillipines
    Ratings:
    +1,284
    Local Time:
    6:57 PM
    1.11
    10.2
    Same on my OVH server, still no updates :D.
     
    • Agree Agree x 1
  7. Sunka

    Sunka Active Member

    910
    238
    43
    Oct 31, 2015
    Rijeka, Croatia
    Ratings:
    +385
    Local Time:
    12:57 PM
    Nginx 1.13.3
    MariaDB 10.1.24
    After upgrade to 10.1.16 can not start mariadb

    Code:
    [root@tvor-ocean ~]# systemctl daemon-reload
    [root@tvor-ocean ~]# mysqlrestart
    Restarting mysql (via systemctl):  Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
                                                               [FAILED]
    
    
    [root@tvor-ocean ~]# systemctl status mariadb.service
    â—Ź mariadb.service - MariaDB database server
       Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
               └─mdb101.conf, migrated-from-my.cnf-settings.conf
       Active: failed (Result: exit-code) since Tue 2016-07-19 02:47:04 CEST; 10s ago
      Process: 23705 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
      Process: 23464 ExecStartPre=/bin/sh -c VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] &&   systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
      Process: 23462 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Main PID: 23705 (code=exited, status=1/FAILURE)
       Status: "MariaDB server is down"
    
    Jul 19 02:47:03 tvor-ocean.pijanitvor.com systemd[1]: Starting MariaDB database server...
    Jul 19 02:47:03 tvor-ocean.pijanitvor.com mysqld[23705]: 2016-07-19  2:47:03 140169375500416 [Note] Using unique option prefix 'ignore-...stead.
    Jul 19 02:47:03 tvor-ocean.pijanitvor.com mysqld[23705]: 2016-07-19  2:47:03 140169375500416 [Note] /usr/sbin/mysqld (mysqld 10.1.16-Ma...05 ...
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: Failed to start MariaDB database server.
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: Unit mariadb.service entered failed state.
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: mariadb.service failed.
    Hint: Some lines were ellipsized, use -l to show in full.
    
    
    
    
    [root@tvor-ocean ~]# journalctl -xe
    Jul 19 02:44:26 tvor-ocean.pijanitvor.com NetworkManager[499]: <info>  (eth1): device state change: ip-config -> failed (reason 'ip-config-unava
    Jul 19 02:44:26 tvor-ocean.pijanitvor.com NetworkManager[499]: <info>  Disabling autoconnect for connection 'Wired connection 1'.
    Jul 19 02:44:26 tvor-ocean.pijanitvor.com NetworkManager[499]: <warn>  (eth1): Activation: failed for connection 'Wired connection 1'
    Jul 19 02:44:26 tvor-ocean.pijanitvor.com NetworkManager[499]: <info>  (eth1): device state change: failed -> disconnected (reason 'none') [120
    Jul 19 02:44:26 tvor-ocean.pijanitvor.com avahi-daemon[480]: Withdrawing address record for fe80::601:81ff:fed1:a402 on eth1.
    Jul 19 02:44:27 tvor-ocean.pijanitvor.com ntpd[484]: Deleting interface #7134 eth1, fe80::601:81ff:fed1:a402#123, interface stats: received=0, s
    Jul 19 02:44:59 tvor-ocean.pijanitvor.com crontab[22891]: (root) LIST (root)
    Jul 19 02:45:01 tvor-ocean.pijanitvor.com systemd[1]: Started Session 6281 of user root.
    -- Subject: Unit session-6281.scope has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-6281.scope has finished starting up.
    --
    -- The start-up result is done.
    Jul 19 02:45:01 tvor-ocean.pijanitvor.com CROND[22935]: (root) CMD (/usr/bin/chown -R nginx:nginx /home/nginx/domains)
    Jul 19 02:45:01 tvor-ocean.pijanitvor.com systemd[1]: Starting Session 6281 of user root.
    -- Subject: Unit session-6281.scope has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-6281.scope has begun starting up.
    Jul 19 02:46:27 tvor-ocean.pijanitvor.com crontab[23229]: (root) LIST (root)
    Jul 19 02:46:27 tvor-ocean.pijanitvor.com kernel: nf_conntrack: falling back to vmalloc.
    Jul 19 02:46:28 tvor-ocean.pijanitvor.com crontab[23323]: (root) LIST (root)
    Jul 19 02:46:28 tvor-ocean.pijanitvor.com crontab[23344]: (root) LIST (root)
    Jul 19 02:46:54 tvor-ocean.pijanitvor.com polkitd[541]: Registered Authentication Agent for unix-process:23424:112209595 (system bus name :1.125
    Jul 19 02:46:54 tvor-ocean.pijanitvor.com systemd[1]: Reloading.
    Jul 19 02:46:54 tvor-ocean.pijanitvor.com systemd[1]: [/etc/systemd/system/multi-user.target.wants/digitalocean-rc-local.service:18] Support for
    Jul 19 02:46:54 tvor-ocean.pijanitvor.com systemd[1]: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. Th
    Jul 19 02:46:54 tvor-ocean.pijanitvor.com systemd[1]: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Pl
    Jul 19 02:46:54 tvor-ocean.pijanitvor.com polkitd[541]: Unregistered Authentication Agent for unix-process:23424:112209595 (system bus name :1.1
    Jul 19 02:47:03 tvor-ocean.pijanitvor.com polkitd[541]: Registered Authentication Agent for unix-process:23457:112210524 (system bus name :1.125
    Jul 19 02:47:03 tvor-ocean.pijanitvor.com systemd[1]: Starting MariaDB database server...
    -- Subject: Unit mariadb.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit mariadb.service has begun starting up.
    Jul 19 02:47:03 tvor-ocean.pijanitvor.com mysqld[23705]: 2016-07-19  2:47:03 140169375500416 [Note] Using unique option prefix 'ignore-db-dir' i
    Jul 19 02:47:03 tvor-ocean.pijanitvor.com mysqld[23705]: 2016-07-19  2:47:03 140169375500416 [Note] /usr/sbin/mysqld (mysqld 10.1.16-MariaDB) st
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: Failed to start MariaDB database server.
    -- Subject: Unit mariadb.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit mariadb.service has failed.
    --
    -- The result is failed.
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: Unit mariadb.service entered failed state.
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com systemd[1]: mariadb.service failed.
    Jul 19 02:47:04 tvor-ocean.pijanitvor.com polkitd[541]: Unregistered Authentication Agent for unix-process:23457:112210524 (system bus name :1.1
    Jul 19 02:47:14 tvor-ocean.pijanitvor.com kernel: Firewall: *TCP_I
     
  8. Sunka

    Sunka Active Member

    910
    238
    43
    Oct 31, 2015
    Rijeka, Croatia
    Ratings:
    +385
    Local Time:
    12:57 PM
    Nginx 1.13.3
    MariaDB 10.1.24
    Log files

    Code:
    [root@tvor-ocean ~]# tail -50 /var/log/mysqld.log
    2016-07-19  2:40:44 140359656331392 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    2016-07-19  2:40:44 140359656331392 [Note] Plugin 'FEEDBACK' is disabled.
    2016-07-19  2:40:44 140359656331392 [ERROR] Unknown/unsupported storage engine: InnoDB
    2016-07-19  2:40:44 140359656331392 [ERROR] Aborting
    
    2016-07-19  2:41:54 140015103744128 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    2016-07-19  2:41:54 140015103744128 [Note] InnoDB: The InnoDB memory heap is disabled
    2016-07-19  2:41:54 140015103744128 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2016-07-19  2:41:54 140015103744128 [Note] InnoDB: Memory barrier is not used
    2016-07-19  2:41:54 140015103744128 [Note] InnoDB: Compressed tables use zlib 1.2.7
    2016-07-19  2:41:54 140015103744128 [Note] InnoDB: Using Linux native AIO
    2016-07-19  2:41:54 140015103744128 [Note] InnoDB: Using SSE crc32 instructions
    2016-07-19  2:41:54 140015103744128 [ERROR] mysqld: Can't create/write to file '/home/mysqltmp/ibwaQ1LK' (Errcode: 13 "Permission denied")
    2016-07-19 02:41:54 7f57ce859880  InnoDB: Error: unable to create temporary file; errno: 13
    2016-07-19  2:41:54 140015103744128 [ERROR] Plugin 'InnoDB' init function returned error.
    2016-07-19  2:41:54 140015103744128 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    2016-07-19  2:41:54 140015103744128 [Note] Plugin 'FEEDBACK' is disabled.
    2016-07-19  2:41:54 140015103744128 [ERROR] Unknown/unsupported storage engine: InnoDB
    2016-07-19  2:41:54 140015103744128 [ERROR] Aborting
    
    2016-07-19  2:43:24 140171698387072 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    2016-07-19  2:43:24 140171698387072 [Note] InnoDB: The InnoDB memory heap is disabled
    2016-07-19  2:43:24 140171698387072 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2016-07-19  2:43:24 140171698387072 [Note] InnoDB: Memory barrier is not used
    2016-07-19  2:43:24 140171698387072 [Note] InnoDB: Compressed tables use zlib 1.2.7
    2016-07-19  2:43:24 140171698387072 [Note] InnoDB: Using Linux native AIO
    2016-07-19  2:43:24 140171698387072 [Note] InnoDB: Using SSE crc32 instructions
    2016-07-19  2:43:24 140171698387072 [ERROR] mysqld: Can't create/write to file '/home/mysqltmp/ibl4lnbD' (Errcode: 13 "Permission denied")
    2016-07-19 02:43:24 7f7c444a3880  InnoDB: Error: unable to create temporary file; errno: 13
    2016-07-19  2:43:24 140171698387072 [ERROR] Plugin 'InnoDB' init function returned error.
    2016-07-19  2:43:24 140171698387072 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    2016-07-19  2:43:24 140171698387072 [Note] Plugin 'FEEDBACK' is disabled.
    2016-07-19  2:43:24 140171698387072 [ERROR] Unknown/unsupported storage engine: InnoDB
    2016-07-19  2:43:24 140171698387072 [ERROR] Aborting
    
    2016-07-19  2:47:04 140169375500416 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    2016-07-19  2:47:04 140169375500416 [Note] InnoDB: The InnoDB memory heap is disabled
    2016-07-19  2:47:04 140169375500416 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2016-07-19  2:47:04 140169375500416 [Note] InnoDB: Memory barrier is not used
    2016-07-19  2:47:04 140169375500416 [Note] InnoDB: Compressed tables use zlib 1.2.7
    2016-07-19  2:47:04 140169375500416 [Note] InnoDB: Using Linux native AIO
    2016-07-19  2:47:04 140169375500416 [Note] InnoDB: Using SSE crc32 instructions
    2016-07-19  2:47:04 140169375500416 [ERROR] mysqld: Can't create/write to file '/home/mysqltmp/iblhbttE' (Errcode: 13 "Permission denied")
    2016-07-19 02:47:04 7f7bb9d5c880  InnoDB: Error: unable to create temporary file; errno: 13
    2016-07-19  2:47:04 140169375500416 [ERROR] Plugin 'InnoDB' init function returned error.
    2016-07-19  2:47:04 140169375500416 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    2016-07-19  2:47:04 140169375500416 [Note] Plugin 'FEEDBACK' is disabled.
    2016-07-19  2:47:04 140169375500416 [ERROR] Unknown/unsupported storage engine: InnoDB
    2016-07-19  2:47:04 140169375500416 [ERROR] Aborting
     
    • Informative Informative x 1
  9. Sunka

    Sunka Active Member

    910
    238
    43
    Oct 31, 2015
    Rijeka, Croatia
    Ratings:
    +385
    Local Time:
    12:57 PM
    Nginx 1.13.3
    MariaDB 10.1.24
    Should I try with yum history undo XX
    It is last yum update and it is just mariadb upgrade
     
  10. tjk

    tjk Member

    74
    16
    8
    Jun 27, 2015
    Ratings:
    +25
    Local Time:
    6:57 AM
    I was just about to update until I saw your error. Anyone else having update issues/errors?
     
  11. Sunka

    Sunka Active Member

    910
    238
    43
    Oct 31, 2015
    Rijeka, Croatia
    Ratings:
    +385
    Local Time:
    12:57 PM
    Nginx 1.13.3
    MariaDB 10.1.24
    I was able to downgrade to 10.1.14 and all went OK. This @eva2000 post is guide

    Waiting to upgrade to 10.1.16 when some things will be clearer
     
    • Informative Informative x 1
  12. RoldanLT

    RoldanLT Well-Known Member

    3,868
    945
    113
    May 25, 2014
    Phillipines
    Ratings:
    +1,284
    Local Time:
    6:57 PM
    1.11
    10.2
    2016-07-19 2:43:24 140171698387072 [ERROR] mysqld: Can't create/write to file '/home/mysqltmp/ibl4lnbD' (Errcode: 13 "Permission denied")
    2016-07-19 02:43:24 7f7c444a3880 InnoDB: Error: unable to create temporary file; errno: 13
     
    • Like Like x 1
  13. eva2000

    eva2000 Administrator Staff Member

    29,702
    6,707
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,009
    Local Time:
    8:57 PM
    Nginx 1.13.x
    MariaDB 5.5
    what's output of
    Code (Text):
    ls -lah /home/mysqltmp
    stat /home/mysqltmp
     
  14. Sunka

    Sunka Active Member

    910
    238
    43
    Oct 31, 2015
    Rijeka, Croatia
    Ratings:
    +385
    Local Time:
    12:57 PM
    Nginx 1.13.3
    MariaDB 10.1.24
    This:
    Code:
    [root@tvor-ocean ~]# ls -lah /home/mysqltmp
    total 8.0K
    drwxrwxrwt  2 mysql mysql 4.0K Jul 19 11:08 .
    drwxr-xr-x. 7 root  root  4.0K Aug 12  2015 ..
    
    
    [root@tvor-ocean ~]# stat /home/mysqltmp
      File: ‘/home/mysqltmp’
      Size: 4096            Blocks: 8          IO Block: 4096   directory
    Device: fd01h/64769d    Inode: 783364      Links: 2
    Access: (1777/drwxrwxrwt)  Uid: (  997/   mysql)   Gid: (  996/   mysql)
    Access: 2016-07-19 11:09:00.786740030 +0200
    Modify: 2016-07-19 11:08:29.210742049 +0200
    Change: 2016-07-19 11:08:29.210742049 +0200
    Birth: -
     
  15. Revenge

    Revenge Active Member

    287
    64
    28
    Feb 21, 2016
    Portugal
    Ratings:
    +227
    Local Time:
    11:57 AM
    1.9.x
    10.1.x
    Updated to 10.1.16 and i can confirm the bug with IPS 4.1 users were having is fixed (y)
     
    • Like Like x 1
    • Informative Informative x 1
  16. pamamolf

    pamamolf Well-Known Member

    2,659
    240
    63
    May 31, 2014
    Ratings:
    +422
    Local Time:
    1:57 PM
    Nginx-1.13.x
    MariaDB 10.1.x
    I got also the same upgrading issue :(

    after running yum update mysql -v give me the old version of MariaDB and when i try to restart it i got this:

    Code:
    Jul 19 13:24:48 vps29.ovh.net mysqld[22605]: 2016-07-19 13:24:48 7f442edca880  InnoDB: Error: unable to create temporary file; errno: 13
    Code:
    [ERROR] mysqld: Can't create/write to file '/home/mysqltmp/ibE8sYLn' (Errcode: 13 "Permission denied")
    ls -lah /home/mysqltmp

    Code:
    [root@vps29 ~]# ls -lah /home/mysqltmp
    total 0
    drwxrwxrwt. 2 mysql mysql  6 Jul 19 13:24 .
    drwxr-xr-x. 5 root  root  47 Jul 14 12:28 ..
    stat /home/mysqltmp

    Code:
    [root@vps29 ~]# stat /home/mysqltmp
      File: ‘/home/mysqltmp’
      Size: 6               Blocks: 0          IO Block: 4096   directory
    Device: fd01h/64769d    Inode: 16825185    Links: 2
    Access: (1777/drwxrwxrwt)  Uid: (  994/   mysql)   Gid: (  992/   mysql)
    Access: 2016-07-19 13:24:39.279837729 +0000
    Modify: 2016-07-19 13:24:38.870837281 +0000
    Change: 2016-07-19 13:24:38.870837281 +0000
    Birth: -
    
     
    Last edited: Jul 20, 2016
  17. eva2000

    eva2000 Administrator Staff Member

    29,702
    6,707
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,009
    Local Time:
    8:57 PM
    Nginx 1.13.x
    MariaDB 5.5
    problem seems to be mariadb 10.1.16 doesn't like the defined tmpdir directory in /etc/my.cnf
    Code (Text):
    2016-07-19  2:47:04 140169375500416 [ERROR] mysqld: Can't create/write to file '/home/mysqltmp/iblhbttE' (Errcode: 13 "Permission denied")
    2016-07-19 02:47:04 7f7bb9d5c880  InnoDB: Error: unable to create temporary file; errno: 13
    

    sounds like a bug in mariadb 10.1.16 if mariadb 5.5/10.0 and 10.1.14 and below all work fine with custom tmpdir defined

    might need to manually downgrade back to 10.1.14 with steps outlined at MariaDB - MariaDB 10.1.15 now available | Centmin Mod Community

    posted a jira issue at [MDEV-10399] custom tmpdir permission denied only in 10.1.16 - JIRA so wait and see

    temp work around for 10.1.16 would be to comment out in /etc/my.cnf the custom tmpdir path and revert back to default /tmp for mysql tmpdir
    Code (Text):
    tmpdir=/home/mysqltmp

    but only do this if your system default /tmp has enough free disk space for roughly 4-6x times the size of your largest mysql database table size

    compare disk free space for /tmp and /home/mysqltmp
    Code (Text):
    df -hT /tmp /home/mysqltmp/
    

    In below example both reside on same device/partition so removing custom tmpdir setting in /etc/my.cnf is fine provided free space available is sufficient ~4-6x times the size of your largest mysql database table size
    Code (Text):
    df -hT /tmp /home/mysqltmp/
    Filesystem              Type  Size  Used Avail Use% Mounted on
    /dev/mapper/centos-root xfs    13G  4.2G  8.9G  32% /
    /dev/mapper/centos-root xfs    13G  4.2G  8.9G  32% /
    

    on small VPS servers and some dedicated default system /tmp lacks the disk free space for mysql tasks so you can end up corrupting data or failing to properly repair corrupted mysql data. That is why centmin mod out of box sets custom tmpdir on /home/mysqltmp as /home is usually the largest disk partition of available disk space on a server
     
    Last edited: Jul 20, 2016
    • Informative Informative x 1
  18. Revenge

    Revenge Active Member

    287
    64
    28
    Feb 21, 2016
    Portugal
    Ratings:
    +227
    Local Time:
    11:57 AM
    1.9.x
    10.1.x
  19. eva2000

    eva2000 Administrator Staff Member

    29,702
    6,707
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,009
    Local Time:
    8:57 PM
    Nginx 1.13.x
    MariaDB 5.5
    beat me to it.. seems specific to CentOS 7 only and systemd
    Sergei to the rescue
    work around would to disable protection creating file at /etc/systemd/system/mariadb.service.d/protecthome.conf with
    Code (Text):
    [Service]
    ProtectHome=false
    

    then for CentOS 7 run
    Code (Text):
    systemctl daemon-reload
    mysqlrestart
    
     
  20. pamamolf

    pamamolf Well-Known Member

    2,659
    240
    63
    May 31, 2014
    Ratings:
    +422
    Local Time:
    1:57 PM
    Nginx-1.13.x
    MariaDB 10.1.x
    Isn't better to use another custom path than disabling this secure measure?

    Also default Centminmod installation will need to automate that fix...

    Does this protection works on Centos 6 ?