it seems that this cron bug might not be root cause for missing or wrong rights, if i activate notify_push on app, it show same erros ( 30 times cron failure ) but it activates it https://paste.yunohost.org/raw/utubuyutiz
still i am on arm and not on x86
The following apps are not (yet?) compatible with Nextcloud 35. You should make sure to upgrade the app, or disable it, or wait for it to become compatible before running this upgrade : occweb_v2
pwa_suite
You can retry the upgrade after updating or disabling those two apps.
I have some apps that are not compatible with NC 35, this is not the first time this has happened.
But what surprised me was that message I didn’t have before
notifications:
35.0.0~ynh1: If you are upgrading to a **new major version** of Nextcloud (e.g. 34, 35), **please make sure that your Nextcloud apps are up to date** from Nextcloud's administration panel beforehand.
Additionally, if you installed **specific Nextcloud apps**, we recommend **making sure that they are compatible with the new major version**.
YunoHost will attempt to check this automatically at the very beginning of the upgrade, but a manual check doesn't hurt either. See https://apps.nextcloud.com/apps/<app_name>
* **Incompatible apps will cause the upgrade to fail.**
* Also make sure the **sury repo signing key** is up to date (run `sudo apt update` and check the output. If needed, this thread may help to renew this key : <https://forum.yunohost.org/t/yarn-and-sury-apt-keys-issues/41617>
I understand this warning, but surprised to see it for the first time.
So, once the update is done, there is this info that I need to edit in a file my.cnf :
I searched and did not find this file, except those files: /etc/mysql/conf.d/mysql.cnf, my.cnf -> /etc/alternatives/my.cnf, /etc/mysql/my.cnf
nano /etc/mysql/conf.d/mysql.cnf
file content:
[mysqld]
nano /etc/mysql/my.cnf
file content:
# The MariaDB configuration file
#
# The MariaDB/MySQL tools read configuration files in the following order:
# 0. "/etc/mysql/my.cnf" symlinks to this file, reason why all the rest is read.
# 1. "/etc/mysql/mariadb.cnf" (this file) to set global defaults,
# 2. "/etc/mysql/conf.d/*.cnf" to set global options.
# 3. "/etc/mysql/mariadb.conf.d/*.cnf" to set MariaDB-only options.
# 4. "~/.my.cnf" to set user-specific options.
#
# If the same option is defined multiple times, the last one will apply.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# If you are new to MariaDB, check out https://mariadb.com/kb/en/basic-mariadb-articles/
#
# This group is read both by the client and the server
# use it for options that affect everything
#
[client-server]
# Port or socket location where to connect
# port = xxxx
socket = /run/mysqld/mysqld.sock
# Import all .cnf files from configuration directory
!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mariadb.conf.d/
Unfortunately, it doesn’t change anything, it tells me it failed.
I also have the same problem I found on GitHub:
And this comment: Unfortunately, Nextcloud's management has shifted very strongly toward “enterprise marketing” in recent years. They are determined to prove that they can keep up with the tech giants in terms of functionality, and in doing so, they often forget their core target audience: the admins who keep the system running.
Is that the cause of the problems?
So I deleted NC 35 and restored the previous version.
I am currently testing Sync-In and have been able to synchronize OnlyOffice with it, but I think that a next update will remove the sync.
It is this file: environment.yaml which allows synchronization and can be found in /var/www/sync-in.
I was thinking of finding this file in /home/younohost.app/sync-in, but no.
