The following error occurred after omv 6 was restarted and it could not be started. I did not perform any special operations, so I could not find the reason. I hope to get some guidance.
Posts by albicocca
-
-
Can you add some function buttons in Compose-->Containers? For example, "stop", "restart", "remove" and the like, this should be easier to use.
In fact, there is another suggestion that has nothing to do with compose.
Many places in the webui cannot perform multiple selection operations (for example, in Rsync-->Tasks, multiple selections cannot be deleted at once), can it be improved?
-
Sorry, I have no idea how to do this.
I'm just tossing around in my own imagination, and this question is also a whim after seeing this post, maybe I don't understand what I want to do.XD
-
I think there is some confusion here, I wasn't talking about this function. The purpose of this function is different, as you read in the documentation.
Yes, I also want to solve the problem of permission management, especially when faced with the filebrowser plug-in, although I can adjust the permissions of existing files, I do not have a good way to control the permissions of new files they create (including files generated by a large number of docker containers in Volumes). I do not want to give them root permissions, so I put them all in the same group, but I hope to find a correct and simple solution.
-
I've never used this feature, but instructions for using it are here.
This function should not achieve the desired effect. Currently, it is more appropriate to use the "usermod" command to add a group.
-
This is strange. As I said the user filebrowser already exists in the system with UID=995 and GID=100 (in my case at least,it is possible that yours has another uid).
I guess all you have done is add it to the OMV GUI and from the GUI add it to the other group besides users. But if it's working for you, leave it as it is. I don't think anything you've done is harmful.
Sorry, I want to insert a simple question.
you mentioned "I guess all you have done is add it to the OMV GUI and from the GUI add it to the other group besides users."
I don't understand how to use "WEBUI=>users=>users=>import" to import the account, about #<username>; <uid>; <tags>; <email>; <password>; . Is there a tutorial on how to use it (I'm still a beginner T-T)
-
The main question is: are you able to boot the OS or not?
Now the GRUB boot menu will appear after the device is started. After that, the page that will stay in the figure will not continue.
-
You shouldn't be editing saltstack or nginx config files that are maintained by saltstack. If you need something other than how the webdav plugin works, you should use webdav in docker.
Yes, I regret a little now. Do you have any solutions to the new problem (the information in the picture is stopped on this page during startup)? -
And you still didn't answer my question: what file did you edit?
I edited /srv/salt/omv/deploy/webdav/default.sls
I didn't find any other default.sls.
If you ONLY edited that file, undo the changes to it and run
omv-salt deploy run webdav
After that, systemctl restart nginx.service and your system will be in it's prior state.I didn't do any other operations. Thank you for the methods you provided, but unfortunately, I can't do these operations now.
It seems that I am very unlucky today. I have just experienced a rare power failure. After starting up, the equipment has a new problem, which should have nothing to do with the above problems.
-
And what file did you edited?
Code
Display MoreFailed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color nginx 2>&1' with exit code '1': debian: ---------- ID: prereq_nginx_certificates Function: salt.state Result: True Comment: States ran successfully. Updating debian. Started: 17:22:28.547562 Duration: 836.578 ms Changes: debian: ---------- ID: remove_ssl_certificates_crt Function: module.run Result: True Comment: file.find: [] Started: 17:22:28.682629 Duration: 9.018 ms Changes: ---------- file.find: ---------- ID: remove_ssl_certificates_key Function: module.run Result: True Comment: file.find: [] Started: 17:22:28.691796 Duration: 1.581 ms Changes: ---------- file.find: ---------- ID: update_ssl_certificates Function: cmd.run Name: update-ca-certificates --fresh Result: True Comment: Command "update-ca-certificates --fresh" run Started: 17:22:28.694157 Duration: 684.878 ms Changes: ---------- pid: 1069453 retcode: 0 stderr: rehash: warning: skipping openmediavault-60788176-8a44-4b5f-a0e3-9efdbb26079e.crt,it does not contain exactly one certificate or CRL stdout: Clearing symlinks in /etc/ssl/certs... done. Updating certificates in /etc/ssl/certs... 129 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. ---------- ID: remove_ssh_certificates Function: module.run Result: True Comment: file.find: [] Started: 17:22:29.379344 Duration: 2.441 ms Changes: ---------- file.find: Summary for debian ------------ Succeeded: 4 (changed=4) Failed: 0 ------------ Total states run: 4 Total run time: 697.918 ms ---------- ID: configure_nginx_site_webgui Function: file.managed Name: /etc/nginx/sites-available/openmediavault-webgui Result: True Comment: File /etc/nginx/sites-available/openmediavault-webgui is in the correct state Started: 17:22:29.386843 Duration: 135.637 ms Changes: ---------- ID: configure_nginx_security Function: file.managed Name: /etc/nginx/openmediavault-webgui.d/security.conf Result: True Comment: File /etc/nginx/openmediavault-webgui.d/security.conf is in the correct state Started: 17:22:29.522619 Duration: 11.33 ms Changes: ---------- ID: execute_nginx_ensite Function: cmd.run Name: nginx_ensite openmediavault-webgui Result: True Comment: Command "nginx_ensite openmediavault-webgui" run Started: 17:22:29.534562 Duration: 7.915 ms Changes: ---------- pid: 1070829 retcode: 0 stderr: stdout: Site configuration file 'openmediavault-webgui' is already enabled. ---------- ID: prereq_nginx_service_monit Function: salt.state Result: True Comment: States ran successfully. Updating debian. Started: 17:22:29.542744 Duration: 418.817 ms Changes: debian: ---------- ID: configure_monit_collectd_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-collectd.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-collectd.conf is in the correct state Started: 17:22:29.792423 Duration: 22.32 ms Changes: ---------- ID: configure_monit_filesystem_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-filesystem.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-filesystem.conf is in the correct state Started: 17:22:29.814836 Duration: 7.672 ms Changes: ---------- ID: configure_monit_nginx_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-nginx.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-nginx.conf is in the correct state Started: 17:22:29.822598 Duration: 7.057 ms Changes:Sorry, what I said may not be accurate. After deleting the "webdav" in Line # 29,38, I opened the plug-in and reported the above error（The information is too long，What I sent is not complete）. It seems that the above operations affect the nginx used by the omv webui. After the device is restarted, the system does have problems.
-
Since I'm no coder, don't know if it's possible to change Line #38 from this:
location /webdav {
To this:
location / {
Please note that should not do this again. This operation did not achieve the expected effect and caused serious problems.
The startup and shutdown of the webdav plug-in will report an error. After the uninstalled plug-in is restarted, the system cannot be started normally. The problem seems to be the modification of 38 lines, which affects the nginx settings of the omv itself. Now I'm trying to repair the system.
-
The port KM0201 is refering is the one of OMV.
You can change it on GUI to something other than 80. (if you haven't already)
I may not have made it clear that I changed the OMV port, but this did not achieve the desired effect. Therefore, I want to change the webdav port, but the webdav plug-in itself does not provide this function.
-
I'm not familiar with webdav, but is it possible because the webUI is running on port 80 and it's causing a conflict? Try changing the port the omv webUI uses to something other than 80 (I believe it's under General)... then you'd access OMV at ip:port
Edit: Nevermind, reading up at earlier posts that have it working, I'm not sure that's the issue.
Thank you. I did this, but it didn't achieve the desired effect.
How to change the webdav port? I think this may be more conducive to solving the problem.
-
The plugin is only providing the server component not a client component. You should install something like nextcloud in docker if you want more features via web browser.
Here's a simple question. In the webdav plug-in, the shared folder is set to "/omv". When I mount it, I set it to http//:ip:80, and the mount fails. The http//:ip:80/webdav is actually connected to the/omv/webdav directory. How can I directly connect to the "/omv" directory?
-
prune will do that. docker image prune will probably do a better job cleaning up than a user would.
Thank you very much for your improvement. Today, I received the update of the Compose plug-in and saw the new functions I hope to see. Thank you very much.
-
prune will do that.
That's a good idea, could you add a button in the compose plug-in to activate this directive? (like "apt clean" in the System -- >omv-extras -- >Settings screen
Sorry, I thought maybe relying too much on the web user interface, which I thought would be easier to use. It's helpful for people who know even less about linux than I do.
-
You are doing it wrong. If you specify a version in your compose file, it will pull the same image you would pull in a management tab. I don't mind adding a prune menu (system, image, volume, container, network options) but I don't see why some of this management needs to be done.
Yes, I can pull to the specified version, I want to express the later problem. "down" or "delete" on an existing yml will not delete an existing image. If I have multiple versions of the image installed, unwanted images will be left on the device. I think the webui needs at least a function to delete images.
-
What do you want to manage about the images?
I hope to have a list showing the existing images, which can pull the specified images with basic management functions such as deletion.
During my use, some dockers cannot use the latest version completely, and may also use "nightly" "develop" or specific version numbers.
I have encountered some situations. For example, when comparing the new version of qbittorrent, errors will occur, while the old version is normal. I use the same configuration and switch between two images to find problems.
After some images are updated, the old versions cannot be deleted normally (until now, I don't know the reason). Finally, they are deleted through some troublesome operations. If there is an image management function, I can at least visually see the existence of old versions of images.
-
I knew that is what you were asking for but I don't think it is needed and would complicate things for noobs. Why do you want to set the path for the volume? portainer and yacht store very little. Basically just the compose files and I think the compose plugin is better for that. Not only does it store the compose files in the omv database, it writes them to files on a data disk. Automatic backup : )
I also think the Compose plug-in is great. If you can optimize the batch operation and add the intuitive image management function, I think for many people, you can no longer need the portal.
My personal usage habit (I don't know how others do it). I put the Docker volume in a unified directory and back it up. As a docker, I think the volume of the portainer should be with other dockers.
albicocca I think you need to add the "whois" package to your OMV install. Other things might not run, but openwrt does:
Thank you very much. In fact, I have installed "whois" before, but the installation of openwrt failed. Just after seeing your message, I successfully installed it again. I don't understand why. Is it because of reboot? XD
-
Have you looked into zfs-auto-snapshot?
Sorry, I didn't see it, was it achieved through Scheduled Tasks?
Use a compose file in the compose plugin if you want to set volumes for these containers.
Yes, I did the same. I mean that I hope to provide options in the "System ->omv extras ->Portainer" of the Web UI. I feel that this function of the Web UI will be more complete.（Maybe to remove the functions on the webui and increase the guidance of exmple in the compose plug -in, I think it is also good, but it may not be friendly to novices.）
