TimeTrex login error after Ubuntu upgrade to 10.10

[MickG01]

After Ubuntu upgrade from 10.04 to 10.10 - 32 bit TimeTrex log in goes to:
http://localhost:8085/interface/DownFor ... on=DBError
which displays:
TimeTrex is unable to connect to its database, please make sure that the database has been started and is running.
If I change the URL to:
http://localhost:8085/interface/
everything works OK
is there a way to make this behavior automatically correct on log in?

[shaunw]

You can login fine and everything works if you use this URL?

http://localhost:8085/interface/

What is the initial URL that redirects to the down for maintenance page?

[MickG01]

http://localhost:8085/interface/Login.php.
I enter a valid login and password.
Then click Submit
Oh invalid Username or password gives what I would consider a correct failure to log in.

[shaunw]

Sorry, I don't understand what the issue is.

TimeTrex appears to be working fine, you are trying to login to it with an invalid username/password and its telling you that.

[MickG01]

I attempt to log in. If I use an invalid UserID or password it behaves exactly as it should.

If I use a correct User ID and password it goes to the URL:

http://localhost:8085/interface/DownFor ... on=DBError

which displays:
TimeTrex is unable to connect to its database, please make sure that the database has been started and is running.

If I then manually change the URL to:
http://localhost:8085/interface/
everything works OK

Why does it not directly go to that URL which is what I would consider correct behavior.

If I attempt to go to the "http://localhost:8085/interface/" URL without entering correct UserID and password it does quite correctly just return to the login screen.

Since a correct login goes to the wrong URL screen which gives an invalid error this is not working correctly.

[shaunw]

My guess is that there is a SQL error happening for some reason. You will need to check your database, PHP and TimeTrex log files to try to find what that error is.

It also could be a permission issue when trying to write to the cache files. You may want to try deleting all the files/directories inside your TimeTrex cache directory to see if that helps.

[MickG01]

Thanks, deleting the contents of the cache seems to have fixed it.

[shaunw]

Assuming you weren't modifying settings in the timetrex.ini.php before this issue occurred, it likely means that you have a permission conflict, the most common cause is that your cron jobs are running as a different user than your web server.

If its not fixed, you will continue to get strange errors and even incorrect information appearing at "random" in TimeTrex.