Skip to main content

System PHP issues with 11.40?

Comments

6 comments

  • regular13
    I forgot to mention...the pages aren't generating any visible errors, they just fail to load. Blank white page.
    0
  • cPanelKenneth
    [quote="regular13, post: 1479611">I forgot to mention...the pages aren't generating any visible errors, they just fail to load. Blank white page.
    Could you open a support ticket with us, please?
    0
  • simonas
    Would it be possible to have more information? I am planning switch to server which has 11.40. Thanks
    0
  • darrencain
    Ever since the update of 11.40 ( Inodes / file usage ) dont display the max limit ( set in cloudlinux ) in cpanel to users. I have reset the limits and re-applied them, no fix. It was working and displaying the file usage limit ( in the user end of cpanel ) before the update.
    0
  • EBdeKock
    We had the same issue with Logaholic after updating to 11.40 Tried force update, it didn't fix: /usr/local/cpanel/bin/update-logaholic --force Also tried: cd /usr/local/cpanel/base/3rdparty/Logaholic php update.php "conf=www.domain.co.za&reset=1" Which gave us an error: mysqli error: [1054: Unknown column 'lastused' in 'field list'] in EXECUTE("UPDATE _logaholic_Profiles SET lastused=xxxxxxx WHERE profilename='www.domain.co.za'") Logged a ticket, cPanel response: =========== There is an active case open with our developers(78249), which should be pushed to the repositories soon. However we do not have a formal ETA available. Once ready, the case number will be listed in our changelog, found here: [url=http://docs.cpanel.net/twiki/bin/view/AllDocumentation/ChangeLog/CPanelVersion1140]CPanelVersion1140 < AllDocumentation/ChangeLog < TWiki You may want to try implementing a work around in the mean time, by adding the column(as VARCHAR 60), to the table(_logaholic_Profiles) using the ALTER command from MySQL CLI. However, I would urge you to make a back up of that database prior to making these changes, to ensure impact to the data is minimized in the event of unforeseen circumstances. =========== Backed up database. Updated max_allowed_packet =64M in /etc/my.cnf. Restarted MySQL Ran: mysql> use logaholicDB_servername mysql> ALTER TABLE _logaholic_Profiles ADD lastused VARCHAR(60); After this I could manually update Logaholic and the client could once again access Logaholic.
    0
  • cPanelKenneth
    Case 78249 will be published in our next 11.40 build (due this week sometime). That will address the specific problem with Logaholic. I urge people having issues with other PHP applications served by cPanel & WHM to open support incidents with us.
    0

Please sign in to leave a comment.