Hey, I face the same issue and my Pool is now offline. Hopefully it will get fixed soon
Just check for new plugins and then filter out by zfs: you should see a new plugin 7.1.3, this one is done to make it working with the latest zfs.
Posts by AlterX
-
-
Hi thanks, good to know...my pool is already sitting on 2.3.1 without issues and it has always been online. So I guess it is only a minor issue on OMV plugin
-
Hello,
I have updated the underneath system with the new open-zfs 2.3 from the official system distribution and now OMV hid the zfs plugin.
I guess that is only a GUI issue, due to incompatibility with current plugin.
So what are the plan to update the omv plugin to support latest zfs that has a great new functionality in regards of expanding an existing pool with a new HD (attach action)?
Thanks
-
I have problems with continuous reboot of mariadb that prevents photoprism to go up.
Where is the manifest that is used by the photoprism plugin?
-
Hello,
I have the photoprism configured within OMV and it always worked well as expected. Few days ago, after a reboot, it started to start and stop, exposing the port and going down. I tried to use postman to understand a bit more, but I see the mariadb goes up and down. No logs are available because continues up and down, just once I was lucky to get it:
Code
Display More2024-06-21 8:04:22 0 [Note] Starting MariaDB 11.4.2-MariaDB-ubu2404 source revision 3fca5ed772fb75e3e57c507edef2985f8eba5b12 as process 1 2024-06-21 8:04:22 0 [Note] InnoDB: Compressed tables use zlib 1.3 2024-06-21 8:04:22 0 [Note] InnoDB: Number of transaction pools: 1 2024-06-21 8:04:22 0 [Note] InnoDB: Using generic crc32 instructions 2024-06-21 8:04:22 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) 2024-06-21 8:04:22 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95 2024-06-21 8:04:22 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF 2024-06-21 8:04:22 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2024-06-21 8:04:22 0 [Note] InnoDB: Completed initialization of buffer pool 2024-06-21 8:04:22 0 [Note] InnoDB: Buffered log writes (block size=512 bytes) 2024-06-21 8:04:22 0 [Note] InnoDB: End of log at LSN=1674603489 2024-06-21 8:04:22 0 [Note] InnoDB: Opened 3 undo tablespaces 2024-06-21 8:04:22 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active. 2024-06-21 8:04:22 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-06-21 8:04:22 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-06-21 8:04:22 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-06-21 8:04:22 0 [Note] InnoDB: log sequence number 1674603489; transaction id 34929871 2024-06-21 8:04:22 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-06-21 8:04:22 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-06-21 8:04:22 0 [Note] Plugin 'wsrep-provider' is disabled. 2024-06-21 8:04:22 0 [Note] Recovering after a crash using tc.log 2024-06-21 8:04:22 0 [Note] Starting table crash recovery... 2024-06-21 8:04:22 0 [Note] Crash table recovery finished. 2024-06-21 8:04:22 0 [Note] InnoDB: Buffer pool(s) load completed at 240621 8:04:22 2024-06-21 8:04:26 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-06-21 8:04:26 0 [Note] Server socket created on IP: '::'. 2024-06-21 8:04:26 0 [Note] mariadbd: Event Scheduler: Loaded 0 events 2024-06-21 8:04:26 0 [Note] mariadbd: ready for connections. Version: '11.4.2-MariaDB-ubu2404' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distributionUPDATE:
pretty sure this has to do with the changes from oracle to not support old machine. This is what I can see from the running pods:
docker.io/mariadb:latest mariadbd 6 seconds ago stopping 0.0.0.0:6060->2342/tcp photoprism-db ed6199ac9df8 photoprism
I need to specify a compatible verison for mariadb as I did for mysql. How and where I can change the manifest?