[rt-users] RT ticket body shows GMT time instead of PST (GMT -7) in the Date: field

2013-04-16 Thread Pete Beebe
Hello, I've noticed a discrepancy in the time displayed in the ticket body when an transaction is entered via e-mail. Looking at the SMTP headers directly from the RT GUI it shows the time as being correct in the Received: sections of the header however the Date: field shows the time in GMT.

[rt-users] RT ticket body shows GMT time instead of PST (GMT -7) in the Date: field

2013-04-17 Thread Pete Beebe
Thanks for the reply. I just checked the 4.0.10 version we have running in our dev environment and it appears the issue still exists on that version. I just noticed that v4.0.11 is now available, when I get a moment I’ll upgrade to that version and retest. ~Pete_Jibe From: Ruslan Zakirov

[rt-users] RT ticket body shows GMT time instead of PST (GMT -7) in the Date: field

2013-04-17 Thread Pete Beebe
Hi Ruslan, Upon further testing it seems that v4.0.10 does have this fix in place for new transactions, only. It doesn’t appear that it corrects older RT records. Does that functionality sound correct to you? Either way, it’s good to know that the newer release addresses this for new

[rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-04 Thread Pete Beebe
Hello, I just completed a migration from MySQL to Oracle as well as an upgrade from 3.8.5 to 4.0.12. So far everything is running well however I have run across one error that occurs when, as super user, I click on the Global--RT At A Glance link. I receive an error in the WebUI followed by

[rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-14 Thread Pete Beebe
Your system config page and SQL results reveal that you have duplicate copies (3 total of each record) of certain global data. This suggests your migration from MySQL to Oracle was flawed. How did you migrate, exactly? As follows: 1. Created new OEL 6.4 x64 server running Apache/Mysqld from

[rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-15 Thread Pete Beebe
Hi Thomas, This might narrow down the issueI just noticed another thread titled RT at a Glance error after upgrade from 4.011 to 4.0.12 that also states the issue at hand. Just to be sure, I repeated the import on our RTDEV server using v4.0.11 of RT (using MySQL only, not Oracle) and

Re: [rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-15 Thread Pete Beebe
Hi Thomas, Just performed the RT migration from MySQL to Oracle using just 4.0.11 and re-tested the Global RT At A Glance error without issue. I will now repeat the 4.0.11 to 4.0.12 upgrade using just Oracle and update with results. ~Pete_Jibe Disclaimer: This electronic message may contain

[rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-15 Thread Pete Beebe
Hi Thomas, The 4.0.11 to 4.0.12 Oracle upgrade completed and this RT At A Glance issue still did not reappear. This was all done on our Dev system, however. The Prod OS/config is a clone of the so I'm at a loss as to what the difference would be that's causing this to occur. ~Pete_Jibe

Re: [rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-17 Thread Pete Beebe
end (other than re-instating those user records). For this particular problem it seems that me laying down a new install base somehow corrected the original issue. ~Pete_Jibe -Original Message- From: Pete Beebe Sent: Thursday, May 16, 2013 10:55 AM To: 'rt-users

Re: [rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-17 Thread Pete Beebe
Hi Thomas, Out of curiosity, how did you reinstate the user records? On the original RT 3.8.5 server I had a couple of mysql dumps available with the previously deleted records still intact. On the original server I copied one of the mysql backups to the RTDEV server, imported it into an

Re: [rt-users] Post upgrade 3.8.5 to 4.0.12 Global-RT At A Glance error

2013-05-20 Thread Pete Beebe
Frustratingly, I still can't reproduce the error locally on a handful of long-lived RT instances all of which have been upgraded through 4.0.12. Hi Thomas, Thank you for spending the time looking into this. Seeing as how my last step of laying down a new install base corrected the matter on