nextcloud / nextcloud/nextcloudpi
NextCloudPi not yet initialized, trying again in a few seconds
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Shell
- Sterne
- 2.9k
- Forks
- 318
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
I have been through all the open and closed tickets and the forum but dont have an answer so am opening a new issue
System information
Docker version 20.10.21, build baeda1f
docker-compose version 1.29.2, build 5becea4c
Docker Images tested 1.50.2, 1.50, 1.49,1.48.3
I previously had this running with 1.50.2 and then had to do a redeploy on docker now all I received is the not yet initialised message.
I have tried:
- Accessing the mariadb server within the image, access works, tables and database exist
- I have tried using a standard docker volume as opposed to a local folder for ncdata and same result
- I have used a mapping to nextcloudpi.local
I have run ncp-update within the image (allowing the update) and can see there is an udpate there to 1.50.3 (is there an updated docker image somewhere?)
Checking the activation page I can see multiple requests to ncp-launcher.php and replies (200).
action:
launch
ref:
nc-admin
config:
{ "PASSWORD":"*","CONFIRM" :"**","USER" : "ncp" }
csrf_token:
*
and response { "token": "iPQba5a4SVRnD+H/H6FsX2Cr0Q72UWIv0I3P2l4W0XE=", "ref": "nc-admin", "output": "" , "ret": "1" }
I can see an error in apache2/error.log regarding the access provisions set in the apache2 conf file
access check of 'localhost' to /ncp-launcher.php failed
I am stuck I think I have tried everything, Any ideas?
NextCloudPi diagnostics
NextCloudPi version v1.50.2
NextCloudPi image NextCloudPi_docker_09-29-22
OS Debian GNU/Linux 11. 5.4.0-125-generic (x86_64)
automount no
USB devices sdd
datadir /data/nextcloud/data
data in SD no
data filesystem ext2/ext3
data disk usage 582G/916G
rootfs usage 72G/136G
swapfile /swapfile
dbdir /data/database
Nextcloud check ok
Nextcloud version 24.0.5.1
HTTPD service up
PHP service up
MariaDB service up
Redis service up
HPB service down
Postfix service up
Internet check no
public IP ***REMOVED SENSITIVE VALUE***
public IP ***REMOVED SENSITIVE VALUE***
Port check 80 closed
Port check 443 closed
IP ***REMOVED SENSITIVE VALUE***
gateway ***REMOVED SENSITIVE VALUE***
Interface eth0
certificates ***REMOVED SENSITIVE VALUE***
NAT loopback no
Uptime 85days
Nextcloud configuration
{
"system": {
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": {
"0": "localhost",
"7": "nextcloudpi",
"5": "nextcloudpi.local",
"8": "nextcloudpi.lan",
"3": "c2ab77cf152f",
"11": "206.83.103.115",
"1": "172.80.19.2",
"14": "c2ab77cf152f"
},
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"dbtype": "mysql",
"version": "24.0.5.1",
"overwrite.cli.url": "https:\/\/c2ab77cf152f\/",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"instanceid": "***REMOVED SENSITIVE VALUE***",
"memcache.local": "\\OC\\Memcache\\Redis",
"memcache.locking": "\\OC\\Memcache\\Redis",
"redis": {
"host": "***REMOVED SENSITIVE VALUE***",
"port": 0,
"timeout": 0,
"password": "***REMOVED SENSITIVE VALUE***"
},
"tempdirectory": "\/var\/www\/nextcloud\/data\/tmp",
"mail_smtpmode": "sendmail",
"mail_smtpauthtype": "LOGIN",
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"preview_max_x": "2048",
"preview_max_y": "2048",
"jpeg_quality": "60",
"overwriteprotocol": "https"
}
}
HTTPd logs
[Wed Nov 23 10:56:14.926730 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:37516] AH01753: access check of 'localhost' to /img/favicon.png failed, reason: unable to get the remote host name
[Wed Nov 23 10:56:26.184628 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:52922] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:56:36.266613 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:39208] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:56:46.704259 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:59874] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:56:57.136345 2022] [authz_host:error] [pid 129:tid 140060515518208] [client 172.80.19.1:47682] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:57:07.248116 2022] [authz_host:error] [pid 129:tid 140060515518208] [client 172.80.19.1:55138] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:57:17.340687 2022] [authz_host:error] [pid 129:tid 140060515518208] [client 172.80.19.1:47216] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:57:27.425251 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:60448] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:57:37.523957 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:47640] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:57:47.944559 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:33126] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:57:58.374916 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:35890] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:58:08.460437 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:57020] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:58:18.558789 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:40038] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:58:28.974685 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:34026] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:58:39.058942 2022] [authz_host:error] [pid 129:tid 140060515518208] [client 172.80.19.1:34140] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:58:49.161254 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:57460] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:58:59.580072 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:46670] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:59:10.026599 2022] [authz_host:error] [pid 129:tid 140060515518208] [client 172.80.19.1:33526] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:59:20.114348 2022] [authz_host:error] [pid 129:tid 140060515518208] [client 172.80.19.1:40334] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Wed Nov 23 10:59:30.506882 2022] [authz_host:error] [pid 130:tid 140060549105408] [client 172.80.19.1:59576] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
Database logs
tail: cannot open '/var/log/mysql/*.log' for reading: No such file or directory
Nextcloud logs
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit dem Einstiegspunkt /ncp-launcher.php, der Apache-Zugriffskonfiguration und dem Fehlerprotokoll sowie den gemeldeten Docker-Image-Versionen; führe ncp-update aus, um den verfügbaren Image-Status zu vergleichen. Erledigt ist die Aufgabe, wenn festgestellt wurde, warum die Initialisierung ständig erneut versucht wird, und bestätigt wurde, dass die Aktivierungsanfrage in der betroffenen Docker-Bereitstellung abgeschlossen wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- apache, docker, docker-compose, php, shell
- Bereich
- backend, devops, infrastructure
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100