Server error while setup step 'warming up the cache'

[toblie]

Hi, badly I am not able to setup the server. While the the step 'warming up the cache' it always throws an error and I am not able to finish the setup.

I would paste the whole error, but the error window prevents to scroll horizontal or select and copy the text... I already tried to create a volume for cache path and also chmod the path recursively. But still the same.

Any idea which can help me?

THX

[christianlupus]

Hello. Let's see if we can get down to it.

First: How is your setup? You write something about a volume. I suspect docker to be in use but please specify it. What container are you using? What HTTP server? What PHP version? What DB? DB Version? Further what did you do yet? Where did you get PK (if not packed with a container image)? Which steps did you perform?

[toblie]

Thanks for your reply! Sorry for the poor informations - will try to add some more. Yes, you're right I am using Docker running on arm64 device (pine64). I pulled the image from https://github.com/Forceu/partkeepr_docker - I think it is a fork from https://github.com/mhubig/docker-partkeepr.

Partkeepr: 1.4.0 HTTP Server: Apache PHP: 7.1.33 DB: MariaDB 10.0.38

I just created the volume, pull and start the image. Then execute: chown www-data:www-data -R /app/app/config

and while trying to fix the error, also exceute chmod 777 -R /app/app/cache/ and create new volume for cache path.

All went fine while first setup only the last step with warming cache in "setup 2/2" fails. I think thats all...

[christianlupus]

I just created the volume, pull and start the image. Then execute:

chown www-data:www-data -R /app/app/config

Inside or outside the container?

Are there any logs in docker logs partkeepr-web? There should be a complete message.

You could enter the container as suggested and find out if the path mentioned in the first image exists (at least the part that is visible in the image or use a web console to read the HTML code manually).

As I suspect a setup issue here, I ping @Forceu.

[toblie]

I changed the permissions within the container... The mentioned path is well filled:

I think the logs won't show any causing: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message ,AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message ,[Wed Nov 25 18:02:54.309621 2020] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.38 (Debian) PHP/7.1.33 configured -- resuming normal operations ,[Wed Nov 25 18:02:54.309943 2020] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND' ,[Wed Nov 25 18:17:52.344599 2020] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully ,AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message ,AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message ,[Thu Nov 26 05:37:35.149582 2020] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.38 (Debian) PHP/7.1.33 configured -- resuming normal operations ,[Thu Nov 26 05:37:35.149834 2020] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND' ,

[Forceu]

Might be related to #811