Ok, thx for that info. I can manage remotely and quash those notification messages that way.
Posts by nasadmin
-
-
The only email notification option I set in the settings is for smart, yet I get emails from root saying a new version is available.
Is it possible to do the update from the command line via ssh? If not, how can I disable those notifications?
-
I decided to simplify things & skip the shared folder approach. From the posts I read and my own experience it doesn't look like the web interface supports shared folders, or at least not very well / intuitively.
The use case for this NAS is mainly as a backup for a single user, so just using rsync to copy their home folder to the NAS and they can use the file manager web interface to obtain a copy of any file(s), or rsync in reverse to restore entire home folder on a crash to restore.
Only thing necessary to resolve now is why smtp doesn't seem to work. I created a separate thread for that issue. -
Where are the logs for SMTP? I get no errors in the web UI when I use the test link. I've double checked the settings and they look correct (same as they are in another machine's Thunderbird email client).
Using ss -atl on the CLI I do see a listener that puzzles me. Looks like a wide open email relay. What is this? Is it normal in OMV? If not how to purge it. If so is it a security concern and open invitation for email spammers? -
After many go-rounds and removal of references (had to set None in options for file manager and users) I was finally able to get the web interface file manager to show the contents of their folders.
However no shared folders can be seen when logging in via the file manager, despite them have proper permissions. It seems the file manager isn't designed to allow access outside of a user's home folder. The Share Management tab has no contents and no apparent way to add contents there, it just has an image that says "It feels lonely here...".
There appears to be some kind of permissions problem. I can't create any folders in the file manager web interface and when I try to delete one created on the CLI I get a forbidden msg.
Here is my current config:Code
Display More$ ls -ls /srv total 12 4 drwxr-xr-x 6 root root 4096 Aug 31 18:13 dev-disk-by-uuid-b71a0164-48d6-41ec-9015-583e339377b7 4 drwxr-xr-x 3 root root 4096 Aug 27 10:46 pillar 4 drwxr-xr-x 7 root root 4096 Aug 27 10:46 salt $ ls -ls /srv/dev-disk-by-uuid-b71a0164-48d6-41ec-9015-583e339377b7/ total 108 16 drwx------ 2 root root 16384 Aug 29 16:58 lost+found 84 drwxrwsr-x+ 1413 root users 81920 Aug 31 17:06 Music 4 drwxrwsr-x 4 root users 4096 Aug 31 18:27 Users 4 drwxrwsr-x+ 43 root users 4096 Aug 31 17:28 Videos $ ls -ls /srv/dev-disk-by-uuid-b71a0164-48d6-41ec-9015-583e339377b7/Users/ total 8 4 drwxr-xr-x 2 mark users 4096 Aug 31 18:35 mark 4 drwxr-xr-x 2 thomas users 4096 Aug 31 18:27 thomas
-
I found it. It wasn't obvious and I don't even recall where the reference was. I am still trying to figure the way storage works under OMV.
No problem with multiple disksNo problem with LVM elements (physical volumes, volume groups & logical volumes)
Not clear on user home folder. I have a logical volume named RAID_storage. I created a symlink to that called raid_space. I used raid_space as my "home" folder for users. In the file manager plugin I erased the /users default and made it just /, hoping users created under OMV's User web interface would be accessible and share the same home folder. That appeared to work, but it didn't. A /users folder was created anyway: /srv/raid_space/raid_space/users. The OMV web UI Users created the user under /srv/raid_space/<username>.
Not clear on shared folders in general and how users can access them. I would hope that a user given the proper access permissions would be able to view any files in any shared folder that user is granted access too.
Although I granted user X read/write access to all shared folders (which are siblings user home folders), I can't see them in the file manager web interface. Perhaps that's by design but it's rather limiting if so. I was hoping a user could browse any files, under his own home folder or any other shared folder he is given access to.---
I'm just very confused about the correct sequence required to define users home folders, shared folders and then how to provide access to them from the file manager plugin. Once referenced, it's not easy to find those references to remove a shared folder.
The Music and Videos shared folders are directly under the LVM Logical Volume, which is what I wanted. "raid_space" is just an alias for the LVM LV. The users created with the Web UI should be under that symlink, but instead they're created under a different folder with the same name as the symlink:Code
Display More$ ls -ls /srv total 12 4 drwxr-xr-x 6 root root 4096 Aug 31 13:20 dev-disk-by-uuid-b71a0164-48d6-41ec-9015-583e339377b7 4 drwxr-xr-x 3 root root 4096 Aug 27 10:46 pillar 0 lrwxrwxrwx 1 root root 54 Aug 31 11:38 raid_space -> dev-disk-by-uuid-b71a0164-48d6-41ec-9015-583e339377b7/ 4 drwxr-xr-x 7 root root 4096 Aug 27 10:46 salt $ ls -ls /srv/raid_space/ total 80 16 drwx------ 2 root root 16384 Aug 29 16:58 lost+found 56 drwxrwsr-x+ 838 root users 53248 Aug 31 16:04 Music 4 drwxrwsr-x+ 5 root users 4096 Aug 31 15:31 raid_space 4 drwxrwsr-x+ 15 root users 4096 Aug 31 15:17 Videos $ ls -ls /srv/raid_space/raid_space/ total 12 4 drwxr-xr-x 2 mark users 4096 Aug 31 15:09 mark 4 drwxr-xr-x+ 2 thomas users 4096 Aug 31 15:31 thomas 4 drwxr-sr-x 3 filebrowser users 4096 Aug 31 12:26 users
-
I created several shared folders, and users which were created using an LVM logical volume. I also setup some of those users under the file manager plugin.
I deleted all of the users in the web UI, and all of the folders under the /srv/dev-disk-by-uuid-* associated with that LVM logical volume using the CLI since the trash can icon wasn't active for one of them (which is why I deleted everything I could to remove that reference, but to no avail).
That shared folder is still showing up in the web UI under Storage--> Shared folders and I can't seem to get rid of it to start over. -
Quote
No. If you want it happen on some frequency, you should schedule the following command: folder2ram -syncall
Perfect. Thanks for that tip!
-
Thanks for the reply. Upon reflection, I've decided to keep using the shared folder area I setup as home for all users under Users--> Settings.
However that isn't where the typical user folders are, such as .ssh, .local, .config etc. Apparently such areas are under the management of OMV. I added ssh keys for one user and that user can ssh into the nas.Getting used to how OMV manages users and their storage, and how the file browser works.
-
Please forgive the noob question, but I can't see the users I created with the web UI under /home folder of boot drive. Where are they located if None is selected for the home folder?
There is one user under /home, I don't recall how I did it, perhaps on cmd line. The other apparently thru the web UI.
Once created with None, can they be moved elsewhere if None is changed, or must it be done manually? (if it's even possible) -
I read in the documentation that the purpose of this plugin is to reduce writes to the boot drive by writing "into one, larger, bulk write that is flushed to the boot drive on shutdown."
The docs say no configuration is necessary (and presumably possible, at least in the UI). I am using this plugin to improve the life of my M.2 SATA SSD, and the nas is not shutdown on a regular basis. When are the logs updated if the system is rarely shutdown? Is it a matter of the default size built into the plugin? i.e. when a log reaches N bytes in size it triggers the write operation regardless of shutdown? -
Ok, well you gave it a good try to resolve. I truly appreciate your efforts!
I need to study the info on docker / compose. The plugins are installed but my first glance at the help leads me to think there's some non-trivial config required before it's ready for use.
Have a wonderful weekend sir! -
1st time it appeared to succeed, but no listener existed on the default port 2222. When I tried to change the port and click save, got the 500 error. Reset the port to 2222 still got 500 error on Save. Using ss -anl | grep tcp to check open ports.
After running the commands in post 29 and returning to the web browser, the yellow Apply box is displayed, service not enabled, default port 2222. NOT clicking Apply but instead doing ctrl-shft-R yields the very same state with yellow Apply box showing. Clicking check mark on yellow Apply box says, "Saving configuration...". After a short time of spinner, results in green success. Checking Enable box and trying to save results in 500 error.
Repeated the purge / reinstall, yellow apply box appears on ctrl-shft-R. I've tried several combinations but no success. I presume the steps in post 29 essentially is a purge & reinstall, so should be a fresh state? If so something isn't being taken into account.Code
Display More# apt-get purge openmediavault-wetty Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: openmediavault-wetty* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 139 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 40933 files and directories currently installed.) Removing openmediavault-wetty (7.0-2) ... Failed to stop container-wetty.service: Unit container-wetty.service not loaded. Removing systemd unit files ... Untagged: docker.io/wettyoss/wetty:latest Deleted: fed698564d8baac68ff3c87d3ab2de3eb60736f6b167959dbc488c9f5ebc50ae Mark modules as dirty ... Processing triggers for openmediavault (7.4.6-1) ... Restarting engine daemon ... Updating workbench configuration files ... (Reading database ... 40890 files and directories currently installed.) Purging configuration files for openmediavault-wetty (7.0-2) ... Removing systemd unit files ... Error: docker.io/wettyoss/wetty:latest: image not known Mark modules as dirty ... Cleaning up configuration database ... Processing triggers for openmediavault (7.4.6-1) ... Updating workbench configuration files ... # omv-mkworkbench all # apt-get install openmediavault-wetty Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: openmediavault-wetty 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/12.9 kB of archives. After this operation, 139 kB of additional disk space will be used. Selecting previously unselected package openmediavault-wetty. (Reading database ... 40893 files and directories currently installed.) Preparing to unpack .../openmediavault-wetty_7.0-2_all.deb ... Unpacking openmediavault-wetty (7.0-2) ... Setting up openmediavault-wetty (7.0-2) ... Trying to pull docker.io/wettyoss/wetty:latest... Getting image source signatures Copying blob e2c1a789ace8 done Copying blob f379b689aea3 done Copying blob 213ec9aee27d done Copying blob c34a027bbf26 done Copying blob fe299d5780c0 done Copying blob 61cefbfca1a9 done Copying blob f7b24f077e5d done Copying blob 2baf0684399d done Copying blob d7f3ac6be6ef done Copying config fed698564d done Writing manifest to image destination Storing signatures fed698564d8baac68ff3c87d3ab2de3eb60736f6b167959dbc488c9f5ebc50ae Updating configuration database ... Updating configuration ... Processing triggers for openmediavault (7.4.6-1) ... Updating workbench configuration files ... Restarting engine daemon ... #
-
Quote
podman can use docker images
That's the part I didn't know.
There is no "Apply", only Open UI, Cancel & Save. You're right, the service isn't enabled; when I check that box & click Save I get the 500 error. -
I'm confused, you say it doesn't depend on docker but downloads the docker image. The 2nd exec command (podman exec -it wetty /bin/bash) says no such container (actually so does the 1st command).
Code
Display More# omv-salt deploy run wetty debian: ---------- ID: stop_wetty_service Function: service.dead Name: container-wetty Result: True Comment: The named service container-wetty is not available Started: 22:08:42.846404 Duration: 10.876 ms Changes: ---------- ID: remove_wetty_container_systemd_unit_file Function: file.absent Name: /etc/systemd/system/container-wetty.service Result: True Comment: File /etc/systemd/system/container-wetty.service is not present Started: 22:08:42.859058 Duration: 0.517 ms Changes: ---------- ID: wetty_systemctl_daemon_reload Function: module.run Result: True Comment: service.systemctl_reload: True Started: 22:08:42.860208 Duration: 375.701 ms Changes: ---------- service.systemctl_reload: True Summary for debian ------------ Succeeded: 3 (changed=1) Failed: 0 ------------ Total states run: 3 Total run time: 387.094 ms
-
Oh, well that's important! There should be a msg about a dependency on docker. I do understand that docker is required for many add ons, but I didn't see that mentioned for WeTTY. When I was trying it initially omv extras & compose wasn't installed. It is now, and was the last time I tried it. The 2nd of those appeared to have pulled some stuff down, but still can't enable it without a 500 error. I did do a ctrl-shft-R before & after clicking Save too.
Is it possibly related to not having any shared space available? Until just now, the only storage was on the boot drive. Now that the 2TB MD initialization has completed I have created an LVM volume group and a Shared_Space logical volume. However I don't see anywhere WeTTY asks for any space so it seems unlikely to be related to that.
Here is the results of those 2 commands:Code# podman image ls --all REPOSITORY TAG IMAGE ID CREATED SIZE docker.io/library/mariadb latest 92520f86618b 2 weeks ago 412 MB docker.io/photoprism/photoprism latest e96d2e809377 7 weeks ago 2.12 GB docker.io/library/caddy latest adf4aeafa6ae 2 months ago 49.8 MB docker.io/filebrowser/filebrowser latest 8f53a859c356 3 months ago 32.1 MB docker.io/wettyoss/wetty latest fed698564d8b 23 months ago 459 MB
Code
Display More# podman pull docker.io/wettyoss/wetty:latest Trying to pull docker.io/wettyoss/wetty:latest... Getting image source signatures Copying blob 61cefbfca1a9 skipped: already exists Copying blob fe299d5780c0 skipped: already exists Copying blob e2c1a789ace8 skipped: already exists Copying blob 2baf0684399d skipped: already exists Copying blob c34a027bbf26 skipped: already exists Copying blob f379b689aea3 skipped: already exists Copying blob f7b24f077e5d skipped: already exists Copying blob d7f3ac6be6ef skipped: already exists Copying blob 213ec9aee27d skipped: already exists Copying config fed698564d done Writing manifest to image destination Storing signatures fed698564d8baac68ff3c87d3ab2de3eb60736f6b167959dbc488c9f5ebc50ae
-
Indeed, no complaints on sending suggestions my way, I appreciate your help. I do see the 500 error in other situations, and after looking over the list you linked I'll be sure to do the ctrl-shift-R when I do, that refreshes in firefox.
-
Regardless, it didn't change anything. I even removed all cookies and site data for the IP I'm using for OMV.
-
Ok, lucky you!
A server error (500) isn't going to be resolved with a browser cache reload. Besides, there's nothing in the browser cache for that port yet, until the server responds to the browser request.
Thanks just the same, and for your help with the other matters.
Greatly appreciated! -
There's nothing to post. When I go to the notifications it just shows the 500 error, and when I click on the 3 vertical dots the "save to clipboard" option isn't active. Is there a log file I can grab it from, or is it under journalctl? I just looked and don't see anything related to WeTTY or thhe port I used in the journal. Oh, just realized it's a web server error. I'll check under nginx...
All I see in the /var/log/nginx/openmediavaullt-webgui_access.log are tons of 500 errors and 200s from Monit, so no help from that, unless it's caused by the browser version which seems highly unlikely.
I got the omv extras plugin installed, and also the docker compose plugin it said to install. Not sure how to setup that compose plugin tho. I have used both docker & compose, but it's been awhile and I never got into compose very deeply, mostly just used what others created for the project.