I've got space problem!

[cr9cA]

Bonjour,

Je n’ai plus accès à nextcloud dont je ne suis pas sur de la version, mais c’est l’avant dernière.
Je suis sur un serveur DEBIAN chez OVH.

J’ai voulu faire la mise à jour hier et elle a bloquée à la création de l’update (ou quelque chose comme cela)

J’ai maintenant le message

“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.”

lorsque j’essaie de me connecter sur mon nextcloud.

J’ai pensé à un pb d’espace sur le serveur alors je suis passé de 80 Go à 160 Go.
J’ai fait une mise à jour DEBIAN sur mon serveur OVH via le terminal, j’ai rebooté et j’ai toujours le même message “internal server error”.

Comment puis je procéder pour m’en sortir.
Merci bien par avance.

[cr9cA]

Hello,

I can no longer access Nextcloud—I’m not sure which version it is, but it’s the second-to-last one.
I’m on a Debian server hosted by OVH.

I tried to update it yesterday, and it got stuck while creating the update (or something like that).

I’m now getting the message

“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.”

When I try to log in to my Nextcloud.

I thought it might be a server space issue, so I upgraded from 80 GB to 160 GB.
I ran a Debian update on my OVH server via the terminal, rebooted, but I’m still getting the same “internal server error” message.

How can I fix this?
Thanks in advance.

[jtr]

@cr9cA

Internal Server Error

This is a generic message.

You need to follow the advice in the support template you removed, which suggests how/where to find various logs.

Also, see the Admin Manual, such as here:

Internal Server Errors - General troubleshooting — Nextcloud 34 Administration...

[cr9cA]

I never removed anything.
So I don’t understand at all what about the support you speak.

My real probleme is to use the space I’ve got know.

Before I had 80Go and it’s blocked the server, now I’ve got 160 Go … how can I use them ?

[vincen]

Salut

Il manque pas mal d’informations pour t’aider mais tu as tenté la mise à jour via le panneau admin de nc ou avec occ ? Si c’est avec le panneau d’admin, il faut la relancer via occ en ligne de commande et il devrait arriver normalement à te remettre ça d’aplomb
La mise à jour Debian c’est loin d’être une bonne idée quand quelque chose est déja cassé ! C’était une mise à jour mineure de paquets je suppose ?
As-tu regardé les logs de ton serveur web (apache, nginx ou autre) et les logs de NC ?

[wwe]

please do not double post! this causes additional useless work for people helping you.
I moved your frech post into english one.

[bb77]

@cr9cA

I thought it might be a server space issue, so I upgraded from 80 GB to 160 GB.
I ran a Debian update on my OVH server via the terminal, rebooted, but I’m still getting the same “internal server error” message.

See my answer here regarding repartitioning after a storage upgrade: Partitionning vps - #2 by bb77.

I suggest you try that and, if you still get the error afterwards, let’s continue the discussion here. However, we would then definitely need more information about your setup to be able to help.

And I’ll say it again here. Make sure you have a backup and/or snapshot of your VPS before you try anything!

[tflidd]

@cr9cA

More details can be found in the server log.”

This is the most important, check your webserver’s error log (/var/log/nginx or /var/log/apache2).
And in you /data folder, there is also a updater.log

what might be interesting is the version number in the version.php in the main folder, and the version in the config/config.php.

@cr9cA

Before I had 80Go and it’s blocked the server, now I’ve got 160 Go … how can I use them ?

The missing space was a guess. So it is not sure if that was the issue, and even if it was it perhaps created some problems in the database. But without log files, this is just guessing.

[bb77]

@tflidd

The missing space was a guess. So it is not sure if that was the issue, and even if it was it perhaps created some problems in the database. But without log files, this is just guessing.

Yep.

@cr9cA Basically, you have two issues here:

1. Your disk might be full, which may or may not have caused the update to fail or become interrupted, ultimately resulting in the internal server error.

2. You extended your disk at OVH. According to their documentation, you also need to manually expand the partition so that the operating system can actually use the additional space.

Regarding (1): First, check whether your disk is actually full. Open a terminal, run:

df -h

and post the output here if you’re unsure how to interpret it.

Regarding (2): As far as I understand it, you’ll need to do this anyway if you want to make use of the additional disk space you purchased, regardless of whether it’s the cause of the internal server error. So you might as well do it now.

Here’s the OVH guide again:

Repartitioning a VPS after a storage upgrade - OVHcloud Documentation

Once that’s done, we can look into getting Nextcloud up and running again, assuming the internal server error persists, which it probably will if the update was interrupted.

But again, back up your data and if posible create a snapshot or a backup of the entire VM beforehand.

[cr9cA]

If I see the result of

> df -h

> Filesystem      Size  Used Avail Use% Mounted on
> udev            1.9G     0  1.9G   0% /dev
> tmpfs           383M  500K  383M   1% /run
> /dev/sda1       158G   76G   76G  50% /
> tmpfs           1.9G     0  1.9G   0% /dev/shm
> tmpfs           5.0M     0  5.0M   0% /run/lock
> tmpfs           1.9G     0  1.9G   0% /tmp
> tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
> tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
> /dev/sda15      124M  8.9M  115M   8% /boot/efi
> tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-networkd.service
> tmpfs           1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
> tmpfs           1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyS0.service
> tmpfs           383M  8.0K  383M   1% /run/user/1000

I do not have to partitionning my partition since it’s already mount on /dev/sda1

What do you think ?

[bb77]

@cr9cA

/dev/sda1 158G 76G 76G 50% /

Yeah, it actually looks like that happened automatically. I have no idea why the OVH documentation says you have to do it manually then. Just to be sure, you could also run:

lsblk

Oh, and by the way: you can also see that the filesystem is now 50% full, which suggests it was indeed completely full before.

If Nextcloud is still showing the internal server error, the first thing I’d try is running the updater from the command line again: Upgrade via built-in updater — Nextcloud 34 Administration Manual

Depending on which step the update was interrupted at, you might get lucky and it will simply complete successfully this time. If not, it should hopefully print an error message that points to the underlying problem or at least tells you what to do next.

If you’re unsure what the output means, post it here. Also have a look at @tflidd’s post, the updater.log may provide additional clues as well.

[cr9cA]

@bb77

Many thanks for all your tips I’ll try tommorrow.

[cr9cA]

@bb77 Hi,

I succeed thanks to the restauration of my “OVH” space and my last SNAPSHOT

Many thanks anyway and enjoy your sunday.