Nextcloud fails

Troubleshooting
1

Creating a bug report/issue

G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=7
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘not applicable’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname -a
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
  • Power supply used | (EG: 5V 1A RAVpower)
  • SD card used | Intenso micro sc HC CLASS 10 16GB

Additional Information (if applicable)

  • Software title | Nextcloud
  • Software was fresh installed
  • This issue has replicated on a fresh installation of DietP
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. …Issue returned after a short time of disconnection.
  2. …

Expected behaviour

Nextcloud should continue work after disconnection.

Actual behaviour

Nextcloud does not work after a short time of disconnection.

Extra details

Odroid XU4 is connected to home net, but does not work as nextcloud server.

2

Welcome to our community.

Could you share a little bit more on your issue? Some error messages? At least some hint’s what is not working. At the moment it’s zero information we have on your issue.

3

I installed the new version (bullseye) of dietpi. After a few days was an interruption between my router and the odroid device (name: owncloud). This caused the failing of nextcloud. After a lot of efforts, I gave up and installed the whole system again. Some minutes ago happend the same. Since I had to reset my router again, my nextcloud stop working.
“systemctl restart mariadb.service” worked
systemctl status apache2 shows:

Capache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-08-12 10:46:03 BST; 20min ago
       Docs: https://httpd.apache.org/docs/2.4/
    Process: 539 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
   Main PID: 562 (apache2)
      Tasks: 67 (limit: 4449)
     Memory: 8.4M
        CPU: 567ms
     CGroup: /system.slice/apache2.service
             ├─562 /usr/sbin/apache2 -k start
             └─564 /usr/sbin/apache2 -k start

Aug 12 11:02:36 Owncloud apache2[564]: [proxy:error] [pid 564:tid 2740892704] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.4-fpm.sock (*:80) failed
Aug 12 11:02:36 Owncloud apache2[564]: [proxy_fcgi:error] [pid 564:tid 2740892704] [client 192.168.0.4:55376] AH01079: failed to make connection to backend: httpd-UDS
Aug 12 11:02:58 Owncloud apache2[564]: [proxy:error] [pid 564:tid 2724107296] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.4-fpm.sock (*:80) failed
Aug 12 11:02:58 Owncloud apache2[564]: [proxy_fcgi:error] [pid 564:tid 2724107296] [client 192.168.0.9:37914] AH01079: failed to make connection to backend: httpd-UDS
Aug 12 11:03:38 Owncloud apache2[564]: [proxy:error] [pid 564:tid 2707321888] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.4-fpm.sock (*:80) failed
Aug 12 11:03:38 Owncloud apache2[564]: [proxy_fcgi:error] [pid 564:tid 2707321888] [client 192.168.0.4:33560] AH01079: failed to make connection to backend: httpd-UDS
Aug 12 11:04:40 Owncloud apache2[564]: [proxy:error] [pid 564:tid 2690536480] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.4-fpm.sock (*:80) failed
Aug 12 11:04:40 Owncloud apache2[564]: [proxy_fcgi:error] [pid 564:tid 2690536480] [client 192.168.0.4:50380] AH01079: failed to make connection to backend: httpd-UDS
Aug 12 11:05:42 Owncloud apache2[564]: [proxy:error] [pid 564:tid 2673751072] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.4-fpm.sock (*:80) failed
Aug 12 11:05:42 Owncloud apache2[564]: [proxy_fcgi:error] [pid 564:tid 2673751072] [client 192.168.0.4:44520] AH01079: failed to make connection to backend: httpd-UDS

I hope that I would be very happy to find a solution. My nextcloud server worked many years with no problems using the last version.
Thank you
Wilfried
4

Issue seems to be with PHP module. Can you share following

dietpi-services status
5

Here comes the output of dietpi-services status:

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: status 

