Posts by tannaroo

  • Backup Plugin / Restore Issue


    I'm running Dell Desktop i5.


    I've had to fully re-install OMV5 a few weeks ago, which I have done on a flash drive.


    I'm now trying to restore from the backup plug by writing the backup image to a new flash drive. Therefore, if my original system drive crashes, I can just replace it with my backup flash drive.

  • Backup Plugin / Restore Issue

    So I have been trying to create a backup using the guide in post #1.


    I have tried 4 different USB brands, creating a backup of my 16gb flash drive operating system to another 16gb and 32gb flash drive.


    I can not get the 'backup' version to boot - keep getting errors on each version (sometimes same) per the image below:


    I've tried using Etcher and USB imager as well.


    Any ideas to get it working?

  • Docker Stacks

    Portainer starts through the webUI.

    Output too big to post but all looks good to me - there was no reference to the by-label ID.

    Thanks for your help....again!

  • Docker Stacks

    Quote from Zoki

    try to get rid of this image

    docker image rm a1c22f3d250f

    After deleting the docker container, I couldn't run this command - "error no such image."


    I've rebooted and docker inspect portainer is referencing back to the uuid disk, so currently working.


    It says no portainer_data and does the 2 docker volumes mean 2 dockers?

    Code
    root@OMV:~# docker volume ls
DRIVER    VOLUME NAME
local     96ddc8e2e81465c5284bbe0283cd0b4031c8a1ee0d4adc4f1723381b2c598373
local     b4735ee123d12add7cf838f58d6daff597fa3351822ea780e94141c1de72ec93
root@OMV:~# docker volume inspect portainer_data
[]
Error: No such volume: portainer_data
root@OMV:~#

  • Docker Stacks

    Quote from Zoki

    I do not understand what I see. This is a portainer installation created 2 month ago and stopped 7 days ago, but the image tag has been removed in the meantime. it does not have a name or did you cut off the name of the container in the last line at the right?

    I can't explain why the dates are like they are but the 7 days ago is the new portainer from the outset of this thread. There is nothing cutoff from what I can see. The containers themselves are also working fine, just not portainer.

    Quote from Zoki

    How are you starting your portainer container?

    I can't at the moment.


    Code
    root@OMV:~# docker image ls
