I tried this with no luck:(
The issue persists…
-EDIT-
I manage to resolve the issue:
pm2 process name is now ‘mm’ instead of ‘MagicMirror’
so
“pm2 start|stop|restart mm” is now the command that I will use
Thanks for your help!!
Cheers:)
The problem seems to be cached api.spotify.com IP address. flush dns servers records and works again.
Thanks guys for your help
Hello.
I recently upgraded to latest version using the upgrade script.
The MagicMirror starts normally but after a while it crashes and restarts the pm2 again and again.
There are no error generated on MagicMirror-error.log
the only logs I found that on /var/log/syslog
Nov 24 11:33:36 magicmirror2 systemd[1]: pm2-pi.service: Start operation timed out. Terminating.
Nov 24 11:33:37 magicmirror2 systemd[1]: pm2-pi.service: Failed with result 'timeout'.
Nov 24 11:33:37 magicmirror2 systemd[1]: Failed to start PM2 process manager.
Nov 24 11:33:37 magicmirror2 systemd[1]: pm2-pi.service: Service RestartSec=100ms expired, scheduling restart.
Nov 24 11:33:37 magicmirror2 systemd[1]: pm2-pi.service: Scheduled restart job, restart counter is at 25.
Nov 24 11:33:37 magicmirror2 systemd[1]: Stopped PM2 process manager.
Nov 24 11:33:37 magicmirror2 systemd[1]: Starting PM2 process manager...
Any suggestions please?
@sdetweil yeah kind of. Although I have set api.spotify.com to be static for some reason. I haven’t had any issues until now. maybe something was changed on Spotify side.
The problem seems to be cached api.spotify.com IP address. flush dns servers records and works again.
Thanks guys for your help
@chassain-0 I have configure it this way to have access remotely to MM using MMM-Remote-Control
@chassain-0 I have edited my previews post.
Sorry. I forget to put them when I’m removing sensitive data.
this is the correct config.
/* Magic Mirror Config Sample
*
* By Michael Teeuw http://michaelteeuw.nl
* MIT Licensed.
*
* For more information how you can configurate this file
* See https://github.com/MichMich/MagicMirror#configuration
*
*/
var config = {
address: "0.0.0.0", // Address to listen on, can be:
// - "localhost", "127.0.0.1", "::1" to listen on loopback interface
// - another specific IPv4/6 to listen on a specific interface
// - "", "0.0.0.0", "::" to listen on any interface
// Default, when address config is left out, is "localhost"
port: 8080,
ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1", "10.0.10.0/24", "10.0.50.0/24"], // Set [] to allow all IP addresses
// or add a specific IPv4 of 192.168.1.5 :
// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
// or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],
language: "en-gb",
timeFormat: 24,
units: "metric",
modules: [
{
module: "alert",
config: {
alert_effect: "flip"
}
},
{
module: "updatenotification",
position: "top_center"
},
.....
{
module: "MMM-NowPlayingOnSpotify",
position: "top_left",
config: {
clientID: “a4r..54f"
clientSecret: “e2...d3"
accessToken: "BQD...95fmg",
refreshToken: "AQAr....YXR3"
}
},
{
module: "MMM-Remote-Control",
// position: 'bottom_left',
}
]
};
/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") {module.exports = config;}
I have still no luck with NowPlayingOnSpotify.
Any suggestion would be much appreciated.
@sdetweil the datetime is correct on my raspberry system
I haven’t had black screen once I updated to v2.13.
seems that only some modules need the “npm install” command
@sdetweil ok I see, thanks.
So is there any workaround to make the module to work again?