[rt-users] RT 3.6.1 and TikiWiki 1.9.7
I have been running RT 3.6.1 for several months now on a very beefy box hardware-wise, and wanted to add TikiWiki to it. Has anyone tried this? I am not having much luck. Any tips, or solutions found by others in the past would be greatly appreciated. Bob F ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Intermittent resolve ticket issue
I have an issue where just recently this symptom began happening on RT 3.6.1. When you resolve a ticket is says in the gui Ticket has been resolved, but remains open. Try a moment later, and then it works. Any ideas? I have found nothing in the logs that indicate an issue. Bob ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Intermittent resolve ticket issue
I have an issue where just recently this symptom began happening on RT 3.6.1. When you resolve a ticket is says in the gui Ticket has been resolved, but remains open. Try a moment later, and then it works. Any ideas? I have found nothing in the logs that indicate an issue. Bob ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
RE: [rt-users] 3.6.1 Ticket Priority never changes
In each Queue, I have the Priority set to start at 10 ( or lower ) and end at 0. I then have the Ticket should be completed in set to 10 days. I have tried it with different params, and still no luck. This is not a HUGE deal, because my team knows that ALL tickets are important, etc., but prioritizing them is a great feature. Thank you for your response. Bob From: Torsten Brumm [mailto:[EMAIL PROTECTED] Sent: Monday, October 02, 2006 2:55 AM To: Farrell,Bob Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] 3.6.1 Ticket Priority never changes Can you go more into detail? How have you set up the Priority Change? 2006/10/2, Farrell,Bob [EMAIL PROTECTED]: All, Any place I may have missed in configuration to allow the priority of tickets to actually function? Everything works great, except it appears the ticket priority is not moving at all. Thanks in advance. Bob Farrell ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com -- MFG Torsten Brumm http://www.torsten-brumm.de ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
RE: [rt-users] 3.6.1 Ticket Priority never changes
I have not. I will try that. Thank you. Bob From: Torsten Brumm [mailto:[EMAIL PROTECTED] Sent: Monday, October 02, 2006 5:32 AM To: Roy El-Hames Cc: Farrell,Bob; rt-users@lists.bestpractical.com Subject: Re: [rt-users] 3.6.1 Ticket Priority never changes @Roy: That was my next question ;-) Thanks @Bob: The End Prio at 0 is not a good idea i think, should the End Prio not greater than the initial Prio? 2006/10/2, Roy El-Hames [EMAIL PROTECTED]: Have you set up any cron jobs to decrease these priorities.. it does n't just happen ..look at rt-crontool. Regards; Roy Farrell,Bob wrote: In each Queue, I have the Priority set to start at 10 ( or lower ) and end at 0. I then have the Ticket should be completed in set to 10 days. I have tried it with different params, and still no luck. This is not a HUGE deal, because my team knows that ALL tickets are important, etc., but prioritizing them is a great feature. Thank you for your response. Bob From: Torsten Brumm [mailto:[EMAIL PROTECTED] ] Sent: Monday, October 02, 2006 2:55 AM To: Farrell,Bob Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] 3.6.1 Ticket Priority never changes Can you go more into detail? How have you set up the Priority Change? 2006/10/2, Farrell,Bob [EMAIL PROTECTED]: All, Any place I may have missed in configuration to allow the priority of tickets to actually function? Everything works great, except it appears the ticket priority is not moving at all. Thanks in advance. Bob Farrell ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com -- MFG Torsten Brumm http://www.torsten-brumm.de ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] 3.6.1 Ticket Priority never changes
All, Any place I may have missed in configuration to allow the priority of tickets to actually function? Everything works great, except it appears the ticket priority is not moving at all. Thanks in advance. Bob Farrell ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] RT 3.6.1 Logging
I cannot get RT to log any errors not sure why. I followed early posts and Wiki / Internet instructions. I DO get one PERL error: RT: DBD::mysql::st execute failed: Unknown column 'main.LookupType' in 'where clause' I did all the schema upgrades. Is there a way to fix this on an in place Production machine? Regards, Bob ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Tickets being LOST
I am getting a symptom on RT 3.6.1 where the RT box Auto Replies, ( with a Ticket number ) but when you go to the Queue, it is not there. If you search it by Ticket number, it says error ticket not recorded. This is now in Production after what I thought was INTENSE lab testing. Any ideas? This is an EMERGENCY type situation, so any input is greatly appreciated. Bob Farrell ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
RE: [rt-users] Tickets being LOST
Last observation: It is NOT on every ticket or particular Queue. It happens randomly. BF From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farrell,Bob Sent: Friday, August 25, 2006 7:25 PM To: rt-users@lists.bestpractical.com Subject: [rt-users] Tickets being LOST I am getting a symptom on RT 3.6.1 where the RT box Auto Replies, ( with a Ticket number ) but when you go to the Queue, it is not there. If you search it by Ticket number, it says error ticket not recorded. This is now in Production after what I thought was INTENSE lab testing. Any ideas? This is an EMERGENCY type situation, so any input is greatly appreciated. Bob Farrell ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
RE: [rt-users] Tickets being LOST
I have the log settings you have below, and nothing is logged. What's up with that ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farrell,Bob Sent: Friday, August 25, 2006 11:14 PM To: Ole Craig Cc: rt-users@lists.bestpractical.com Subject: RE: [rt-users] Tickets being LOST Will do. Also, I thought you could add correspondence via RT when resolving a ticket. It just gives the canned template. I can only converse via email with reply in RT from the interface. Was it always that way ? -Original Message- From: Ole Craig [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 10:36 PM To: Farrell,Bob Cc: rt-users@lists.bestpractical.com Subject: RE: [rt-users] Tickets being LOST Bob - Suggest you start logging at a finer level, e.g.: Set($LogToSyslog, 'debug'); Set($LogToScreen, 'error'); Set($LogToFile , 'debug'); Set($LogDir, '/var/log'); Set($LogToFileNamed , rt.log); On Fri, 2006-08-25 at 22:27 -0400, Farrell,Bob wrote: I left the defaults of log to rt log in RT_Siteconfig. I can find nothing logged. Also, It appeared I could not reopen a resolved ticket via an email response, but it does, it just takes like 30 minutes. Not sure what I did wrong. -Original Message- From: Ole Craig [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 8:20 PM To: Farrell,Bob Cc: rt-users@lists.bestpractical.com Subject: RE: [rt-users] Tickets being LOST Bob - Do you have logging setup? (RT_SiteConfig.pm, what are the values for $LogToSyslog $LogDir $LogToFileNamed What do you see in the logs when this happens? On Fri, 2006-08-25 at 20:14 -0400, Farrell,Bob wrote: Last observation: It is NOT on every ticket or particular Queue. It happens randomly. BF __ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farrell,Bob Sent: Friday, August 25, 2006 7:25 PM To: rt-users@lists.bestpractical.com Subject: [rt-users] Tickets being LOST I am getting a symptom on RT 3.6.1 where the RT box Auto Replies, ( with a Ticket number ) but when you go to the Queue, it is not there. If you search it by Ticket number, it says error ticket not recorded. This is now in Production after what I thought was INTENSE lab testing. Any ideas? This is an EMERGENCY type situation, so any input is greatly appreciated. Bob Farrell ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com -- /Ole Craig Security Engineer Team lead, customer support 303-381-3802 (main support hotline) 303-381-3824 (my direct line) 303-381-3801 (fax) www.stillsecure.com . . . ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them.
All, I have two machines that I want to move to RT 3.6.1, on new machines running MySql 5.0.22-1. Both units have MySql 4.0.18 on them. The RT machine with RT 3.4.1 imported just fine. The RT Machine with 3.0.11 did not. I built a standalone NEW box without issue. I understand this maybe a MySql issue, and no fault of RT, but was wondering if anyone had any ideas that could assist me. The mysql dump from 3.4.1 was a simple mysql dump to a backup.sql file and imported fine. The 3.0.11 mysql dump gave me table rt3.atrribute missing in the logs when bringing up the RT interface after login, and I could not navigate anywhere, although I did see the queues in the drop down menu. Any MySql gurus out there that may have run across this before? I added the attribute table, and now can see ALL tickets, etc, but no comments /data /email correspondence in them under the History section. I also get an internal error has occurred when creating a ticket in the RT 3.0.11 to 3.6.1 box, but the ticket does in fact get created. ( still wont fly with the admins though ) A requirement of this facility that uses RT 3.0.11 is that all History, time worked, etc. is retained in the migration. I am hoping to use the existing Rt3.0.11 mysql dumps and move the data, not go the upgrade mysql revision by revision route. Could this be repaired via an RT setting, or am I stuck in mysql upgrade land ? Or perhaps a person has an idea I have not even thought of. Any help would be greatly appreciated. Kudos to Jesse Vincent and the Team, as the new box, and the 3.4.1 upgrade are working flawlessly ! Thanks Bob ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them.
Mathew, Do you mean make upgrade for the RT make or from the mysql prompt? Bob -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 6:47 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them. You're stuck doing the upgrade. Each revision introduces new aspects to the database schema that need to be integrated smoothly in order to make everything work well. It isn't that big a process. Simply import the database onto the new machine's instance of MySQL and run 'make upgrade' for 3.6.1. It will update the schema to the proper settings for use with the newer version. The same can be done for 3.4.1. By trying other methods you are creating more work than will be done by simply running the upgrade in the first place. Mathew Snyder Farrell,Bob wrote: All, I have two machines that I want to move to RT 3.6.1, on new machines running MySql 5.0.22-1. Both units have MySql 4.0.18 on them. The RT machine with RT 3.4.1 imported just fine. The RT Machine with 3.0.11 did not. I built a standalone NEW box without issue. I understand this maybe a MySql issue, and no fault of RT, but was wondering if anyone had any ideas that could assist me. The mysql dump from 3.4.1 was a simple mysql dump to a backup.sql file and imported fine. The 3.0.11 mysql dump gave me table rt3.atrribute missing in the logs when bringing up the RT interface after login, and I could not navigate anywhere, although I did see the queues in the drop down menu. Any MySql gurus out there that may have run across this before? I added the attribute table, and now can see ALL tickets, etc, but no comments /data /email correspondence in them under the History section. I also get an internal error has occurred when creating a ticket in the RT 3.0.11 to 3.6.1 box, but the ticket does in fact get created. ( still won't fly with the admins though ) A requirement of this facility that uses RT 3.0.11 is that all History, time worked, etc. is retained in the migration. I am hoping to use the existing Rt3.0.11 mysql dumps and move the data, not go the upgrade mysql revision by revision route. Could this be repaired via an RT setting, or am I stuck in mysql upgrade land ? Or perhaps a person has an idea I have not even thought of. Any help would be greatly appreciated. Kudos to Jesse Vincent and the Team, as the new box, and the 3.4.1 upgrade are working flawlessly ! Thanks Bob -- -- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them.
AND /usr/local/rt3/sbin/rt-setup-database --dba root \ --prompt-for-dba-password \ --action schema \ --datadir /MY/rt/sourcedir/rt-3.4.4/etc/upgrade/3.0.11 -Original Message- From: Farrell,Bob Sent: Monday, August 21, 2006 9:07 PM To: Farrell,Bob; Mathew Snyder Cc: RT-Users@lists.bestpractical.com Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. I ran /usr/local/rt3/sbin/rt-setup-database --dba root \ --prompt-for-dba-password \ --action schema \ --datadir /MY/rt/sourcedir/rt-3.0.11/etc/upgrade/3.6.1 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farrell,Bob Sent: Monday, August 21, 2006 9:04 PM To: Mathew Snyder Cc: RT-Users@lists.bestpractical.com Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. What if there is no 3.0.11 ? ( it starts at 3.1.0 ) Thanks for all of your help. Bob -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 8:30 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them. Farrell,Bob wrote: Mathew, Do you mean make upgrade for the RT make or from the mysql prompt? Bob -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 6:47 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them. You're stuck doing the upgrade. Each revision introduces new aspects to the database schema that need to be integrated smoothly in order to make everything work well. It isn't that big a process. Simply import the database onto the new machine's instance of MySQL and run 'make upgrade' for 3.6.1. It will update the schema to the proper settings for use with the newer version. The same can be done for 3.4.1. By trying other methods you are creating more work than will be done by simply running the upgrade in the first place. Mathew Snyder Farrell,Bob wrote: All, I have two machines that I want to move to RT 3.6.1, on new machines running MySql 5.0.22-1. Both units have MySql 4.0.18 on them. The RT machine with RT 3.4.1 imported just fine. The RT Machine with 3.0.11 did not. I built a standalone NEW box without issue. I understand this maybe a MySql issue, and no fault of RT, but was wondering if anyone had any ideas that could assist me. The mysql dump from 3.4.1 was a simple mysql dump to a backup.sql file and imported fine. The 3.0.11 mysql dump gave me table rt3.atrribute missing in the logs when bringing up the RT interface after login, and I could not navigate anywhere, although I did see the queues in the drop down menu. Any MySql gurus out there that may have run across this before? I added the attribute table, and now can see ALL tickets, etc, but no comments /data /email correspondence in them under the History section. I also get an internal error has occurred when creating a ticket in the RT 3.0.11 to 3.6.1 box, but the ticket does in fact get created. ( still won't fly with the admins though ) A requirement of this facility that uses RT 3.0.11 is that all History, time worked, etc. is retained in the migration. I am hoping to use the existing Rt3.0.11 mysql dumps and move the data, not go the upgrade mysql revision by revision route. Could this be repaired via an RT setting, or am I stuck in mysql upgrade land ? Or perhaps a person has an idea I have not even thought of. Any help would be greatly appreciated. Kudos to Jesse Vincent and the Team, as the new box, and the 3.4.1 upgrade are working flawlessly ! Thanks Bob - - -- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com RT. You will first run the ./configure with whichever options you require. Then verify that all perl modules are installed with 'make testdeps'. Once all modules are squared away run 'make upgrade'. This will prepare all the scripts necessary to update the database schema. Once 'make upgrade' has completed you will need to cd to etc/upgrade within the RT source directory. Inside you will find several directories which require a command be run for each. The command will look similar to this: /usr/local/rt3/sbin/rt-setup-database --dba root \ --prompt-for-dba-password \ --action schema \ --datadir /your/rt/sourcedir/rt-3.4.4/etc/upgrade/version You'll have to replace '--action schema
RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them.
IT WORKED ! Thanks Mathew ! -Original Message- From: Farrell,Bob Sent: Monday, August 21, 2006 9:13 PM To: Farrell,Bob; 'Mathew Snyder' Cc: 'RT-Users@lists.bestpractical.com' Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. AND /usr/local/rt3/sbin/rt-setup-database --dba root \ --prompt-for-dba-password \ --action schema \ --datadir /MY/rt/sourcedir/rt-3.4.4/etc/upgrade/3.0.11 -Original Message- From: Farrell,Bob Sent: Monday, August 21, 2006 9:07 PM To: Farrell,Bob; Mathew Snyder Cc: RT-Users@lists.bestpractical.com Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. I ran /usr/local/rt3/sbin/rt-setup-database --dba root \ --prompt-for-dba-password \ --action schema \ --datadir /MY/rt/sourcedir/rt-3.0.11/etc/upgrade/3.6.1 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farrell,Bob Sent: Monday, August 21, 2006 9:04 PM To: Mathew Snyder Cc: RT-Users@lists.bestpractical.com Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. What if there is no 3.0.11 ? ( it starts at 3.1.0 ) Thanks for all of your help. Bob -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 8:30 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them. Farrell,Bob wrote: Mathew, Do you mean make upgrade for the RT make or from the mysql prompt? Bob -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 6:47 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them. You're stuck doing the upgrade. Each revision introduces new aspects to the database schema that need to be integrated smoothly in order to make everything work well. It isn't that big a process. Simply import the database onto the new machine's instance of MySQL and run 'make upgrade' for 3.6.1. It will update the schema to the proper settings for use with the newer version. The same can be done for 3.4.1. By trying other methods you are creating more work than will be done by simply running the upgrade in the first place. Mathew Snyder Farrell,Bob wrote: All, I have two machines that I want to move to RT 3.6.1, on new machines running MySql 5.0.22-1. Both units have MySql 4.0.18 on them. The RT machine with RT 3.4.1 imported just fine. The RT Machine with 3.0.11 did not. I built a standalone NEW box without issue. I understand this maybe a MySql issue, and no fault of RT, but was wondering if anyone had any ideas that could assist me. The mysql dump from 3.4.1 was a simple mysql dump to a backup.sql file and imported fine. The 3.0.11 mysql dump gave me table rt3.atrribute missing in the logs when bringing up the RT interface after login, and I could not navigate anywhere, although I did see the queues in the drop down menu. Any MySql gurus out there that may have run across this before? I added the attribute table, and now can see ALL tickets, etc, but no comments /data /email correspondence in them under the History section. I also get an internal error has occurred when creating a ticket in the RT 3.0.11 to 3.6.1 box, but the ticket does in fact get created. ( still won't fly with the admins though ) A requirement of this facility that uses RT 3.0.11 is that all History, time worked, etc. is retained in the migration. I am hoping to use the existing Rt3.0.11 mysql dumps and move the data, not go the upgrade mysql revision by revision route. Could this be repaired via an RT setting, or am I stuck in mysql upgrade land ? Or perhaps a person has an idea I have not even thought of. Any help would be greatly appreciated. Kudos to Jesse Vincent and the Team, as the new box, and the 3.4.1 upgrade are working flawlessly ! Thanks Bob - - -- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com RT. You will first run the ./configure with whichever options you require. Then verify that all perl modules are installed with 'make testdeps'. Once all modules are squared away run 'make upgrade'. This will prepare all the scripts necessary to update the database schema. Once 'make upgrade' has completed you will need to cd to etc/upgrade within the RT source directory. Inside you will find several
RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them.
WOW ! Yes, we run postgresql as well at our companies. Funny, but seem easier to me. Thanks Again ! BF -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 9:41 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. Farrell,Bob wrote: IT WORKED ! Thanks Mathew ! -Original Message- From: Farrell,Bob Sent: Monday, August 21, 2006 9:13 PM To: Farrell,Bob; 'Mathew Snyder' Cc: 'RT-Users@lists.bestpractical.com' Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. AND /usr/local/rt3/sbin/rt-setup-database --dba root \ --prompt-for-dba-password \ --action schema \ --datadir /MY/rt/sourcedir/rt-3.4.4/etc/upgrade/3.0.11 -Original Message- From: Farrell,Bob Sent: Monday, August 21, 2006 9:07 PM To: Farrell,Bob; Mathew Snyder Cc: RT-Users@lists.bestpractical.com Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. I ran /usr/local/rt3/sbin/rt-setup-database --dba root \ --prompt-for-dba-password \ --action schema \ --datadir /MY/rt/sourcedir/rt-3.0.11/etc/upgrade/3.6.1 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farrell,Bob Sent: Monday, August 21, 2006 9:04 PM To: Mathew Snyder Cc: RT-Users@lists.bestpractical.com Subject: RE: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 witholder MySql versions on them. What if there is no 3.0.11 ? ( it starts at 3.1.0 ) Thanks for all of your help. Bob -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 8:30 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them. Farrell,Bob wrote: Mathew, Do you mean make upgrade for the RT make or from the mysql prompt? Bob -Original Message- From: Mathew Snyder [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 6:47 PM To: Farrell,Bob Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them. You're stuck doing the upgrade. Each revision introduces new aspects to the database schema that need to be integrated smoothly in order to make everything work well. It isn't that big a process. Simply import the database onto the new machine's instance of MySQL and run 'make upgrade' for 3.6.1. It will update the schema to the proper settings for use with the newer version. The same can be done for 3.4.1. By trying other methods you are creating more work than will be done by simply running the upgrade in the first place. Mathew Snyder Farrell,Bob wrote: All, I have two machines that I want to move to RT 3.6.1, on new machines running MySql 5.0.22-1. Both units have MySql 4.0.18 on them. The RT machine with RT 3.4.1 imported just fine. The RT Machine with 3.0.11 did not. I built a standalone NEW box without issue. I understand this maybe a MySql issue, and no fault of RT, but was wondering if anyone had any ideas that could assist me. The mysql dump from 3.4.1 was a simple mysql dump to a backup.sql file and imported fine. The 3.0.11 mysql dump gave me table rt3.atrribute missing in the logs when bringing up the RT interface after login, and I could not navigate anywhere, although I did see the queues in the drop down menu. Any MySql gurus out there that may have run across this before? I added the attribute table, and now can see ALL tickets, etc, but no comments /data /email correspondence in them under the History section. I also get an internal error has occurred when creating a ticket in the RT 3.0.11 to 3.6.1 box, but the ticket does in fact get created. ( still won't fly with the admins though ) A requirement of this facility that uses RT 3.0.11 is that all History, time worked, etc. is retained in the migration. I am hoping to use the existing Rt3.0.11 mysql dumps and move the data, not go the upgrade mysql revision by revision route. Could this be repaired via an RT setting, or am I stuck in mysql upgrade land ? Or perhaps a person has an idea I have not even thought of. Any help would be greatly appreciated. Kudos to Jesse Vincent and the Team, as the new box, and the 3.4.1 upgrade are working flawlessly ! Thanks Bob - - -- ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media
[rt-users] 3.61
I have been using RT for the last few years. I am getting the classic Youre almost there message, and would always solve it via the rt.conf file and add the perl parameters. This file does not appear to exist anymore. I am trying to find which file to edit so that RT can utilize mod_perl2. I now see perl.conf and perl-HTML-Mason.conf in the conf.d include directory. Any help would be appreciated. Bob ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] 3.6.1
I have been using RT for the last few years. I am getting the classic Youre almost there message, and would always solve it via the rt.conf file and add the perl parameters. This file does not appear to exist anymore. I am trying to find which file to edit so that RT can utilize mod_perl2. I now see perl.conf and perl-HTML-Mason.conf in the conf.d include directory. Any help would be appreciated. Bob ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
