OsTicket unbearably slow

timoy

I've been using OsTicket for about 3 months now and think it is great. About 1 week ago I enabled the stale ticket, and I'm not sure if it is a coincidence or not, but it seems as if that made OsTicket go REALLY slow. I disabled the stale ticket, cleared the system log, and it is still really slow.

We are using the latest release. What is bothering me is that it worked perfectly for several months.

Is there anything I Can do to speed this back up?

Hosted on Hostgator VPS with 2 processors

OsTicket Ver 1.6 ST

INCOMING EMAIL: POP

OUTGOING: php mail function

php version 5.2.17

Apache 2.2.19

Thanks

timoy

I turned off the "Enable Auto Cron" option and now the ticket system is fine.

It was taking about 28 seconds to load each screen, now it is back to normal )

Marky34

I turned off the "Enable Auto Cron" option and now the ticket system is fine.
It was taking about 28 seconds to load each screen, now it is back to normal )

I have the same problem and when I turned "autocron" off it´s fast again, BUT it didn´t fetch the emails with POP3 even when I´m pushing the "refresh" button.

PLEASE HELP.

ntozier

If you shut off autocron it will not collect emails, unless you setup a cron job to fetch mail every X amount of time.

Please see:

http://osticket.com/wiki/POP3/IMAP_Settings(http://osticket.com/wiki/POP3/IMAP_Settings)

Marky34

If you shut off autocron it will not collect emails, unless you setup a cron job to fetch mail every X amount of time.
Please see:
http://osticket.com/wiki/POP3/IMAP_Settings(http://osticket.com/wiki/POP3/IMAP_Settings)

Thanks for your email. Unfortunately, I´m using osTicket on a webhotell and cannot setup cron-job. Is it possible somehow to fix this problem with the auto-cron?

It worked perfect before and now it´s extreamly slow.

Marky34

I´m using osTicket on a webhotel so I don´t have access to cron.

Is it possible to solve the problem with autocron somehow instead?

ntozier

There are other threads on the forums with similar problems and what those people did to solve it. I recommend searching. It's not something that I have ever had a problem with.