I've been running Nextcloud in a jail for a while. I recently upgraded the jail to 12.2 but now Mariadb won't start. I don't see any error messages nor any log entries, it just silently fails to start. I've exhausted my knowledge in trying to figure out how to make this work. Any suggestions on getting this thing to work? What am I missing?
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
Mariadb not starting after upgrade
- Thread starter Sparks
- Start date
Basil Hendroff
Wizard
- Joined
- Jan 4, 2014
- Messages
- 1,644
I see this is your first message on the forum. If you want the best possible chance of evoking a response from the community, you need to provide a lot more background information. Have a read of the Forum Rules (front and centre of the header on this page - in red). The section of interest in this instance is Posting to get a Response, but you should spend some time familiarising yourself with the rest of the guidelines as well. Some things to consider adding to this thread:
- What resource did you use to install NC? For example, if you used @danb35's resource Scripted installation of Nextcloud 21 in iocage jail, it may be better to raise the issue in the discussion area for the resource.
- How did you go about upgrading the jail? Did you also upgrade the packages in the jail? If so, did you run the mariadb upgrade script after upgrading the packages?
- What version of NC were you running?
- Anything else you can think of that might be helpful.
- Joined
- Nov 25, 2013
- Messages
- 7,776
There's a file named something.err either in /var/db/mysql or in /var/log/mysql or similar. That's the MariaDB error logfile.
Probably you have a configuration statement in your my.cnf that was deprecated and is now illegal with a new MariaDB version.
Probably you have a configuration statement in your my.cnf that was deprecated and is now illegal with a new MariaDB version.
There is a file named <database>.err in the /var/db/mysql directory but it hasn't been written to since prior to the upgrade so there doesn't appear to be any useful information there. There is also a mysqld.err file in /var/log/mysql that was created after the upgrade but it hasn't been written to (zero bytes).
I originally installed Nextcloud using the community plugin in FreeNAS back in 11.x.
I ran the
pkg upgrade command inside the jail to upgrade the packages as well as the io upgrade command. I did not run the mariadb upgrade script. What's that?Nextcloud version 20.
Basil Hendroff
Wizard
- Joined
- Jan 4, 2014
- Messages
- 1,644
Unfortunately, I don't use plugins so I'm unable to help further. I'll have to pass the baton to someone else. I get the feeling though that plugin jails aren't designed to be upgraded 'under the hood'. If you're still experimenting with NC, the best NC supported resource on the forum is that mentioned in my post above. I'd encourage you to switch to that. My only other thought is to roll back to a previous snapshot if you have one available for the plugin jail.
Last edited:
I've made a little progress here. I looked at the jail JSON file that seems to define the packages that are required for the jail. It appears to require mysql80-server instead of mariadb. So I replaced mariadb with mysql and started getting messages in the .err file.
This is from boot up of the jail. I see the XA crash recovery but I'm not sure what that means or what to do about it.
2021-11-16T05:18:19.6NZ mysqld_safe mysqld restarted
2021-11-16T05:18:19.891665Z 0 [Warning] [MY-011068] [Server] The syntax 'slave_load_tmpdir' is deprecated and will be removed in a future release. Please use replica_load_tmpdir instead.
2021-11-16T05:18:19.891711Z 0 [Warning] [MY-011069] [Server] The syntax '--master-info-repository' is deprecated and will be removed in a future release.
2021-11-16T05:18:19.891736Z 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-repository' is deprecated and will be removed in a future release.
2021-11-16T05:18:19.891786Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-11-16T05:18:19.891913Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2021-11-16T05:18:19.895567Z 0 [System] [MY-010116] [Server] /usr/local/libexec/mysqld (mysqld 8.0.26) starting as process 93481
2021-11-16T05:18:19.983131Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-11-16T05:18:21.443523Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-11-16T05:18:21.905812Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2021-11-16T05:18:21.925498Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2021-11-16T05:18:22.072028Z 0 [Warning] [MY-013746] [Server] A deprecated TLS version TLSv1 is enabled for channel mysql_main
2021-11-16T05:18:22.072711Z 0 [Warning] [MY-013746] [Server] A deprecated TLS version TLSv1.1 is enabled for channel mysql_main
2021-11-16T05:18:22.076009Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-11-16T05:18:22.076833Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2021-11-16T05:18:22.242426Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /tmp/mysqlx.sock
2021-11-16T05:18:22.242706Z 0 [System] [MY-010931] [Server] /usr/local/libexec/mysqld: ready for connections. Version: '8.0.26' socket: '/tmp/mysql.sock' port: 3306 Source distribution.This is from boot up of the jail. I see the XA crash recovery but I'm not sure what that means or what to do about it.
Similar threads
