# Interner Serverfehler / Snap nach Update

**URL:** <https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672>\
**Category:** 🇩🇪 Deutsch (german)\
**Tags:** update\_problems, snap, nc30, php, php83\
**Created:** [January 22, 2025, 8:14pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672 "2025-01-22T20:14:05Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmchp](https://help.nextcloud.com/letter_avatar/lmchp/32/6_22734026db12803ebb3e059622ac3534.png) [@lmchp](https://help.nextcloud.com/u/lmchp)\
**Post date:** [January 22, 2025, 8:14pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/1 "2025-01-22T20:14:05Z")

</div>

Umgebung:  
Raspberry PI 3 @ Ubuntu 24.04.1 LTS (server)

```auto
# snap list nextcloud
 Name Version Rev Tracking Publisher Notes
 nextcloud 30.0.5snap1 46217 latest/stable nextcloud ✓ -
# php -v
PHP 8.3.6 (cli) (built: Dec 2 2024 12:36:18) (NTS)

Mysql (?) / Apache (?)

daten liegen auf externer USB-hdd (spinning) 

```

- Am 21.01.25 / 6:00 Uhr war auto-upgrade (45729 \> 46217)
- am Vormittag erste Meldungen zu Sync. Fehlern auf Clients
- WebLogin liefert die wohl bekannte Kachel zum /Error 500/:

> Interner Serverfehler
> 
> Der Server konnte die Anfrage nicht fertig stellen.  
> Sollte dies erneut auftreten, sende bitte die nachfolgenden technischen Einzelheiten an deinen Server-Administrator.
> 
> Weitere Details können im Server-Protokoll gefunden werden.  
> Technische Details
> 
> Entfernte Adresse: \<ext. IP\>  
> Anfragekennung: XXXyyyZZZ

einzige Auffälligkeit in Logs:

```auto
2025-01-22T14:36:46.199363+01:00 raspi-3 nextcloud.apache[2119]: Error: Failed opening required '/var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/../symfony/polyfill-iconv/bootstrap.php' (include_path='/snap/nextcloud/46217/htdocs/3rdparty/pear/archive_tar:/snap/nextcloud/46217/htdocs/3rdparty/pear/console_getopt:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear-core-minimal/src:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear_exception:/snap/nextcloud/current/htdocs/apps:/var/snap/nextcloud/current/nextcloud/extra-apps') in /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php:41
2025-01-22T14:36:46.199774+01:00 raspi-3 nextcloud.apache[2119]: Stack trace:
2025-01-22T14:36:46.199953+01:00 raspi-3 nextcloud.apache[2119]: #0 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php(45): {closure}()
2025-01-22T14:36:46.200165+01:00 raspi-3 nextcloud.apache[2119]: #1 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/autoload.php(25): ComposerAutoloaderInitMail::getLoader()
2025-01-22T14:36:46.200672+01:00 raspi-3 nextcloud.apache[2119]: #2 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/composer/autoload.php(5): require_once('...')
2025-01-22T14:36:46.201099+01:00 raspi-3 nextcloud.apache[2119]: #3 /snap/nextcloud/46217/htdocs/lib/private/legacy/OC_App.php(118): require_once('...')
2025-01-22T14:36:46.201315+01:00 raspi-3 nextcloud.apache[2119]: #4 /snap/nextcloud/46217/htdocs/lib/private/AppFramework/Bootstrap/Coordinator.php(76): OC_App::registerAutoloading()
2025-01-22T14:36:46.201479+01:00 raspi-3 nextcloud.apache[2119]: #5 /snap/nextcloud/46217/htdocs/lib/private/AppFramework/Bootstrap/Coordinator.php(48): OC\AppFramework\Bootstrap\Coordinator->registerApps()
2025-01-22T14:36:46.201662+01:00 raspi-3 nextcloud.apache[2119]: #6 /snap/nextcloud/46217/htdocs/lib/base.php(659): OC\AppFramework\Bootstrap\Coordinator->runInitialRegistration()
2025-01-22T14:36:46.201814+01:00 raspi-3 nextcloud.apache[2119]: #7 /snap/nextcloud/46217/htdocs/lib/base.php(1134): OC::init()
2025-01-22T14:36:46.201973+01:00 raspi-3 nextcloud.apache[2119]: #8 /snap/nextcloud/46217/htdocs/console.php(28): require_once('...')
2025-01-22T14:36:46.202175+01:00 raspi-3 nextcloud.apache[2119]: #9 /snap/nextcloud/46217/htdocs/occ(11): require_once('...')
2025-01-22T14:36:47.232984+01:00 raspi-3 nextcloud.apache[2119]: #10 {main}

```

/var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/symfony  
existiert nicht!

Einige krude Versuche diverse php-Reparaturen durchzuführen  
(minimal \> full, Nachinstallation von php-iconv, etc.) waren alle ohne Erfolg.

Ebenso Neuinst. der rev. 46217 (per snap: revert… \> remove… \> install)  
Mehr noch zeigte nach dem revert auch die rev. 45729 den gleichen Fehler… 🥴 😩

Zwischenzeitlich hab ich noch entdeckt, dass die Fehlermeldung einfach reproduziert werden kann - per:

```auto
# nextcloud.occ
An unhandled exception has been thrown:
Error: Failed opening required '/var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/../symfony/polyfill-iconv/bootstrap.php' (include_path='/snap/nextcloud/46217/htdocs/3rdparty/pear/archive_tar:/snap/nextcloud/46217/htdocs/3rdparty/pear/console_getopt:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear-core-minimal/src:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear_exception:/snap/nextcloud/current/htdocs/apps:/var/snap/nextcloud/current/nextcloud/extra-apps') in /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php:41
Stack trace:
#0 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php(45): {closure}()
#1 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/autoload.php(25): ComposerAutoloaderInitMail::getLoader()
#2 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/composer/autoload.php(5): require_once('...')
#3 /snap/nextcloud/46217/htdocs/lib/private/legacy/OC_App.php(118): require_once('...')
#4 /snap/nextcloud/46217/htdocs/lib/private/AppFramework/Bootstrap/Coordinator.php(76): OC_App::registerAutoloading()
#5 /snap/nextcloud/46217/htdocs/lib/private/AppFramework/Bootstrap/Coordinator.php(48): OC\AppFramework\Bootstrap\Coordinator->registerApps()
#6 /snap/nextcloud/46217/htdocs/lib/base.php(659): OC\AppFramework\Bootstrap\Coordinator->runInitialRegistration()
#7 /snap/nextcloud/46217/htdocs/lib/base.php(1134): OC::init()
#8 /snap/nextcloud/46217/htdocs/console.php(28): require_once('...')
#9 /snap/nextcloud/46217/htdocs/occ(11): require_once('...')
#10 {main}root@raspi-3:/snap/nextcloud

```

Dank für jeden weiterführenden Tip…

---

<div class="post-metadata">

**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\
**Post date:** [January 22, 2025, 8:53pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/2 "2025-01-22T20:53:30Z")

</div>

@lmchp willkommen in der community

nicht verzagen, keine panik

siehe [Nextcloud snap wiki](https://github.com/nextcloud-snap/nextcloud-snap/wiki) vor allem [FAQ’s](https://github.com/nextcloud-snap/nextcloud-snap/wiki/FAQ's) die Lösung deines Problems, erst mal zurück auf die letzte funktionierende instanz See [what to do if an update breaks my Nextcloud](https://github.com/nextcloud-snap/nextcloud-snap/wiki/What-do-I-do-if-an-update-breaks-Nextcloud%3F)

```auto
sudo snap revert nextcloud

```

wir benötigen aber vorher deine logs… dafür ist der [debugging script](https://github.com/nextcloud-snap/nextcloud-snap/wiki/Issue-Debugging-Scripts#debugging-script) ideal. einfach die Ausgabe hierhin posten, siehe [Getting help](https://github.com/nextcloud-snap/nextcloud-snap/wiki/Getting-help)

wenn die snap wieder läuft, mach eine datensicherung siehe [**Backup, restore & migrate**](https://github.com/nextcloud-snap/nextcloud-snap/wiki/Backup-and-Restore)

---

<div class="post-metadata">

**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\
**Post date:** [January 22, 2025, 9:14pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/4 "2025-01-22T21:14:17Z")

</div>

> [@lmchp](#):
>
> ```auto
> An unhandled exception has been thrown:
> Error: Failed opening required '/var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/../symfony/polyfill-iconv/bootstrap.php' (include_path='/snap/nextcloud/46217/htdocs/3rdparty/pear/archive_tar:/snap/nextcloud/46217/htdocs/3rdparty/pear/console_getopt:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear-core-minimal/src:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear_exception:/snap/nextcloud/current/htdocs/apps:/var/snap/nextcloud/current/nextcloud/extra-apps') in /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php:41
> 
> ```

hier gesehen: [Internal server error - mail/composer/autoload.php](https://help.nextcloud.com/t/internal-server-error-mail-composer-autoload-php/177984)

möglicherweise hilft

```auto
sudo nextcloud.occ db:add-missing-indices

```

---

<div class="post-metadata">

**Author:** ![lmchp](https://help.nextcloud.com/letter_avatar/lmchp/32/6_22734026db12803ebb3e059622ac3534.png) [@lmchp](https://help.nextcloud.com/u/lmchp)\
**Post date:** [January 23, 2025, 12:37am UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/5 "2025-01-23T00:37:17Z")

</div>

Hi, danke für’s /Schnelle/…

ja, /last known good/ war rev-45729.  
revert - hatte ich oben schon geschrieben, hatte damit dann die selben Fehler…!

und der Aufruf von nextcloud.occ mit Parametern ändert nichts am Ergebnis - fällt mithin schon vor Auswertung der Parameter auf die Nase:

```auto
> sudo nextcloud.occ db:add-missing-indices
An unhandled exception has been thrown:
Error: Failed opening required '/var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/../symfony/polyfill-iconv/bootstrap.php' (include_path='/snap/nextcloud/46217/htdocs/3r
dparty/pear/archive_tar:/snap/nextcloud/46217/htdocs/3rdparty/pear/console_getopt:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear-core-minimal/src:/snap/nextcloud/46217/htdocs/3rdparty/pe
ar/pear_exception:/snap/nextcloud/current/htdocs/apps:/var/snap/nextcloud/current/nextcloud/extra-apps') in /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_re
al.php:41
Stack trace:
#0 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php(45): {closure}()
#1 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/autoload.php(25): ComposerAutoloaderInitMail::getLoader()
#2 /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/composer/autoload.php(5): require_once('...')
#3 /snap/nextcloud/46217/htdocs/lib/private/legacy/OC_App.php(118): require_once('...')
#4 /snap/nextcloud/46217/htdocs/lib/private/AppFramework/Bootstrap/Coordinator.php(76): OC_App::registerAutoloading()
#5 /snap/nextcloud/46217/htdocs/lib/private/AppFramework/Bootstrap/Coordinator.php(48): OC\AppFramework\Bootstrap\Coordinator->registerApps()
#6 /snap/nextcloud/46217/htdocs/lib/base.php(659): OC\AppFramework\Bootstrap\Coordinator->runInitialRegistration()
#7 /snap/nextcloud/46217/htdocs/lib/base.php(1134): OC::init()
#8 /snap/nextcloud/46217/htdocs/console.php(28): require_once('...')
#9 /snap/nextcloud/46217/htdocs/occ(11): require_once('...')

```

Done:

- erneut /revert’ed/ (auf 45729)
- Debugging script - gab zuviel… hm, kein .txt-upload?
- Na dann so: [https://pastebin.com/NQz6wVh0](https://pastebin.com/NQz6wVh0)

Danke für jede Mühe…

---

<div class="post-metadata">

**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\
**Post date:** [January 23, 2025, 7:14am UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/6 "2025-01-23T07:14:22Z")

</div>

@lmchp

dieser Fehler erscheint immer wieder:

```auto
22T23:10:37+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"require(/var/snap/nextcloud/45729/nextcloud/extra-apps/mail/vendor/composer/../symfony/polyfill-iconv/bootstrap.php): Failed to open stream: No such file or directory at /var/snap/nextcloud/45729/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php#41","userAgent":"--","version":"30.0.2.2","data":{"app":"PHP"}}

```

zusammen mit :

```auto
Error: Failed opening required '/var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/../symfony/polyfill-iconv/bootstrap.php' (include_path='/snap/nextcloud/46217/htdocs/3rdparty/pear/archive_tar:/snap/nextcloud/46217/htdocs/3rdparty/pear/console_getopt:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear-core-minimal/src:/snap/nextcloud/46217/htdocs/3rdparty/pear/pear_exception:/snap/nextcloud/current/htdocs/apps:/var/snap/nextcloud/current/nextcloud/extra-apps') in /var/snap/nextcloud/46217/nextcloud/extra-apps/mail/vendor/composer/autoload_real.php:41

```

und verursacht eine sehr hohe speicherauslastung… der Raspi 3b hat ohnehin ziemlich wenig speicher…

ich tendiere daher zu speicherproblemen, lasse mich jedoch sehr gerne eines besseren belehren.

---

<div class="post-metadata">

**Author:** ![SysKeeper](https://help.nextcloud.com/letter_avatar/syskeeper/32/6_22734026db12803ebb3e059622ac3534.png) [@SysKeeper](https://help.nextcloud.com/u/SysKeeper)\
**Post date:** [January 23, 2025, 7:29am UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/7 "2025-01-23T07:29:31Z")

</div>

> [@scubamuc](#):
>
> `No such file or directory`

Wobei das erst mal so klingt als ob Dateien fehlen? Hast du die Mail App mal manuell installiert oder so?

---

<div class="post-metadata">

**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\
**Post date:** [January 23, 2025, 9:18am UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/8 "2025-01-23T09:18:35Z")

</div>

@lmchp

> [@SysKeeper](#):
>
> Hast du die Mail App mal manuell installiert oder so?

wenn das der fall sein sollte, dann könnte es helfen die app zu deaktivieren siehe [FAQ's · nextcloud-snap/nextcloud-snap Wiki · GitHub](https://github.com/nextcloud-snap/nextcloud-snap/wiki/FAQ's#q-nextcloud-snap-is-not-working-because-of-third-party-app-incompatibility-what-can-i-do)

list apps:  
` sudo nextcloud.occ app:list`

disable app:  
` sudo nextcloud.occ app:disable appname`

remove app:  
` sudo nextcloud.occ app:remove appname`

---

<div class="post-metadata">

**Author:** ![lmchp](https://help.nextcloud.com/letter_avatar/lmchp/32/6_22734026db12803ebb3e059622ac3534.png) [@lmchp](https://help.nextcloud.com/u/lmchp)\
**Post date:** [January 23, 2025, 10:49am UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/9 "2025-01-23T10:49:33Z")

</div>

Re. Speicher:

- die snap nextcloud läuft auf dem Raspi seit 3+Jahren
- es gibt nur 5 (zahme) Clients (4x DavX5+ 1x TB-AddOn), die sehr asynchron  
und nur max. alle 4-6h sync’en…
- auf dem RasPi laufen noch andere Anwendungen, die gelegentlich das System (CPU) auslasten… was die Nutzung der Cloud nie merklich störte…
- insbesondere “Speicher” war noch nie ein Thema…
- das Mail-AddOn hatte ich vor ca. 3-6 Monaten mal testweise “geklickt” und dann “vergessen”; es lief seit dem entsprechend störungsfrei.

Re.: Error…  
Die fehlend bemängelten Dateien existieren schlicht auch nicht.  
Und auch jeder Versuch die Konsole: nextcloud.occ zu verwenden scheitert daran - sie ist also kaputt&dysfunktional.

Also keine Analyse, keine Modifikation auf diesem Weg möglich.

Q:

- wieso fällt die (zentrale) nextcloud.occ auf die Nase wg. eines /Irks/ im AddOn-Setup? Bug oder ist die Fehlermeldung fehl-leitend?
- wie entferne ich händisch/im Dateisystem ein AddOn?

---

<div class="post-metadata">

**Author:** ![lmchp](https://help.nextcloud.com/letter_avatar/lmchp/32/6_22734026db12803ebb3e059622ac3534.png) [@lmchp](https://help.nextcloud.com/u/lmchp)\
**Post date:** [January 23, 2025, 10:52am UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/10 "2025-01-23T10:52:53Z")

</div>

ja, s.o. - die lief so ~6 Monate quasi ungenutzt aber unauffällig/störungsfrei…

ich werde mal testweise dummy-files im system anlegen und schauen wie / was sich verändert…

---

<div class="post-metadata">

**Author:** ![lmchp](https://help.nextcloud.com/letter_avatar/lmchp/32/6_22734026db12803ebb3e059622ac3534.png) [@lmchp](https://help.nextcloud.com/u/lmchp)\
**Post date:** [January 23, 2025, 2:04pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/11 "2025-01-23T14:04:33Z")

</div>

uff.  
Nach etwas Suche in den Quelltexten und try&error Schleifen, hab ich endlich per rename:  
`root@raspi-3: /var/snap/nextcloud/45729/nextcloud/extra-app# mv mail/ .mail/`

was /positives/: Das WebIF gibt wieder “Laut”:

 ![image](https://help.nextcloud.com/uploads/default/original/3X/2/6/26d8d0708d9026bd907de916749a5bef12c1c49e.jpeg)

und die Konsole (nextcloud.occ) arbeitet auch wieder

```auto
nextcloud.occ upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Turned on maintenance mode
Updating database schema
Updated database
Disabled incompatible app: mail
Updating <app_api> ...
Updated <app_api> to 4.0.3
Update app groupfolders from App Store
Restore default tags that are missing

 Done
 1/1 [============================] 100%
Purify and migrate collected mail addresses
 Done
    0/0 [------->--------------------] 0%
Insert background jobs for all accounts
 Done
 1/1 [============================] 100%
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Resetting log level

```

läuft durch.  
Ferner enthält /snap/nextcloud/current/htdocs/3rdparty  
nun, neben dem initial fehlenden “symfony/” auch noch weitere ca. 15 Verzeichnisse, die beim defekten Update Vorgestern wohl ebenfalls ihren Weg nicht ins System gefunden hatten…

Danke!

---

<div class="post-metadata">

**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\
**Post date:** [January 23, 2025, 2:28pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/12 "2025-01-23T14:28:00Z")

</div>

> [@scubamuc](#):
>
> wenn die snap wieder läuft, mach eine datensicherung siehe [**Backup, restore & migrate**](https://github.com/nextcloud-snap/nextcloud-snap/wiki/Backup-and-Restore)

das ist sicher eine sinnvolle Idee?

---

<div class="post-metadata">

**Author:** ![lmchp](https://help.nextcloud.com/letter_avatar/lmchp/32/6_22734026db12803ebb3e059622ac3534.png) [@lmchp](https://help.nextcloud.com/u/lmchp)\
**Post date:** [January 23, 2025, 3:21pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/13 "2025-01-23T15:21:00Z")

</div>

👍 already done …war das Erste nach der Reanimation

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [January 31, 2025, 3:21pm UTC](https://help.nextcloud.com/t/interner-serverfehler-snap-nach-update/215672/14 "2025-01-31T15:21:21Z")

</div>

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.