Posts by Nick0

  • Fans on all of the time.

    Quote from fbeye

    Is there a separate Ethernet Interface on the back of the server for IDRAC? Mine has that and that is how I access my iLO [Your DRAC]. If so, connect it to your Switch and it should obtain an IP, or through your bios there should be a DRAC or configuration to set an IP or DHCP.

    Hi there,


    There is no extra ethernet port on the machine, so I am guessing it is without IDRAC. I do have the BMS (Board Management System) though.

  • Fans on all of the time.

    Quote from fbeye

    I have HP Proliant DL380 G9 and DL380G10 Rack Servers at home and HP uses iLO/ Bios configurations. Mine by default was set to 90% Fan Speed, usually per spec for a legitimate small room enclosure where high data being processed but at home, yeah, no. So over some days I played around and set the Fan Speed MINIMUM [It can go higher if system demands it] but at least it can settle to 61% and lemme tell ya, it stays at 61% and is way quieter.. Maybe just a function of your server until you modify?

    Thank you for this - I think that this machine should be able to run on default settings as I have an identical machine doing just that. Good stuff to know though, so I appreciate the information :)

  • Fans on all of the time.

    Hello and many thanks.


    sensors

    and ipmitool dsr list gives me an issue with fan 3, reporting speed at 0 rpm, bit it is running full tilt, so that's not right.

    If I run System Services (F10 during boot), I get to the graphical Unified Server Configurator, where I have run Hardware Diagnostics, which pulls up an issue with Fan 3, like this:



    Ctrl-E during boot launches the BMC Configuration Utility, where I can view event the System Event Log, where I find lots and lots of errors like this:



    There are also similar errors for the other 2 fans.


    My BIOS is listed as the latest for the Poweredge R210 II, 2.10.0, but I don't get how I can access IDRAC or find it's version.


    Thanks,

    Nick.

  • Fans on all of the time.

    Quote from raulfg3

    not related to OMV, please google a bit about this problem on Debian.

    Hi there,


    Thanks for your reply.


    I'm not suggesting this is OMV-related, I just wondered can this be investigated through the logs that OMV generates and that they might be able to be used to narrow down the issue. I do have an identical server running nicely, so I know there's a problem here somewhere other than incompatibility between the hardware and OMV / Debian.


    I shall go and see what I can find related to Debian.


    Thanks for your help.

    Nick.

  • Fans on all of the time.

    Hello all,


    I have a fresh installation of OMV running on a Dell Poweredge R210 II server. I have noticed that all the internal fans are running at high speeds, all the time. Looking inside I saw that one fan wasn't working so I have replaced that one and it now works. Still I have the issue of the fans running at full speed all the time.


    How would I best go around troubleshooting this? The inside of the case is dust free, heat sink included. The CPU has a pretty good covering of thermal paste, too.


    Not sure where to start here at all, so any advice gratefully received, as usual.


    Thanks,

    Nick.

  • .env file not foumnd when using Compose plugin.

    EDIT: This appears to be working now - I am not sure why! I will leave open in case this happens again before the whole thing is up and running.


    Hello all,


    I am getting this error when checking my compose file / env file in the Compose plugin.


    env file /srv/dev-disk-by-uuid-c2a977a3-533c-4f40-a677-069261ea1301/compose/endurain/.env not found: stat /srv/dev-disk-by-uuid-c2a977a3-533c-4f40-a677-069261ea1301/compose/endurain/.env: no such file or directory


    The compose file is saved as "endurain" and the I reference the .env file in that compose file as "endurain.env"


    Thank you,

    Nick.

  • Postgres authentication error using Compose plugin

    Quote from ryecoaaron

    You are doing it different since you took the env_file param out of the compose file. You can add it back. The .env file will just be named immich.env (or whatever you named the compose file).

    Thank you for spotting that, ryecoaaron - I'm not even sure why I removed that! Good to know how the .env file is named, too and it's all working now thanks to you. I also learned about environment variables :) Thanks again for helping me to fix this - just the 15,000 photos to migrate manually now :O

  • Postgres authentication error using Compose plugin

    Quote from ryecoaaron

    I don't use immich but it looks like the container doesn't have the postgres password and you aren't passing the postgres password to the immich container in the compose file. As I mentioned before, when you use the env_file parameter in a compose file, it automatically passes all values in the env_file to the container. You need to manually pass the environment variables to each container that needs them. While this may seem like extra work, it is better in my opinion because you aren't passing environment variables to container that don't need them.

    Many thanks,


    So, does this mean that I should add:

    Code
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}

    to the part of the compose file that deals with the container_name: immich_server, right at the top (line 13)? Is this what you mean by: "manually pass the environment variables to each container that needs them."?


    I was under the impression that the variables at the bottom of the compose file were used for the whole file, but is it really the case that they also need to be added to the part of the compose file that has the container that will be calling for them? Sorry, I am probably not explaining this very well!


    If I try adding POSTGRES_PASSWORD: ${DB_PASSWORD} like this:

    Code
    services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    # extends:
    #   file: hwaccel.transcoding.yml
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    volumes:

    ... I am still getting the same error.


    So, it seems that I am still not understanding this. I did rum immich up without the compose plugin and it worked (this was with the compose and .env file in the same folder and using the docker-compose up -d command, so I am thinking the current problem means that things need to be done differently with the plugin.


    Thanks,

    Nick.

  • Postgres authentication error using Compose plugin

    Hello all,


    After some help here with including my environment variables in the Compose plugin, I am back with another issue. When pressing 'up' in the plugin, with my compose and variable files added and correctly edited, I get this error:


    "PostgresError: password authentication failed for user "postgres""


    The odd thing is that I have already run this application outside of the Compose plugin, and it worked. I can't understand what might be wrong but the logs would definitely suggest a postgres authentication error. The default password for postgres is "postgres", i have changed mine to a 20 character string of upper, lowercase letters and numbers (no special characters).


    Logs from the troublesome container are here and my compose file and environment variables are below:


    Compose:

    Environment variables:

  • Compose Plugin enviroment field.

    No, you are great at explaining - I get it now. Thanks for bearing with me! Check is looking much better.


    Nick :)

  • Compose Plugin enviroment field.

    Quote from gderf

    You need to post compose and environment files in code boxes. They way you have posted them here removes all the required formatting making them impossible to debug - to the point that many will not even look at them.

    Thank you and entirely rewritten for clarity.

  • Compose Plugin enviroment field.

    Hello ryecoaaron,


    Many thanks and apologies for forgetting the compose! Please see below for examples:


    Compose file:



    env file:



    So, I delete

    Code
    env_file:
      - .env


    from the compose file (2 instances),and add the following to under environment (in the docker file)


    Code
    UPLOAD_LOCATION
