[resolved] Loading screen taking too long

phantomofrussia

Hello, I have installed a fresh install of osTicket 1.9.3 on a fresh install of Ubuntu server 14.04Whenever I am creating a new ticket the "Loading" screen will stay on much longer than it used to on another installation of osticket has had on a different server. It might take about 30-60 seconds while before it was 1-2 seconds. I have the latest PHP, and MySQL installed on the server. Similar thing happens when I click Post Reply to a ticket as well.Thanks,Simon

long loading screen.jpg

phantomofrussia

any thoughts?This server is a VM and I have checked the performance logs and the server load is minimal.

phantomofrussia

After doing some troubleshooting I have found this only happens when osTicket has to send an email to the user notifying them of the ticket or update. If I opt out of that everything is super fast like before.

ntozier

Please help us to help you by posting some more information about your setup. This thread should give you a good idea of the generic information that we're looking for:Please read before requesting assistanceAlso since I haven't had this problem I'm going to compare it to my setup.

phantomofrussia

Below you will find the versions versions of PHP, server, and etc.:We

use IMAP for email fetching and sendmail for outgoing mail. I had the

exact same setup on a 12.02 Ubuntu server and osTicket 1.9.0 install

with no issues.Ubuntu Server: 14.04Web Server: Apache 2.4.7PHP: 5.5.9-1ubuntu4.3MySQL: 5.5.38

ntozier

Thanks

Chefkeks

Stupid question maybe, but does it also happen when you use SMTP to send the mails?

phantomofrussia

I do not have SMTP setup.

phantomofrussia

Well... looks like I got it figured out. Because the machine did not have a FQDN, sendmail was taking longer to work. I added the following line to /etc/hosts file:127.0.0.1 computername.domain.com computername localhostand the problem went away.

Chefkeks

Great you solved your problem :)

CharlesB

@[deleted] Thanks for posting your solution!I had the same issue, but with a new install. Since we hadn't been running any old version I had nothing to compare it to, and thought that the long delay was just "the way things were". I checked my /etc/hosts and sure enough, no FQDN.