REPOSITORY                         TAG       IMAGE ID       CREATED        SIZE
lscr.io/linuxserver/syncthing      latest    3e86dd0e8a0b   8 days ago     49MB
plexinc/pms-docker                 latest    50eaaf5e3424   8 days ago     631MB
lscr.io/linuxserver/resilio-sync   latest    f2c2f16c41dd   2 weeks ago    211MB
uroni/urbackup-server              latest    ba6cf74a3d2a   2 weeks ago    177MB
dlandon/logitechmediaserver        latest    53a4242e55d1   5 weeks ago    1.38GB
portainer/portainer-ce             latest    0df02179156a   2 months ago   273MB

    I feel this portainer image from 2 months ago is not correct, as I created a portainer image last week per post #2.

  • Docker Stacks

    Here you go. It all looks good except for portainer which keeps referencing back to the bylabel ID but none exists anymore.


  • Docker Stacks

    Unfortunately the issue has resurfaced. The output of docker inspect portainer shows for log path and mounts the disk label whereas all were changed to uuid, with the /srv/by-label directories deleted:

    Code
            "LogPath": "/srv/dev-disk-by-label-Chimp/AppData2/Docker/containers/75ba                                                                                        5e06fcd2ba6cdf2e02e4c9bdb72afd577dfdada7a97266ff8faab5b893e7/75ba5e06fcd2ba6cdf2                                                                                        e02e4c9bdb72afd577dfdada7a97266ff8faab5b893e7-json.log",

      "Mounts": [
            {
                "Type": "volume",
                "Name": "portainer_data",
                "Source": "/srv/dev-disk-by-label-Chimp/AppData2/Docker/volumes/                                                                                        portainer_data/_data",

    My portainer docker-compose.yml is defintely mapped to by..uuid


    docker volume ls is showing 2 volumes - is this causing the issue?

  • Heimdall + Openmediavault

    Quote from raulfg3

    you need to write the URL heimdall must open when push the button.


    and example for netatmo a remote temp monitor for my home, but all apps works in a simmilar way ( URL, can be a Ip too eg: http://192.168.1.100:9000 to open your portainer page if 192.168.1.100 is the IP of your NAS).


    I've done that in both the 'add application' and 'edit configuration' but it only takes you to the login page of the application. It doesn't actually log you in.

  • Heimdall + Openmediavault

    Quote from Bobur

    There is a config section on bottom of the edit window.

    I saw that but thats only to bring in the api data from the enhanced apps. It doesn't actually log you into the app.


    I also found the app seemed unfinished. For example, if you add a user thee is no way to remove them.

  • nginx failure, then succeeds but then fails agains

    Quote from Zoki

    Can you check the logs in /var/log/nginx?

    The only thing that was happening around that time is a scheduled job of Clam AV running for one of my data folders.

    Code
    root@OMV:~# cat /var/log/nginx/error.log
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1156 exited on signal 9
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1155 exited on signal 9
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1157 exited on signal 9
2022/02/06 10:07:17 [alert] 1154#1154: worker process 1158 exited on signal 9
2022/02/06 10:13:28 [alert] 16515#16515: worker process 16517 exited on signal 9

  • nginx failure, then succeeds but then fails agains

    Quote from Zoki

    A load of 15 is rather high for a simple nas. Do you still have troubles with a disk where the kernal waits for timeouts?

    Not that I'm aware.


    But not sure if this could be an issue. The original drive which failed last week is the internal drive and I have not removed this as I'd need to open the desktop and physicall remove it. However, BIOS sequence is setup to boot from USB (the new OMV5 installation), which is does. The failed internal drive is not mounted, so OMV should be ignoring it.

  • nginx failure, then succeeds but then fails agains

    Quote from chente

    nginx is the web server that OMV uses to display the interface in your browser.

    Have you installed any application directly on the host?

    Have you installed a desktop system?

    No. The hardware is only used for OMV5.


    Initially I had OMV5 installed for a couple of years but got this error a week ago (see earlier posts) which was traced to a bad system drive.


    So I did a fresh install of OMV5 onto a new USB flash drive. Was back up and running and everything worked fine for a week but then started getting the emails etc again yesterday.

  • nginx failure, then succeeds but then fails agains

    Its happened again Re: nginx failure then succeeded.


    I also received an email ahead of the nginx failure about my loadavg

    Description: loadavg (1min) of 15.5 matches resource limit [loadavg (1min) > 8.0]


    Is this a hardware (Dell i5 machine) issue even though all of my hardware tests were passed and only using a handful (4) of conatiners

  • Docker Stacks

    Quote from KM0201

    This might be another good example of why using Symlinks in docker is a pretty good idea. Since UUID's can change on a new install, it could put OP back in this situation (although now he'd be wise to it). With Symlinks, you can keep them consistent across new installs, you just have to create your links before installing docker. That's what I did when I clean installed 6 earlier this month and it actually worked very well. In my situation, all of my "/config" directories (or in the case of Portainer, /data), are under /NAS/AppData. All of my Media, is under /NAS/Media... This makes setting up my symlinks from memory easy, and also if I want to install new containers, my paths are easy to set from memory. I've got a few other paths I link outside of AppData and Media, but since I know them and know they are consistent.. it's quite easy.

    I'm still slightly confused with the setup. If I understand correctly (notwithstanding the order):


    1) Docker installed on a separate external drive


    2) Portainer plus all containers on another drive (i.e. /config files) - which is backed up onto another external drive, in case the first drive goes down


    3) Symlinks to make it easier to navigate and get No. 2 working irrespective of their UUIDs

  • Heimdall + Openmediavault

    sorry to bump this thread but I'm testing Heindall on my pi unit. How does one get the autologin details so that for example it will automatically log in to OMV once the OMV icon is selected?

  • nginx failure, then succeeds but then fails agains

    Following the nginx errors I had last week, which was tracked down to a faulty hard drive, I did a new install last week on a new USB drive.


    Its been working fine all week but today I was presented with over 80 nginx error/fail emails.


    I've run all of the PC tests through the BIOS which passed.


    On the bootup - I noticed this error, not sure if its relat


    I also noticed these outputs:

    Code
    root@OMV:~# dmesg | grep error
[    9.009450] EXT4-fs (sdg1): re-mounted. Opts: errors=remount-ro
[   10.813203] platform regulatory.0: Direct firmware load for regulatory.db fai                led with error -2
root@OMV:~# dmesg | grep fail
[   10.813106] platform regulatory.0: firmware: failed to load regulatory.db (-2)
[   10.813203] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   10.813204] cfg80211: failed to load regulatory.db
root@OMV:~#


    Can anyone shed any light why I keep getting these nginx issues (not sure what nginx is) ?