7 hours ago, toasti said:

for example UID and GID

But these are the only two from what I see that are not compatible.

I've updated the template now but you have to manually update your template since my templates doesn't update automatically.

2 hours ago, OneBehler said:

Can you point me in the right direction to correct?

I think some plugin is causing this, I've tried the container now (fresh install) and it works just fine: magicmirror2.log

 

2 hours ago, OneBehler said:

[04.10.2021 16:27.23.890] [ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'simple-git'

Here is the error that is causing this, are you sure that you've also deleted the magicmirror2 folder that was created in your appdata directory and installed the container after you did so (please back up your configuration file and try a complete fresh install)?

Most times some plugins are causing this because the are deprecated or outdated.

15 minutes ago, ich777 said:

... are you sure that you've also deleted the magicmirror2 folder that was created in your appdata directory and installed the container after you did so (please back up your configuration file and try a complete fresh install)?

Most times some plugins are causing this because the are deprecated or outdated.

I did not delete the folder.  I will try this and let you know

Did the delete and fresh install.  Odd that it did that, but worked.  Any insight on how to prevent that from happening in future?  Thanks again for your help.

35 minutes ago, OneBehler said:

Any insight on how to prevent that from happening in future?

Don't know which plugins or addons you've got installed...

This should not happen on a default installation from MagicMirror2.

 

Most of the times this is caused by some plugin because it is deprecated or incompatible.

Hi,
I am using Photoprism (latest version) on Unraid (latest version).
After upgrading to the latest docker build of Photoprism last sunday, I am now facing regular intense writes to my NVME disks every 15 minutes. This has not been the case before the update.
I have already disabled "Webdav Autoindex - Safety Delay" and "Webdav Autoimport- Safety Delay" without any effect.

Is there any timer I may tweak to undo this behaviour?

Best regards
Christian

2 minutes ago, ChrisFr said:

After upgrading to the latest docker build of Photoprism last sunday, I am now facing regular intense writes to my NVME disks every 15 minutes. This has not been the case before the update.

I would recommend to create an issue on their official Github issue tracker: Click

 

I've only created the template for the official Photoprism container.

 

Are you also sure this is caused by Photoprism and not another container? Anything in the logs from the container?

22 minutes ago, ich777 said:

I would recommend to create an issue on their official Github issue tracker: Click

 

I've only created the template for the official Photoprism container.

 

Are you also sure this is caused by Photoprism and not another container? Anything in the logs from the container?

I have raised the issue on Github, thanks.

I have disabled all the other containers and NVME still being written to. Seems like it is the new face recognition, need to check if there are options to disable or tweak regular runs.

12 minutes ago, ChrisFr said:

I have raised the issue on Github, thanks.

I have disabled all the other containers and NVME still being written to. Seems like it is the new face recognition, need to check if there are options to disable or tweak regular runs.

 

I updated one of my PhotoPrism dockers yesterday but wanted to wait to update my second docker until I know there's no issues. It seems like the update has been pulled. Both dockers run different versions now and both are "up to date". Let's hope for a fix soon.

 

Thanks ich777 for the great template btw!

@ChrisFr & @benediktleb both of you can try to create a variable in the template with the Key: 'PHOTOPRISM_DISABLE_FACES' and the Value: 'true' (both without quotes) and see if this will stop the writes, but keep in mind this will disable face detection.

For more variables you can look here: Click

2 hours ago, ich777 said:

But these are the only two from what I see that are not compatible.

I've updated the template now but you have to manually update your template since my templates doesn't update automatically.

 

OK, so I have to compare the complete template with the newest docker-compose from PP to edit, add and maybe delete some settings. For example "PHOTOPRISM_THUMB_FILTER" is no more part of the docker-compose - so just delete it in the template or will it corrupt anything? This setting is integrated in the gui of PP in the meantime.

11 minutes ago, toasti said:

For example "PHOTOPRISM_THUMB_FILTER" is no more part of the docker-compose - so just delete it in the template or will it corrupt anything?

But you can still configure it like it is mentioned here: Click

 

I also don't think a Docker compose file is the best thing to create a template, I would stick to the official documentation from the variables itself, I know the Docker compose file is also in the official documentation but you don't have to define everything.

 

You are completely right about the UID, GID and UMASK variables: Click

Anyways, if you leave them as they are now you should not run into any trouble...

I am in contact with the developer on a regular basis and he let me know to check all these settings and compare with the docker-compose. That's the reason why I compared it.

 

OK, so I will stop PP, do a backup, change the config -> then update it and restart and cross my fingers.

 

Thanks for your support - I hope it will run without any troubles...

58 minutes ago, ich777 said:

@ChrisFr & @benediktleb both of you can try to create a variable in the template with the Key: 'PHOTOPRISM_DISABLE_FACES' and the Value: 'true' (both without quotes) and see if this will stop the writes, but keep in mind this will disable face detection.

For more variables you can look here: Click

Thank You!

Actually I do like to have the face recognition enabled. I tried your template/variable hint with the parameter "PHOTOPRISM_WAKEUP_INTERVAL". Seems like this one may tweak the interval the worker thread runs.

@ich777Should we use 2 Devices for IGPU or only one ? :

devices:
- "/dev/dri/renderD128:/dev/dri/renderD128" # Intel GPU
- "/dev/dri/card0:/dev/dri/card0"

Edited October 5, 20214 yr by Masterwishx

47 minutes ago, Masterwishx said:

@ich777Should we use 2 Devices for IGPU or only one ? :

?

For what exactly?

 

I would strongly recommend to pass through the device /dev/dri:

36 minutes ago, ich777 said:

For what exactly?

 

Sorry i forgot , its for PhotoPrism ,

i added 

PHOTOPRISM_INIT: "tensorflow-amd64-avx2" is working and when only first time container start i have message about starting avx2.

but for gpu they write : 

 

 

Optional hardware devices for video transcoding and machine learning:

# devices:

# - "/dev/video11:/dev/video11" # Video4Linux (h264_v4l2m2m)

# - "/dev/dri/renderD128:/dev/dri/renderD128" # Intel GPU

# - "/dev/dri/card0:/dev/dri/card0"

 

 

# Hardware video transcoding options:

# PHOTOPRISM_FFMPEG_BUFFERS: "64" # FFmpeg capture buffers (default: 32)

# PHOTOPRISM_FFMPEG_BITRATE: "32" # FFmpeg encoding bitrate limit in Mbit/s (default: 50)

# PHOTOPRISM_FFMPEG_ENCODER: "h264_v4l2m2m" # Use Video4Linux for AVC transcoding (default: libx264)

# PHOTOPRISM_FFMPEG_ENCODER: "h264_qsv" # Use Intel Quick Sync Video for AVC transcoding (default: libx264)

# PHOTOPRISM_INIT: "intel-graphics tensorflow-amd64-avx2" # Enable TensorFlow AVX2 & Intel Graphics support

 

1 minute ago, Masterwishx said:

but for gpu they write

Do it like in my example above, this will basically expose the whole /dev/dri device which includes renderD128 and card0.

 

Please keep in mind don't pass this through as a path, you have to do that as a device like in the example above.

 

You don't have to user /dev/dri:/dev/dri

2 minutes ago, ich777 said:

You don't have to user /dev/dri:/dev/dri

OK thanks , i saw now i forgot "intel-graphics tensorflow-amd64-avx2" instead "tensorflow-amd64-avx2"...

Thanks again for this cool container, next spteps they should add Multi user support  

Also we have now Face AI,  if somebody dont know ...

@ich777 forgot to ask maybe you know i was some warning in console ffmpeg also befor IGP added to container :

WARNING: library configuration mismatch

 

is my config right and having iGPU enabled ?

16 minutes ago, Masterwishx said:

WARNING: library configuration mismatch

Please see this issue here: Click

 

Also keep in mind this is not my container, I've only created the template for the official Photoprism container.

14 minutes ago, ich777 said:

I've only created the template

Yea i know , sorry for bothering im fist time trying setup iGPU to container and ffmpeg , i thought maybe you know about it...

5 minutes ago, Masterwishx said:

sorry for bothering

No worries, but it would be best to search for this specific error on the Photoprism Github.

Hi ich777,

I have the exact same problem as OneBehler.

Just wanted to let you know that MichMich and khassel are facing the same problem here as well and it seems to be a major problem with the new 2.17 release. Here's my log: 

I can bash in to the container if i only load some 3rd party modules (MMM-DVB, and Remotecontrol are working fine). 

I think the easiest way is to stay at 2.15 for now (everything worked fine there with all modules). Do you know how to stop the autoupdate?

 

---Checking if UID: 99 matches user---
usermod: no changes
---Checking if GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
---Checking if UID: 99 matches user---
usermod: no changes
---Checking if GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
---MagicMirror² up-to-date---
---Looking for new modules to install---
Module 'MMM-GoogleFit' found!
Module 'MMM-Remote-Control' found!
Module 'MMM-DVB' found!
---Preparing Server---
---Configuration file found!---
---Please wait, permissions are set, this can take some time...---
---Starting Server---

> [email protected] server
> node ./serveronly

[06.10.2021 12:32.03.489] [LOG] Starting MagicMirror: v2.17.1
[06.10.2021 12:32.03.491] [LOG] Loading config ...
[06.10.2021 12:32.03.493] [LOG] Loading module helpers ...
[06.10.2021 12:32.03.494] [LOG] No helper found for module: alert.
[06.10.2021 12:32.03.499] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.499] [LOG] Module helper loaded: updatenotification
[06.10.2021 12:32.03.500] [LOG] No helper found for module: clock.
[06.10.2021 12:32.03.641] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.641] [LOG] Module helper loaded: MMM-Remote-Control
[06.10.2021 12:32.03.641] [LOG] No helper found for module: MMM-Remote-Control-Repository.
[06.10.2021 12:32.03.641] [LOG] No helper found for module: compliments.
[06.10.2021 12:32.03.674] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.674] [LOG] Module helper loaded: newsfeed
[06.10.2021 12:32.03.727] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.727] [LOG] Module helper loaded: MMM-DVB
[06.10.2021 12:32.03.729] [ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'request'
Require stack:
- /magicmirror2/modules/MMM-GoogleFit/node_helper.js
- /magicmirror2/js/app.js
- /magicmirror2/serveronly/index.js
[06.10.2021 12:32.03.729] [LOG] Loading module helpers ...
[06.10.2021 12:32.03.729] [LOG] No helper found for module: alert.
[06.10.2021 12:32.03.729] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.730] [LOG] Module helper loaded: updatenotification
[06.10.2021 12:32.03.730] [LOG] No helper found for module: clock.
[06.10.2021 12:32.03.730] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.730] [LOG] Module helper loaded: MMM-Remote-Control
[06.10.2021 12:32.03.730] [LOG] No helper found for module: MMM-Remote-Control-Repository.
[06.10.2021 12:32.03.731] [LOG] No helper found for module: compliments.
[06.10.2021 12:32.03.731] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.731] [LOG] Module helper loaded: newsfeed
[06.10.2021 12:32.03.731] [LOG] Initializing new module helper ...
[06.10.2021 12:32.03.731] [LOG] Module helper loaded: MMM-DVB
[06.10.2021 12:32.03.732] [ERROR] Whoops! There was an uncaught exception...
[06.10.2021 12:32.03.734] [ERROR] Error: Cannot find module 'request'
Require stack:
- /magicmirror2/modules/MMM-GoogleFit/node_helper.js
- /magicmirror2/js/app.js
- /magicmirror2/serveronly/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
at Function.Module._resolveFilename (/magicmirror2/node_modules/module-alias/index.js:49:29)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.<anonymous> (/magicmirror2/modules/MMM-GoogleFit/node_helper.js:2:17)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/magicmirror2/modules/MMM-GoogleFit/node_helper.js',
'/magicmirror2/js/app.js',
'/magicmirror2/serveronly/index.js'
]
}
[06.10.2021 12:32.03.734] [ERROR] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[06.10.2021 12:32.03.734] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

 

It keeps repeating after those lines..

Edited October 6, 20214 yr by KronosMagna

1 hour ago, KronosMagna said:

Just wanted to let you know that MichMich and khassel are facing the same problem here as well and it seems to be a major problem with the new 2.17 release.

But this isn't my container I think or am I wrong?

 

1 hour ago, KronosMagna said:

I think the easiest way is to stay at 2.15 for now (everything worked fine there with all modules). Do you know how to stop the autoupdate?

No, my container can't be stopped from auto updating.

 

But a fresh install is working fine since I've tried that a few days ago.