Nextcloud redis internal server error

Задача:

Убрать ошибку “Internal Server Error” в Nextcloud

—————————————————————

Уже сталкивался с ошибкой в статье “Ошибка nextcloud — Internal Server Error“, в этот раз попробую разобрать решение проблемы более детально.

Ошибка появилась после отключения питания на сервере

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

Немного информации о сервере:

• FreeBSD 13.0 release p4
• Nginx 1.20.1
• PHP 8.0.11
• MariaDB 10.5.12
• Redis 6.0.15
• memcached
• APCu
• OPcache

Кеширование Nextcloud (часть конфига nextcloud)

  'memcache.local' => '\OC\Memcache\APCu',
  'memcache.distributed' => '\OC\Memcache\Redis',
  'filelocking.enabled' => 'true',
  'memcache.locking' => '\OC\Memcache\Redis',
  'redis' =>
  array (
    'host' => '/tmp/redis.sock',
    'port' => 0,
    'dbindex' => 0,
    'password' => '5e49d5aa132cc547847847849ba6c62c295730dbac10',
    'timeout' => 1.5,
  ),

Я сразу проверил службы отвечающие за кеш

root@cloud:/ # service memcached status
memcached is running as pid 1013.
root@cloud:/ # service redis status
redis is not running.
root@cloud:/ #

Проверяем конфиг Редиса

root@cloud:/ # cat /usr/local/etc/redis.conf | grep -v '^#' | grep -v '^$' | grep -v '^;'
protected-mode yes
tcp-backlog 511
unixsocket /tmp/redis.sock
unixsocketperm 766
timeout 0
tcp-keepalive 300
daemonize yes
supervised no
pidfile /var/run/redis/redis.pid
loglevel notice
logfile /var/log/redis/redis.log
databases 16
always-show-logo yes
save 900 1
save 300 10
save 60 10000
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename dump.rdb
dir /var/db/redis/
requirepass 5e49d5aa132cc547847847849ba6c62c295730dbac10
slave-serve-stale-data yes
slave-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
slave-priority 100
lazyfree-lazy-eviction no
lazyfree-lazy-expire no
lazyfree-lazy-server-del no
slave-lazy-flush no
appendonly no
appendfilename "appendonly.aof"
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
aof-use-rdb-preamble no
lua-time-limit 5000
slowlog-log-slower-than 10000
slowlog-max-len 128
latency-monitor-threshold 0
notify-keyspace-events ""
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
aof-rewrite-incremental-fsync yes
root@cloud:/ #

Проверяем лог Redis

root@cloud:/ # cat /var/log/redis/redis.log

853:C 27 Oct 2021 20:53:04.227 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
853:C 27 Oct 2021 20:53:04.227 # Redis version=6.0.15, bits=64, commit=00000000, modified=0, pid=853, just started
853:C 27 Oct 2021 20:53:04.227 # Configuration loaded
                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           Redis 6.0.15 (00000000/0) 64 bit
  .-`` .-```.  ```/    _.,_ ''-._
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 853
  `-._    `-._  `-./  _.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |           http://redis.io
  `-._    `-._`-.__.-'_.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'

853:M 27 Oct 2021 20:53:04.230 # Server initialized
853:M 27 Oct 2021 20:53:04.231 # Short read or OOM loading DB. Unrecoverable error, aborting now.
853:M 27 Oct 2021 20:53:04.231 # Internal error in RDB reading offset 0, function at rdb.c:2405 -> Unexpected EOF reading RDB file
root@cloud:/ #

Проверяем каталог

root@cloud:/ # ls -lh /var/db/redis/
total 348
-rw-r--r--  1 redis  redis     0B Oct 27 14:41 dump.rdb
-rw-r--r--  1 redis  redis   348K Oct 27 14:41 temp-79488.rdb
root@cloud:/ #

Файлы .rdb – это дампы на диске для резервного копирования или сохранения. Их можно безопасно удалить, конечно в рамках решения проблем c nextcloud, ну а сама база данных Redis полностью находится в памяти. 

Удаляем файлы и пробуем запустить

root@cloud:/ # service redis start
Starting redis.
root@cloud:/ # service redis status
redis is not running.
root@cloud:/ # rm /var/db/redis/*
root@cloud:/ # ls -lh /var/db/redis/
total 0
root@cloud:/ # service redis start
Starting redis.
root@cloud:/ # service redis status
redis is running as pid 1462.
root@cloud:/ # ls -lh /var/db/redis/
total 0
root@cloud:/ # service redis stop
Stopping redis.
Waiting for PIDS: 1462.
root@cloud:/ # ls -lh /var/db/redis/
total 8
-rw-r--r--  1 redis  redis   4.8K Oct 27 22:52 dump.rdb
root@cloud:/ # service redis start
Starting redis.
root@cloud:/ #

Как видим, dump файл заново создался. Проверяем работу Nextcloud, всё работает