[ INFO ] DietPi-Services | redis-server		 inactive (dead)
[  OK  ] DietPi-Services | mariadb		 active (running) since Fri 2022-08-12 11:05:13 BST; 1h 28min ago
[ INFO ] DietPi-Services | php7.4-fpm		 inactive (dead)
[  OK  ] DietPi-Services | apache2		 active (running) since Fri 2022-08-12 10:46:03 BST; 1h 47min ago
[ INFO ] DietPi-Services | cron			 inactive (dead)
[  OK  ] DietPi-Services | ssh			 active (running) since Fri 2022-08-12 10:46:03 BST; 1h 47min ago
[ INFO ] DietPi-Services | dietpi-vpn		 inactive (dead)
[ INFO ] DietPi-Services | dietpi-cloudshell	 inactive (dead)
[  OK  ] DietPi-Services | dietpi-ramlog	 active (exited) since Fri 2022-08-12 10:32:25 BST; 2h 0min ago
[FAILED] DietPi-Services | ● dietpi-preboot.service - DietPi-PreBoot
     Loaded: loaded (/etc/systemd/system/dietpi-preboot.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2022-08-12 10:32:27 BST; 2h 0min ago
    Process: 423 ExecStart=/boot/dietpi/preboot (code=exited, status=2)
   Main PID: 423 (code=exited, status=2)
        CPU: 110ms

Aug 12 10:32:26 Owncloud systemd[1]: Starting DietPi-PreBoot...
Aug 12 10:32:27 Owncloud DietPi-PreBoot[430]: /boot/dietpi/func/dietpi-set_cpu: line 204: syntax error in conditional expression
Aug 12 10:32:27 Owncloud DietPi-PreBoot[430]: [67B blob data]
Aug 12 10:32:27 Owncloud DietPi-PreBoot[430]: [150B blob data]
Aug 12 10:32:27 Owncloud systemd[1]: dietpi-preboot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 12 10:32:27 Owncloud systemd[1]: dietpi-preboot.service: Failed with result 'exit-code'.
Aug 12 10:32:27 Owncloud systemd[1]: Failed to start DietPi-PreBoot.
[ INFO ] DietPi-Services | dietpi-postboot	 inactive (dead)
[ INFO ] DietPi-Services | dietpi-wifi-monitor	 inactive (dead)
6

I don’t hope but it looks like you have some file system issues. At least more services are not running like cron, php or redis.

Can you check for kernel error messages

dmesg -l err,crit,alert,emerg
7 
dmesg -l err,crit,alert,emerg
[    0.016011] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.017385] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.018708] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.020000] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    6.113560] exynos-adc 12d10000.adc: IRQ index 1 not found
[    6.335637] OF: graph: no port node found in /soc/hdmi@14530000
[    6.391385] dwc3 12000000.dwc3: Failed to get clk 'ref': -2
[    6.532565] dwc3 12400000.dwc3: Failed to get clk 'ref': -2
[   14.986954] cgroup2: Unknown parameter 'memory_recursiveprot'
[   17.632111] proc: Bad value for 'hidepid'
[   20.744717] proc: Bad value for 'hidepid'
8

could you try to restart redis

systemctl restart redis-server
journalctl -u redis-server
9

Here is the output:

root@Owncloud:~# systemctl restart redis-server
root@Owncloud:~# journalctl -u redis-server
-- Journal begins at Fri 2022-08-12 17:55:57 BST, ends at Sat 2022-08-13 08:18:55 BST. --
Aug 13 08:18:55 Owncloud systemd[1]: Starting Advanced key-value store...
Aug 13 08:18:55 Owncloud redis-server[672]: 672:C 13 Aug 2022 08:18:55.350 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
Aug 13 08:18:55 Owncloud redis-server[672]: 672:C 13 Aug 2022 08:18:55.351 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 13 08:18:55 Owncloud redis-server[672]: 672:C 13 Aug 2022 08:18:55.351 # Redis version=6.0.16, bits=32, commit=00000000, modified=0, pid=672, just started
Aug 13 08:18:55 Owncloud redis-server[672]: 672:C 13 Aug 2022 08:18:55.351 # Configuration loaded
Aug 13 08:18:55 Owncloud redis-server[672]: WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
Aug 13 08:18:55 Owncloud redis-server[672]: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 13 08:18:55 Owncloud redis-server[672]: Redis version=6.0.16, bits=32, commit=00000000, modified=0, pid=672, just started
Aug 13 08:18:55 Owncloud redis-server[672]: Configuration loaded
Aug 13 08:18:55 Owncloud redis-server[672]: 672:M 13 Aug 2022 08:18:55.358 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
Aug 13 08:18:55 Owncloud redis[672]: Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
Aug 13 08:18:55 Owncloud redis-server[672]: 672:M 13 Aug 2022 08:18:55.367 # Server initialized
Aug 13 08:18:55 Owncloud redis-server[672]: 672:M 13 Aug 2022 08:18:55.368 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Aug 13 08:18:55 Owncloud redis[672]: Server initialized
Aug 13 08:18:55 Owncloud redis[672]: WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Aug 13 08:18:55 Owncloud systemd[1]: Started Advanced key-value store.
10

that looks like redis has been started, can you check

systemctl status redis-server
11 
root@Owncloud:~# systemctl status redis-server
● redis-server.service - Advanced key-value store
     Loaded: loaded (/lib/systemd/system/redis-server.service; disabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: http://redis.io/documentation,
             man:redis-server(1)

B.T.W. I was impatient. So I installed a new version of dietpi on another memory card. The new system is working even when I closed the connection to my router.
I still have the old memory card with the not working system. So we can continue to find out, why it fails, if you want.
Regards
Wilfried

12

Not sure if it would make sense to continue looking in the case. Probably some issues with the SD card or file corruption. Good you solved it while creating a new installation.

13

Okay, so we stop searching at this point. Thank you very much for your help. I would ask for help again, if the issue would return with the new installation.
Bye
Wilfried