DB_DATA_LOCATION
TZ
IMMICH_VERSION
DB_PASSWORD


    then in the environment box, I put:


    Code
    UPLOAD_LOCATION=${value}
DB_DATA_LOCATION=${value}
TZ=${value}
IMMICH_VERSION=${value}
DB_PASSWORD=${value}


    Is that right? It looks to me like the ${values} belong in the compose file (these files are examples from Immich).

    Thank you, Nick.


    I have re-written this considering @ryecoaaron's post below.

  • Compose Plugin enviroment field.

    Hello all,


    I am running an up to date version of OMV Version 7.7.17-1 (Sandworm) and trying to install Immich via Docker and using the Compose plugin.


    I have installed many times using the plugin with no issues at all, but this time I have a question regarding the environment box below the file bow (where you usually paste your Docker Compose file).


    When installing Immich through a terminal, it asks that you place the compose and environment files, docker-compose.yml and .env in the immich-app directory before running docker compose up -d.


    This works as you'd expect and the application is ready soon after at http://local:2283.


    So, using the Compose plugin, I am pasting the contents of the docker-compose.yml file in the "File " field and the contents of .env in the "Environment" field. When checking before using the "up" button (docker compose up -d), or checking the file, I am getting this error message:


    Code
    env file /srv/dev-disk-by-uuid-12e915d2-077d-412b-9876-a2ff94c50866/compose/immich/.env not found: stat /srv/dev-disk-by-uuid-12e915d2-077d-412b-9876-a2ff94c50866/compose/immich/.env: no such file or directory
END OF LINE


    Obviously, I am misunderstanding things here so can someone point me in the right direction, please?


    thank you,

    Nick.

  • docker-ripper error.

    EDIT#1: Just used your one and it looks like its working fine. Will update later on.


    EDIT#2: All looks good. I just ssh'd in and it looks like its ripping away nicely. Thanks!


    OK, sorry - here is my latest stab at it:


    Hopefully this isn't totally wrong.

  • docker-ripper error.

    Ah, thanks ryecoaaron - I did try that but I get the same error: