Re: [rt-users] Date::Parse issue causing auth cookies to expire - constant login request.
You may find the following from the archives to be helpful: http://lists.bestpractical.com/pipermail/rt-users/2006-September/041908.html Russ wrote: > Hi, > > I'm having trouble with a fresh install of Request Tracker 3.6.3 on a > Gentoo system. The install seems to be all up and running using FastCGI > (Not FCGID) and accepts the inital login of the root user. However the > instant you try and click anything from the menus it immediatly drops > you back to the login box. Once re-authenticated you reach your > desination but every click results in a login box first. As I > understand it the inbuilt authentication system is cookie based and have > discovered this problem in a log file: > > Jan 15 21:01:17 hostname RT: Successful login for root from 192.168.1.2 > (/opt/rt3/share/html/autohandler:256) > Jan 15 21:01:17 hostname RT: RT::Date used date::parse to make > 1970-01-01 -28800 > > So, from what I'm gathering the cookies are being set with a date way in > the past resulting in every click checking the cookie to see if its > still valid, finding an expiry date way in the past and requiring a new > cookie to be set through authentication. So I think the problem is > either in RT::Date or date::parse. Timezones are configured on the host > system and in RT's own configuration files. I have recompiled/checked > the latest version of date::parse from TimeDate-1.16.tar.gz and checked > both site_perl and vendor_perl Date modules matched. > > Does anyone have any ideas on how I can get this working. Is there a > glitch in the latest version of this module that I am unaware of? > > Thanks for any assistance you can offer. > > Russ > ___ 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] Odd behavior... Repeated Login and Attachment Problems
Hello, The alter table command below solved my repeated login problem also: ALTER TABLE sessions CHANGE a_session a_session LONGBLOB; In addition, I couldn't retrieve attachments after upgrading from 3.4.? to 3.6.1. Another poster provided the following similar solution: ALTER TABLE Attachments CHANGE Content Content LONGBLOB; In both cases the previous type was LONGTEXT. I observe in /opt/rt3/etc/mysql.schema LONGTEXT is defined as the type for both. I have also observed several of the posters with these problems operate Gentoo as I do. My first guess is this is not a Gentoo specific problem but wonder why I have not seen such reports on other platforms. Is this a likely bug worth reporting? Regards, David Roy El-Hames wrote: > What version of RT ?? There are few postings and suggested solutions but > the only one that worked for me was : > ALTER TABLE sessions CHANGE a_session a_session LONGBLOB; > I would suggest you look up the other solutions for this mailing list > first.. > my system is also gentoo and rt-3.6.1 > Roy > > [EMAIL PROTECTED] wrote: >> Hi all, >> >> I'm trying to install rt on a gentoo machine apache2 for the >> webserver. When I logon to rt it works fine, I changed my password, >> but everytime I >> click on some link. (ie. Configuration, Tools, Preferences) it asks me >> to re-authenticate. >> >> It's like it's never saving my information. I know I have cookies >> enabled, other websites work fine. Any ideas as to what could be causing >> the problem. >> >> >> -- >> Samir >> ___ 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] Attachments getting mangled
[EMAIL PROTECTED] wrote: > All, > >> Hello, Chris. >> Could you backup your DB, and run next to SQL queries? >> ALTER TABLE Attachments CHANGE Content Content LONGBLOB NULL; >> >> Then check if you could binary attachments without problems and report >> back. >> This query is safe but anyway I would suggest you to backup data. > > Running this fixed my attachment corruption problem, thanks! > > I think the Gentoo Installation Guide mentions changing some aspects of the > RT database in the comments section near the end of the document. This may > be why both Jeremy and I had this problem (we're both running on GenToo). I > followed the threads listed in that Guide to finally get it working, but I > honestly don't remember everything that was tweaked along the way. > > Perhaps someone more knowledgeable could change the GentooInstallGuide to > reflect the above fix for future users? Changing the Content type in the Attachments table from LONGTEXT to LONGBLOB via ALTER TABLE Attachments CHANGE Content Content LONGBLOB NULL; worked for me also. I observe the following in /opt/rt3/etc/schema.mysql: CREATE TABLE Attachments ( . . Content LONGTEXT NULL , . . ) TYPE=InnoDB; Is this an error in the RT3 MySQL schema? Running Gentoo and RT 3.6.1 Regards, David ___ 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] rt-3.6.1 glitch - Transactions not supported by database
Point of clarification: Recompiling DBD::mysql must be against the updated MySQL client library. One approach may be to update the MySQL install on the RT box prior to recompiling DBD::mysql. David Oberlitner wrote: > The MySQL client library has changed. > > Recompiling DBD::mysql solved the same problem for me. > > David > > Odhiambo Washington wrote: >> | >| >> | >| 2006/8/19, Odhiambo Washington <[EMAIL PROTECTED]>: >> | >| >I have rt-3.6.1 installed on a host different than the DB server. Today >> | >| >I moved my database from one server to the other (dump then import). >> | >| >MySQL-4.0.26 was in the old box, while the new box is MySQL-4.0.27. >> | >| >Both support InnoDB. >> | >| > >> | >| >error: Transactions not supported by database at >> | >| >> | >| Did you check that new DB is using InnoDB engine? >> | >| Maybe that information was not stored in the dump, and it was >> | >| recreated as MyISAM. >> | > > > ___ > 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] rt-3.6.1 glitch - Transactions not supported by database
The MySQL client library has changed. Recompiling DBD::mysql solved the same problem for me. David Odhiambo Washington wrote: > | >| > | >| 2006/8/19, Odhiambo Washington <[EMAIL PROTECTED]>: > | >| >I have rt-3.6.1 installed on a host different than the DB server. Today > | >| >I moved my database from one server to the other (dump then import). > | >| >MySQL-4.0.26 was in the old box, while the new box is MySQL-4.0.27. > | >| >Both support InnoDB. > | >| > > | >| >error: Transactions not supported by database at > | >| > | >| Did you check that new DB is using InnoDB engine? > | >| Maybe that information was not stored in the dump, and it was > | >| recreated as MyISAM. > | > ___ 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] Upgraded MySQl to 4.1.21 - now getting "transactionsnotsupported"
Jeremy,
The MySQL client library has changed.
Recompiling DBD::mysql solved the same problem for me.
David
Peake, Jeremy wrote:
> ooops, nevermind. it doesn't work after the downgrade. I can "OPEN" a
> ticket. but cannot "TAKE" "COMMENT" "REPLY" "RESOLVE"
>
>
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] *On Behalf Of *Peake,
> Jeremy
> *Sent:* Tuesday, August 15, 2006 8:56 AM
> *To:* rt-users@lists.bestpractical.com
> *Subject:* RE: [rt-users] Upgraded MySQl to 4.1.21 - now getting
> "transactionsnotsupported"
>
> I downgraded to MySQL 4.1.20 and it works fine.
>
>
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] *On Behalf Of *Peake,
> Jeremy
> *Sent:* Tuesday, August 15, 2006 8:30 AM
> *To:* rt-users@lists.bestpractical.com
> *Subject:* [rt-users] Upgraded MySQl to 4.1.21 - now getting
> "transactions notsupported"
>
> After the MySQL upgrade, it appears the Rt database was set to myisam.
> I changed it back to innodb, restarted Mysql and the web server. Still
> getting this error when I try to comment, reply or resolve any ticket.
> Any ideas?
>
>
>
> *error:* Transactions not supported by database at
> /usr/lib/perl5/vendor_perl/5.8.7/i686-linux/DBI.pm line 1657.
>
> *context:**** ...*
> *1653:*sub begin_work {
> *1654:*my $dbh = shift;
> *1655:*return $dbh->set_err(1, "Already in a transaction")
> *1656:*unless $dbh->FETCH('AutoCommit');
> *1657:*$dbh->STORE('AutoCommit', 0); # will croak if driver doesn't
> support it
> *1658:*$dbh->STORE('BegunWork', 1); # trigger post commit/rollback
> action
> *1659:*return 1;
> *1660:*}
> *1661:*
> *...*
> *code stack:* /usr/lib/perl5/vendor_perl/5.8.7/i686-linux/DBI.pm:1657
> /usr/lib/perl5/site_perl/5.8.7/DBIx/SearchBuilder/Handle.pm:682
> /opt/rt3/lib/RT/Ticket_Overlay.pm:2302
> /opt/rt3/share/html/Ticket/Elements/PreviewScrips:82
> /opt/rt3/share/html/Ticket/Update.html:137
> /opt/rt3/share/html/autohandler:279
>
>
>
>
> ___
> 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
