Nextcloud Hanging on deployment 1/2 in Truenas Scale
Description
Problem/Justification
Impact
Attachments
Activity
Nicholas Falter August 11, 2023 at 3:41 AM
I couldn’t resolve the issue, so I just uninstalled truenas scale, installed truenas core, and then it worked.
Ryan Hoke July 4, 2023 at 5:38 AM
Christian,
I left a comment on your ticket, can you please provide more information on your datasets? I created and added docker user and group to the postgres datasets and deployment still hangs with nextcloud pod seemingly failing to start apache. The postgres pod log looks like it is up and listening for connections.
If I do not use any host paths at all I get the same result so I don’t understand how added permissions changed anything. Thanks.
Christian Lewin July 2, 2023 at 12:25 PM
Have you tried my solution I used for this ticket: ?
Please check if all group permissions of your dataset are set correctly, i.e. if the group has read/write access to the directory.
Nicholas Falter July 1, 2023 at 3:35 AM
Thanks for the tip, William, but I similarly to Ryan have upgraded and am unfortunately still encountering the issue. I checked the logs and there seems to be no change. Is there any more information that I could provide that would be helpful? What other steps could I attempt? Thanks for the assistance!
Ryan Hoke June 30, 2023 at 9:35 PM
Hello,
I have update to 22.12.3.1 with the same results.
Details
Details
Assignee
Triage TeamReporter
Nicholas FalterComponents
Fix versions
Affects versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
I am a beginner with truenas. I’ve been attempting to install and use Nextcloud (version 1.6.31)
on Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz
Memory: 1.9GiB
I have been getting an issue with nextcloud hanging on “DEPLOYING 1/2” I have configured my dataset using all default values, and installed Nextcloud using the following configuration:
The nextcloud logs are as follows:
Inside the ngix logs I am repeatedly getting:
2023-06-26 00:00:02.232536+00:00172.16.0.1 - - [26/Jun/2023:00:00:02 +0000] "GET /status.php HTTP/2.0" 502 157 "-" "kube-probe/1.25"
2023-06-26 00:00:07.232249+00:00172.16.0.1 - - [26/Jun/2023:00:00:07 +0000] "GET /status.php HTTP/2.0" 502 157 "-" "kube-probe/1.25"
2023-06-26 00:00:07.232397+00:002023/06/26 00:00:07 [error] 29#29: *45 no live upstreams while connecting to upstream, client: 172.16.0.1, server: localhost, request: "GET /status.php HTTP/2.0", upstream: "http://localhost/status.php", host: "localhost"
It seemed that on the forums other people were having the same issue:
If I am reporting this in the wrong place or a solution exists, please let me know!