Status.php - server replied: Intrernal Server Error

ℹ️ Support
1

Running nextcloud on a Ubuntu 16:04 - been running well for several months, came in this morning and the kde client is saying No COnnection to Next65cloud at https://nextcloud.restylegraphics.co.uk. Error transfering https://nextcloud.restylegraphics.co.uk/status.php - server replied: Internal Server Error,

I am able to ping the vm and nothing has changed in my configuration - where do I begin to diagnose the problem?

Thank you for your help

2

Check in your webserveur log (for apache it’s /var/log/apache2/error.log, for nginx it’s /var/log/nginx/error.log ) and in the nextcloud log file /path/to/your/nextcloud/data/nextcloud.log

Note : i have see some similar bug on my install when the servers are overloaded, eventually tape “top” in your shell for see process’s consumption .

3

Thank you for your reply.

The system is not under heavy load

Looks like a issue within the Apache log.

Apache log -

Mon Jan 15 10:18:46.529262 2018] [:error] [pid 482] [client 192.168.1.21:59604] PHP Fatal error: Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An $
[Mon Jan 15 10:18:46.529753 2018] [:error] [pid 482] [client 192.168.1.21:59604] PHP Fatal error: Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An $
[Mon Jan 15 10:19:20.078858 2018] [:error] [pid 478] [client 192.168.1.21:59622] PHP Fatal error: Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An $
[Mon Jan 15 10:19:20.079258 2018] [:error] [pid 478] [client 192.168.1.21:59622] PHP Fatal error: Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An $

Nextcloud.log -

{“reqId”:“QtEADIOMIflwDSP0vE81”,“level”:3,“time”:“2017-09-12T12:00:35+00:00”,“remoteAddr”:“192.168.1.30”,“user”:"–",“app”:“appstoreFetcher”,“method”:“POST”,“url”:"/index.php",$
{“reqId”:“QNgtpTjE00V8VfPGH9lM”,“level”:2,“time”:“2017-09-16T09:57:08+00:00”,“remoteAddr”:“192.168.1.30”,“user”:"–",“app”:“core”,“method”:“GET”,“url”:"/",“message”:“Trusted do$
{“reqId”:“2Pg3zIJhEQ8sA5mtFFPX”,“level”:2,“time”:“2017-09-16T09:57:08+00:00”,“remoteAddr”:“192.168.1.30”,“user”:”–",“app”:“core”,“method”:“GET”,“url”:"/js/core/merged-templa$
{“reqId”:“ZDzV50qTOsT3ujdP68Jd”,“level”:2,“time”:“2017-09-22T12:31:37+00:00”,“remoteAddr”:“192.168.1.37”,“user”:"–",“app”:“core”,“method”:“POST”,“url”:"/login",“message”:“Logi$
{“reqId”:“PkP2Xm8Hqni8RVhir1mZ”,“level”:2,“time”:“2017-09-22T12:32:20+00:00”,“remoteAddr”:“192.168.1.37”,“user”:”–",“app”:“core”,“method”:“POST”,“url”:"/login?user=johnparry75$
{“reqId”:“GcxtHGeJoBzdylS0MZGF”,“level”:2,“time”:“2017-09-22T12:35:43+00:00”,“remoteAddr”:“192.168.1.37”,“user”:"–",“app”:“core”,“method”:“POST”,“url”:"/login?user=johnparry75$

4

Check your database server.

1 Like
5

Tape on your database server
sudo service mysql status

If it not running or fail, restart it with the following command :
sudo service mysql restart
If it’s running, check in your /path/to/nextcloud/config/config.php if the database informations are true (login, host, password).
If the informations are true and the database server is running, check if your database server bind (listen) on the correct IP address/Hostname with the following command :
cat /etc/mysql/my.cnf | grep "bind"

If you bind on 192.168.1.42 and in your config.php you have write 127.0.0.1, mysql server don’t accept your client request.

6

sudo /etc/init.d/mysql start
[…] Starting mysql (via systemctl): mysql.serviceJob for mysql.service failed because the control process exited with error code. See “systemctl status mysql.service” and “journalctl -xe” for details.
failed!

journalctl -xe | tail -20
– Unit mysql.service has failed.

– The result is failed.
Jan 15 14:00:21 systemd[1]: mysql.service: Unit entered failed state.
Jan 15 14:00:21 systemd[1]: mysql.service: Failed with result ‘exit-code’.
Jan 15 14:00:22 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Jan 15 14:00:22 systemd[1]: Stopped MySQL Community Server.
– Subject: Unit mysql.service has finished shutting down
– Defined-By: systemd
– Support:

– Unit mysql.service has finished shutting down.
Jan 15 14:00:22 systemd[1]: Failed to reset devices.list on /system.slice/mysql.service: Operation not permitted
Jan 15 14:00:22 systemd[1]: Starting MySQL Community Server…
– Subject: Unit mysql.service has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit mysql.service has begun starting up.

7

Hi, ich bekomme den gleichen Fehler 500 Internal Server Error bei Zugriff auf status.php. Ich habe alle oben genannten Punkte überprüft. Mein DB-SErver läuft und der Nextcloud Server ist auch eingeloggt wie ich an der Processlist sehen kann. Beim Aufruf vom Linux Client erhalte ich allerdings den o.g. Fehler und beim Zugriff über den Browser nur einen weißen Bildschirm. Alle REchte und Eigentümereigenschaften sind richtig. Das Problem tritt auf seit ich die VM wegen eines Hardware-Fehlers auf einen anderen Server umziehen musste.

Hat jemand eine Idee, wo ich noch nachsehen könnte?

Gruß
Ulrich