root@cloud:/ # sudo -u www php /usr/local/www/nextcloud/occ status
The process control (PCNTL) extensions are required in case you want to interrupt long running commands - see https://www.php.net/manual/en/book.pcntl.php
  - installed: true
  - version: 22.2.0.2
  - versionstring: 22.2.0
  - edition:
root@cloud:/ #

Internal Server Error в Nextcloud

Убрать ошибку “Internal Server Error” в Nextcloud

Уже сталкивался с ошибкой в статье “Ошибка nextcloud — Internal Server Error“, в этот раз попробую разобрать решение проблемы более детально.

Ошибка появилась после отключения питания на сервере

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

Немного информации о сервере:

• FreeBSD 13.0 release p4
• Nginx 1.20.1
• PHP 8.0.11
• MariaDB 10.5.12
• Redis 6.0.15
• memcached
• APCu
• OPcache

Кеширование Nextcloud (часть конфига nextcloud)

Я сразу проверил службы отвечающие за кеш

Проверяем конфиг Редиса

Проверяем лог Redis

Файлы .rdb – это дампы на диске для резервного копирования или сохранения. Их можно безопасно удалить, конечно в рамках решения проблем c nextcloud, ну а сама база данных Redis полностью находится в памяти.

Удаляем файлы и пробуем запустить

Как видим, dump файл заново создался. Проверяем работу Nextcloud, всё работает

Источник

Nextcloud 13 — New Instalation 500 Internal Server Error #8406

Steps to reproduce

I’ve installed Nextcloud 13 with the following procedure:

apt-get install apache2 mariadb-server -y
systemctl start apache2
systemctl enable apache2
systemctl start mysql
systemctl enable mysql
apt-get install php7.1-xml php7.1 php7.1-cgi php7.1-cli php7.1-gd php7.1-curl php7.1-zip php7.1-mysql php7.1-mbstring wget unzip -y
mysql_secure_installation

created a database named «nextclouddb» and a user ‘nextcloud’@’localhost’.
Downloaded and unpacked nextcloud 13 then:

chown -R www-data:www-data /var/www/html/nextcloud/

sudo -u www-data php7.1 occ maintenance:install —database mysql —database-name nextclouddb —database-user nextcloud —admin-user admin

configured config.php and then:

sudo -u www-data php /var/www/html/nextcloud/occ maintenance:update:htaccess
sudo systemctl restart apache2

Expected behaviour

When I connect from my browser to http://127.0.0.1/nextcloud or http://localhost/nextcloud I should see the nextcloud start page.

Actual behaviour

Here is the error on the browser:

• @author Joas Schilling * @author Jörn Friedrich Dreyer * @author Lukas Reschke * @author Morris Jobke * @author Robin Appelman * @author Sergio Bertolín * @author Thomas Müller * @author Vincent Petry * * @license AGPL-3.0 * * This code is free software: you can redistribute it and/or modify * it under the terms of the GNU Affero General Public License, version 3, * as published by the Free Software Foundation. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU Affero General Public License for more details. * * You should have received a copy of the GNU Affero General Public License, version 3, * along with this program. If not, see * */ require_once DIR . ‘/lib/versioncheck.php’; try < require_once DIR . ‘/lib/base.php’; OC::handleRequest(); > catch(OCServiceUnavailableException $ex) < OC::$server->getLogger()->logException($ex, array(‘app’ => ‘index’)); //show the user a detailed error page OC_Response::setStatus(OC_Response::STATUS_SERVICE_UNAVAILABLE); OC_Template::printExceptionErrorPage($ex); > catch (OCHintException $ex) < OC_Response::setStatus(OC_Response::STATUS_SERVICE_UNAVAILABLE); try < OC_Template::printErrorPage($ex->getMessage(), $ex->getHint()); > catch (Exception $ex2) < OC::$server->getLogger()->logException($ex, array(‘app’ => ‘index’)); OC::$server->getLogger()->logException($ex2, array(‘app’ => ‘index’)); //show the user a detailed error page OC_Response::setStatus(OC_Response::STATUS_INTERNAL_SERVER_ERROR); OC_Template::printExceptionErrorPage($ex); > > catch (OCUserLoginException $ex) < OC_Response::setStatus(OC_Response::STATUS_FORBIDDEN); OC_Template::printErrorPage($ex->getMessage(), $ex->getMessage()); > catch (Exception $ex) < OC::$server->getLogger()->logException($ex, array(‘app’ => ‘index’)); //show the user a detailed error page OC_Response::setStatus(OC_Response::STATUS_INTERNAL_SERVER_ERROR); OC_Template::printExceptionErrorPage($ex); > catch (Error $ex) < try < OC::$server->getLogger()->logException($ex, array(‘app’ => ‘index’)); > catch (Error $e) < $claimedProtocol = strtoupper($_SERVER[‘SERVER_PROTOCOL’]); $validProtocols = [ ‘HTTP/1.0’, ‘HTTP/1.1’, ‘HTTP/2’, ]; $protocol = ‘HTTP/1.1’; if(in_array($claimedProtocol, $validProtocols, true)) < $protocol = $claimedProtocol; >header($protocol . ‘ 500 Internal Server Error’); header(‘Content-Type: text/plain; charset=utf-8’); print(«Internal Server Errornn»); print(«The server encountered an internal error and was unable to complete your request.n»); print(«Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.n»); print(«More details can be found in the webserver log.n»); throw $e; > OC_Response::setStatus(OC_Response::STATUS_INTERNAL_SERVER_ERROR); OC_Template::printExceptionErrorPage($ex); >

