Admin account problem with 1.2.2 upgrade and Postgresql

Hello, After almost a year of running OTRS 1.1.2 (before that 1.0.1) successfully with Postresql 7.2, we decided to upgrade to OTRS 1.2.2. Followed the instructions in the UPGRADING file, and all seems to have proceeded normally with the database upgrade. Copied over Kernel/Config.pm, Kernel/Config/GenericAgent.pm, as well as .procmail and .forward files which deliver mail to OTRS. The problem is that although we are able to login normally with our user and admin accounts, no ticket, queue, or group information appears. Logging into the root@localhost admin account shows a blank AgentFrontend page rather than the AdminSelectBox. OTRS shows the generic message that a user needs to be created rather than working with UserID 1, but when attempting to create a user, the system reports that admin has not permission and that "You have to be in the a permitted group!". The data is definitely still inside Postgresql, as I can see the user (6 users in addition to root@localhost) information from the 'system_user' table and the queue information (17 queues) from the 'queue' table. The only thing that occurs to me is that the permissions on the database itself might be wrong. The data is all there, and the update proceeded normally. Any ideas on how to get this one fixed ? Nothing in the logs shows up that is useful, as I suspect that this might be all Postgres database table permission related. Has anyone had a similar experience that might be able to shed some light ? -Eddie

On Thursday, March 18, 2004 3:13 AM
Eddie Urenda
The only thing that occurs to me is that the permissions on the database itself might be wrong. The data is all there, and the update proceeded normally. Any ideas on how to get this one fixed ?
Are you really sure you're working on your PostGreSQL? Is there potentially another MySql installed, now having overtaken the installation someho? I could think of a faulty /etc/sysconfig/otrs pointing towards a MySql now. Recheck your Config.pm to verify your database connection. If you haven't done so: Make a backup of your database. Now.
Nothing in the logs shows up that is useful, as I suspect that this might be all Postgres database table permission related.
As neither the upgrade of OTRS' source code nor the database upgrade script does anything to the permissions, I wouldn't expect this, but nii. Regards, Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388

On Thursday 18 March 2004 15:04, Robert Kehl wrote:
On Thursday, March 18, 2004 3:13 AM
Eddie Urenda
wrote: The only thing that occurs to me is that the permissions on the database itself might be wrong. The data is all there, and the update proceeded normally. Any ideas on how to get this one fixed ?
Are you really sure you're working on your PostGreSQL? Is there potentially another MySql installed, now having overtaken the installation someho? I could think of a faulty /etc/sysconfig/otrs pointing towards a MySql now.
this looks suspicious close to my problem. see bug no. 366 -- Regards, Wiktor Wodecki net mobile AG - 40470 Duesseldorf - Germany 923B DCF8 070C 9FDD 5E05 9AE3 E923 5A35 182C 9783

this looks suspicious close to my problem. see bug no. 366
Thank you Wiktor, this is indeed very similar. Somehow the permission values got nuked with the upgrade (this is worrisome to me). I did a: INSERT INTO group_user (user_id, group_id, permission_key, permission_value, create_by, create_time, change_by, change_time) VALUES (1, 2, 'rw', 1, 1, current_timestamp, 1, current_timestamp); per Martin's suggestion in bug 331 and the admin account is now back to normal. Still no graphs icon though, so I need to look into why that is not appearing (I have explicitly set a path using StatsPicDir but no icon appears). -Eddie

Still no graphs icon though, so I need to look into why that is not appearing (I have explicitly set a path using StatsPicDir but no icon appears).
Ignore this. I need to review all of the permissions which somehow where not preserved because of the upgrade (including the graphs group settings). All tickets appear now though, and all is well. Thanks for the help with this, -Eddie

On Thursday 18 March 2004 15:16, Wiktor Wodecki wrote:
The only thing that occurs to me is that the permissions on the database itself might be wrong. The data is all there, and the update proceeded normally. Any ideas on how to get this one fixed ?
Are you really sure you're working on your PostGreSQL? Is there potentially another MySql installed, now having overtaken the installation someho? I could think of a faulty /etc/sysconfig/otrs pointing towards a MySql now.
this looks suspicious close to my problem. see bug no. 366
ok, I found the problem on this one. There are two problems with the dbupdate scripts (I'm looking at the postgresql one, but I assume similar problems are on the mysql side). Have a look at http://bugs.otrs.org/show_bug.cgi?id=366 for the exact problem and a solution. However you have to set the admin right as in http://bugs.otrs.org/show_bug.cgi?id=331 and then manually readd all user-group relations via the admin frontend. Since our setup grew quite large until now I'm thinking about getting in pl/pgsql language to create a stored procedure which could be used to update the db. This wouldn't work on mysql however (which doesn't know stored procedures). Maybe one of the OTRS developers might give me a helping hand with that ;-) -- Regards, Wiktor Wodecki net mobile AG - 40470 Duesseldorf - Germany 923B DCF8 070C 9FDD 5E05 9AE3 E923 5A35 182C 9783

Are you really sure you're working on your PostGreSQL? Is there potentially another MySql installed, now having overtaken the installation someho? I could think of a faulty /etc/sysconfig/otrs pointing towards a MySql now.
Positive. MySql is not installed on the system, log information shows that user otrs is logging into the otrs database.
Recheck your Config.pm to verify your database connection.
All database DSN's are commented out except for the Postgresql entry.
If you haven't done so: Make a backup of your database. Now.
Definitely, thanks.
As neither the upgrade of OTRS' source code nor the database upgrade script does anything to the permissions, I wouldn't expect this, but nii.
I can't determine what this might be then or how to fix it. -Eddie
participants (3)
-
Eddie Urenda
-
Robert Kehl
-
Wiktor Wodecki