Thank you for asking My VM is running very well, I am very satisfied. Everything works. I have now installed MC without problems and did not have to change the sources.list.
I have deactivated the automatic Saturday update, I have too much respect for it. I do it manually once a month now that you have published it on your homepage.
For your information. I have also activated NFS and it works. I know itâs a security risk, but Iâm not a bank and I need my videos. I added the following to the fstab and it works: XXX.XXX.XXX.XXX:/nfsshare /mnt/nfs/video nfs defaults 0 0
I was finally able to put my bare-metal server online for our association.
I analyze the way it is built and I try to understand how to administer it well (update of the Ubuntu base, Nextcloud and its applications, and docker images which are part of it).
I twice lost the link between Nextcloud and Collabora (.odt files would no longer open, with a connection error message, but why ?), but reinstalling Collabora fixed the problem.
Until this morning, when the ârichdocumentsâ application went to 3.6.0, and the reinstallation of Collabora could not do anything.
After searching on this forum, I found the solution here
Adding the two lines indicated by âhelgeâ and relaunching Apache fixes the problem.
But I realized that, despite the fact that I did an Nextcloud update (at least I thought so) with the script: sudo bash /var/scripts/update.sh,
I didnât see any changes in this scripts directory, in particular, the menu.sh script is not present, although it seems to be part of the scripts copied during the global installation.
Also, the versions of the scripts on my machine and on the master branch of git are not the same.
Is it possible to update the script directory to stay at the git level, and is there a script to do it?
Would relaunching a full installation do this job without breaking existing configuration items?
PS: I am an old retired IBM AIX sysadmin and Iâm not very comfortable with docker
update.sh gets the latest nextcloud_update.sh and runs that, but it doesnât download all the latest scripts from Github, New functions and scripts are only released in new versions of Nextcloud, and regarding menu.sh thatâs not released until Nextcloud 19 or 18.0.5. You could download it manually though - it will run, and it will work with the current lib.sh file.
I donât know why the check didnât kick in and added the config. I would have to take a look at it, when I have time.
Anyway, it should be sorted in 19.0.1, but if you want to can just run it ḿanually. In the VM you can use nextcloud_occ as an alias for running the occcommand.
First I started the update process with ssh and putty and it showed the same error as before and I had to cancel the update to NC19, restore the snapshot and start again.
Then I updated Ubuntu with sudo apt-get update and sudo apt-get upgrade and started again.
Then I repeated the update script: sudo bash /var/scripts/update.sh
Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.
You shouldnât run the startup script for update. The fact that itâs still there tells me that something went wrong during the initial run, or you didnât reboot the server properly. The last thing that happens is that the startup script is removed. but it only happens if you reboot.
The correct way of updating is using the update script:
The start script was suppressed I ran it a second time and then everything worked. I took the message as an instruction. I thought it was the normal process. Thank you and have a nice weekend.
My VM is running very well, I am very satisfied. Everything works. I have now installed MC without problems and did not have to change the sources.list.
