Today, I finally got access to my production server that the IT department set up on our VM box in KY.
I'm in California, which is where my ad-hoc production server has been residing while we try osTicket out.
To migrate the server:
- I did a mysql dump of the osTicket database using Navicat
- Installed osTicket on the new server
- Imported the osTicket Data
- Re-Edited email passwords
I also setup the cron job, and waited for my test messages to get processed.
They didn't.
After spending a better part of my day trying to figure out why it wasn't working, I decided to enable to Auto-Cron, which worked exactly like it was supposed to.
I also copied the files from the ad-hoc development server to the production server, and the cron job still wasn't working.
I enabled Debugging for the Event Log, and my findings were rather odd.
When the Auto-Cron is enabled, both the Auto Cron & Cron job will run, but, that is the only time the Cron will actually run. (See below Quote)
I have updated the time zone on osTicket so that it matches the server time.
I am thinking that this is related some how to the timezones and time differences between the two servers; the cron script doesn't seem to bomb out at all.
Suggestions?
Thanks
Tue, Sep 1 2009 2 Autocron
cron job executed 172.16.81.125
Tue, Sep 1 2009 1 Cron Job
External cron job executed
Tue, Sep 1 2009 1 Autocron
cron job executed 172.16.81.125
Tue, Sep 1 2009 1 Autocron
cron job executed 172.16.81.125
Tue, Sep 1 2009 1 Cron Job
External cron job executed
Tue, Sep 1 2009 1 Autocron
cron job executed 172.16.81.125
Tue, Sep 1 2009 1 Autocron
cron job executed 172.16.81.125
Tue, Sep 1 2009 1 Cron Job
External cron job executed
Tue, Sep 1 2009 1 Autocron
cron job executed 172.16.81.125
Tue, Sep 1 2009 1 Cron Job
External cron job executed
Tue, Sep 1 2009 1 Autocron
cron job executed 172.16.81.125