Error on cli.php command run

[sprindesk]

I'm getting errors when I run this command " sudo -u sprintally php /home/sprintally/public_html/photos/cli.php -C cron " on SHH.

root@server:~# sudo -u sprintally php /home/sprintally/public_html/photos/cli.php -C cron
* Processing checkHtaccess
* Enforce .htaccess files
✅ [DONE] Enforce completed (everything OK)
* Processing storageDelete

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

** errorId #f22985aed7d56bc5 **
>> ErrorException [0]: Undefined array key "expires_gmt"
At /home/sprintally/public_html/photos/app/lib/classes/class.lock.php:37

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

 

[Rodolfo]

Hi, this seems to be a bug.

Go to chv_locks table and look for any row with empty lock_expires_gmt value, take a screenshot and upload it here to examine the situation.

 

[sprindesk]

Screenshot -

 

[Rodolfo]

look for any row with empty lock_expires_gmt value

Seems that there's no matching rows.

I'm afraid that the issue is somewhere else and I'm unable to determine where. You can open a bug report if you manage to replicate this in the Docker infra.

Try to truncate the locks table.

 

[sprindesk]

I'm not using Docker.

 

[Rodolfo]

Docker is required for bug reporting, thats why I mentioned it.

I'm afraid that I can't assist you. This is because I can't determine why your installation is doing this and it will require to investigate in-site if you want a proper solution.

 

[Rodolfo]

Dear @sprindesk,

Unfortunately, this ticket has more than 14 days without a reply or feedback from you. We will now consider this ticket abandoned and its status is now closed.

Please, don't hesitate to create a new ticket if this matter is still causing you trouble. If this is already solved you can ignore this message.