• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

ErrorException [0]: Undefined array key "expires_gmt" Issues in cron.

Version
3.20.16
PHP version
7.4.26
Database driver
MySQL
Database version
5.5.5-10.4.24-MariaDB
Web browser
Chrome

ashkir

👽 Chevereto Freak
Has anyone figured out how to get cron to not error out? I’m guessing this is related to an update that happened and something didn’t execute quite right.

Processing checkHtaccess
* Enforce .htaccess files
✅ [DONE] Enforce completed (everything OK)
  • Processing cleanUnconfirmedUsers
  • Processing removeDeleteLog
  • Processing deleteExpiredImages
  • Processing storageDelete
  • Processing tryForUpdates

Aw, snap! Internal Server Error [debug @ print,error_log]

** errorId #bc6acbfd7b50d3e7 **
> ErrorException [0]: Undefined array key "expires_gmt"
At /home/nickpic/domains/nickpic.host/public_html/app/lib/classes/class.lock.php:37

Stack trace:
#0 /home/nickpic/domains/nickpic.host/public_html/app/lib/classes/class.lock.php(37): G\errorsAsExceptions()
#1 /home/nickpic/domains/nickpic.host/public_html/app/cron.php(100): CHV\Lock->create()
#2 /home/nickpic/domains/nickpic.host/public_html/app/cron.php(32): tryForUpdates()
#3 /home/nickpic/domains/nickpic.host/public_html/app/loader.php(242): require_once('/home/nickpic/domains/nickpic.host/public_html/app/cron.php')
#4 /home/nickpic/domains/nickpic.host/public_html/cli.php(36): include_once('/home/nickpic/domains/nickpic.host/public_html/app/loader.php')

Aw, snap! Internal Server Error [debug @ print,error_log]

** errorId #bc6acbfd7b50d3e7 **
> ErrorException [0]: Undefined array key "expires_gmt"
At /home/nickpic/domains/nickpic.host/public_html/app/lib/classes/class.lock.php:37

Stack trace:
#0 /home/nickpic/domains/nickpic.host/public_html/app/lib/classes/class.lock.php(37): G\errorsAsExceptions()
#1 /home/nickpic/domains/nickpic.host/public_html/app/cron.php(100): CHV\Lock->create()
#2 /home/nickpic/domains/nickpic.host/public_html/app/cron.php(32): tryForUpdates()
#3 /home/nickpic/domains/nickpic.host/public_html/app/loader.php(242): require_once('/home/nickpic/domains/nickpic.host/public_html/app/cron.php')
#4 /home/nickpic/domains/nickpic.host/public_html/cli.php(36): include_once('/home/nickpic/domains/nickpic.host/public_html/app/loader.php')
 
Man. I'm still scratching my head on this. I tried on a new install with a large queue and it worked fine. I'm going through the past updates to try and figure otu where the key expires_gmt comes into Chevereto and what the value is supposed to be. I got slammed with over 14,000 DMCA requests today and I'm gonna get shut down if I don't finish these deletions today.
 
Ouch, but you should be worry about something else. You are running 3.20.16, that's not the latest for V3. Update to latest then try again.
Once you're in a database above 1M> I've been testing every upgrade simply because the database upgrades are causing issues each time, so I've been testing them in an offline environment. So we've been upgrading a bit slowly. Also the upgrades stopped working in .17 due to "06:27:25 Missing license info"

It stopped working after I bought v4
 
I've been testing every upgrade simply because the database upgrades are causing issues each time, so I've been testing them in an offline environment
That's odd, database changes for 3.20.X appeared until 3.20.6, everything above that doesn't require any fancy DB upgrade query handling because there's no schema change from there. Most likely you have a broken schema, a totally normal thing to happen if you run a huge website.
 
Back
Top