3,054
edits
Changes
Jump to navigation
Jump to search
mLine 13:
Line 13: − + Line 23:
Line 23: − + Line 45:
Line 45: − + Line 66:
Line 66: + + + − === Upgrade ===+ − yum update {{#var:smecontribname}} {{#var:contribname}} smeserver-php-fpm smeserver-webapps-common --enablerepo=smecontribs,epel,fws + + + + + + + + + + + + + + + + + + + + + Line 83:
Line 106: − + − + + + + + + Line 113:
Line 141: − + Line 133:
Line 161: − + + + + + + Line 149:
Line 182: + + + + + + + + + + + + + + + Line 155:
Line 203: − + Line 161:
Line 209: + + + − OCC maintenance:mode --off+ − OCC maintenance:repair+ − + − + − + + + + + + + + + + + + − === Use a dedicated domain to connect to Nextcloud ===+ − db domains set cloud.mydomain.com domain Description "Nextcloud" Content Primary Nameservers internet TemplatePath WebAppVirtualHost DocumentRoot /usr/share/nextcloud RequireSSL enabled letsencryptSSLcert enabled+ − signal-event domain-create cloud.mydomain.com+ + + + + + + − #this one to let nextcloud DAV be redirect correctly+ − + − signal-event nextcloud-update+ + − #only if you use a Let's Encrypt certificate+ − expand-template /etc/dehydrated/domains.txt − dehydrated -c − </syntaxhighlight>+ − === Move user space from uuid to username ===+ − User stored using ldap from SME with initial install will create a space with their ldap uuid. This is not very user friendly and further more it will lead to ios app issues.+ − Recent version will use the username for new users, but for those already created you will need to do the following+ − you will need to do as admin : − − # choose ldap − # choose expert − # fill the 3 fields as presented above, or using the cli do − OCC ldap:set-config s01 ldapExpertUUIDGroupAttr cn − OCC ldap:set-config s01 ldapExpertUUIDUserAttr uid − OCC ldap:set-config s01 ldapExpertUsernameAttr uid − # in cli, you will then need to do : − OCC user:list and save the content − cd /home/e-smith/files/nextcloud/data ; mv OLDUUID username − OCC files:scan username − # delete the UUID association for users − # you should then be able to login as the user with its previous files − Only drawback, trash history might be gone, a trick inside the db using a script could workaround that and avoid the OCC files:scan username+ + + − === Mount with davfs on Fedora Clients ===+ − While you might love the easy setup of the gnome client for nextcloud, you might encounter some frustration of having your favourite applications not showing nextcloud as mounted and needing to find it to sometime not being able to access it. − Here is a workaround+ − First as root<syntaxhighlight lang="bash">+ − dnf install davfs2 -y − usermod -aG davfs2 $YOURUSER − echo "use_locks 0" >> /etc/davfs2/davfs2.conf − echo "https://example.com/nextcloud/remote.php/webdav /home/$YOURUSER/nextcloud davfs user,rw,auto 0 0 − " >> /etc/fstab + − </syntaxhighlight>then you should log out /log in with your user in order to have the group membership. You can also just do "su -l USERNAME"+ + + + + + + + + + + + + − then as your user (replace your_password by your password, or a token;):<syntaxhighlight lang="bash">+ − mkdir ~/nextcloud − mkdir ~/.davfs2 − echo "https://example.com/nextcloud/remote.php/webdav your_Nextcloud_username your_password" >> ~/.davfs2/secrets − chmod 0600 ~/.davfs2/secrets − </syntaxhighlight>then just mount ! <syntaxhighlight lang="bash"> − mount ~/nextcloud − </syntaxhighlight> − From there you can tweak the cache configuration to make it easier for you if you are far from the server, default cache size is 50MiByte, you could increase it to let's say 3 GiByte in ~/.davfs2/davfs2.conf for your user <syntaxhighlight lang="bash">+ − cache_size 3G+ − </syntaxhighlight>you should see the folder mount at every logon from now on! if you do not want that, change "auto" in the fstab by "noauto". − Then add the following in ~/bash_profile or ~/bash_rc. You could user also mount -a and to try to put something in /etc/gdm/PostLogin/" instead<syntaxhighlight lang="bash">+ − mount /home/username/nextcloud+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + − if [ ${USERNAME} = "myuser" ];then+ − umount -fl /home/myuser/nextcloud+ − fi+ + + + + + + + + + + − Adapted from those sources:+ − * http://www.tuxfixer.com/mount-webdav-remote-storage-in-fedora-linux-via-davfs2/ − * https://docs.nextcloud.com/server/13/user_manual/files/access_webdav.html − + − ==== failure to do online upgrade from 13.0.2 ====+ − The following extra files have been found: assets − cd /usr/share/nextcloud/ − rm -rf assets − yum update smeserver-nextcloud --enablerepo=smecontribs − + − + − Nextcloud is only build to upgrade from one major release to the next. If you try to install the nextcloud-15 rpm while you already have installed the nextcloud-13, you might have encounter the following issue. + − + − '''“Updates between multiple major versions are unsupported”'''+ − + − <tt>goto usr/share/nextcloud</tt>+ − + − copy everything except <tt>/data</tt> and <tt>/config</tt> to temp folder+ − + − download intermediate version of '''nextcloud''' from <nowiki>https://nextcloud.com/changelog/</nowiki>+ − − unzip and copy files to /usr/share/nextcloud, dont overwrite /data or /config − − change ownership in /usr/share/nextcloud chown -R apache:www . − − goto <nowiki>https://yoururl/nextcloud</nowiki> and run the updater − − logon to nextcloud and make sure it is all working as expected − − repeat above for each major update until you are one update from the latest major update. At that point you can follow the usual process. source (https://bugs.contribs.org/show_bug.cgi?id=10670#c3) − − ==== Upgrading from 17.0.1.x to 17.07.x ==== − You can use the built in updater.+ − The only issue experienced was right at the end of the process with a http 500 error. I just did 'retry' and it completed.+ + + − You may need to update your database which I did as follows - note it may take a very long time with a lot of files:+ − − OCC maintenance:mode --on − OCC db:convert-filecache-bigint − OCC maintenance:mode --off Line 313:
Line 440: − + − For reference, whilst looking at resetting file caches I found this.+ + + − It is probably extremely dangerous but wanted to make a note.+ − https://github.com/nextcloud/server/issues/8113#issuecomment-565876798+ − + + + − We are still building Koozali SME v10 and have been testing installation of Nextcloud, currently on version 20.+ − We have packages in smedev.+ − You will also need packages from some other repos.+ + Line 345:
Line 477: + + + + + + +
→Remove legacy nextcloud rpm without deleting /usr/share/nextcloud content
|licence= AGPLv3
|licence= AGPLv3
|url= https://nextcloud.com
|url= https://nextcloud.com
|category= Contrib
|category= Cloud
|tags=cloud,files,dropbox,seafile,pydio,ajaxplorer,owncloud
|tags=cloud,files,dropbox,seafile,pydio,ajaxplorer,owncloud
}}
}}
<!-- keep this first element as is, you can add some if needed -->
<!-- keep this first element as is, you can add some if needed -->
{{#smeversion: {{#var:smecontribname}} }}
{{#smeversion: {{#var:smecontribname}} }}
{{#smeversion: {{#var:contribname}} }}
{{#smeversion: nextcloud-src }}
=== Description ===
=== Description ===
</tab>
</tab>
<tab name="For sme9">
<tab name="For sme9">
You do not need to follow the Repo pages of [https://wiki.contribs.org/Fws fws] and [https://wiki.contribs.org/Remi-safe remi-safe] to isntall those two needed repos, instead use the packages to install them followed by a yum-modify event. Then run the main installation.
You do not need to follow the Repo pages of [https://wiki.contribs.org/Fws fws] and [https://wiki.contribs.org/Remi-safe remi-safe] to install those two needed repos, instead use the packages to install them followed by a yum-modify event. Then run the main installation.
yum install smeserver-extrarepositories-remi-safe smeserver-extrarepositories-fws smeserver-extrarepositories-epel
yum install smeserver-extrarepositories-remi-safe smeserver-extrarepositories-fws smeserver-extrarepositories-epel
signal-event yum-modify
signal-event yum-modify
then
then
signal-event nextcloud-update
signal-event nextcloud-update
if you want to add SME user admin as administrator of nextcloud do
OCC group:adduser admin admin
</tab>
</tab>
</tabs>
</tabs>
you might want to set your default phone region (use your country 2 letter code - low case)
occ config:system:set default_phone_region --value="us"
you might want to have nextcloud accessible to the Internet
config setprop nextcloud access public
signal-event nextcloud-update
signal-event nextcloud-update
=== Use a dedicated domain to connect to Nextcloud ===
first change the first line variable content with you nextcloud domain as defined with your DNS provider.
<syntaxhighlight lang="bash">
NEXTCLOUDDOMAIN="cloud.mydomain.com"
db domains set $NEXTCLOUDDOMAIN domain Description "Nextcloud" Content Primary Nameservers internet TemplatePath WebAppVirtualHost DocumentRoot /usr/share/nextcloud RequireSSL enabled letsencryptSSLcert enabled
signal-event domain-create $NEXTCLOUDDOMAIN
# this one to let nextcloud DAV be redirect correctly and to have collabora recognize the domain
config setprop nextcloud VirtualHost $NEXTCLOUDDOMAIN
signal-event nextcloud-update
# only if you use a Let's Encrypt certificate
expand-template /etc/dehydrated/domains.txt
dehydrated -c
</syntaxhighlight>
=== Configuration ===
=== Configuration ===
|GENERATED
|GENERATED
|string
|string
|password for your main admin user for nextcloud *
|password for your main admin user for nextcloud (*)
|-
|-
|AdminUser
|AdminUser
|nextcloudadmin
|nextcloudadmin
|string
|string
|main admin user for your installation *
|main admin user for your installation (*)
|-
|cliurl
|enabled
|enabled,disabled
|force overwrite.cli.url to https://domain/nextcloud or https://domain if virtualhost is set; disable it if you have specific needs and then use occ command to set your value
|-
|-
|DbName
|DbName
|empty
|empty
|domain name
|domain name
|
|domain dedicated to nextcloud, needs to also be defined as domain on the server
|-
|-
|access
|access
|528M
|528M
|number
|number
|if a number will be converted to Megabytes, otherwise use the usual suffix : 2T for 2 terrabytes etc...
|webinterface : if a number will be converted to Megabytes, otherwise use the usual suffix : 2T for 2 terrabytes etc...
|-
|memory_limit
|1024M
|number
|for cli like occ command or cron: if a number will be converted to Megabytes, otherwise use the usual suffix : 2T for 2 terrabytes etc...
|-
|-
|Shares
|Shares
|strings coma separated
|strings coma separated
|will exclude from nexcloud access any ibay via nextcloud. Default excludes Primary ibay. If you want to include Primary set it with a random string.
|will exclude from nexcloud access any ibay via nextcloud. Default excludes Primary ibay. If you want to include Primary set it with a random string.
|-
|opcache.memory_consumption
|32
|number
|update this value if Nextcloud says that it should be
|-
|opcache.interned_strings_buffer
|128
|number
|update this value if Nextcloud says that it should be
|-
|PHPBaseDir
|
|colon separated string
|php base dir you want to add to the default example /home/e-smith/files/ibays/musique/files:/usr/share/GeoIP/GeoLite2-Country.mmdb:/proc/cpuinfo
|-
|-
|UseSMB
|UseSMB
|allow you to set ibay access via samba share or via Local driver in nextcloud. Enabled is for samba, this allow you to access as your user and have your quota accounted. It might be a little slower, and need you to have your password loaded in the session. Local driver if disabled, will let you access only what apache user (www) has right to access as member of a group.
|allow you to set ibay access via samba share or via Local driver in nextcloud. Enabled is for samba, this allow you to access as your user and have your quota accounted. It might be a little slower, and need you to have your password loaded in the session. Local driver if disabled, will let you access only what apache user (www) has right to access as member of a group.
|}
|}
* the SME admin user is also an admin of your nextcloud installation. You have two admin account as per default installation on SME Server.
(*) the SME admin user is also an admin of your nextcloud installation. You have two admin account as per default installation on SME Server.
config setprop nextcloud ExcludeIbay ibay1,ibay2
config setprop nextcloud ExcludeIbay ibay1,ibay2
signal-event nextcloud-update
signal-event nextcloud-update
=== LDAP/AD Integration Settings ===
Do not change the LDAP/AD integration settings for "1. Server: Localhost" or you will break the Nextcloud install. If you want to add a second LDAP/AD server, click the "+" symbol to add another configuration and then add the appropriate LDAP/AD settings.
=== Command line ===
=== Command line ===
if you happen to need tweaking your installation, here is how to access the command line for Nextcloud on SME, we made it easier for you, just log as root and use the OCC command (using capitals), This command will execute for you what you need as the www user, using the needed version of php. Here two examples: <syntaxhighlight lang="bash">
if you happen to need tweaking your installation, here is how to access the command line for Nextcloud on SME, we made it easier for you, just log as root and use the OCC command (using capitals), This command will execute for you what you need as the www user, using the needed version of php. Here two examples: <syntaxhighlight lang="bash">
occ maintenance:mode --off
occ maintenance:repair
</syntaxhighlight>to seek for additional command consult Nextcloud documentation : https://docs.nextcloud.com/server/13.0.0/admin_manual/configuration_server/occ_command.html
</syntaxhighlight>to seek for additional command consult Nextcloud documentation : https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html
=== Uninstall ===
=== Upgrade ===
yum remove {{#var:smecontribname}} {{#var:contribname}}
yum update {{#var:smecontribname}} {{#var:contribname}} --enablerepo=smecontribs
=== CLI upgrade of Nextcloud software ===
You should rather prefer the online updater, but in case:<syntaxhighlight lang="bash">
occ maintenance:mode --on
sudo -u www /usr/bin/php74 --define memory_limit=1024M -d apc.enable_cli=1 /usr/share/nextcloud/updater/updater.phar --no-interaction
occ upgrade
occ maintenance:mode --off
</syntaxhighlight>In case of a huge db, you can choose the online updater and then only issue the db update doing<syntaxhighlight lang="bash">
occ upgrade
occ maintenance:mode --off
</syntaxhighlight>
starting 25 to upgrace to 26, you should do
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
occ maintenance:mode --on
sudo -u www /usr/bin/php81 --define memory_limit=1024M -d apc.enable_cli=1 /usr/share/nextcloud/updater/updater.phar --no-interaction
occ upgrade
occ maintenance:mode --off
</syntaxhighlight>In case of a huge db, you can choose the online updater and then only issue the db update doing<syntaxhighlight lang="bash">
occ upgrade
occ maintenance:mode --off
</syntaxhighlight>
=== Restore info loglevel ===
config setprop nextcloud CloudDomain cloud.mydomain.com
<syntaxhighlight lang="bash">
occ config:system:set loglevel --value=3
</syntaxhighlight>
=== Uninstall ===
{{Warning box| if you plan to reinstall and had the nextcloud rpm installed do not yum remove it or rpm -e it as it would put you in a situation where you will not be able to reinstall and restore your old data. nextcloud-src rpm if present do not create such situation and can be removed safely.}}
Uninstalling the rpms
yum remove {{#var:smecontribname}} {{#var:contribname}}-src
rpm -e --justdb nextcloud
# go to preference
those folders will then remain
* /usr/share/nextcloud : software and config
* /home/e-smith/files/nextcloud : user data
also you will have mariadb or mariadb105 with nextcloud db and user.
And finally, db configuration with entry for nextcloud.
If all of those remains as is, a simple reinstall of the contrib will bring back nextcloud running. If you uninstalled it because your install was non functional or want a complete removal, there are extra steps.
In case of deleting either the db or part of the software folder, whenever you will try to reinstall the contrib, process will fail as db and files are not in sync.
In case you need to reinstall from scratch, '''first, backup what you might want to restore latter''':
cd /home/e-smith/files/nextcloud/data
mysqldump nextcloud > nextcloud55.sql
mysqldump105 nextcloud > nextcloud105.sql
config print nextcloud /root/nextcloud.config
tar -czf /root/nextcloud.tar.gz /home/e-smith/files/nextcloud/data /usr/share/nextcloud
then erase all what is remaining:
mysql -e "DROP DATABASE `config getprop nextcloud DbName`;DROP USER IF EXISTS `config getprop nextcloud DbUser`;"
mysql105 -e "DROP DATABASE `config getprop nextcloud DbName`;DROP USER IF EXISTS `config getprop nextcloud DbUser`;"
rm -rf /usr/share/nextcloud
rm -rf /home/e-smith/files/nextcloud
#this one is optional, and should not cause issue if still there
config delete nextcloud
and you should be able to start a new install from scratch
=== Release schedule ===
see https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule
as per 2024/01:
{| class="wikitable"
!Version
!Name
!Release date
!End of life
|-
|'''29'''
|
|2024-04-24
|
|-
|'''28'''
|Hub 7
|2023-12-12
|2024-12
|-
|'''27'''
|Hub 6
|2023-06-13
|2024-06
|-
|'''26'''
|Hub 4
|2023-03-21
|2024-03
|-
|'''<s>25</s>'''
|<s>Hub 3</s>
|<s>2022-10-19</s>
|<s>2023-10</s>
|-
|'''<s>24</s>'''
|<s>Hub 3</s>
|<s>2022-05-03</s>
|<s>2023-05</s>
|-
|'''<s>23</s>'''
|<s>Hub 2</s>
|<s>2021-11-30</s>
|<s>2022-12</s>
|-
|'''<s>22</s>'''
|<s>Hub</s>
|<s>2021-07-06</s>
|<s>2022-07</s>
|-
|'''<s>21</s>'''
|<s>Hub</s>
|<s>2021-02-22</s>
|<s>2022-02</s>
|-
|'''<s>20</s>'''
|<s>Hub</s>
|<s>2020-10-03</s>
|<s>2021-11</s>
|-
|'''<s>19</s>'''
|<s>Hub</s>
|<s>2020-06-03</s>
|<s>2021-06</s>
|-
|'''<s>18</s>'''
|<s>Hub</s>
|<s>2020-01-16</s>
|<s>2021-01</s>
|}
=== Change Database ===
If you are in the situation your are unable to update your nextcloud because of database requirements, you might need to install a newer and then migrate your db.
Here a simple procedure, after having the new db working as a sclo [[Mariadb105]] for SME10 as example.<syntaxhighlight lang="bash">
occ maintenance:mode --on
mysqldump `config getprop nextcloud DbName` > nextcloud.sql
echo "CREATE DATABASE IF NOT EXISTS `config getprop nextcloud DbName` CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;"| mysql105
mysql105 `config getprop nextcloud DbName`< nextcloud.sql
echo "CREATE USER IF NOT EXISTS `config getprop nextcloud DbUser`@localhost IDENTIFIED BY '`config getprop nextcloud DbPassword`';"| mysql105
echo "GRANT ALL PRIVILEGES ON `config getprop nextcloud DbName`.* TO `config getprop nextcloud DbUser`@localhost; FLUSH PRIVILEGES;" | mysql105
occ config:system:set dbhost --value localhost:/var/lib/mysql/mariadb105.sock --type string
occ maintenance:mode --off
</syntaxhighlight>
After checking that all is working you can then delete yourself the old db from the previous mysql server, or keep it as a backup for a while.
If it fails and just want to go back to previous state:
occ maintenance --on
occ config:system:set host --value localhost --type string
occ maintenance --off
</syntaxhighlight>And Finally to umount in gdm using "sudo vim /etc/gdm/PostSession/"<syntaxhighlight lang="bash">
=== File Scan ===
<syntaxhighlight lang="bash">
# scan all, could take hours if you have a lot of files
occ files:scan -v --all
# scan all that is inside a username path (including external storages mounted there)
occ files:scan -v myusername
#scan only a subfolder of a user (path needs a heading / and is relative to /home/e-smith/files/nextcloud/data)
occ files:scan -v --path="/myusername/files/myfolder/mysubfolder" myusername
#For external storage one has to use a user and the mount point in the user space, e.g. admin
occ files:scan -v --path="/admin/files/name_of_external_storage"
</syntaxhighlight>If you use groupgfolders app, then you might consider, to list the golders id<syntaxhighlight lang="bash">
occ groupfolders:list
</syntaxhighlight>then for folder group with id 1<syntaxhighlight lang="bash">
occ groupfolders:scan 1
</syntaxhighlight>
</syntaxhighlight>
=== Known issues ===
=== Known issues ===
==== Web or GUI upgrade from NC25 to NC26 ====
Due to the change of php version needed from php74 to php80 and higher, you need to issue the following command while using NC25 to be able to then upgrade to NC26. NC25 is the first to be able to handle php80, and NC26 requires php80 or higher.
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
signal-event nextcloud-update
signal-event nextcloud-update
</syntaxhighlight>then proceed to online web upgrade
</syntaxhighlight>
==== issue upgrading from 13.0.2 to 15.0.0 RPM ====
==== Issue importing files in db "Entry path/to/file will not be accessible due to incompatible encoding" ====
<syntaxhighlight lang="bash">
yum install convmv --enablerepo=epel
#first test to see the changes
convmv -f utf-8 -t utf-8 --nfc -r /home/e-smith/files/nextcloud/data/username
#check, then with --notest
convmv -f utf-8 -t utf-8 --nfc -r --notest /home/e-smith/files/nextcloud/data/username
#then rescan
occ files:scan -p /username/files/
</syntaxhighlight>this might also occurs on ibays / home folders and their files not all visibles from nextcloud, simply adapt the path for convmv /home/e-smith/files/ibays/ibayname/files/ or /home/e-smith/files/users/userame/home/
==== Remove legacy nextcloud rpm without deleting /usr/share/nextcloud content ====
for installs done before smeserver-nextcloud 1.2.0-16, the rppm nextcloud was required and was conflicting with web update. Since 1.2.0-16 it is not required anymroe and we use a nextcloud-src rpm which updates itself in /usr/share/nextcloud-src and is only used if you install the first time or restart from scratch your install.
To remove the nextcloud rpm which is not needed and save your files:
rpm -e --justdb nextcloud
source https://unix.stackexchange.com/questions/208722/how-to-remove-an-rpm-package-while-keeping-certain-files
==== User cannot see shares/files ====
==== User cannot see shares/files ====
This appeared to fix the issue and the user could now see the files.
This appeared to fix the issue and the user could now see the files.
====Reset Database====
====Upgrading beyond 20.x====
To set the default phone region:
OCC config:system:set default_phone_region --type string --value="GB"
To fix missing indices - this may take a while so be patient:
OCC db:add-missing-indices
===Koozali SMEv10 testing===
==== NC 20-21 : open_basedir restriction in effect. File(/templates/) is not within the allowed path ====
this is a bug in NC. It has been fixed in NC 22 and not backported to NC20. This is just log noise. You can ignore it while waiting to update
see https://help.nextcloud.com/t/error-file-templates-is-not-within-the-allowed-path-s-after-update-from-20-xx-to-21-0-3/119843
===Reset Database===
For reference, whilst looking at resetting file caches I found this.
It is probably extremely dangerous but wanted to make a note.
https://github.com/nextcloud/server/issues/8113#issuecomment-565876798
=== Bugs ===
=== Bugs ===
[[Category: Contrib]]
[[Category: Contrib]]
<!-- Please keep there the template revision number as is -->
<!-- Please keep there the template revision number as is -->
===References===
# https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html
# https://help.nextcloud.com/t/migration-from-mysql-to-mariadb/6816/3
# https://help.nextcloud.com/t/changing-mariadb-socket-when-hosting-multiple-db-ubuntu/68294
# https://markus-blog.de/index.php/2019/10/21/how-to-migrate-nextcloud-17-database-backend-from-mysql-to-postgresql/
# https://www.ullright.org/ullWiki/show/nextcloud-cheatsheet