Well that looks in order, the feeds are all there in both the mysql feed table and in the data folders, and the permissions/ownership is right.
One more thing to try since the feeds apparently cannot be found hence the “does not exist or was deleted” messgae, when you recently updated, was that to remedy this or do you suspect it may be the trigger?
Did you need to replace the settings.php? If yes, did you copy default.settings.php or default.emonpi.settings.php?
Either way can you confirm your emoncms is looking for the feed data in the right place ie are the paths in your emoncms/settings.php still like so?
Looks like mysql input, feeds table and feed data are all ok. Is your emoncms feed list showing blank?
Could you try
emoncms/feed/list.json
My hunch is that there is something amiss in the redis cache of the feed list data at this point…
A redis flush might sort it, or it may thow an error if redis is not updating correctly.
Worth checking the settings.php though as @pb66 suggested
I’ve never (knowingly) changed the settings.php (I bought the emontx and emonhub and used the GUI to config them)
I ran a diff between a “default.emonpi.settings.php” and “settings.php” in /var/www/emoncms and it showed no changes
The settings are as displayed in Paul’s quote.
However, I only have a phpfina and phptimeseries in /home/pi/data. Should I create a phpfiwa dir with the same perms as the other two?
pi@emonpi(ro):data$ ls -ld /home/pi/data/phpfiwa/ /home/pi/data/phpfina/ /home/pi/data/phptimeseries/
ls: cannot access /home/pi/data/phpfiwa/: No such file or directory
drwxr-xr-x 2 www-data root 1024 Sep 25 08:00 /home/pi/data/phpfina/
drwxr-xr-x 2 www-data root 1024 Aug 17 08:44 /home/pi/data/phptimeseries/
pi@emonpi(ro):data$
I’ve left the emoncms/feed/list.json running for 5+ minutes and Firefox still only shows me the swirling loading icon and nothing else.
I found another one of your comments suggesting “redis-cli flushall”, is that the correct command here as well?
phpfiwa is being phased out AFAIK so the lack of a folder would only be a concern if you had old feeds to import or you wanted to go against the flow and enable the disabled phpfiwa feed engine in emoncms.
The spinner on the feeds page is an issue, is there any info if you hit F12 in your browser? (actually I’m not sure if dev tools is F12 in Firefox)
is worth trying, the same can also be done from within emoncms on the admin page, there is a flush button on the right of the redis section.
[EDIT] Actually, since you can query your input and feed table from the command line it looks like your mysql tables are ok, hopefully @TrystanLea will have a further ideas if flushing redis doesn’t work.
To answer a previous question, I ran the update in August to see what extra little goodies you had added.
I ran the redis-cli flushall, and no noticeable change.
I took a look at /var/log/apache2/error.log and found a load of segmentation fault messages. I tried opening emoncms/feed/list.json and, you see an apache2 chew up 90+% of a core for 40 seconds before the seg fault, after 10 attempts the browser shows a “The connection was reset” message:
I’m very much beyond my domain of knowledge, but tried changing the Apache log level up until I got to trace8 and nothing looks to be too out of whack (to an untrained eye):
This is the first time I’m delving into the processes and working of emoncms and am NOT clear on what works and where, hence appreciate all your help and guidance. But also apologise for the potentially daft questions etc
This is identical to the problem that I encountered prior to this post.
The error messages were the same, and after failing to resolve, I resorted to an earlier backup, only to meet the same segmentation problem again a week later, so I eventually re-formatted and rebuilt my system in raspbian stretch.
So, yes this appears to be an issue rather than a glitch.
Aahh sorry, no, afraid not, but I assume it would be the current ‘apt’ version available in the jessie repo, as I update fairly regularly.
I assume v2.2.5-1
Segmentstion faults was the reason v2.2.7 was downloaded from git rather than using v2.2.5 deb package.
With PHP 5.x you must be using 2.2.7 or 2.2.8 or 3.1.3>. PHP 7 must be 3.0.0 >.there has been alot of change this year so i would recommrnd staying up to date using PECL currently 3.1.4 for both PHP versions.
Looking through Paul Reed’s problems, I’m conscious that mine was working well until I added an additional process onto a virtual feed and that’s when I started to see spining loaders etc. Hence was going to focus on reverting that change first.
In particular this feed:
mysql> select * from feeds;
+----+----------------------+--------+--------------+------+-------+----------+--------+---------+--------+----------------------+
| id | name | userid | tag | time | value | datatype | public | size | engine | processList |
+----+----------------------+--------+--------------+------+-------+----------+--------+---------+--------+----------------------+
...
| 47 | Inp Exp Daily Delta | 1 | Virtual | NULL | NULL | 2 | 0 | 0 | 7 | 53:24,56:25,30:47 |
+----+----------------------+--------+--------------+------+-------+----------+--------+---------+--------+----------------------+
24 rows in set (0.00 sec)
I cannot access any of this via the browser, hence would it be as simple as removing the last entry from that feed, i.e. 53:24,56:25,30:47 becomes 53:24,56:25?
[EDIT]
I haven’t done any SQL since Uni, would the following be appropriate?
UPDATE feeds SET processList='53:24,56:25' WHERE id=47
Clive, when you say that you ‘can’t access any of this via the browser’. Are you finding same as I did, that you can no longer open phpmyadmin to check & edit MYSQL?
I’m a real early starter to the emoncms side of things, but used to be a UNIX admin, hence am happy with the OS aspects, but less so with the MySQL and app aspects.
Until now I’ve only ever managed the feeds via the emoncms feeds web page, but ever since this problem started, this page never appears, hence the interest in an alternate route.
I’ve not installed phpmyadmin, and am more than happy to NOT tinker with the DB too much!
Is the change to that one field sufficient to change that process list? Or would I need to do something in addition?
I removed the newly added process from the virtual feed (3rd from this list 53:24,56:25,30:47), but still had problems loading the feeds page, I stopped Apache, ran redis-cli flushall and restarted Apache and could then load the page.
The last updates to the feeds being 30 hrs out of date, hence I clutched at a straw and restarted emonhub - no change.
I then rebooted the emonhub and the feeds now work correctly and the solar with divert app shows me current data, but understandably with a 30hr gap.
I really appreciate your time, effort and patience with me and this problem.
When I came across OEM project it looked to be a fantastic and highly configurable monitoring product, I’ve been really happy with my deployment. In addition, the support and info within these community pages are fantastic.