The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Failed to validate my.cnf file for version 5.6

Discussion in 'Database Discussions' started by Kent Brockman, Aug 30, 2016.

Tags:
  1. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello guys! I'm interested in upgrading and old server to MariaDB 10.1 but the starting point is MySQL 5.5. When trying to upgrade to 5.6, this warning comes up:

    Code:
    System Specific Warnings
    Severity: Critical
    Message: The system detected issues with the current “/etc/my.cnf” file. These issues may interfere with the upgrade to MySQL 5.6:
    
    Failed to validate my.cnf file for version 5.6:
    160830  2:58:27 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
    160830  2:58:27 [ERROR] Aborting
    What does this mean? The my.cnf does contain nothing weird. In fact is the same configuration as in other servers where it worked just fine. Even if I rename my.cnf to something else, the error is the same. And I didn't found anything like this by googling.

    Any ideas?
    Thanks in advance
     
  2. vacancy

    vacancy Member

    Joined:
    Sep 20, 2012
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    What's in the my.cnf file content?
     
  3. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    Even if I emptied the my.cnf file the message is the same. So, I need some MySQL expert from cPanel here.
     
  4. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,470
    Likes Received:
    198
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    Did you restart MySQL after renaming the file? Silly question I know. You don't mention it though so I thought I would. :)
     
  5. rpvw

    rpvw Well-Known Member

    Joined:
    Jul 18, 2013
    Messages:
    121
    Likes Received:
    34
    Trophy Points:
    28
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    MySQL / MariaDB reads the my.cnf configuration files in a preset order. See the SQL docs for full details

    As well as an /etc/my.cnf , I found a /usr/my.cnf file that is read after the /etc/my.cnf

    You might want to search for any additional my.cnf files your system has :) perhaps your issue lies there.
     
  6. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    @Infopro: nope! Since this message happens at prerequisites checkpoint, I didn't thought a restart would be necessary.
    I can test that of course, but late in the night, because this server have huge sites in production actually.
     
  7. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    @rpvw:
    Please read my originally quoted code, it states that the conflict originate on “/etc/my.cnf”.

    Just for the curious, this is the content of my /etc/my.cnf:

    Code:
    [myisamchk]
    ft_min_word_len=2
    key_buffer_size=64M
    sort_buffer_size=64M
    read_buffer=2M
    write_buffer=2M
    
    [mysqld]
    bind-address=127.0.0.1
    tmp_table_size=120M
    max_heap_table_size=120M
    
    sort_buffer_size=6M
    read_buffer_size=2M
    read_rnd_buffer_size=2M
    default-storage-engine=INNODB
    
    query_cache_type=1
    query_cache_size=128M
    query_cache_limit=1M
    
    ft_min_word_len=2
    key_buffer_size=64M
    long_query_time=5
    max_allowed_packet=268435456
    max_connections=200
    myisam_sort_buffer_size=8M
    net_buffer_length=16K
    open_files_limit=50000
    table_cache=6000
    table_definition_cache=6000
    table_open_cache=6000
    thread_cache_size=16
    innodb_file_per_table=1
    
    innodb_buffer_pool_size=61865984
    [mysqldump]
    max_allowed_packet=16M
    quick
    
    [mysqlhotcopy]
    interactive-timeout
    Anything you can criticize? Let me know please.
     
  8. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,811
    Likes Received:
    671
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hi @Kent Brockman,

    The specific reason for the failed validation should appear in /usr/local/cpanel/logs/error_log when this happens. Do you notice any additional output in this log that's not in the UI?

    Thanks.
     
  9. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    @cPanelMichael:

    The response obtained is the same that is logged in the file. Some images will clarify that:


    tail errorlog.jpg blocker when upgrading to mysql56.jpg
     
  10. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,811
    Likes Received:
    671
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  11. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    Code:
    # mysql --version
    mysql  Ver 14.14 Distrib 5.5.35, for Linux (x86_64) using readline 5.1
     
  12. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,811
    Likes Received:
    671
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    The only time I've seen this happen in the past is when a third-party installation of Percona was installed, but that doesn't look to be the case here. Would you mind opening a support ticket so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome.

    Thank you.
     
  13. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    You're almost there pal. Yes, this is a VPS which originally came with Percona and I asked the hosting provider to switch it back to native MySQL. It was almost 2 years ago. Maybe some Percona debris may remain? And if so, will the tech ops in a ticket be able to cleanse it? I cannot move the sites hosted right now and at the same time wanted to at least upgrade to MySQL 5.6 to improve performance (the target of the switch is arrive to MariaDB 10 and PHP 7)
     
  14. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,811
    Likes Received:
    671
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    It's possible some leftover configuration data from the Percona installation is causing this problems. We can help to determine if that's the case in the support ticket, yes.

    Thank you.
     
Loading...

Share This Page