MMM-UkNationalRail - stops updating on mirror

[randomnoise]

@nwootton not sure what version of node I’m running atm (I’m away for work)… I’ll try the npm start dev when I’m back & see if anything stands out.

I run the mirror standalone so, yes I guess it could be an issue with something in the pi browser, but it is a fairly standard mm build installed following the instructions from mm git page.

I’ll report back once I’ve tried the dev start.

[randomnoise]

BTW does the npm dev start give any detail beyond what is logged to the mm_error_log file seen when running using pm2?

[nwootton]

So still running without issues.

Got all the expected “No departure info” errors in the console for the overnight period where trains don’t actually run.

Have you updated the module itself?

[nwootton]

@randomnoise The mm_error_log file is not something I’ve come across, I assume it is the failure report generated by PM2 that lists all the times it has had to restart a service.

npm start dev displays the mirror, but also has a full JS console output running down the side of the screen. The “No departure info” message in my previous post is an example of that output.

[nwootton]

Still running without issue this morning, although I’m now getting emails about hitting my daily API usage allowance from the Transport API.

The only errors I’m getting are ones that the module generates when it doesn’t get the expected train info from Transport API - generally around 02:00 when no passenger trains are actually running.

Sorry to say that without being able to replicate the issue, there is very little more I can do.

[randomnoise]

@nwootton no worries, I’ll be home again on Sun so will try the dev console & see if anything stands out. As you say it may be electron related so I might just do a full pi + mm rebuild / reinstall.

Thanks for having a look in to it.

[randomnoise]

@nwootton after running since Sunday with no errors & console open, today train times finally crashed around 10:30am… then the entire mirror seems to have fallen over tonight just before I came home… the clock had stopped, all modules not updating and even the dev console was gone!

Hard reset of mirror, but of course nothing to see in pm2 logs as I didn’t start it with pm2…

unless the dev console also logs to a file somewhere then this exercise was in vain.

I think I’ll just try a full reinstall at the weekend & see if it behaves itself. I wish I’d taken a note of all the other tweaks I added to get the pi running as I liked.

[randomnoise]

@nwootton, Well after a full rebuild I still have never been able to get to the bottom of why it locks up. Still does it on occasion (Although it seems to be less frequent these days).

I have a new weird bug with the train times for you now though! Recently (may have been since the clocks changed, although I only noticed it the other day as I was checking time on a train I was going to catch) I seem to be showing times an hour behind! It’s bizarre as I don’t think there are any settings anywhere in the mirror for adjusting times other than the PI config settings (mine is showing correct time & UTC if I run a ‘date’ command in putty).

Any thoughts on what this could be?

[randomnoise]

I’ve expanded to show 8 results here as well…

[randomnoise]

Hmm, weirdly York station works ok.

Maybe something is up with the api data for STN.