Hello,
I have an osticket installation working perfectly since several months ago. Now I'm having problems with new tickets opened via web.
User side:
When the user tries to open a ticket, get the following error:
:-(
Not sure what happened.. something broke though.
The ticket is opened, but empty and nobody receives notification by email.
Agent side:
We can see the ticket content of any old ticket (created before this problem starts) and respond.
But we can't check the ticket content nor response any ticket that was opened with the error mentioned before.
When we try to open one of the "error tickets" it takes too long to open, and when it opens it is empy and no way to send responses.
I tried opening a ticket for a user from the agent panel and I received the same error.
E-mail tickets:
I tried opening a ticket via e-mail, and it works perfectly, any user can open tickets via email and we can chceck the ticket content and send responses, also all email notifications works with tickets opened via email, lit it also works with tickets opened before this error starts.
This is really very strange, I can't figure out whats going on.
This is my system information screenshot:
https://prnt.sc/81_Z5eN_g90b
checking the error log I see the following:
https://soporteargentina.com/scp/tickets.php?queue=1
[Fri Sep 02 16:44:23.891483 2022] [:error] [pid 1554:tid 140711735301888] [client 186.19.99.19:34756] Failed loading /usr/local/ioncube/ioncube_loader_lin_8.0.so: /usr/local/ioncube/ioncube_loader_lin_8.0.so: cannot open shared object file: No such file or directory, referer: https://soporteargentina.com/scp/tickets.php?id=47
[Fri Sep 02 16:44:24.524369 2022] [:error] [pid 1554:tid 140711693338368] [client 186.19.99.19:34758] Failed loading /usr/local/ioncube/ioncube_loader_lin_8.0.so: /usr/local/ioncube/ioncube_loader_lin_8.0.so: cannot open shared object file: No such file or directory, referer: https://soporteargentina.com/scp/tickets.php?queue=1
[Fri Sep 02 16:44:24.871030 2022] [:error] [pid 1554:tid 140711676552960] [client 186.19.99.19:34760] Failed loading /usr/local/ioncube/ioncube_loader_lin_8.0.so: /usr/local/ioncube/ioncube_loader_lin_8.0.so: cannot open shared object file: No such file or directory, referer: https://soporteargentina.com/scp/tickets.php?queue=1
[Fri Sep 02 16:44:26.645570 2022] [:error] [pid 7925:tid 140711876491008] [client 186.19.99.19:34762] Failed loading /usr/local/ioncube/ioncube_loader_lin_8.0.so: /usr/local/ioncube/ioncube_loader_lin_8.0.so: cannot open shared object file: No such file or directory, referer: https://soporteargentina.com/scp/tickets.php?queue=1
[Fri Sep 02 16:44:56.876700 2022] [:error] [pid 7925:tid 140711876491008] [client 186.19.99.19:34762] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /home/soporte/public_html/include/class.orm.php on line 528, referer: https://soporteargentina.com/scp/tickets.php?queue=1
[Fri Sep 02 17:01:46.450489 2022] [:error] [pid 7925:tid 140711868098304] [client 181.45.77.217:35142] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /home/soporte/public_html/include/class.schedule.php on line 777, referer: http://soporteargentina.com/scp/tickets.php
[Fri Sep 02 17:01:46.869080 2022] [:error] [pid 1554:tid 140711626196736] [client 181.45.77.217:35144] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /home/soporte/public_html/include/class.schedule.php on line 794, referer: http://soporteargentina.com/scp/tickets.php
[Fri Sep 02 17:01:49.983307 2022] [:error] [pid 7925:tid 140711718516480] [client 181.45.77.217:35146] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /home/soporte/public_html/include/class.orm.php on line 237, referer: http://soporteargentina.com/scp/tickets.php
[Fri Sep 02 17:01:52.685840 2022] [:error] [pid 7925:tid 140711701731072] [client 181.45.77.217:35148] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /home/soporte/public_html/include/class.schedule.php on line 839, referer: http://soporteargentina.com/scp/tickets.php
The problem is not related to the 30 sec timeout because it worked perfectly until now with the same settings, anyway I changed it to 300 and still having the same problem.
