Jump to content

gekoch

Members
  • Posts

    32
  • Joined

Posts posted by gekoch

  1. 18 minutes ago, ich777 said:

    I've now removed this driver version, please try to install driver version 550.40.07 it is working flawlessly with Plex and Jellyfin on my server.

     

    I will investigate what is causing that and re-upload the driver when I found the cause of the issue.

     

    Great, thx 550.40.07 is working well

     

    Andy

  2. On 2/20/2024 at 5:52 AM, AgentXXL said:

     

    You're not using the correct driver for the T1000. If you go to the Nvidia site and do a search for the latest driver for Linux x64, you'll find that you need to use the 535.154.05 version.

    QuadroT1000Driver.jpg

    QuadroT1000Driver1.jpg

     

     

    When I check the website for the same card I see this driver version:

    image.png.e104146a5cd5c0d48f0b4f5fe72ac38f.png

     

     

    After installing 550.54.14 on unraid 6.12.8 transcoding with emby is not working anymore.

    switching back to 535.154.05 is solving the problem but why?

     

    Andy

     

  3. Hy

     

    It took me several days to figure this one out but I'm still not sure what causes the problem.

    My Setup:

    I have an nvidia T1000 in my unraid server used to transcode movies especialy when using emby. When I start an mkv file with emby it starts transcoding with ffmpeg. On Unraid 6.12.6 this works flawless.

    However after updating to 6.12.8 emby can't transcode it using ffmpeg. Attached two log files. Both with the same movie one with the old and one with the new unraid version.

    In the log file running the new unraid version you can see the error:

    17:25:44.862 [h264_nvenc @ 0x114dd40] Failed locking bitstream buffer: invalid param (8): ~hfE?
    17:25:44.862 Error submitting video frame to the encoder
    17:25:44.872 [libmp3lame @ 0x10c74c0] 3 frames left in the queue on closing
    17:25:45.121 Conversion failed!

     

    I'm not sure what exactly causes the problem so I hope someone can help me....

     

    Thx

    Andy

    new OS 6.12.8.txt old OS 6.12.6.txt

  4. 27 minutes ago, itimpi said:

    No.  That is the current syslog taken from RAM at the time you create the diagnostics and only has entries from after the reboot.  It is not the one from the syslog server which is in the logs folder on the flash drive (assuming you are using the mirror to flash option).

     

    ok thx for the explanation. In an earlier post I did add the syslog file directly from the log file folder.

    So the system is currently running on 6.12.2 for the past 2 hours, fingers crossed ;-)

     

     

  5. As soon as the first new release (6.12) was out I updated to the latest version from 6.11.5 . But just after 2 hours of runtime the server crashed without any reasons so I had to reboot with the reset button on the server itself and tried again. After 5 hours another crash. So I reverted back to 6.11.5. Again with 6.11.5 I had no problems at all for several days.

     

    Then 6.12.1 was released and I thought they might have solved an issue that I had with my setup. So I just did the update and after 2 hours again a crash.... So 6.12.1 is again not stable on my machine but I have no Idea why. The 6.11.5 version was stable for several months without any issue.

    Here is the diagnostic files I took before reverting back to 6.11.5.

     

    Any Ideas?

     

    Thx Andy

    nas-diagnostics-20230625-1934.zip

  6. hy

     

    Just had something weird happen and I hope someone can explain this to me.

     

    My UNRAID system just rebooted without notice. After the reboot my 2 cache protected SSD were not recognized as the correct SSD. The old SSD that I exchanged a few weeks a go were displayed instead. I tried to start the array but the cache protected device was marked as disabled.

    So I stopped the array set the devices to "not installed", started the array, stopped it again and chosen the newer larger SSD and started the array again.

    Now everything is back working as nothing would have happend.

     

    But can someone explain to me what exactly happed. Attached to log files:

    nas-diagnostics-20230510-2149.zip

  7. 7 minutes ago, 7hr08ik said:

    Hey guys, need some help...

     

    Updated the container today. It wont boot up anymore.

     

    I run NordVPN, and everything has been running just fine for the past ... months/years...

    Today I get the following...

     

    2023-03-30 11:33:59.588541 [info] Host is running unRAID
    2023-03-30 11:33:59.616601 [info] System information Linux 6c0837b709c6 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux
    2023-03-30 11:33:59.648620 [info] OS_ARCH defined as 'x86-64'
    2023-03-30 11:33:59.675093 [info] PUID defined as '99'
    2023-03-30 11:33:59.708465 [info] PGID defined as '100'
    2023-03-30 11:33:59.758393 [info] UMASK defined as '000'
    2023-03-30 11:33:59.787916 [info] Permissions already set for '/config'
    2023-03-30 11:33:59.817953 [info] Deleting files in /tmp (non recursive)...
    2023-03-30 11:33:59.852272 [info] VPN_ENABLED defined as 'yes'
    2023-03-30 11:33:59.879422 [info] VPN_CLIENT defined as 'openvpn'
    2023-03-30 11:33:59.908262 [info] VPN_PROV defined as 'custom'
    2023-03-30 11:33:59.944211 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ch337.nordvpn.com.udp.ovpn
    2023-03-30 11:33:59.994356 [warn] VPN confi
    2023-03-30 11:33:59.994416                                              guration file /config/openvpn/*****.nordvpn.com.udp.ovpn remote port is missing or malformed, assuming port '1194'
    2023-03-30 11:34:00.025007 [info] VPN remote server(s) defined as '***.***.***.**,'
    2023-03-30 11:34:00.051578 [info] VPN remote port(s) defined as '1194,'
    2023-03-30 11:34:00.077905 [info] VPN remote protcol(s) defined as 'udp,'
    2023-03-30 11:34:00.107301 [crit] VPN_DEVICE_TYPE not found in /config/openvpn/*****.nordvpn.com.udp.ovpn, exiting...
    
    ** Press ANY KEY to close this window ** 

     

    How can i add VPN_DEVICE_TYPE to the config?

     

    I have tried re-downloading configs. I have tried multiple configs from Nord, and I always get the same response.

    Deleted, and reinstalled the container. Tried with a clean appdata folder (renamed original and allowed it to recreate)

     

    I have the same problem. i had to revert back to 4.5.2-1-01 which solved it for me 

  8. I'm running the latest plugin version but since then some scripts do not get executed regularly.

     

    I have 5 scripts that should run every minute but one of them is mostly running every 2 minutes and sometimes every 1 minute.

    How can we fix this? Before the update the scripts were working as intended...

     

    EDIT: Most of the script set to a minute interval with "* * * * *" are running in a 2 minute interval at best, and the script takes around 0.1 to 2 seconds of run time.

    Even after a restart of the whole system the problem still persist. 

  9. I did just update from 6.11.1 to 6.11.5.

    Ihave a few pip packages running so that the scripts I use can work properly.

     

    In 6.11.1 the paho-mqtt worked flawless.

    Now when i try to install it via pip3 install paho-mqtt I get this error:

    Collecting paho-mqtt
      Using cached paho-mqtt-1.6.1.tar.gz (99 kB)
      Preparing metadata (setup.py) ... error
      ERROR: Command errored out with exit status 1:
       command: /usr/bin/python3 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-q2n_lrtx/paho-mqtt_4bc42d8c1fdd41d2b2b46d5e70e4bfe2/setup.py'"'"'; __file__='"'"'/tmp/pip-install-q2n_lrtx/paho-mqtt_4bc42d8c1fdd41d2b2b46d5e70e4bfe2/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-l0w8az9o
           cwd: /tmp/pip-install-q2n_lrtx/paho-mqtt_4bc42d8c1fdd41d2b2b46d5e70e4bfe2/
      Complete output (11 lines):
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
        File "/usr/lib64/python3.9/site-packages/setuptools/__init__.py", line 18, in <module>
          from setuptools.dist import Distribution
        File "/usr/lib64/python3.9/site-packages/setuptools/dist.py", line 38, in <module>
          from setuptools import windows_support
        File "/usr/lib64/python3.9/site-packages/setuptools/windows_support.py", line 2, in <module>
          import ctypes
        File "/usr/lib64/python3.9/ctypes/__init__.py", line 8, in <module>
          from _ctypes import Union, Structure, Array
      ImportError: libffi.so.7: cannot open shared object file: No such file or directory
      ----------------------------------------
    WARNING: Discarding https://files.pythonhosted.org/packages/f8/dd/4b75dcba025f8647bc9862ac17299e0d7d12d3beadbf026d8c8d74215c12/paho-mqtt-1.6.1.tar.gz#sha256=2a8291c81623aec00372b5a85558a372c747cbca8e9934dfe218638b8eefc26f (from https://pypi.org/simple/paho-mqtt/). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
    
          
    ERROR: Could not find a version that satisfies the requirement paho-mqtt (from versions: 0.4.90, 0.4.91, 0.4.92, 0.4.94, 0.9, 0.9.1, 1.0, 1.1, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.3.1, 1.4.0, 1.5.0, 1.5.1, 1.6.0, 1.6.1)
    ERROR: No matching distribution found for paho-mqtt

     

    Apparently the Distro changed from 6.11.1 to 6.11.5...

     

    Andy

  10. 3 minutes ago, Kilrah said:

    I think I got that working. 

    If you specify PUID/PGID environment variables those will be used in the container. Note that it will take ownership of the entire appdata folder and contents, since Arduino IDE stores all its config and libraries there it needs to be able to access them. 

    I would still recommend making copies of the sketches into the folder instead of building a whole environment in random folders.

     

    ok thx will try it

  11. yes I've done that, first it seemed to work without problem but as soon as I throw some "load" to the VM it crashed UNRAID the same way as with the "OLD" VM. 

     

    EDIT:

    Now even starting the VM lets UNRAID crash, not responding to a reboot nothing need to pull the power plug

×
×
  • Create New...