- /tmp/elabftwmysql:/var/lib/mysql
do your docker images also exist on a zfs volume? not sure if that matters tbh.
/var/lib/docker/ iirc
And I'm running into a similar error
/var/lib/ is on an ext4 volume
the only thing on
datastore (which is my only ZFS volume) is the stuff that elabctl puts there when it reads the elabctl.conf
I tried
elabctl uninstall followed by elabctl install with the default values, which point to an ext4 volume, and have the same error
I'm going to try removing
zfsutils-linux and see if the issue persists
2022-07-12 19:13:51+02:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1.el8 started.
2022-07-12 19:13:51+02:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-07-12 19:13:51+02:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1.el8 started.
2022-07-12 19:13:52+02:00 [Note] [Entrypoint]: Initializing database files
2022-07-12T17:13:52.042553Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use au thentication_policy instead.
2022-07-12T17:13:52.042567Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.29) initializing of server in progress as process 42
2022-07-12T17:13:52.054078Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-07-12T17:13:53.238893Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-07-12T17:13:56.404692Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-in secure option.
2022-07-12 19:14:02+02:00 [Note] [Entrypoint]: Database files initialized
2022-07-12 19:14:02+02:00 [Note] [Entrypoint]: Starting temporary server
2022-07-12T17:14:02.872144Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use au thentication_policy instead.
2022-07-12T17:14:02.872163Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 91
2022-07-12T17:14:02.890474Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-07-12T17:14:03.087866Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-07-12T17:14:03.441798Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-07-12T17:14:03.441865Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channe l.
2022-07-12T17:14:03.480641Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: /var/run/mysqld/mysqlx.sock
2022-07-12T17:14:03.480764Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.29' socket: '/var/run/mysqld/mysqld.sock' po rt: 0 MySQL Community Server - GPL.
2022-07-12 19:14:03+02:00 [Note] [Entrypoint]: Temporary server started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leapseconds' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/tzdata.zi' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone1970.tab' as time zone. Skipping it.
2022-07-12 19:14:05+02:00 [Note] [Entrypoint]: Creating database elabftw
2022-07-12 19:14:05+02:00 [Note] [Entrypoint]: Creating user elabftw
2022-07-12 19:14:05+02:00 [Note] [Entrypoint]: Giving user elabftw access to schema elabftw
2022-07-12 19:14:05+02:00 [Note] [Entrypoint]: Stopping temporary server
2022-07-12T17:14:05.792537Z 13 [System] [MY-013172] [Server] Received SHUTDOWN from user root. Shutting down mysqld (Version: 8.0.29).
2022-07-12T17:14:08.130313Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.29) MySQL Community Server - GPL.
2022-07-12 19:14:08+02:00 [Note] [Entrypoint]: Temporary server stopped
2022-07-12 19:14:08+02:00 [Note] [Entrypoint]: MySQL init process done. Ready for start up.
2022-07-12T17:14:09.053252Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use au thentication_policy instead.
2022-07-12T17:14:09.053270Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 1
2022-07-12T17:14:09.060015Z 1 [System] [MY-013576]
_ _ _____ _______ __
___| | __ _| |__ | ___|_ _\ \ / /
/ _ \ | / _| | '_ \| |_ | | \ \ /\ / /
| __/ |__| (_| | |_) | _| | | \ V V /
\___|_____\__,_|_.__/|_| |_| \_/\_/
Using elabctl configuration file: using default values (no config file found)
Using elabftw configuration file: /etc/elabftw.yml
---------------------------------------------
Name Command State Ports
----------------------------------------------------------------------------------------------
elabftw /init Up (healthy) 0.0.0.0:443->443/tcp,:::443->443/tcp
mysql docker-entrypoint.sh --def ... Up 3306/tcp, 33060/tcp
I retried the installation with
zfsutils-linux installed and it was successful again, using the default data locations
I'm not certain how to proceed from here though. I like using ZFS because of the redundancy, and expanding a
zpool is trivial
because this is does affect mysql on zfs I would assume it will get pushed quickly for ubuntu
Hi. I tried to update to the most current version, but I get an error about incorrect time format that is not covered by any Github issue etc. as far as I have found. The db:update command throws the following error: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0
000-00-00 00:00:00' for column 'datetime' at row 1
000-00-00 00:00:00' for column 'datetime' at row 1
Is there a way to roll back to a previous version?
also if you want support please open a proper github issue with all information so it's easier to debug
Okay, I tried again and this time everything worked fine. Again, I followed the instructions you linked, only this time I did not do "After, manually run the last lines of schema71:". Thats the only thing I did differently really. In any case, happy it worked and thank you for the troubleshooting guide.
I'm just trying to set up a elabftw instance on a Kubuntu VM to test the utf8 stuff prior to the update to 4.3.x. Did
services.web.depends_on contains an invalid type, it should be an array" with the last command. What is wrong?
elabctl install and elabctl start but all I get is "ERROR: The Compose file '/etc/elabftw.yml' is invalid because:services.web.depends_on contains an invalid type, it should be an array" with the last command. What is wrong?
@HClO4 you are asking what is wrong but you are not showing that part of your config file! So it's hard to say. Does it look exactly like this? https://github.com/elabftw/elabimg/blob/1338801d49fdd3c4ac8e71f58cc5b64b04799235/src/docker-compose.yml-EXAMPLE#L26-L28 If yes, upgrade your docker-compose version.
4 replies
Hello everyone! I don't know if anyone here is using LabVIEW, but just in case I've made a LabVIEW client library for eLabFTW using API v1 documentation and testing it on https://demo.elabftw.net.