Charts stopped updating

[liddelljs]

I am running a website on the same pi as I have MX installed and the charts stopped updating today. Went flat line for about 30 mins and the chart pages now all show the data up to 8am this morning but nothing since (the time hasn't updated either). I am also running an external website and these charts are fine (the charts on the MX interface are also fine), leading me to believe it is something to do with the transfer to the /var/www directory on the pi or an issue with a file in the directory itself (Haven't changed anything here). Diags file doesn't report any errors. Are there specific files I could try and delete the var/www directory in case one of them is corrupted?


Cheers
Steve

[steve]

More information about your setup, and clarification on what actually happened, please?

You have MX automatically doing FTP to an external server, and that's working OK, and you have also listed all of the files on the 'extra files' screen without 'ftp' ticked so that MX is copying them to a local directory? And it's only the graphs which are affected, the other pages are OK? But the local charts actually flat-lined for a period rather than not updating, and yet the external charts didn't flat-line? That sounds very odd if I've understood correctly, and I have no idea how one set of graphs can flat-line and not another, when they are using the same data.

[liddelljs]

Hi Steve,
You are correct on all counts. I could only assume that something was not updating correctly to the /var/www directory on the pi as it was the only difference between the website on the pi and the external domain. I tried deleting all the files apart from the css file in the var/www directory on the pi to let it update with fresh files but hasn't made any difference.

I'll keep searching. I'm sure it is something simple.

Cheers
Steve

[steve]

What settings are you using on the extra files page for the copying to /var/www locally?

[liddelljs]

I have process, realtime and utf8 selected for the extra files transfer (no ftp). What has me a bit baffled is that it was all working perfectly up until this morning and I haven't changed anything.
Just one query - in the extra files transfer, I am transferring (for example) the trends.htm file in the pi web directory to the trends.htm file in the var/www directory. Should I be transferring the trendsT.htm file to the trends.htm file?

Cheers
Steve

[steve]

You shouldn't have 'process' ticked for files that don't contain web tags, e.g. the json files, and for the htm files it is better to do what you are doing and transfer the already processed files rather than the 'T' files. Again, you shouldn't have 'process' ticked in that case. But note that the standard files don't get processed at the realtime interval, so transferring the already-processed files with 'realtime' selected is pointless, as they won't change until the next 'full' update.

You are probably getting clashes by processing the files at the realtime interval when they are also being processed at the 'normal' interval, and it may be that something has got 'stuck' as a result.

My advice would be to untick all of the boxes for your copies, except those which are intended to be done at realtime, in which case just tick 'realtime' for those. That may well get it going again, but a restart of MX would probably be a good idea at this point.

[liddelljs]

Thanks Steve. Followed your suggestions, including a restart of MX and my router for good measure but no change. Has me baffled. I'm thinking it is more likely to be a problem with my setup and link through my dynamic dns account rather than MX itself as everything else on MX is working fine. Last resort will be to delete everything from the /var/www directory and start again.
Thanks for your help.

Steve

[liddelljs]

Hi Steve,
I did a complete reinstall on MX and deleted all files from the var/www directory and fixed the problem but I did notice something during the install that might have been the cause of my problems. In build 3037, I noticed that the json files now sit in the web directory. My extra web files were calling for the json files from the main directory where they sat in build 3036. Possibly why the data pages were ok but the trend pages weren't updating?

Cheers
Steve

[steve]

Yes - always a good idea to read the release notes.