ceyo14

Members
  • Posts

    140
  • Joined

  • Last visited

Posts posted by ceyo14

  1. 10 minutes ago, ceyo14 said:

     @Marzel So I couldn't connect to the docker and saw that it updated... this changed the port again to 5000. how can I prevent this from happening?

    ok, I figured it out... instead of extra parameters or post arguments, you need to add a Variable... there I put the following.

     

    image.png.b781cb383e95f5d709888427e1ce4f4b.png

     

    In case someone needs this, or me in the future.

    • Thanks 1
  2. On 4/16/2023 at 5:51 PM, ceyo14 said:

    @Marzel Can you please change the ENV to the Unraid template instead of the image? I assign an IP address to the Docker and I would like it to listen to port 80 and not 5000. I can change it using Portainer but I have to recreate the docker and I am worried about updates...

     

    ASPNETCORE_URLS            http://*:80

     @Marzel So I couldn't connect to the docker and saw that it updated... this changed the port again to 5000. how can I prevent this from happening?

  3. Thanks for posting this, I had been using ipvlan without issue with Untangle and OPNsense, but recently switched to Sophos XG and it immediately had issues with it, I changed it to macvlan and have had no further issues but remember I switched to ipvlan for a reason, I mean I can't remember why now but I was curious why Sophos didn't like ipvlan... but this seems like a much better option regardless.

  4. @Marzel Can you please change the ENV to the Unraid template instead of the image? I assign an IP address to the Docker and I would like it to listen to port 80 and not 5000. I can change it using Portainer but I have to recreate the docker and I am worried about updates...

     

    ASPNETCORE_URLS            http://*:80

  5. On 2/1/2023 at 6:30 AM, dada051 said:

    Here, manual patching without script, is it OK?

    I believe it was stated that on reboot it gets overwritten, hence why it says not to use scripts. so if you changed it manually you can just install this plugin so it will do it for you and stop once you upgrade as it is made to work up to version 6.11.5 and not anything newer.

  6. On 7/29/2022 at 4:10 AM, ich777 said:

    No, I don't will maintain it any further because such a "toxic" Docker shouldn't exist in the CA App that can crash the whole server and prevent the whole server from running correctly even after a restart.

    I understand, can I ask that you undeprecate the agent? I was able to use another docker and it seems to be working so far. but obviuosly I get the mmessage about it being deprecated and I am guessing if I remove it I won't be able to re install the agent...

  7. On 8/8/2022 at 3:37 AM, JorgeB said:

    Problems with the flash drive, try a different USB port, and make sure it's USB 2.0, not 3.0

    I haven't had any further lockups yet... it's been up 7 days and I plan to change some hardware so if anything I will open another thread if needed. thanks for your help.

    • Like 1
  8. 13 hours ago, JorgeB said:
    Aug  5 23:01:33 NAS kernel: macvlan_broadcast+0x116/0x144 [macvlan]
    Aug  5 23:01:33 NAS kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

     

    Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)).

    ok, I just fixed that, hopefully it improves stability.

     

    This is something else that is happening lately, this is the output when trying to boot, the reason sometimes after the second boot it comes up. (what I mentioned above about it refusing to boot)

     

    image.png.ee3801a901802717fb4924e6e2cdbc70.png

     

    Including fresh logs and diagnostics... not sure if it helps.

     

    Thanks a lot for the help.

    nas-diagnostics-20220807-1931.zip syslog

  9. On 8/3/2022 at 1:31 AM, ChatNoir said:

     

    I still see this message :

    Aug  2 18:03:29 NAS root: Fix Common Problems: Warning: The plugin check_mk_agent.plg is not known to Community Applications and is possibly incompatible with your server

     

    that is for the plugin, it was already installed but it appears to have been deprecated... I left it to use with the new docker. it is working.

    syslog

  10. On 7/30/2022 at 10:07 PM, ceyo14 said:

    ok, I enabled the Mirror to Flash Option, will reply when it crashes again.

     

    FYI I replaced a deprecated CheckMK docker from CA and installed one from the DockerHUB. only change, this was performed today, hopefully this is irrelevant.

     

    ok, today it locked up but was able to sort of login through the IPMI, sent reboot through the Terminal but it didn't respond, sent cold boot and it started normally... I do see the Parity drive is reporting issues, I am looking to replace it, Parity Check started but was going at 13MB/s... so I canceled it.

     

    Please let me know if there is anything else.

    nas-diagnostics-20220802-1814.zip

  11. On 7/29/2022 at 4:32 AM, JorgeB said:

    Enable the syslog server and post that after a crash.

    ok, I enabled the Mirror to Flash Option, will reply when it crashes again.

     

    FYI I replaced a deprecated CheckMK docker from CA and installed one from the DockerHUB. only change, this was performed today, hopefully this is irrelevant.

  12. On 7/18/2022 at 1:12 AM, ich777 said:

    I think you are talking about the Checkmk-RAW container.

    On what Unraid version are you?

     

    This is the output from a fresh pulled container from the CA App:

      Reveal hidden contents
    text  error  warn  system  array  login  
    
    ### CREATING SITE 'cmk'
    Adding /opt/omd/sites/cmk/tmp to /etc/fstab.
    Going to set TMPFS to off.
    Preparing tmp directory /omd/sites/cmk/tmp...Generating configuration for core (type nagios)...
    Precompiling host checks...OK
    Updating core configuration...
    Executing post-create script "01_create-sample-config.py"...OK
    Adding /opt/omd/sites/cmk/tmp to /etc/fstab.
    Going to set TMPFS to off.
    Created new site cmk with version 2.1.0p6.cre.
    
      The site can be started with omd start cmk.
      The default web UI is available at http://7e9bd108ff7f/cmk/
    
      The admin user for the web applications is cmkadmin with password: eibBNKpS
      For command line administration of the site, log in with 'omd su cmk'.
      After logging in, you can change the password for cmkadmin with 'htpasswd etc/htpasswd cmkadmin'.
    
    ### STARTING XINETD
    Starting internet superserver: xinetd.
    ### STARTING SITE
    Preparing tmp directory /omd/sites/cmk/tmp...Starting agent-receiver...OK
    Starting mkeventd...OK
    Starting rrdcached...OK
    Starting npcd...OK
    Starting nagios...OK
    Starting apache...OK
    Starting redis...OK
    Initializing Crontab...OK
    ### STARTING CRON
    ### CONTAINER STARTED

     

     

    Maybe try the following:

    1. Remove the container
    2. Remove the directory that was created in your appdata folder for checkmk
    3. Pull a fresh copy from the CA App

     

    Scratch that, after installing it on my server, I couldn't stop the container and also couln't remove it. I've then restarted my server and Docker and emhttp weren't working properly anymore. After starting the Docker service manually the container auto started but I've never enabled that, I had to remove the image for the container itself manually to get everything back to a working state.

    I pulled both the Checkmk-RAW and Checkmk Agen plugin from the CA App because they gave me both a lot of trouble in the past and I really want that this happens to someone which is not that familiar with the command line and how to remove a Docker image manually...

    Will you still work on this?, Or do you think that at this point you will not continue supporting CheckMK?

     

    I always wanted to get this running but haven't had much time to get it to work. I mean actually using it... it ran if I stayed away from 2.0

     

    I understand whatever your decision is, not expecting anything, just wondering...

  13. I need some help identifying this, I have seen the server refuse to boot giving something about a USB device, it says sda which is the unraid flash drive, I checked it on a windows PC and it didn't find any errors and another reboot usually worked. today it locked up again but it booted up in the first try after a cold boot, but this time the parity drive threw a Helium error which I have never seen but just appeared.

     

    FYI I run my router in a Nested VM so it boots without internet.

    nas-diagnostics-20220728-2246.zip

  14. On 7/8/2021 at 4:11 AM, ich777 said:

    Can you try to reinstall the container with this tag again:

    grafik.png.4bb37155858ff9adbe56a78b4404c9bc.png

     

    The creator from the container updated it yesterday again and I think it should now work.

     

    ok, I just reinstalled, hopefully it goes better, not an issue with this docker stopped so it is definitely something with it.

     

    I will update if I have more issues.

    • Thanks 1
  15. 9 hours ago, ich777 said:

    This is really strange, I don't get it why it works on some systems and on some not...

    Also this is very unlikely that a Docker can hang the whole server, since this shouldn't happen anyways, I only can think of a filesystem problem or something similar when mounting the path.

     

    Just as an alternative, if you follow this step by step you should be ready to go in about 5 to 10 minutes and you will have full monitoring over your whole server if this is something you can work with.

     

    Also another benefit would be that this is completely customizable...

    it doesn't actually lock up the server, what doesn't work that I can tell is the WebGUI, obviously the Checkmk Docker and for some reason if I try and pull diagnostics using SSH, it freezes and never completes....

     

    VMs and other docker still work though

  16. 28 minutes ago, ich777 said:

    Oh I thought this where instant lockups...

     

    If you want to upgrade to 2.0 simply append this to the repository: ':2.0.0-latest' (without quotes) like so:

    IMG_20210704_070250.thumb.jpg.cf62996f82ede7d2c83f7bb7e94b5e04.jpg

     

    its the WebGUI and that docker that lockup... webgui I get a 500 error, docker just stays loading....

     

    I just got it again after upgrading to 2.0...

     

    28 minutes ago, ich777 said:

     

    Have you already seen that I've released Prometheus plugins for monitoring unRAID eventually this would be an alternative:

     

     

    I will have to check this out.

  17. 5 hours ago, ceyo14 said:

    ok, just made the changes and started the docker... For reference I have 4 day 4 hours of uptime currently...

     

    let see how it goes...

    I think that helped, before it would be pretty quick to lockup... its been a few hours and I've been able to use it so I think we are good.

     

    so how do I update to the new 2.0 version?

  18. On 6/30/2021 at 1:25 PM, ich777 said:

    I tested it now on a new set up 6.9.2 machine and have no problems (can you try to turn on the advanced view in your Docker template and remove '--ulimit nofile=1024' at extra parameters):

    grafik.thumb.png.68819de49f2e7324e4bd817d32d0de22.png

     

    Please report back if it works for you.

    ok, just made the changes and started the docker... For reference I have 4 day 4 hours of uptime currently...

     

    let see how it goes...

  19. of course, its not like I am paying you... lol

     

    obviously I understand that with so many things on my server it may work for you and I have something else that "bothers" it...

     

    Let me know how it works for you to then see what we can try on mine. if anything write a PM to check this out more in depth.

    • Like 1
  20. 33 minutes ago, ich777 said:

    This is also happening for v1.5.0?

    I have to look into this after the weekend, I will setup a completely fresh installed test server where I can test this.

    Are you on Unraid 6.9.2?

     

    yes on 1.5.0, have not changed to 2.0.0

     

    I am running 6.9.2 and a bunch of other things...

     

    not sure if these help, but I am including diagnostics as of now, working normally... without the checkmk docker running

    nas-diagnostics-20210618-1338.zip

    • Like 1