Bug #8972 | Created Users cannot be found in Manage Users, but exist elsewhere | ||
---|---|---|---|
Submitted: | 5 Mar 2005 1:48 | Modified: | 23 Apr 2005 1:14 |
Reporter: | P.J. Gifford | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Eventum | Severity: | S2 (Serious) |
Version: | 1.5 | OS: | Linux (Linux (Debian)) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[5 Mar 2005 1:48]
P.J. Gifford
[21 Mar 2005 20:41]
Bryan Alsdorf
Do any errors show up in /path-to-eventum/logs/errors.log?
[22 Mar 2005 3:37]
P.J. Gifford
Brian, There is nothing the the errors.log file (file size is 0). Does it matter what version of mySQL I'm running. I currently have version 3.23.49 which I obtained simply by doing an apt-get from Debian. If I connect to mySQL directly, I can query and see the users in the eventum_user table, just not from the web browser client. By the way, I downloaded v 1.5.1 since my post, but this behavior has not changed. Thanks, PJ
[22 Mar 2005 3:38]
P.J. Gifford
Bryan, that is... sorry.
[22 Mar 2005 3:54]
Bryan Alsdorf
PJ, Can you send me a copy of your user and project_user tables? /bryan
[22 Mar 2005 14:03]
P.J. Gifford
Bryan, Forgive me, but what is the easiest way to send you those tables, that is, extract them from mySQL? I am fairly new to mySQL administration. I assume that once they are exctracted from mySQL, I'll be able to zip them and use the "Files" feature of this bug site to get them to you. I will be able to figure it out, but if its real easy for you to tell me, please do. Thanks, PJ
[22 Mar 2005 21:55]
Bryan Alsdorf
To dump data from MySQL you can use the mysqldump command. See the manual for detailed usage information. In this case, the command is: mysqldump -uroot -p db_name eventum_user eventum_project_user Of course you will need to use the correct username and database name.
[23 Mar 2005 1:14]
P.J. Gifford
Bryan, I attached the dump of user and project_user to the Files area. Thanks, PJ
[23 Apr 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".