[Dynamix File Integrity plugin]

On 5/30/2022 at 8:18 PM, Jake0010 said:

<br /> <b>Fatal error</b>: Allowed memory size of 134217728 bytes exhausted (tried to allocate 218365648 bytes) in <b>/usr/local/emhttp/plugins/dynamix.file.integrity/include/ProgressInfo.php</b> on line <b>40</b><br />

 

What can be done to perma-FIX the plugin?  I don't want to manually edit anything.  I just want this to work.  I started with sha256 and switched to blake3.  The same error is happening on the save hdd for me.

I've done this and it wasn't enough. I also changed this file, part of the plugin itself (and the one that's actually complaining):

/usr/local/emhttp/plugins/dynamix.file.integrity/include/ProgressInfo.php

 

I've added this line, just below the top:

 

ini_set('memory_limit', '512MB');

 

So the file now looks like this:

 

<?
$plugin = 'dynamix.file.integrity';
$docroot = $docroot ?: $_SERVER['DOCUMENT_ROOT'] ?: '/usr/local/emhttp';
$translations = file_exists("$docroot/webGui/include/Translations.php");
ini_set('memory_limit', '512MB');

 

That might be too large, but I believe PHP won't allocate that much memory unless it needs it...

It works - but it doesn't survive a reboot either, unfortunately.

Maybe @bonienl can incorporate a version of this into the next release of the plugin?

[[Support] Linuxserver.io - Nextcloud]

I installed this today and hit a couple of problems.

 

1. It timed out after I got the setup done. (Solution - just wait 5 minutes)

 

When I entered the admin name & password, all the database details, it ran and then timed out. While googling for a solution it was still running behind the scenes, and by the time I came back to it (5 minutes or so) loading the web page gave me a login screen. It seems that something in the webserver config is timing out if the initial set up is slow. I didn't dig any deeper, to be fair.

 

2. It's very slow. (Solution - install Redis)

 

I had about 4GB of data to sync, and it was estimating about 24 hours or more to complete the upload. I installed the official Redis docker image from Community Applications (I accepted the defaults) and then once that was running I made changes to /mnt/user/appdata/nextcloud/www/nextcloud/config/config.php as follows, to enable using it:

(Based on https://docs.nextcloud.com/server/18/admin_manual/configuration_server/caching_configuration.html )

 'memcache.distributed' => '\OC\Memcache\Redis',
  'redis' => [
       'host' => 'redis',
       'port' => 6379,
  ],
  'memcache.locking' => '\OC\Memcache\Redis',

After a reboot, it's down to under an hour to sync. From Googling, if you have a lot of small files it can be slow no matter what you do, but I'll take a twenty-fold speed increase any day!

 

I hope this helps a few other people, who might have the same issues. I didn't find any discussion of them on this thread so far.

[[Support] Linuxserver.io - Nextcloud]

I am having a lot of problems with this container - I followed the instructions linked in the first page here, and SpaceInvaderOne's guide.

 

Firstly when I open the WebUI the certificate is flagged as invalid, and Chrome 80 won't let me just accept it and connect anyway. Safari does, but then when I enter the details to set up admin, MariaDB login details etc it times out. I get a 'gateway timeout' error.

 

Nothing shows up in the log files, but I can see that it has created folders for the admin user, so I presume it's trying and failing to do something... 

 

Google hasn't helped me, so I suspect I'm doing something wrong - but I can't even figure out how to find out what!

 

Any ideas?

 

Cheers!

[[Support] SpaceinvaderOne - Macinabox]

This is a great tool, thanks very much!

 

It does create a very minor problem though - when I run the 'Fix Common Problems' plugin I get this error reported:

 

The following directories exist with similar names, only differing by the 'case' which will play havoc with Windows / SMB access.  Windows does NOT support folder names only differing by their case and strange results will happen should you attempt to manipulate the folders or files

/mnt/user/appdata/macinabox
/mnt/user/appdata/MacinaBox

Now obviously I'm not sharing appdata over SMB - but would it be possible to update the container to only create one or other of these, so the 'Common Problems' plugin stops complaining?

 

Thanks!