Hello, please help. Nextcloud stopped working for me and I can’t get to the files, but if I run dietpi-manager, I can see the hard drive there and it’s not full. When entering dietpi-status, it gives me an error only for Dietpi-vpn. I’ve searched everywhere but I don’t know what exactly is the error to find the right topic. And when I enter the ip in the PC search, it says “You should replace this page with your own web pages as soon as possible”.
DietPi-Services
─────────────────────────────────────────────────────
Mode: status
[ OK ] DietPi-Services | redis-server active (running) since Sat 2023-09-23 15:33:24 BST; 9min ago
[ OK ] DietPi-Services | mariadb active (running) since Sat 2023-09-23 15:33:25 BST; 9min ago
[ OK ] DietPi-Services | php7.4-fpm active (running) since Sat 2023-09-23 15:33:25 BST; 9min ago
[ OK ] DietPi-Services | lighttpd active (running) since Sat 2023-09-23 15:33:26 BST; 9min ago
[ OK ] DietPi-Services | cron active (running) since Sat 2023-09-23 15:33:26 BST; 9min ago
[ OK ] DietPi-Services | dropbear active (running) since Sat 2023-09-23 15:05:29 BST; 37min ago
[FAILED] DietPi-Services | ● dietpi-vpn.service - VPN Client (DietPi)
Loaded: loaded (/etc/systemd/system/dietpi-vpn.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2023-09-23 15:05:29 BST; 37min ago
Main PID: 922 (code=exited, status=203/EXEC)
CPU: 18ms
Sep 23 15:05:29 DietPi systemd[1]: Starting VPN Client (DietPi)...
Sep 23 15:05:29 DietPi systemd[922]: dietpi-vpn.service: Failed to locate executable /usr/sbin/openvpn: No such file or directory
Sep 23 15:05:29 DietPi systemd[922]: dietpi-vpn.service: Failed at step EXEC spawning /usr/sbin/openvpn: No such file or directory
Sep 23 15:05:29 DietPi systemd[1]: dietpi-vpn.service: Main process exited, code=exited, status=203/EXEC
Sep 23 15:05:29 DietPi systemd[1]: dietpi-vpn.service: Failed with result 'exit-code'.
Sep 23 15:05:29 DietPi systemd[1]: Failed to start VPN Client (DietPi).
[ OK ] DietPi-Services | dietpi-cloudshell active (running) since Sat 2023-09-23 15:05:29 BST; 37min ago
[ OK ] DietPi-Services | dietpi-ramlog active (exited) since Sat 2023-09-23 15:05:15 BST; 37min ago
[ OK ] DietPi-Services | dietpi-preboot active (exited) since Sat 2023-09-23 15:05:15 BST; 37min ago
[ OK ] DietPi-Services | dietpi-postboot active (exited) since Sat 2023-09-23 15:05:15 BST; 37min ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead)
DietPi-Services
─────────────────────────────────────────────────────
Mode: command
[FAILED] DietPi-Services | Invalid input command “command”. Aborting…
Usage: dietpi-services [ []]
Available commands:
Interactive menu to apply service modes and settings
status Print service status info
start Start service
stop Stop service
restart Restart service
enable Autostart service on boot
disable Do not autostart service on boot
mask Mask service to prevent its usage entirely
unmask Unmask service to allow its usage
Available services:
<service_name> Apply command to a single available systemd or sysvinit service
Apply command to all available services known to DietPi
- Masked services are skipped unless command is “unmask”.
- Disabled services are skipped if command is “restart”.
- Services required for network or shell sessions are skipped.
- You can include/exclude services by editing the following file:
/boot/dietpi/.dietpi-services_include_exclude
root@DietPi:~# ncc status
- installed: true
- version: 25.0.1.1
- versionstring: 25.0.1
- edition:
- maintenance: false
- needsDbUpgrade: false
- productname: Nextcloud
- extendedSupport: false
Can you share more info about your system please:
Required Information
- DietPi version |
cat /boot/dietpi/.version
- Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
- Kernel version |
uname -a
- Architecture |
dpkg --print-architecture
- SBC model |
echo $G_HW_MODEL_NAME
or (EG: RPi3)- Power supply used | (EG: 5V 1A RAVpower)
- SD card used | (EG: SanDisk ultra)
You can also have a look into the logs, you can find it in the admin settings:
http://<your_IP>/nextcloud/index.php/settings/admin/logging
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=21
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
bullseye 0
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
arm64
-bash: syntax error near unexpected token `(’
power original 5v 1a
SanDisk ultra 32GB
Did you already tried to reboot your system?
can you share following afterwards
dietpi-services status
dmesg -l 0,1,2,3
journalctl -u mariadb
DietPi-Services
─────────────────────────────────────────────────────
Mode: status
[ OK ] DietPi-Services | redis-server active (running) since Fri 2023-09-29 12:01:07 BST; 39s ago
[ OK ] DietPi-Services | mariadb active (running) since Fri 2023-09-29 12:01:27 BST; 19s ago
[ OK ] DietPi-Services | php7.4-fpm active (running) since Fri 2023-09-29 12:01:08 BST; 38s ago
[ OK ] DietPi-Services | lighttpd active (running) since Fri 2023-09-29 12:01:09 BST; 38s ago
[ OK ] DietPi-Services | cron active (running) since Fri 2023-09-29 12:01:09 BST; 38s ago
[ OK ] DietPi-Services | dropbear active (running) since Sat 2023-09-23 15:05:29 BST; 5 days ago
[FAILED] DietPi-Services | ● dietpi-vpn.service - VPN Client (DietPi)
Loaded: loaded (/etc/systemd/system/dietpi-vpn.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2023-09-23 15:05:29 BST; 5 days ago
Main PID: 922 (code=exited, status=203/EXEC)
CPU: 18ms
Warning: journal has been rotated since unit was started, output may be incomplete.
[ OK ] DietPi-Services | dietpi-cloudshell active (running) since Sat 2023-09-23 15:05:29 BST; 5 days ago
[ OK ] DietPi-Services | dietpi-ramlog active (exited) since Sat 2023-09-23 15:05:15 BST; 5 days ago
[ OK ] DietPi-Services | dietpi-preboot active (exited) since Sat 2023-09-23 15:05:15 BST; 5 days ago
[ OK ] DietPi-Services | dietpi-postboot active (exited) since Sat 2023-09-23 15:05:15 BST; 5 days ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead)
Sep 29 11:54:35 DietPi /etc/mysql/debian-start[1119220]: Looking for 'mariadb' as: /usr/bin/mariadb
Sep 29 11:54:35 DietPi /etc/mysql/debian-start[1119220]: Looking for 'mariadb-check' as: /usr/bin/mariadb-check
Sep 29 11:54:35 DietPi /etc/mysql/debian-start[1119220]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
Sep 29 11:54:35 DietPi /etc/mysql/debian-start[1119220]: There is no need to run mysql_upgrade again for 10.5.19-MariaDB.
Sep 29 11:54:35 DietPi /etc/mysql/debian-start[1119220]: You can use --force if you still want to run mysql_upgrade
Sep 29 11:54:35 DietPi /etc/mysql/debian-start[1119228]: Checking for insecure root accounts.
Sep 29 11:54:35 DietPi /etc/mysql/debian-start[1119232]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
Sep 29 12:00:33 DietPi systemd[1]: Stopping MariaDB 10.5.19 database server...
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] Event Scheduler: Purging the queue. 0 events
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] InnoDB: FTS optimize thread exiting.
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] InnoDB: Starting shutdown...
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] InnoDB: Dumping buffer pool(s) to /mnt/cloud/dietpi_userdata/mysql/ib_buffer_pool
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] InnoDB: Restricted to 2016 pages due to innodb_buf_pool_dump_pct=25
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] InnoDB: Buffer pool(s) dump completed at 230929 12:00:33
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] InnoDB: Shutdown completed; log sequence number 5033678985; transaction id 24215468
Sep 29 12:00:33 DietPi mariadbd[1119196]: 2023-09-29 12:00:33 0 [Note] /usr/sbin/mariadbd: Shutdown complete
Sep 29 12:00:33 DietPi systemd[1]: mariadb.service: Succeeded.
Sep 29 12:00:33 DietPi systemd[1]: Stopped MariaDB 10.5.19 database server.
Sep 29 12:00:33 DietPi systemd[1]: mariadb.service: Consumed 3.242s CPU time.
Sep 29 12:01:07 DietPi systemd[1]: Starting MariaDB 10.5.19 database server...
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] Starting MariaDB 10.5.19-MariaDB-0+deb11u2 source revision f8a85af8ca1c937b8d4f847477bd282f80251cde as process 1120978
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Uses event mutexes
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Number of pools: 1
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Using ARMv8 crc32 instructions
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Using Linux native AIO
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Completed initialization of buffer pool
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: 128 rollback segments are active.
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: 10.5.19 started; log sequence number 5033678985; transaction id 24215469
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Loading buffer pool(s) from /mnt/cloud/dietpi_userdata/mysql/ib_buffer_pool
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] Plugin 'FEEDBACK' is disabled.
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] Server socket created on IP: '127.0.0.1'.
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] Reading of all Master_info entries succeeded
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] Added new Master_info '' to hash table
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] /usr/sbin/mariadbd: ready for connections.
Sep 29 12:01:08 DietPi mariadbd[1120978]: Version: '10.5.19-MariaDB-0+deb11u2' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 11
Sep 29 12:01:08 DietPi systemd[1]: Started MariaDB 10.5.19 database server.
Sep 29 12:01:08 DietPi /etc/mysql/debian-start[1121003]: Looking for 'mariadb' as: /usr/bin/mariadb
Sep 29 12:01:08 DietPi /etc/mysql/debian-start[1121003]: Looking for 'mariadb-check' as: /usr/bin/mariadb-check
Sep 29 12:01:08 DietPi /etc/mysql/debian-start[1121003]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
Sep 29 12:01:08 DietPi /etc/mysql/debian-start[1121003]: There is no need to run mysql_upgrade again for 10.5.19-MariaDB.
Sep 29 12:01:08 DietPi /etc/mysql/debian-start[1121003]: You can use --force if you still want to run mysql_upgrade
Sep 29 12:01:08 DietPi mariadbd[1120978]: 2023-09-29 12:01:08 0 [Note] InnoDB: Buffer pool(s) load completed at 230929 12:01:08
Sep 29 12:01:21 DietPi mariadbd[1120978]: 2023-09-29 12:01:21 0x7f944ce100 InnoDB: Assertion failure in file ./storage/innobase/rem/rem0rec.cc line 877
Sep 29 12:01:21 DietPi mariadbd[1120978]: InnoDB: We intentionally generate a memory trap.
Sep 29 12:01:21 DietPi mariadbd[1120978]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
Sep 29 12:01:21 DietPi mariadbd[1120978]: InnoDB: If you get repeated assertion failures or crashes, even
Sep 29 12:01:21 DietPi mariadbd[1120978]: InnoDB: immediately after the mariadbd startup, there may be
Sep 29 12:01:21 DietPi mariadbd[1120978]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Sep 29 12:01:21 DietPi mariadbd[1120978]: InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
Sep 29 12:01:21 DietPi mariadbd[1120978]: InnoDB: about forcing recovery.
Sep 29 12:01:21 DietPi mariadbd[1120978]: 230929 12:01:21 [ERROR] mysqld got signal 6 ;
Sep 29 12:01:21 DietPi mariadbd[1120978]: This could be because you hit a bug. It is also possible that this binary
Sep 29 12:01:21 DietPi mariadbd[1120978]: or one of the libraries it was linked against is corrupt, improperly built,
Sep 29 12:01:21 DietPi mariadbd[1120978]: or misconfigured. This error can also be caused by malfunctioning hardware.
Sep 29 12:01:21 DietPi mariadbd[1120978]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Sep 29 12:01:21 DietPi mariadbd[1120978]: We will try our best to scrape up some info that will hopefully help
Sep 29 12:01:21 DietPi mariadbd[1120978]: diagnose the problem, but since we have already crashed,
Sep 29 12:01:21 DietPi mariadbd[1120978]: something is definitely wrong and this may fail.
Sep 29 12:01:21 DietPi mariadbd[1120978]: Server version: 10.5.19-MariaDB-0+deb11u2 source revision: f8a85af8ca1c937b8d4f847477bd282f80251cde
Sep 29 12:01:21 DietPi mariadbd[1120978]: key_buffer_size=134217728
Sep 29 12:01:21 DietPi mariadbd[1120978]: read_buffer_size=131072
Sep 29 12:01:21 DietPi mariadbd[1120978]: max_used_connections=5
Sep 29 12:01:21 DietPi mariadbd[1120978]: max_threads=153
Sep 29 12:01:21 DietPi mariadbd[1120978]: thread_count=5
Sep 29 12:01:21 DietPi mariadbd[1120978]: It is possible that mysqld could use up to
Sep 29 12:01:21 DietPi mariadbd[1120978]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467887 K bytes of memory
Sep 29 12:01:21 DietPi mariadbd[1120978]: Hope that's ok; if not, decrease some variables in the equation.
Sep 29 12:01:21 DietPi mariadbd[1120978]: Thread pointer: 0x7f44000c68
Sep 29 12:01:21 DietPi mariadbd[1120978]: Attempting backtrace. You can use the following information to find out
Sep 29 12:01:21 DietPi mariadbd[1120978]: where mysqld died. If you see no messages after this, something went
Sep 29 12:01:21 DietPi mariadbd[1120978]: terribly wrong...
Sep 29 12:01:21 DietPi mariadbd[1120978]: stack_bottom = 0x7f944cd868 thread_stack 0x49000
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(my_print_stacktrace)[0x5589bda590]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(handle_fatal_signal)[0x558971d304]
Sep 29 12:01:21 DietPi mariadbd[1121131]: addr2line: 'linux-vdso.so.1': No such file
Sep 29 12:01:21 DietPi mariadbd[1120978]: linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0x7fac23f7a8]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(gsignal)[0x7fab892eac]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(abort)[0x7fab87faa0]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x558946534c]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589a4824c]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589a290f8]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589adb3d0]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589a59910]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589a5d124]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589a5e114]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589a5e78c]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5589a6b974]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55899ca900]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(handler::ha_write_row(unsigned char const*))[0x558972977c]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(write_record(THD*, TABLE*, st_copy_info*, select_result*))[0x558952128c]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(mysql_insert(THD*, TABLE_LIST*, List<Item>&, List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates, bool, select_result*))[0x5589527bfc]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(mysql_execute_command(THD*))[0x5589554ba8]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x55895581e4]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x5589559b48]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(do_command(THD*))[0x558955b7ec]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(do_handle_one_connection(CONNECT*, bool))[0x558962ff38]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(handle_one_connection)[0x5589630194]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x558992e958]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(start_thread)[0x7fabc72648]
Sep 29 12:01:21 DietPi mariadbd[1120978]: ??:0(clone)[0x7fab931c1c]
Sep 29 12:01:21 DietPi mariadbd[1120978]: Trying to get some variables.
Sep 29 12:01:21 DietPi mariadbd[1120978]: Some pointers may be invalid and cause the dump to abort.
Sep 29 12:01:21 DietPi mariadbd[1120978]: Query (0x7f44010520): INSERT INTO `oc_filecache` (`mimepart`, `mimetype`, `mtime`, `size`, `etag`, `storage_mtime`, `permissions`, `name`, `parent`, `checksum`, `path_hash`, `path`, `storage`) VALUES('1', '2', '1695481480', '-1', '6516ae816f68b', '1695481480', '31', 'text', '39', '', 'e505b2b71d73ec572a7d58c816b633db', 'appdata_ock2gwc8lm4h/text', '2')
Sep 29 12:01:21 DietPi mariadbd[1120978]: Connection ID (thread ID): 67
Sep 29 12:01:21 DietPi mariadbd[1120978]: Status: NOT_KILLED
Sep 29 12:01:21 DietPi mariadbd[1120978]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off
Sep 29 12:01:21 DietPi mariadbd[1120978]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
Sep 29 12:01:21 DietPi mariadbd[1120978]: information that should help you find out what is causing the crash.
Sep 29 12:01:21 DietPi mariadbd[1120978]: Writing a core file...
Sep 29 12:01:21 DietPi mariadbd[1120978]: Working directory at /mnt/cloud/dietpi_userdata/mysql
Sep 29 12:01:21 DietPi mariadbd[1120978]: Resource Limits:
Sep 29 12:01:21 DietPi mariadbd[1120978]: Limit Soft Limit Hard Limit Units
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max cpu time unlimited unlimited seconds
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max file size unlimited unlimited bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max data size unlimited unlimited bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max stack size 8388608 unlimited bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max core file size 0 unlimited bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max resident set unlimited unlimited bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max processes 15104 15104 processes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max open files 32768 32768 files
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max locked memory 8388608 8388608 bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max address space unlimited unlimited bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max file locks unlimited unlimited locks
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max pending signals 15104 15104 signals
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max msgqueue size 819200 819200 bytes
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max nice priority 0 0
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max realtime priority 0 0
Sep 29 12:01:21 DietPi mariadbd[1120978]: Max realtime timeout unlimited unlimited us
Sep 29 12:01:21 DietPi mariadbd[1120978]: Core pattern: core
Sep 29 12:01:21 DietPi mariadbd[1120978]: Kernel version: Linux version 6.1.21-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023
Sep 29 12:01:21 DietPi systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
Sep 29 12:01:21 DietPi systemd[1]: mariadb.service: Failed with result 'signal'.
Sep 29 12:01:21 DietPi systemd[1]: mariadb.service: Consumed 2.046s CPU time.
Sep 29 12:01:26 DietPi systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 1.
Sep 29 12:01:26 DietPi systemd[1]: Stopped MariaDB 10.5.19 database server.
Sep 29 12:01:26 DietPi systemd[1]: mariadb.service: Consumed 2.046s CPU time.
Sep 29 12:01:26 DietPi systemd[1]: Starting MariaDB 10.5.19 database server...
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] Starting MariaDB 10.5.19-MariaDB-0+deb11u2 source revision f8a85af8ca1c937b8d4f847477bd282f80251cde as process 1121192
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Uses event mutexes
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Number of pools: 1
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Using ARMv8 crc32 instructions
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Using Linux native AIO
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Completed initialization of buffer pool
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=5033678985,5033678985
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Starting final batch to recover 2 pages from redo log.
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: 128 rollback segments are active.
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: 10.5.19 started; log sequence number 5033679474; transaction id 24215476
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] InnoDB: Loading buffer pool(s) from /mnt/cloud/dietpi_userdata/mysql/ib_buffer_pool
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] Plugin 'FEEDBACK' is disabled.
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] Server socket created on IP: '127.0.0.1'.
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] Reading of all Master_info entries succeeded
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] Added new Master_info '' to hash table
Sep 29 12:01:27 DietPi mariadbd[1121192]: 2023-09-29 12:01:27 0 [Note] /usr/sbin/mariadbd: ready for connections.
Sep 29 12:01:27 DietPi mariadbd[1121192]: Version: '10.5.19-MariaDB-0+deb11u2' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 11
Sep 29 12:01:27 DietPi systemd[1]: Started MariaDB 10.5.19 database server.
Sep 29 12:01:27 DietPi /etc/mysql/debian-start[1121217]: Upgrading MySQL tables if necessary.
Sep 29 12:01:28 DietPi mariadbd[1121192]: 2023-09-29 12:01:28 0 [Note] InnoDB: Buffer pool(s) load completed at 230929 12:01:28
Sep 29 12:01:28 DietPi /etc/mysql/debian-start[1121220]: Looking for 'mariadb' as: /usr/bin/mariadb
Sep 29 12:01:28 DietPi /etc/mysql/debian-start[1121220]: Looking for 'mariadb-check' as: /usr/bin/mariadb-check
Sep 29 12:01:28 DietPi /etc/mysql/debian-start[1121220]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
Sep 29 12:01:28 DietPi /etc/mysql/debian-start[1121220]: There is no need to run mysql_upgrade again for 10.5.19-MariaDB.
Sep 29 12:01:28 DietPi /etc/mysql/debian-start[1121220]: You can use --force if you still want to run mysql_upgrade
Sep 29 12:01:28 DietPi /etc/mysql/debian-start[1121228]: Checking for insecure root accounts.
I restarted the system several times and it didn’t help.
dmesg -l 0,1,2,3 and it won’t tell me anything about this.
are you sure MariaDB log was created right after a reboot? Because I see a couple of database restarts over half a day.
I will post again after the reboot.
DietPi-Services
─────────────────────────────────────────────────────
Mode: status
[ OK ] DietPi-Services | redis-server active (running) since Sun 2023-10-01 07:57:10 BST; 18s ago
[ OK ] DietPi-Services | mariadb active (running) since Sun 2023-10-01 07:57:11 BST; 18s ago
[ OK ] DietPi-Services | php7.4-fpm active (running) since Sun 2023-10-01 07:57:12 BST; 17s ago
[ OK ] DietPi-Services | lighttpd active (running) since Sun 2023-10-01 07:57:12 BST; 16s ago
[ OK ] DietPi-Services | cron active (running) since Sun 2023-10-01 07:57:11 BST; 18s ago
[ OK ] DietPi-Services | dropbear active (running) since Sun 2023-10-01 07:57:09 BST; 19s ago
[FAILED] DietPi-Services | ● dietpi-vpn.service - VPN Client (DietPi)
Loaded: loaded (/etc/systemd/system/dietpi-vpn.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-10-01 07:57:09 BST; 19s ago
Process: 455 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config /etc/openvpn/client.ovpn (code=exited, status=203/EXEC)
Main PID: 455 (code=exited, status=203/EXEC)
CPU: 22ms
Oct 01 07:57:09 DietPi systemd[1]: Starting VPN Client (DietPi)...
Oct 01 07:57:09 DietPi systemd[455]: dietpi-vpn.service: Failed to locate executable /usr/sbin/openvpn: No such file or directory
Oct 01 07:57:09 DietPi systemd[455]: dietpi-vpn.service: Failed at step EXEC spawning /usr/sbin/openvpn: No such file or directory
Oct 01 07:57:09 DietPi systemd[1]: dietpi-vpn.service: Main process exited, code=exited, status=203/EXEC
Oct 01 07:57:09 DietPi systemd[1]: dietpi-vpn.service: Failed with result 'exit-code'.
Oct 01 07:57:09 DietPi systemd[1]: Failed to start VPN Client (DietPi).
[ OK ] DietPi-Services | dietpi-cloudshell active (running) since Sun 2023-10-01 07:57:09 BST; 20s ago
[ OK ] DietPi-Services | dietpi-ramlog active (exited) since Sun 2023-10-01 07:57:09 BST; 20s ago
[ OK ] DietPi-Services | dietpi-preboot active (exited) since Sun 2023-10-01 07:57:09 BST; 19s ago
[ OK ] DietPi-Services | dietpi-postboot active (exited) since Sun 2023-10-01 07:57:09 BST; 19s ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead)
[ 0.597732] bcm2708_fb soc:fb: Unable to determine number of FBs. Disabling driver.
root@DietPi:~# journalctl -u mariadb
-- Journal begins at Sun 2023-10-01 07:57:08 BST, ends at Sun 2023-10-01 07:57:54 BST. --
Oct 01 07:57:09 DietPi systemd[1]: Starting MariaDB 10.5.19 database server...
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] Starting MariaDB 10.5.19-MariaDB-0+deb11u2 source revision f8a85af8ca1c937b8d4f847477bd282f80251cde as process 511
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] InnoDB: Uses event mutexes
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] InnoDB: Number of pools: 1
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] InnoDB: Using ARMv8 crc32 instructions
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] InnoDB: Using Linux native AIO
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
Oct 01 07:57:10 DietPi mariadbd[511]: 2023-10-01 7:57:10 0 [Note] InnoDB: Completed initialization of buffer pool
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] InnoDB: 128 rollback segments are active.
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] InnoDB: 10.5.19 started; log sequence number 5060786532; transaction id 24353041
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] InnoDB: Loading buffer pool(s) from /mnt/cloud/dietpi_userdata/mysql/ib_buffer_pool
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] Plugin 'FEEDBACK' is disabled.
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] Server socket created on IP: '127.0.0.1'.
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] Reading of all Master_info entries succeeded
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] Added new Master_info '' to hash table
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] /usr/sbin/mariadbd: ready for connections.
Oct 01 07:57:11 DietPi mariadbd[511]: Version: '10.5.19-MariaDB-0+deb11u2' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 11
Oct 01 07:57:11 DietPi systemd[1]: Started MariaDB 10.5.19 database server.
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[535]: Upgrading MySQL tables if necessary.
Oct 01 07:57:11 DietPi mariadbd[511]: 2023-10-01 7:57:11 0 [Note] InnoDB: Buffer pool(s) load completed at 231001 7:57:11
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[539]: Looking for 'mariadb' as: /usr/bin/mariadb
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[539]: Looking for 'mariadb-check' as: /usr/bin/mariadb-check
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[539]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[539]: There is no need to run mysql_upgrade again for 10.5.19-MariaDB.
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[539]: You can use --force if you still want to run mysql_upgrade
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[550]: Checking for insecure root accounts.
Oct 01 07:57:11 DietPi /etc/mysql/debian-start[554]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
ok let’s fix the first issue with dietpi-vpn
. Are you till using this VPN function to connect from your DietPi system to a public VPN provider?
For Nextcloud. You are able to login and navigate inside Nextcloud? But you are not able to open files? Do you see the files still within Nextcloud interface?
yes i can see the files but i can’t open them it says error “this file can’t be opened please contact admin” and i dont use vpn.