Re: [rt-users] RT 3.8.1: Tickets interface logs you out
I can try that ... did you know if that changed in 3.8.0 to 3.8.1? Do you know what the database schema upgrade in the UPGRADING.mysql is for? I haven't gotten through that step without errors, but 3.8.0. seems to work just fine without successfully getting through it. Thanks for the suggestions Trent From: Chris Nelson [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 10:46 AM To: Golemon, Buck Cc: Trenton Taylor; [EMAIL PROTECTED] Subject: Re: [rt-users] RT 3.8.1: Tickets interface logs you out I may be way off here (I'm a total newbie). But Todd Green wrote this a couple days ago - might this help? Just hit and fixed this issue yesterday. My solution was to was to add the following to etc/RT_SiteConfig.pm Set($WebSessionClass , 'Apache::Session::File'); When I asked him what it was actually doing, this is what he said: In my digging I determined that by default the sessions are being written to the SQL database. Notes from others having similar issues indicated this might be part of the issue. My current production environment (3.4.2) writes the sessions to files instead of to the database so I used the same option in the new environment as well. Sorry if that's not helpful. -Chris On Thu, Sep 11, 2008 at 1:30 PM, Golemon, Buck [EMAIL PROTECTED] wrote: So you think it's in regard to upgrading? I'll try with a fresh database and let you know how it goes. --Buck -Original Message- From: Trenton Taylor [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 10:26 AM To: Golemon, Buck Subject: RE: [rt-users] RT 3.8.1: Tickets interface logs you out A bunch of us have the issue but it's being ignored on the lists ... I think jesse considers it our problem for not upgrading correctly. I upgraded from rt 3.6.6 to 3.8.0 and ran the upgrade script at the end of the install ... no errors and no log out issues in the interface I then upgraded from 3.8.0 to 3.8.1 and ran the upgrade script that was mentioned at the end of the install ... no errors but am logged out on some web clicks. I went back to 3.8.0 and don't have any problems now ... Did you follow the UPGRADING.mysql document? I got errors when trying it. Nobody has responded to me on the list .. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Golemon, Buck Sent: Thursday, September 11, 2008 9:17 AM To: [EMAIL PROTECTED] Subject: [rt-users] RT 3.8.1: Tickets interface logs you out After installing a new version of RT, I've noticed that whenever I click Tickets or interact with the query builder such that it reloads the page, it logs me out. I still remembers it's state after I log back in, but this is extremely annoying. Has anyone else had this problem? Please let me know if there's any other information you need. --Buck Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.19/1664 - Release Date: 2008-09-10 7:00 PM ___ 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.19/1664 - Release Date: 2008-09-11 7:03 AM Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you
[rt-users] schema.mysql-4.0-4.1.pl - uninitialized value output
When following the UPGRADING.mysql doc, I get this error: [EMAIL PROTECTED] rt-3.8.1]# perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 root ** sql.queries Use of uninitialized value in numeric gt () at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt () at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt () at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt () at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. The file sql.queries has data in it ... I don't really have anything to compare it to so I'm not sure if I should proceed or not. I had previously upgraded from RT 3.6.6 to 3.8.0 and then finally 3.8.1. I ran the upgrade (/opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade) inbetween each of those but missed the UPGRADING.mysql doc. I'm trying to go back and do this schema upgrade now. 1. Does anyone know what (or if I need to) I can do about the uninitialized value error? 2. Once that is resolved, what is the best way to get my database back on track and upgraded properly? DB: mysql-server.i386 4.1.20-3.RHEL4.1.el4_6 CENTOS 4.6 Thanks in advance, Trent Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. ___ 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 requiring login for some links
I checked some of my configs against the suggestions in the list, but I haven't come across anything that fixes it. Our RT is mostly functional except it prompts for a login if you select another queue from the homepage (it goes to the queue fine) and then try to open any of the tickets. Attempting to open that ticket will force a login. After a successful login, it goes to the ticket. Centos 4.6 Mysql 4.1.20-3.RHEL4.1.el4_6 RT 3.8.1 We did 3.6.6 to 3.8.0 to 3.8.1 with all db upgrades in between. If anyone knows a fix, I'd appreciate it. Trent From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Hopps Sent: Thursday, August 28, 2008 12:16 PM To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT requiring login for every click Firefox 3.0.1, IE 7.0.5730.11 both behave the same, and I'm running MYSQL 5.0.51a-3ubuntu5 and have been since Day 1. I performed the DB updates when upgrading from 3.6.6 to 3.8.0, and I also ran the update when going from 3.8.0 to 3.8.1. -Steve On Thu, Aug 28, 2008 at 2:03 PM, Kenneth Crocker [EMAIL PROTECTED] wrote: Steve, What DataBase are you using and what browser? Kenn LBNL On 8/28/2008 11:46 AM, Steve Hopps wrote: I'm also having this problem since upgrading from 3.8.0 to 3.8.1. http://3.8.1. The //Apache::Session::File// work-around does fix this but it behaves differently than it used to, and I'm concerned about security with this setting turned on. Anyone had any luck solving this? The suggestion below didn't apply to me -Steve Marco, I had a similar problem after the 3.8.1 upgrade even though my database was updated correctly, and I saw the same problem with the file session handler. I was actually able to fix my issue by taking a trailing slash off my $WebBaseURL.It seemed like URLs with multiple // in them were resulting in the extra login prompts. So, that might be something to look at if you've exhausted all the other possibilities. Worked for me. -- Matt On Thu, Aug 28, 2008 at 6:02 AM, Marco Avvisano marco.avvisano at regione.toscana.it http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users wrote: / // I have the same problem but not for every click // // RT 3.8.1 // Mysql 4.1.22 // OS: Linux 2.4.21-37.ELsmp // // any suggestions // // thanks // // Marco // // - Original Message - // From: Ruslan Zakirov ruz at bestpractical.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users // To: Mark Hazen markh at intechgra.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users // Cc: rt-users at lists.bestpractical.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users // Sent: Wednesday, August 06, 2008 10:34 PM // Subject: Re: [rt-users] RT requiring login for every click // // // I saw your followups on this issue, but I want to comment this. // // Yes, these fixes I was talking about have been integrated into 3.8.0 // and as well several fixes would be in 3.8.1 (3.8.1rc1 is available at // this moment for download from our server). // // Affects: RT on mysql 4.1 and newer with utf8 as default DB charset // WHEN RT's DB was created, changing mysql options would not help much // // Symptoms: constant login requests on every action // // Check: change session handler to Apache::Session::File, if problem // goes away then it's this issue. // // Otherwise issue is different and needs more investigation. In this // case (according to Mark's further comments) situation is different. // // Hope this would help isolate different problems in future. // // On Tue, Aug 5, 2008 at 5:24 AM, Mark Hazen markh at intechgra.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users wrote: // Hiya folks, // // I saw this mentioned on the list a couple months back, but under Gentoo, // and while the issue was related to the MySQL language configuration, // there was a note from ruz at bp http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users stating that this was an issue related the // default charset setting for MySQL (under Gentoo, though) which had been // addressed for the next release (under 3.6, so it'd be incorporated into // 3.8 I'm guessing). // // When a user (admin user in this case) logs in, they get the home page, // but any subsequent clicks bring the login page up again. The system and // Apache logs don't reveal any errors, just a successful login message // when the logins are made. // // I've checked the database and the cookie, and the RT_SID is identical // and being updated with each request. We did have default-character-set // as utf8 as recommended for Dovecot on the same machine, but I've // commented that out and restarted all associated services, and we still // have the multiple
[rt-users] dependency question about GD in cpan
I'm running CentOS 4.6 and I'm stuck on the GD dependency ... Does anyone else have issues with GD in Cpan? I can just install from an RPM but I'm curious why Cpan always gives me headaches on GD. Thanks in advance ... Test Summary Report --- t/axestype.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 13 tests but ran 0. t/bugfixes.t (Wstat: 65280 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 255 Parse errors: Bad plan. You planned 33 tests but ran 1. t/use.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 10 tests but ran 0. Files=6, Tests=63, 1 wallclock secs ( 0.01 usr 0.11 sys + 0.07 cusr 0.30 csys = 0.49 CPU) Result: FAIL Failed 3/6 test programs. 1/63 subtests failed. make: *** [test_dynamic] Error 2 BWARFIELD/GDGraph-1.44.tar.gz /usr/bin/make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports BWARFIELD/GDGraph-1.44.tar.gz Running make install make test had returned bad status, won't install without force Failed during this command: LDS/GD-2.39.tar.gz : writemakefile NO '/usr/bin/perl Makefile.PL' returned status 512 MVERB/GDTextUtil-0.86.tar.gz : make_test NO BWARFIELD/GDGraph-1.44.tar.gz: make_test NO Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. ___ 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] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script)
Nope ... Still no upgraded DB. We use Mysql. I am basically running a new instance of RT and an additional archive DB now. We don't have many tickets on the new DB so I could easily delete them if someone could explain to me what is going wrong with the upgrade script. Kenn ... what did your upgrade command look like? Anything different than mine? (/opt/rt3.6/sbin/rt-setup-database --action schema \ --datadir etc/upgrade/3.5.1 --dba root --prompt-for-dba-password) Thanks in advance to anyone who helps out ... Trent -Original Message- From: Kenneth Crocker [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 12:02 PM To: Trenton Taylor Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script) Trenton, Did you get an answer to this? I just finished the same upgrade. We use Oracle. Kenn LBNL On 4/17/2008 8:30 AM, Trenton Taylor wrote: I'm trying to upgrade my RT system from 3.4.5 to 3.6.4 via: # command: /opt/rt3.6/sbin/rt-setup-database --action schema \ --datadir etc/upgrade/3.5.1 --dba root --prompt-for-dba-password But I am getting this error: #: Creating database schema. Problem with statement: CREATE TABLE Attachments ( id INTEGER NOT NULL AUTO_INCREMENT, TransactionId integer NOT NULL , Parent integer NOT NULL DEFAULT 0 , MessageId varchar(160) NULL , Subject varchar(255) NULL , Filename varchar(255) NULL , ContentType varchar(80) NULL , ContentEncoding varchar(80) NULL , Content LONGTEXT NULL , Headers LONGTEXT NULL , Creator integer NOT NULL DEFAULT 0 , Created DATETIME NULL , PRIMARY KEY (id) ) TYPE=InnoDB Table 'Attachments' already exists at /opt/rt3.6/sbin/rt-setup-database line 220, SCHEMA line 464. Thanks in advance - Trent Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. ___ 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 Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. ___ 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] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script)
I tried running my old database (the one that installs with 3.4.5) and the webpage is blank after a user logs in. If I skip the Schema and run the Insert, I get: Use of uninitialized value in concatenation (.) or string at /opt/rt3.6/sbin/rt-setup-database line 164, STDIN line 1. [Mon Apr 21 19:45:31 2008] [crit]: Can't locate /content in @INC (@INC contains: /opt/rt3/lib /opt/rt3/local/lib /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi /usr/lib/perl5/5.8.6 .) at /opt/rt3.6/sbin/rt-setup-database line 464, STDIN line 1. (/opt/rt3/lib/RT.pm:295) Thanks for the help ... Any more ideas? -Original Message- From: Kenneth Crocker [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 12:38 PM To: Trenton Taylor Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script) Trenton, What I found was that I didn't need to BUILD the schema, just upgrade it. In fact, there are 3 DB upgrade executions we did (due to 3.5.1), which were: 1) action schema 2) action acl 3) action insert Turns out, the only one that did anything was action insert. The DB changes due to 3.5.1 do not really change any schema design or major stuff like that, it merely adds two new queries (10 unowned my tickets) as default and updates the privileges so they can be used. I actually upgraded and forgot to run the DB upgrade part and RT worked fine, except those two queries were NOT listed or available. I ran the three actions and those two queries were available for home page selection. I'm not familiar with how MySQL works as a database (in terms of schema changes) so perhaps it requires a rebuild. Here's what I used as my commands: 1) Typed /tools/bin/perl/apps/rt/rt-[3.6.4]/sbin/rt-setup-database -dba rtadm -prompt-for-dba-password -action schema -datadir etc/upgrade/[3.5.1] enter as one line. 2) Typed /tools/bin/perl/apps/rt/rt-[3.6.4]/sbin/rt-setup-database -dba rtadm -prompt-for-dba-password -action acl -datadir etc/upgrade/[3.5.1] enter as one line. 3) Typed /tools/bin/perl/apps/rt/rt-[3.6.4]/sbin/rt-setup-database -dba rtadm -prompt-for-dba-password -action insert -datadir etc/upgrade/[3.5.1] enter as one line. Hope this helps. Kenn LBNL On 4/21/2008 12:10 PM, Trenton Taylor wrote: Nope ... Still no upgraded DB. We use Mysql. I am basically running a new instance of RT and an additional archive DB now. We don't have many tickets on the new DB so I could easily delete them if someone could explain to me what is going wrong with the upgrade script. Kenn ... what did your upgrade command look like? Anything different than mine? (/opt/rt3.6/sbin/rt-setup-database --action schema \ --datadir etc/upgrade/3.5.1 --dba root --prompt-for-dba-password) Thanks in advance to anyone who helps out ... Trent -Original Message- From: Kenneth Crocker [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 12:02 PM To: Trenton Taylor Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script) Trenton, Did you get an answer to this? I just finished the same upgrade. We use Oracle. Kenn LBNL On 4/17/2008 8:30 AM, Trenton Taylor wrote: I'm trying to upgrade my RT system from 3.4.5 to 3.6.4 via: # command: /opt/rt3.6/sbin/rt-setup-database --action schema \ --datadir etc/upgrade/3.5.1 --dba root --prompt-for-dba-password But I am getting this error: #: Creating database schema. Problem with statement: CREATE TABLE Attachments ( id INTEGER NOT NULL AUTO_INCREMENT, TransactionId integer NOT NULL , Parent integer NOT NULL DEFAULT 0 , MessageId varchar(160) NULL , Subject varchar(255) NULL , Filename varchar(255) NULL , ContentType varchar(80) NULL , ContentEncoding varchar(80) NULL , Content LONGTEXT NULL , Headers LONGTEXT NULL , Creator integer NOT NULL DEFAULT 0 , Created DATETIME NULL , PRIMARY KEY (id) ) TYPE=InnoDB Table 'Attachments' already exists at /opt/rt3.6/sbin/rt-setup-database line 220
Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script)
Well now you nailed down exactly what my issue is. I don't have the My Tickets or Unowned Tickets in the options. When I try to run the 3 upgrade scripts, I get the following: 1. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root --prompt-for-dba-password --action schema In order to create or update your RT database,this script needs to connect to your mysql instance on localhost as root. Please specify that user's database password below. If the user has no database password, just press return. Password: Creating database schema. Problem with statement: CREATE TABLE Attachments ( id INTEGER NOT NULL AUTO_INCREMENT, TransactionId integer NOT NULL , Parent integer NOT NULL DEFAULT 0 , MessageId varchar(160) NULL , Subject varchar(255) NULL , Filename varchar(255) NULL , ContentType varchar(80) NULL , ContentEncoding varchar(80) NULL , Content LONGTEXT NULL , Headers LONGTEXT NULL , Creator integer NOT NULL DEFAULT 0 , Created DATETIME NULL , PRIMARY KEY (id) ) TYPE=InnoDB Table 'Attachments' already exists at /opt/rt3.6/sbin/rt-setup-database line 220, SCHEMA line 464. 2. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root --prompt-for-dba-password --action acl In order to create or update your RT database,this script needs to connect to your mysql instance on localhost as root. Please specify that user's database password below. If the user has no database password, just press return. Password: Done setting up database ACLs. 3. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root --prompt-for-dba-password --action insert In order to create or update your RT database,this script needs to connect to your mysql instance on localhost as root. Please specify that user's database password below. If the user has no database password, just press return. Password: Use of uninitialized value in concatenation (.) or string at /opt/rt3.6/sbin/rt-setup-database line 164, STDIN line 1. [Mon Apr 21 20:12:58 2008] [crit]: Can't locate /content in @INC (@INC contains: /opt/rt3/lib /opt/rt3/local/lib /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi /usr/lib/perl5/5.8.6 .) at /opt/rt3.6/sbin/rt-setup-database line 464, STDIN line 1. (/opt/rt3/lib/RT.pm:295) I obviously need to get through these scripts successfully in order to have those options. Any ideas? Trent -Original Message- From: Kenneth Crocker [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 1:05 PM To: Trenton Taylor Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script) Trenton, By webpage, do you mean the Homepage? In 3.6.4, the first time any user signs on it will be blank. that's because the homepage settings (click Edit on the right of the RT at a glance tool bar (blue). Select what you want to see and then click home. After that, the homepage will come up with your selections every time. As to the DB upgrade, I'd advise to run all three commands anyway, can't hurt. Kenn LBNL On 4/21/2008 12:49 PM, Trenton Taylor wrote: I tried running my old database (the one that installs with 3.4.5) and the webpage is blank after a user logs in. If I skip the Schema and run the Insert, I get: Use of uninitialized value in concatenation (.) or string at /opt/rt3.6/sbin/rt-setup-database line 164, STDIN line 1. [Mon Apr 21 19:45:31 2008] [crit]: Can't locate /content in @INC (@INC contains: /opt/rt3/lib /opt/rt3/local/lib /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4
Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script)
I'm running the script as root with the root password for the SQL database. I can give myself whatever permissions needed. Am I missing that step? I though root had unlimited privilege to the DB. -Original Message- From: Kenneth Crocker [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 2:28 PM To: Trenton Taylor Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script) Trenton, Yep. Access to DataBases for the purpose of altering them is always limited. I had to have the permissions changed so I could run those scripts, then change them back to whatever. I suggest you speak to your DBA and Unix technicians about this. Kenn LBNL On 4/21/2008 1:45 PM, Trenton Taylor wrote: Well now you nailed down exactly what my issue is. I don't have the My Tickets or Unowned Tickets in the options. When I try to run the 3 upgrade scripts, I get the following: 1. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root --prompt-for-dba-password --action schema In order to create or update your RT database,this script needs to connect to your mysql instance on localhost as root. Please specify that user's database password below. If the user has no database password, just press return. Password: Creating database schema. Problem with statement: CREATE TABLE Attachments ( id INTEGER NOT NULL AUTO_INCREMENT, TransactionId integer NOT NULL , Parent integer NOT NULL DEFAULT 0 , MessageId varchar(160) NULL , Subject varchar(255) NULL , Filename varchar(255) NULL , ContentType varchar(80) NULL , ContentEncoding varchar(80) NULL , Content LONGTEXT NULL , Headers LONGTEXT NULL , Creator integer NOT NULL DEFAULT 0 , Created DATETIME NULL , PRIMARY KEY (id) ) TYPE=InnoDB Table 'Attachments' already exists at /opt/rt3.6/sbin/rt-setup-database line 220, SCHEMA line 464. 2. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root --prompt-for-dba-password --action acl In order to create or update your RT database,this script needs to connect to your mysql instance on localhost as root. Please specify that user's database password below. If the user has no database password, just press return. Password: Done setting up database ACLs. 3. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root --prompt-for-dba-password --action insert In order to create or update your RT database,this script needs to connect to your mysql instance on localhost as root. Please specify that user's database password below. If the user has no database password, just press return. Password: Use of uninitialized value in concatenation (.) or string at /opt/rt3.6/sbin/rt-setup-database line 164, STDIN line 1. [Mon Apr 21 20:12:58 2008] [crit]: Can't locate /content in @INC (@INC contains: /opt/rt3/lib /opt/rt3/local/lib /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi /usr/lib/perl5/5.8.6 .) at /opt/rt3.6/sbin/rt-setup-database line 464, STDIN line 1. (/opt/rt3/lib/RT.pm:295) I obviously need to get through these scripts successfully in order to have those options. Any ideas? Trent -Original Message- From: Kenneth Crocker [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 1:05 PM To: Trenton Taylor Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script) Trenton, By webpage, do you mean the Homepage? In 3.6.4, the first time any user signs on it will be blank. that's because the homepage settings (click Edit on the right of the RT at a glance tool bar (blue). Select what you want to see and then click home. After that, the homepage will come up with your selections every time. As to the DB upgrade, I'd advise to run all three commands anyway, can't hurt. Kenn LBNL On 4/21/2008 12:49 PM, Trenton Taylor wrote: I tried running my old database (the one that installs with 3.4.5) and the webpage is blank after a user logs in. If I skip the Schema and run the Insert, I get: Use of uninitialized value in concatenation
[rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script)
I'm trying to upgrade my RT system from 3.4.5 to 3.6.4 via: # command: /opt/rt3.6/sbin/rt-setup-database --action schema \ --datadir etc/upgrade/3.5.1 --dba root --prompt-for-dba-password But I am getting this error: #: Creating database schema. Problem with statement: CREATE TABLE Attachments ( id INTEGER NOT NULL AUTO_INCREMENT, TransactionId integer NOT NULL , Parent integer NOT NULL DEFAULT 0 , MessageId varchar(160) NULL , Subject varchar(255) NULL , Filename varchar(255) NULL , ContentType varchar(80) NULL , ContentEncoding varchar(80) NULL , Content LONGTEXT NULL , Headers LONGTEXT NULL , Creator integer NOT NULL DEFAULT 0 , Created DATETIME NULL , PRIMARY KEY (id) ) TYPE=InnoDB Table 'Attachments' already exists at /opt/rt3.6/sbin/rt-setup-database line 220, SCHEMA line 464. Thanks in advance - Trent Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. ___ 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
