Opened 5 years ago

# Doesn't accept successful database upgrade

Reported by: Owned by: akaihola rjollos normal TracHoursPlugin normal database upgrade 0.11

### Description

I followed the instructions to install and enable TracHoursPlugin and its dependencies on a Trac 0.12 installation.

However, when browsing to http://myserver/myenv, I still get this message:

Error

TracError: The Trac Environment needs to be upgraded.



Database is up to date, no upgrade necessary.


But the same error is still shown when I try to visit the site.

Any advice on how to debug this?

### comment:1 Changed 5 years ago by akaihola

• Resolution set to invalid
• Status changed from new to closed

This was a problem in my trac.ini permissions. Sorry.

### comment:2 Changed 5 years ago by akaihola

See t:#9649 for a description of the permissions problem.

### comment:4 Changed 5 years ago by rjollos

I knew this problem sounded familiar. Glad it's working for you!

### comment:5 Changed 5 years ago by falkb

The same problem is reported in TimingAndEstimationPlugin from time to time (e.g. #9519). I wonder if it's possible that the file ownership problem (which is the actual problem) is signalled by the GUI as warning or error.

### comment:6 Changed 5 years ago by akaihola

A comment to Trac's #5535 seems to indicate that a fix is on its way to Trac v0.13.

### Changed 4 years ago by grubio

Trac 0.11.7 log file

### comment:7 follow-up: ↓ 8 Changed 4 years ago by grubio

• Resolution invalid deleted
• Status changed from closed to reopened
• Trac Release changed from 0.12 to 0.11

Hello, I've been having this problem too. Checked the permissions both of the .ini file and the sqlite db file and they were fine. It is something within the plugin which I built with python setup.py bdist_egg ...

If I disable TracHours and restart apache the upgrade message goes away. I'm attaching my log file in case that it can come helpful.

### comment:8 in reply to: ↑ 7 ; follow-up: ↓ 9 Changed 4 years ago by rjollos

Hello, I've been having this problem too.

Could you confirm that you repeatedly run trac-admin $ENV upgrade but the upgrade message persists? ### comment:9 in reply to: ↑ 8 ; follow-up: ↓ 10 Changed 4 years ago by grubio Replying to rjollos: Replying to gustavo@42ideas.mx: Hello, I've been having this problem too. Could you confirm that you repeatedly run trac-admin$ENV upgrade but the upgrade message persists?

Sure, I'll take some time today and let you know. Was the plugin updated?

### comment:10 in reply to: ↑ 9 ; follow-up: ↓ 11 Changed 4 years ago by rjollos

Sure, I'll take some time today and let you know. Was the plugin updated?

Yes, latest version is 0.6dev-r11981. There's also another database upgrade related issue in #10308 that I've been trying to decipher. Some comments in #8690 seem to be related to the issue you see.

### comment:11 in reply to: ↑ 10 ; follow-up: ↓ 12 Changed 4 years ago by anonymous

Sure, I'll take some time today and let you know. Was the plugin updated?

Yes, latest version is 0.6dev-r11981. There's also another database upgrade related issue in #10308 that I've been trying to decipher. Some comments in #8690 seem to be related to the issue you see.

What version should I try? The branch for 0.11 or the trunk? Remember I'm using 0.11.4

### comment:12 in reply to: ↑ 11 ; follow-up: ↓ 13 Changed 4 years ago by rjollos

What version should I try? The branch for 0.11 or the trunk? Remember I'm using 0.11.4

You'll want to use the 0.11 branch for now. I'm working to get the trunk compatible with Trac 0.11.

Everything looks normal in your log file. Do you have the exact same symptoms as reported in comment:description? That is, does trac-admin $TRACENV upgrade seem to have no effect and you just get repeatedly prompted to upgrade? Some more details about your configuration would also be helpful (Database, Python version, ...). Just curious, what keeps you on 0.11.4 rather than upgrading to at least 0.11.7? ### comment:13 in reply to: ↑ 12 ; follow-up: ↓ 14 Changed 4 years ago by grubio Replying to rjollos: Replying to anonymous: What version should I try? The branch for 0.11 or the trunk? Remember I'm using 0.11.4 You'll want to use the 0.11 branch for now. I'm working to get the trunk compatible with Trac 0.11. Everything looks normal in your log file. Do you have the exact same symptoms as reported in comment:description? That is, does trac-admin$TRACENV upgrade seem to have no effect and you just get repeatedly prompted to upgrade? Some more details about your configuration would also be helpful (Database, Python version, ...).

Just curious, what keeps you on 0.11.4 rather than upgrading to at least 0.11.7?

Ok, I'm gonna try on another fresh env since this one seems to be pretty messed up. The reason I'm staying in 0.11.4 is because I have those envs in a dreamhost account and they offer this "one click" no hassle installation so that's what I did, tried 0.12.x by hand but many plugins still don't work so I sticked with 0.11.x branch, did not noticed that there is a 0.11.7 update though (the one click installer don't show updates, guess I'm gonna have to update it manually)

### comment:14 in reply to: ↑ 13 Changed 4 years ago by rjollos

.. tried 0.12.x by hand but many plugins still don't work so I sticked with 0.11.x branch, did not noticed that there is a 0.11.7 update though (the one click installer don't show updates, guess I'm gonna have to update it manually)

I'd highly recommend you go with 0.12 or even 1.0. Both represent major improvements over the previous release.

What plugins aren't working for you with 0.12? My experience is that 0.12 support is pretty equivalent to 0.11 support by now, if not better. Many newer plugins only support 0.12 and greater. If a plugin has not been adapted to 0.12 by now, in most cases it is unmaintained and has numerous unfixed issues by now.

If you point me to the plugins that you are having trouble with on 0.12, I might be able to help with getting the 0.12 issues resolved. In many cases a plugin only requires an hour or two of work to get it up and running on 0.12.