Upgrade from v1.15.6?

aglyons

Are there any concerns about upgrading from V1.15.6 to the current v1.16.5 or v1.17.2?

Is that too far a jump? Should I step the updates?

KevinTheJedi

Nope you are fine. We’ve made our upgrader seamless so versions as early as 1.6 (released in 2008) can upgrade straight to the latest. Our upgrader does incremental database patches so it should never be an issue.

As always, you should make a full backup of the database and codebase before embarking on an upgrade. You should also have all the prerequisites met before upgrading. In addition you should download and install the latest plugins and language packs before upgrading. Once all of the above is done simply copy over the new code and run the upgrader via the UI. You can follow our documentation here:

https://docs.osticket.com/en/latest/Getting%20Started/Upgrade%20and%20Migration.html

Cheers.

aglyons

So if I read you correctly, and the link you shared, I do have a slight problem coming from 1.15.6.

should I be doing a migration rather than an update?

UPDATE: Nevermind, I got caught by that again. 1.15 is later than 1.6.

aglyons

So all did not go as planned.

I took the server offline, copied all the server files to my local system.

I cleared out all files on the server, uploaded the 'upload' folder files from the 1.16.5 zip file download.

I then uploaded my original ost-config.php file form the includes DIR.

With the server still configured to run PHP 7.4, the update screen comes up telling my to change to PHP v8. Once I change to PHP v8 all I get are 500 errors.

THe 500 error consists of this
[Wed Nov 16 15:13:47.303095 2022] [proxy_fcgi:error] [pid 15510:tid 140488011134720] [client 76.64.152.84:0] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Error: Call to undefined function set_time_limit() in /home/runcloud/webapps/Support_Dinner_Uncomplicated/include/class.upgrader.php:170\nStack trace:\n#0 /home/runcloud/webapps/Support_Dinner_Uncomplicated/include/class.upgrader.php(27): StreamUpgrader->__construct()\n#1 /home/runcloud/webapps/Support_Dinner_Uncomplicated/scp/upgrade.php(20): Upgrader->__construct()\n#2 {main}\n thrown in /home/runcloud/webapps/Support_Dinner_Uncomplicated/include/class.upgrader.php on line 170'

ramrajone

aglyons
Your PHP still shows version 7.4, you may need to restart the service to take effect

aglyons

ramrajone

I checked the log. The error message is in the post above.

aglyons Got error 'PHP message: PHP Fatal error: Uncaught Error: Call to undefined function set_time_limit() in /home/runcloud/webapps/Support_Dinner_Uncomplicated/include/class.upgrader.php:170

aglyons

ramrajone

That is me setting it back to v7.4.

If I set PHP to v8 I am unable to run the updater because of a 500 error.

My hosting management UI looks after restarting the services whenever PHP versions are changed.

ramrajone

aglyons
That error 500 is generic, check server logs, most likely permissions, or maybe missing PHP module for 8.1

aglyons

I should add that when the server is set to PHP v8, the 500 error ONLY shows on the updater page.

(/scp/system.php)

Going to the front end prior to performing the upgrader script I get the "Support Ticket System Offline" message.

I have made a clone of my install and performed the update process (clearing out the files from the server and uploading the ZIP file) twice.

Still the same results.

aglyons

Some more details that may shed some light.

My server is an NGINX/Apache hybrid managed by Runcloud. I've been running two different OSTIckets on these servers with no issues. Perhaps v1.16.5 has some differences that don't play nicely with NGINX in some way?

Running PHP 7.4.32, PHP 8.0.24

Disabled PHP extensions:
getmyuid,passthru,leak,listen,diskfreespace,tmpfile,link,ignore_user_abort,shell_exec,dl,set_time_limit,exec,system,highlight_file,source,show_source,fpassthru,virtual,posix_ctermid,posix_getcwd,posix_getegid,posix_geteuid,posix_getgid,posix_getgrgid,posix_getgrnam,posix_getgroups,posix_getlogin,posix_getpgid,posix_getpgrp,posix_getpid,posix,_getppid,posix_getpwuid,posix_getrlimit,posix_getsid,posix_getuid,posix_isatty,posix_kill,posix_mkfifo,posix_setegid,posix_seteuid,posix_setgid,posix_setpgid,posix_setsid,posix_setuid,posix_times,posix_ttyname,posix_uname,proc_open,proc_close,proc_nice,proc_terminate,escapeshellcmd,ini_alter,popen,pcntl_exec,socket_accept,socket_bind,socket_clear_error,socket_close,socket_connect,symlink,posix_geteuid,ini_alter,socket_listen,socket_create_listen,socket_read,socket_create_pair,stream_socket_server

KevinTheJedi

Richard63 That is unrelated.

aglyons

You need to contact your hosting company for further assistance. set_time_limit is a built-in PHP method. If that doesn’t exist it sounds like your PHP installation has deeper issues.

Cheers.

ramrajone

aglyons
NGINX out of box is not supported, so that's the reason some things working and some broken

Richard63

Since it's complaining about a time limit, maybe it's related to this thread concerning session limits.
https://forum.osticket.com/d/101833-users-having-to-double-submit-tickets-through-web-portal

Thre is a fix in there too.

Also be sure to disable your plugins before upgrading. One plugin disturbed things on my system too.

aglyons

My management UI, Runcloud, disables certain extensions by default by have complete access to enable them if needed. Turns out set_time_limit is one of those extensions that is disabled by default.

I changed that and can go forward with the upgrade.