Dro

Members
  • Posts

    53
  • Joined

  • Last visited

Posts posted by Dro

  1. 4 hours ago, alturismo said:

    did you try to fix the error you see ?

     

    image.png.5b6286d8eefd691af040ff10a1e4df03.png

     

    may the faulty setup works on the "old" version, but rather try setup your mounts properly ?


    What you see in the screenshot is not how the actual mounts are setup. Plex works fine prior to updating the OS so the issue is something with the Plex container and unRAID 6.12.7-rc2. On 6.12.6 the Plex container is using the latest update and this issue doesn’t happen. Not sure where the bug is but it seems to think the mounts are using : but if you look at them they are how they are supposed to be. 

  2. Help! Updated Plex, it Orphaned the Image. Trying to add the container back and this is happening. Seems something is broken with the latest?

     

    EDIT: Well, it appears the issue is related to unraid Version 6.12.7-rc2

     

    I downgraded, now the plex container works.. Looks like the latest Plex update doesnt play nicely with it.


    image.thumb.png.ffeeef4c6b0276efa4f8770a557061ee.png

  3. 1 hour ago, JorgeB said:

    There are multiple call traces related to the NIC, also if the server is rebooting by itself, vs. crashing or hanging, that usually always suggests a hardware problem.


    the server has 2  dual port 10gb NICs as it was used at one point as an iscsi datastore for ESXi into a Zfs pool basically had its own iscsi network isolated for that purpose. It ran like that without any issues and worked great. 

     

    I believe the server is just rebooting. Not hanging or technically crashing. Can you tell which NIC it may be? Could a bad DAC cable also cause this? 

     

     

     

  4. 1 hour ago, JorgeB said:

    You just need to post the syslog from wherever it's being saved to.

    Ok, i cleared the log, will wait for a reboot so we don't have a lot of old information. So far server has been up for 5 hours.. I have Zabbix monitoring everything so ill get alerted right away when the server restarts. Will post the time it happens and provide the syslog along with it.. appreciate the help.

  5. I do have syslog enabled. And it is copying the file to disk. I figured if that was set running diagnostics would pull that file. But good to know it doesn’t. How would you like me to provide the syslog file from the one that is saved? Is there a specific method? I do not have the mirror to flash option enabled. Just a local syslog directory that the file is stored. Will that suffice?

  6. Hello,

    Having issues with my server.. Server has been stable for quite awhile (its all mostly new hardware within the year) then all of a sudden I started getting random, daily reboots, usually every 24hrs. Now today it has been happening almost every 20 minutes.. Its driving me crazy.. Usually when I run stable for awhile then start seeing reboots I replace the USB drive. This has already been done and i'm still having the same issues. I'm also already set on IPVLAN

     

    v 6.12.6

     

    Here are the things ive done

     

    Checked File System

    Installed brand new USB thumb drive

    Ram Memtest
    Double Checked IPVLAN

    Went through the logs myself the best I could. I do some suspicious things maybe related to the NICs but I am not sure.

    This is all 10gb SFP+ multiple 10gb NICs

    Again, this current configuration has run just fine. So i am not sure what has all of a sudden started happening.

     

    Attached is the diagnostic logs.. Looking for any direction Thank you!

     

    mdronet-unraid1-diagnostics-20231230-2055.zip

  7. anyone have issues setting up a minecraft java server? I keep getting connection refused no matter what. It's driving me crazy. Everything appears to be setup properly. If i use another docker container with just a backend minecraft server i can connect to that server using the same exact settings i am using in AMP with zero issues.. If i then remove that server, then try to set it up in AMP i cannot connect.. So i know its not something simple like a firewall problem.. Any advice on whatelse to check? I've spent hours trying to figure this out.

  8. Same issue here.. Random disconnects from the network. Rebooting is the only thing that brings the server back online. Not sure if this is the cause or not. It's about the only thing I am seeing in syslog. Then it may last for 6-12 hours then disconnect again.

     

  9. On 5/3/2022 at 10:06 AM, Squid said:

    Delete the .txz from /config/plugins/snmp (or whatever the folder is)

     

    Reboot

     

    If the .txz does not re-appear in the folder after rebooting then the author now knows why its failing to reinstall on a reboot.

     

    I just performed this step. Deleted the .txz, rebooted, the .txz did NOT comeback.. This is on 6.10 rc3 now.. Latest update...

    Only way the .txz is coming back is if I go into apps, search for SNMP, Install.. Then it shows up again and my SNMP works..

  10. For me the issue is not that it won’t install. I have zero issues installing it. It’s just that when I reboot the server the SNMP app is no longer present. I know this because zabbix throws an alert about “no snmp data collection” I go to check and sure enough snmp is missing. I reinstall it, everything comes right back up and I’m good to go. If I reboot again, same issue.  Rinse, repeat. I’m getting no errors on anything that I’m aware of.  I’m on the latest RC

     

    Im glad to do any kind of testing or log gathering. Let me know what kind of information is needed. 
     

    Thanks

  11. On 4/2/2022 at 11:13 AM, BigJuanKer said:

     

    Which worked perfectly until the next reboot :(

     

    I'm currently waiting for 6.10 to get out of RC and into stable and then i'll try again.

    Yep, same. I just reinstall it everytime I need to reboot. Oh well. I use snmp for zabbix. So if I forget it at least reminds me of no snmp data. 

  12. On 2/28/2022 at 9:24 AM, BigJuanKer said:

    Sorry for the delay, I have not been getting notifications of replies to this topic and check in today "just in case"!

     

    On the only system I can reboot easily at this time I have now successfully installed the SNMP plugin.  I needed to remove the plugin from the "failed plugins tab", goto /boot/config/plugins and manually delete the snmp directory and all it's contents, reboot and then install the plugin through the app store as normal.  This completed without issue and even gave a good output during the log.  I have not included it as it will not tell you anything.

     

    However, on Thor, I have not been able to reboot, but removed the failed plugin, deleted the /boot/config/plugins/snmp directory and then retried installation.  I received the following log:

     

    plugin: installing: https://raw.githubusercontent.com/kubedzero/unraid-snmp/main/snmp.plg
    plugin: downloading https://raw.githubusercontent.com/kubedzero/unraid-snmp/main/snmp.plg
    plugin: downloading: https://raw.githubusercontent.com/kubedzero/unraid-snmp/main/snmp.plg ... done
    plugin: downloading: https://raw.githubusercontent.com/kubedzero/unraid-snmp/main/packages/perl-5.32.0-x86_64-1.txz ... done
    
    +==============================================================================
    | Skipping package perl-5.32.0-x86_64-1 (already installed)
    +==============================================================================
    
    plugin: downloading: https://raw.githubusercontent.com/kubedzero/unraid-snmp/main/packages/libnl-1.1.4-x86_64-3.txz ... done
    
    +==============================================================================
    | Skipping package libnl-1.1.4-x86_64-3 (already installed)
    +==============================================================================
    
    plugin: downloading: https://raw.githubusercontent.com/kubedzero/unraid-snmp/main/packages/net-snmp-5.9-x86_64-1.txz ... done
    
    +==============================================================================
    | Skipping package net-snmp-5.9-x86_64-1 (already installed)
    +==============================================================================
    
    plugin: downloading: https://raw.githubusercontent.com/kubedzero/unraid-snmp/main/packages/unraid-snmp-2021.05.21-x86_64-1.txz ... done
    
    +==============================================================================
    | Skipping package unraid-snmp-2021.05.21-x86_64-1 (already installed)
    +==============================================================================
    
    
    +==============================================================================
    | Testing SNMP by listing mounts, /boot should be present
    +==============================================================================
    
    snmpwalk -v 2c localhost -c public hrFSMountPoint
    snmpwalk failureCouldn't find /boot mount point. SNMP output:
    Timeout: No Response from localhost
    plugin: run failed: /bin/bash retval: 1
    
    Updating Support Links
    
    
    
    Finished Installing. If the DONE button did not appear, then you will need to click the red X in the top right corner

     

     

    I will get a chance to reboot Thor in the next few hours and will report back once I have tested it again.

     

    I have now been able to reboot Thor and it also worked.  Deleting the /boot/config/plugins/snmp folder seems to be the key.  Once it downloads EVERYTHING again it seems to work.

     

    I have a third server to try but see no reason why I should not have success there also. 

     

    Thanks for the help :)

     

    Same issue here i reboot and poof, gone.. I gather from this, delete snmp folder, reinstall, issue is fixed?

     

  13. As I've mentioned I had already gone through that previous thread and applied all the suggestions none of that has helped. Is it being suggested that I need to change my hardware based on that thread? When no hardware is actually plugged into the slot that is throwing the error?

  14. Hello,

    I've been dealing with this issue for awhile and i still can't seem to resolve it. Anyone know how to fix it?

    My BIOS has been fully updated to the latest version, I don't have any devices plugged into the PCIE slot in question with the issue. I have also appended this in my syslinux.cfg file as found in another support thread. pci=nommconfto to try to just ignore the error all together and it still hasn't helped. It seems the device in question is in one of the screenshots below.. I have also disabled all power management. I never used to have this issue, nothing has really changed it just started happening randomly about a month or so ago and hasn't stopped since. The only PCIE devices I have are a dualport solarflare 10gb SFP+ NIC and a LSI 9211-8i HBA.

    Motherboard is ROG STRIX Z370-H GAMING BIOS 2603

     

    Screenshot 2021-08-30 081933.png

    Screenshot 2021-08-30 082021.png

  15. All of a sudden now I can no longer get into Ombi. I am using my plex username and password. I tried to research this issue for quite awhile and ran a few potential fixes myself but still can't seem to figure out what is happening. Everything is completely updated to latest version, all docker containers and unraid. Any idea how to resolve this? Logging into Plex works fine with the same username/password. I do have 2FA setup but I have had it setup the first time it became available and have had no issues with Ombi. This just started this week.. My 192.168.1.193 is the workstation I am trying to login from and the other is my gateway but I am not sure what it means when it tries to authenticate from that IP. I am trying to login from the same location each time on the same PC.

     

    Also, inside plex I do not see any OMBI devices. I was hoping I could just remove it and have it generate a new token. But it's not there.

     

     Thank you!
    image.thumb.png.f8aa833c6f6c6727b56ed43a1afc6d77.png
     

  16. On 8/29/2020 at 11:32 AM, ich777 said:

    If someone is experinced in webdesign and can help me out it will be soon... :D

     

    Edit: I've written two manuals how to create a iSCSI target on Unraid for the time.

    Shouldn't be that hard to do it that way fir the time.

    Only a few commands.

    Sorry if I missed it, can you share the manual? I want to try to setup unRAID as an ISCSI target for an ESXi cluster using multiple SSD pools/MPIO