Hi guys, I was running a v5 system under Ubuntu with no problems, but thought I would try the latest checkout from GitHub.
All seemed to go ok according to the documented upgrade process. I have made the modifications to the settings.php file to default everything back to MySQL to get things all complete with the upgrade before I 'play' with TimeStore.
Jumping into the web front end, I completed the DB upgrade scripts (was only a few columns from memory) and all my inputs and feeds came up.
I hit the "Refresh feed size" button and all the feeds show a "size" that is concurrent with the data in my MySQL DB, and I can view all historical data.
I had a bit of an error in the input process list screens where the screen seemed to show all the steps as a vertical line of single characters .. I modified one of them, and everything seemed tom come right.
I see values changing in the input view and in the feeds view that suggests I am getting data feeds from my devices and that my processes are all running ok.
However, in the input screen I am getting the value "NaNs ago" for last updated value and "inactive" for updated in feeds ...
I cant work out what the problem is or where to look for errors .. I am using the same database user as I was before - it can clearly see the data and is a RW user.
Ideas and suggestions?
Re: Problems upgrading from v5 to v7 ...
It may well be my fault for missing to update the upgrading documentation page with the steps for v7. It sounds like an error that would be caused by redis being missing but then I would have expected that it should have given you the error
"Can't connect to redis database, it may be that redis-server is not installed or started see readme for redis installation"
The steps to install redis are:
sudo apt-get install redis-server
sudo pecl install redis
Add pecl redis module to php5 config
sudo sh -c 'echo "extension=redis.so" > /etc/php5/apache2/conf.d/20-redis.ini'
sudo sh -c 'echo "extension=redis.so" > /etc/php5/cli/conf.d/20-redis.ini'
I will update the documentation.
Re: Problems upgrading from v5 to v7 ...
Thanks Trystan, I had seen that from the install notes and installed it ok ... I did also get the error though as I forgot to restart Apache !!
Now here is a very interesting thing for you ... I went away for a few days, came back and all is working ok .. it makes no sense to me at all ..
I did a reboot or two while I was troubleshooting last week (too lazy to just stop and start services - and I updated the kernal anyways!) ... but that didnt seem to make any change at all to the operation - I was still getting data appear, but not recorded ..
Not sure if there is anything I can look at and/or send to you that you want to look at?
Re: Problems upgrading from v5 to v7 ...
Thanks for the update, good to hear its working.
Re: Problems upgrading from v5 to v7 ...
My guess is that there was some change in the storage of data regarding timezone information ... the only thing I can think of that could cause that sort of problem ...
Re: Problems upgrading from v5 to v7 ...
Trystan ... seems the problem can be repeated!
I had a drive failure on my server .. no real biggie ...
I built a new box - pretty standard Ubuntu server, latest LTS kernel, etc.
Restored by MySQL dbs to the new instance.
Re-downloaded EmonCMS from GIT, re-established Apache sites and configs, etc ...
And I got the same errors ...
https://www.dropbox.com/s/bwiwrv7ljoel4kk/Screenshot%202014-01-25%2013.4...
The inactive entries are ok - I havent got those streams back up and going yet ... its just the "NaNs ago" entries that have be baffled ... the value entries are all ok and showing changing values as expected.
Feeds are all showing "inactive", but graphs have recent data ...
Ideas?
Re: Problems upgrading from v5 to v7 ...
I think it may be redis needing to have its database reloaded from the persistent mysql copy, Try doing a redis flush
$ redis-cli
> flushall