Server configuration

Here is my config.php:

Operating system:

Web server:
Apache 2

Database:

PHP version:

Nextcloud version: (see Nextcloud admin page)

Updated from an older Nextcloud/ownCloud or fresh install:

The text was updated successfully, but these errors were encountered:

Источник

Internal Server Error #13597

Steps to reproduce

Visit your website

Expected behaviour

I expect a login screen.

Actual behaviour

I get this error:

The file /var/www/nextcloud/lib/private/Files/Node/Node.php exists.

Server configuration

Operating system: Ubuntu 16.04

Web server: Apache2

Database: mariaDB (& redis)

PHP version: 7.0.32

Nextcloud version: 15

Updated from an older Nextcloud/ownCloud or fresh install: from 14

Where did you install Nextcloud from: What does this question mean?

Signing status: What does this question mean?

I can’t do that because I can’t log in.

List of activated apps:

Nextcloud configuration:

Are you using external storage, if yes which one: local/smb/sftp/.

Are you using encryption: yes/no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/.

Client configuration

Browser:

Operating system:

Web server error log

Nextcloud log (data/nextcloud.log)

Browser log

The text was updated successfully, but these errors were encountered:

Same issue here, I first upgraded from Ubuntu 16.04 to 18.04 then used the upgrader in nextcloud web to upgrade from 13 to 14. I now have exactly the same issues. My mobile nextcloud app although still works fine. So I guess it has something to do with the changes from PHP 7.0 to 7.2.

I’m still stuck. Did you already found a solution?

Nextcloud
Interne serverfout

De server was niet in staat je aanvraag te verwerken.

Stuur de hieronder afgebeelde technische details naar de server beheerder wanneer dit opnieuw gebeurt.

Meer details in de serverlogging,
Technische details

Источник

[Nextcloud 14] Internal Server Error #11205

I have installed Nextcloud and was working for a few hours and then it’s showing an Internal Server Error. I have checked the server log and haven’t found what’s the problem.

BTW, I have other apps working fine. The issue is just with nextcloud 14.

Client Error

Server Log

The text was updated successfully, but these errors were encountered:

Your server log is incomplete. Can you please post more content of your server log?
Have a look at it with «less» or «cat» and not with «vi».

And check first that your database is reachable if you use MySQL or PostgreSQL.

This also happens for me, during first time LDAP login. The error logs are:

$ name = $ user -> getBackendClassName ();

GitMate.io thinks possibly related issues are #6839 (Nextcloud got internal Server error after update APP:OnlyOFFICE, need to remove this APP completely), #2741 (Calendar app: internal server error after upgrading to Nextcloud 11), #7622 (NextCloud Server Listener ), #8326 (Internal Server Error (Template not found) when loading Calendar after upgrade to Nextcloud 13.x), and #5056 (nextcloud 12 upgrade error).

I’m pretty sure I stumbled across this issue this morning. I had added a user through the IMAP verification, and then it disappeared from the users list and when I try logging in to the account, it errors. There is no sign of the account in the users list or under occ user:info [username] .

Источник

Internal Server Error #911

Running Docker container latest . Everything was working fine (apps installed, mobile connected, etc), until I moved the volume files to a larger volume 10GB to 50GB, and then:

Pretty useless error message and I have NO idea where to find server log . I’m not even sure what filename I’m looking for. There is a file under nextcloud_nextcloud/_data named nextcloud.log . Is that the server log ? I’ve tried removing that file to see if it would be re-created and/or update after a restart of the container and a refresh of the error page, but nothing.

sure I could just start all over again, but fyi, this is the second time I’ve tried using Nextcloud (the first was a few years ago) and I recall having the same issue back then; Internal Server Error and nothing else in terms of error details. I guess this is fine for the end-user, they just call the admin, but where’s the support for the admin? I would love nothing more than for this open-source cloud solution to work, but if nextcloud is really this fragile, then I guess its just not the solution I’m looking for. Back to Google?? (ugh!)

Obviously pretty disappointed by this, but any and all support are very much appreciated.
Cheers!

EDIT:
Went back through the docs to find mention of a Nextcloud Server Log File. Does this file NOT exist unless its enabled in the Admin Page??

Also, when I connect to the container and try to view the Webserver Log Files, this is what I get:

Does this get written somewhere on the host? This could just be a docker thing, I’m really not sure, but either way, it would be nice to find these log files, and eventually solve «Internal Server Error».

The text was updated successfully, but these errors were encountered:

Источник