PM2 restart question (more of a linux question than MM)

[sdetweil]

@wyovino said:

I saw the warning post about the April 1st upgrade and Pi Zero W

no… pi02w is an armv7l processor, pi3 in pi0w physical shape…

[wyovino]

@sdetweil

Got it!

In the user crontab:

30 2 * * * /usr/local/bin/node /usr/local/bin/pm2 restart mm

Restarts the mirror every day at 2:30 am local time.

As always, thanks for your quick response!

Bill

[JohnGalt]

@wyovino

Bill, I’m glad you found what you were looking for.

I’m curious - what issue are you addressing by restarting the MagicMirror daily?

I read this thread with interest because I too have thought about resorting to daily restarts on one of my mirrors. [I’ve figured out that daily restarts won’t meet my needs / fix my problem - so I haven’t gone down that road (yet). I guess I could design a cron schedule that staggers the restart enough that the photo display doesn’t show the same pictures every day, but not yet…]

[wyovino]

@JohnGalt My mirror was sometimes stalling - falling to update even the clock.

[JohnGalt]

@wyovino – Ok, good to know.

One of my magic mirrors stops every few days. There is only one module running on that mirror, MMM-BackgroundSlideshow, so it’s obvious when it happens.

[sdetweil]

@JohnGalt someone else has reported an out of memory w that module on discord

[JohnGalt]

@sdetweil – Well, I’m not surprised. I have the pictures on a USB drive attached to the raspberry pi, and the more pictures on the drive the worse it gets. It does feel like the software is loading up memory with the pictures.

I tried some time ago pulling the pictures from a share on my NAS, (you had advised someone to do that on another thread) but I never got that to work.

Thanks for letting us know about the memory issue.

[sdetweil]

@JohnGalt what didn’t work? , glad to help if you want to try agsin

[JohnGalt]

@sdetweil --Hi Sam

That was a while ago and my memory is foggy, but the issue was mapping a share on my NAS to the Raspberry Pi on which the MM is running…

As best I recall, I tried following directions to map the drive, but it didn’t work. I seem to recall being left with the sense that the process [a] had changed over time due to changes in distributions, and/or [b] that there was something left out of the directions that were likely too obvious to mention for someone who already knew, but was non-obvious to someone out of the know. At that point I gave up.

Fast forward to today - I’m happy to invest the time to learn and get it done if you’re willing to help!! I appreciate it. I sent you an email regarding how to best proceed.

[thartley]

@JohnGalt Hello. I have the same issue not being able to map to a NAS drive using the Terminal commands. I can map to the drive using the Files GUI. I couldn’t get it to work either - the problem seems to between my chair and the keyboard. Even though I got it to map with the FM, I still couldn’t get the MMM_ImagesPhotos module to access the NAS, which in my case is a USB flash drive on my Windows router USB port. I didn’t test to see if the drive letter is persistent between reboots/power failures. -Thanks

[sdetweil]

@thartley see instructions, next message

The trick is MMM-ImagesPhotos uses a fixed folder name, uploads, do you have to create a link from that to your mounted file share

Using the ln command

[sdetweil]

if your NAS is Synology, like mine
create a shared folder using the Control Panel, Shared folder function

make sure the permissions are set for whatever user will be accessing it (here sam for me)

you should be able to see this share on a Windows or Mac system

now you need to enable access from the PI/linux this takes 2 steps

1. create a folder of some name in the /media folder,
   this will require sudo

     sudo mkdir /media/xxx 

2. create an entry in the /etc/fstab file
   this will require sudo

     sudo nano /etc/fstab 

here is mine for the media folder above

//192.168.2.32/media /media/xxx cifs username=sam,password=xxxxxxx,iocharset=utf8,file_mode=0777,dir_mode=0777 

//NAS_ipaddress/shared_name local_system_folder (from step1),

set the username and password required to access this share (as defined in your nas)
save the fstab entry ctrl-o, ctrl-x
now mount the folder

sudo mount -a 

then look at the mounted folder

ls /media/xxx 

(from step 1) you should see the files listed from the shared folder

from now on, when the system boots up, it will automount this share.
if the nas is down, or something causes lost connection, do

sudo mount -a

again to reconnect

now, for the MMM-ImagesPhotos step
it uses a hard coded folder for the images

 MMM-ImagePhotos/uploads

we need to make that point to the mounted folder
so,
rename the folder out of the way

cd ~/MagicMirror/modules/MMM-ImagePhotos
mv uploads old_uploads

now create a link , need sudo for this

sudo ln -s /media/xxx uploads

then check it

ls uploads

you should see the same output as in the end of step 2 above

now MMM-ImagePhotos will pull images from the mounted and linked share from your nas (file server…)

[JohnGalt]

@thartley – Follow Sam’s instructions.

I am traveling so didn’t get to finish mine. I got to a point where I got a message that the action was in progress, but it would never finish. After some research I’m pretty sure I have a permission problem and will check it out when I get home in a couple of weeks.