Archived Forum

I presume that you've copied across the settings.php file from your previous install to your v8.5 folder.
Are any errors showing in your browser console?
...or the Emonhub log. (change logging to debug).

Paul

No, I forgot to mention that. I've renamed the default settings file, and changed the mysql settings. Since logging in works, I expect those to be correct.

I was thinking more about the data folder locations in settings.php

Paul

Good point, although that should point to the symlinked location /var/www/emoncms. Let met check that when I get home.

The data locations are available:

pi@ns2 /var/lib $ ls -lsa | grep php
28 drwx-wx-wt  2 root      root      24576 Apr 28 18:39 php5
 4 drwxr-xr-x  2 www-data  root       4096 Jan  1 13:12 phpfina
 4 drwxr-xr-x  2 www-data  root       4096 Mar 15 08:31 phpfiwa
 4 drwxr-xr-x  2 www-data  root       4096 Mar 15 08:30 phptimeseries

​And there are feeds being updated in those directory's too. But some simple power to kwhd feeds are not being updated, although their single input works, and their power feed also updates.

Below an example of an simple power to kwhd that has no updating kwhd feed

pi@ns2 /var/lib/phpfiwa $ ls -lsa
12508 -rw-r--r--  1 www-data www-data 12759876 Apr 28 18:49 3_0.dat
 2088 -rw-r--r--  1 www-data www-data  2126648 Apr 28 18:49 3_1.dat
  212 -rw-r--r--  1 www-data www-data   212668 Apr 28 18:49 3_2.dat
   40 -rw-r--r--  1 www-data www-data    35448 Apr 28 18:49 3_3.dat
    4 -rw-r--r--  1 www-data www-data       44 Jun  5  2014 3.meta
    4 -rw-r--r--  1 www-data www-data       16 Jul 20  2014 3.npoints

pi@ns2 /var/lib/phpfina $ ls -lsa
   4 -rw-r--r--  1 www-data www-data    1472 Apr 27 16:29 4.dat
   4 -rw-r--r--  1 www-data www-data      16 Jun  5  2014 4.meta
   4 -rw-r--r--  1 www-data www-data       4 Jul 20  2014 4.npoints

Found the issue by creating a new dummy input, and 2 feeds from that. After pushing some json via the browser, the returned error gave the correct clue;

Fatal error: Uncaught exception 'Exception' with message 
'DateTimeZone::__construct(): Unknown or bad timezone (1)'

It seems that after doing this upgrade, my timezone needed to be set to something else than 1 ;-)

All works ok now. Maybe something to put in the database update function?

Glad it's sorted.

This error would have been listed in the emonhub log if checked (I speak from my own experience!!) and it's always worth a look when things are not working as expected.

Paul