Jump to content

ADvorsky

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by ADvorsky

  1. The container stops with the following log output after the first sync run:
     

    Attempting to perform a database vacuum to optimise database
    Database vacuum is complete
    core.time.TimeException@/usr/lib/ldc/x86_64-linux-gnu/include/d/std/datetime/systime.d(9101): Invalid ISO Extended String: 2024-Sep-19 17:22:58.440
    ----------------
    ??:? [0x55e4b1223da5]
    ??:? [0x55e4b1220a31]
    ??:? [0x55e4b1220692]
    ??:? [0x55e4b1246eef]
    ??:? [0x55e4b1246f5d]
    ??:? [0x55e4b123660e]
    ??:? [0x55e4b122d6e7]
    ??:? [0x55e4b122cb8a]
    ??:? [0x55e4b12bde1a]
    ??:? [0x55e4b12bb54e]
    ??:? void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int function(char[][])*).runAll() [0x14a210b9db7b]
    ??:? _d_run_main2 [0x14a210b9d995]
    ??:? _d_run_main [0x14a210b9d7ed]
    ??:? [0x14a21081c249]
    ??:? __libc_start_main [0x14a21081c304]
    ??:? [0x55e4b1202100]

     

  2. 9 hours ago, mihcox said:

    This did not help, after formatting it like the below, it was deleted after rebooting.

    Yes, it vanishes on my system as well after each reboot, but the nics are present as configured in the file. Without the file present during boot the 10gb nic is not available.

    That's why i have a copy of that file to recreating it after each reboot on array start ;)

  3. I had a similar issue including the vanishing network-rules.cfg after each restart...
    (btw, for this everybody replying to a previous thread of mine insists i have something installed that removes it, which is actually not the case. i still think that its unraid itself removing the file due to reasons during startup after reading it.)
    The machine has 2 NICs, the onboard (which whyever cannot be disabled in the bios) and the 10GBit Nic

    Here is my network-rules.cfg:

    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="e4:1d:9c:92:ce:44", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="22:48:5c:05:16:45", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
    

    It is merely to make sure the 10GBit is eth0 because Unraid has some special handling for eth0 as we all know...

    As well, I made sure its there before restarting the server (user script just writes it to /boot/config each hour ;) )

    hope this helps you as well ;)

  4. just for your info.... tailscales magic dns might break your docker containers.

    /etc/resolv.conf gets copied to all freshly started contaieners from the host, which points to a dns not existing inside the container...

    disabling magic dns resolved this issue.

  5. 1 hour ago, dlandon said:

    Some users are reporting an unresponsiveness issue potentially related to UD.  I cannot reprodice the issue and would need to Team Viewer into someone's server to troubleshoot.  Anyone willing to let me access their server so I can figure this out, please PM me so we can make arrangements.

     

    After uninstalling and re installing a lot of plugin and nothing changed....

    I just cleared all browser data, cookies, etc... 

    And voila... it worked again 🤦‍♂️

     

    So for everyone having issues this kind, dont be as stupid as i was... Just do the same and clear your browser data... :) 

×
×
  • Create New...