md array setup

    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.

    • Official Post

    the wetty plugin will have issues if your system can't download the wetty docker image (docker.io/wettyoss/wetty:latest).


    what is the output of:


    sudo podman image ls --all

    sudo podman pull docker.io/wettyoss/wetty:latest

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    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


    • Official Post
    Quote from nasadmin

    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.

    It doesn't depend on docker. It uses podman which shares nothing with omv-extras, compose plugin, or docker as a service. It does download the wetty docker image.


    Quote from nasadmin

    Is it possibly related to not having any shared space available?

    No. wetty will keep the needed files for the container on the OS drive. There is no data in those files since it can easily be downloaded again.


    Quote from nasadmin

    Here is the results of those 2 commands:

    It looks like the image is already on your system. What is the output of:


    sudo omv-salt deploy run wetty

    sudo podman exec -it wetty /bin/bash

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    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).


    • Official Post
    Quote from nasadmin

    I'm confused, you say it doesn't depend on docker but downloads the docker image.

    docker is a service. podman is not docker. docker and docker images are two different things. podman can use docker images and that is what the wetty plugin does. So, the plugin does not depend on docker (the service).

    Quote from nasadmin

    The 2nd exec command (podman exec -it wetty /bin/bash) says no such container (actually so does the 1st command).

    The saltstack output tells me that you don't have wetty enabled in the omv web interface. Check the "Enabled" checkbox and click save. Don't click apply. Rerun the commands from post #25.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    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.

    • Official Post
    Quote from nasadmin

    There is no "Apply"

    Apply is the yellow bar that pops up after clicking save.


    Quote from nasadmin

    the service isn't enabled; when I check that box & click Save I get the 500 error.

    What about:


    sudo apt-get purge openmediavault-wetty

    sudo omv-mkworkbench all

    sudo apt-get install openmediavault-wetty


    ctrl-shift-R in the web interface

    try to enable and save

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    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.


    • Official Post
    Quote from nasadmin

    I presume the steps in post 29 essentially is a purge & reinstall, so should be a fresh state?

    For the most part. it should be in a fresh state. The podman man stuff isn't purge when the plugin is. I have tried to reproduce but I can't. I guess you could file a bug report to have Volker look at it (he wrote the plugin) but it might just be easier to use wetty in a docker compose file (an example is available in the compose plugin).

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    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!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login