On Fri, Dec 7, 2012 at 3:17 AM, [email protected]
<[email protected]> wrote:
> CREATE TABLE `Users` (
>   `id` int(11) NOT NULL AUTO_INCREMENT,
>   `Name` varchar(200) NOT NULL DEFAULT '',
>   `Password` varbinary(40) DEFAULT NULL,

It should be:

Password VARCHAR(256) NULL  ,

So your upgrade failed and you didn't notice an error.


>   `Comments` text,
>   `Signature` text,
>   `EmailAddress` varchar(120) CHARACTER SET ascii DEFAULT NULL,
>   `FreeformContactInfo` text,
>   `Organization` varchar(200) DEFAULT NULL,
>   `RealName` varchar(120) DEFAULT NULL,
>   `NickName` varchar(16) DEFAULT NULL,
>   `Lang` varchar(16) CHARACTER SET ascii DEFAULT NULL,
>   `EmailEncoding` varchar(16) CHARACTER SET ascii DEFAULT NULL,
>   `WebEncoding` varchar(16) CHARACTER SET ascii DEFAULT NULL,
>   `ExternalContactInfoId` varchar(100) DEFAULT NULL,
>   `ContactInfoSystem` varchar(30) DEFAULT NULL,
>   `ExternalAuthId` varchar(100) DEFAULT NULL,
>   `AuthSystem` varchar(30) DEFAULT NULL,
>   `Gecos` varchar(16) DEFAULT NULL,
>   `HomePhone` varchar(30) DEFAULT NULL,
>   `WorkPhone` varchar(30) DEFAULT NULL,
>   `MobilePhone` varchar(30) DEFAULT NULL,
>   `PagerPhone` varchar(30) DEFAULT NULL,
>   `Address1` varchar(200) DEFAULT NULL,
>   `Address2` varchar(200) DEFAULT NULL,
>   `City` varchar(100) DEFAULT NULL,
>   `State` varchar(100) DEFAULT NULL,
>   `Zip` varchar(16) DEFAULT NULL,
>   `Country` varchar(50) DEFAULT NULL,
>   `Timezone` varchar(50) CHARACTER SET ascii DEFAULT NULL,
>   `PGPKey` blob,
>   `Creator` int(11) NOT NULL DEFAULT '0',
>   `Created` datetime DEFAULT NULL,
>   `LastUpdatedBy` int(11) NOT NULL DEFAULT '0',
>   `LastUpdated` datetime DEFAULT NULL,
>   `AuthToken` varchar(16) CHARACTER SET ascii DEFAULT NULL,
>   PRIMARY KEY (`id`),
>   UNIQUE KEY `Users1` (`Name`),
>   KEY `Users4` (`EmailAddress`)
> ) ENGINE=InnoDB AUTO_INCREMENT=101751 DEFAULT CHARSET=utf8;
>
>
>
>
>
> sky.schumacher
> [email protected]
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of 
> Ruslan Zakirov
> Sent: Thursday, December 06, 2012 3:16 PM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: [rt-users] Odd problem with ROOT account after an upgrade
>
> On Fri, Dec 7, 2012 at 2:18 AM, SkyS <[email protected]> wrote:
>> I recently upgraded a RT install from 3.6.1 to 4.0.7 I managed to get
>> everything going, yet now I am having a bit of a problem.
>>
>> Since the upgrade, i have to manually re-set the root password.
>> Once I log in and log off, i can no longer log in as root unless i
>> re-set the password again.
>>
>> Anyone have any advise on how to even trouble shoot the problem?
>
> You have not upgraded properly. I suspect that Password field in Users table 
> of your DB is short. One of ugprade scripts makes it wide enough to hold new 
> hashing algorithm. Output of "SHOW CREATE TABLE Users" can confirm my 
> assumption.
>
>>
>> Thanks.
>>
>>
>>
>> --
>> View this message in context:
>> http://requesttracker.8502.n7.nabble.com/Odd-problem-with-ROOT-account
>> -after-an-upgrade-tp52109.html Sent from the Request Tracker - User
>> mailing list archive at Nabble.com.
>> --------
>> We're hiring! http://bestpractical.com/jobs
>
>
>
> --
> Best regards, Ruslan.



-- 
Best regards, Ruslan.
--------
We're hiring! http://bestpractical.com/jobs

Reply via email to