Jump to content

dhstsw

Members
  • Posts

    103
  • Joined

  • Last visited

Posts posted by dhstsw

  1. Hi,

    As said, no chibisafe-server container in CA (and, in the while, even the "old" chibisafe template went dark, no traces of it).

    There's the one in hub.docker.com, and that's the one i tried to use.
    Only that there's no documentation of it (at least, i didn't find one).

    so:

    Quote

    1. Create docker network - "docker network create NETOWK"

    Ok.

     

    Quote

    2. Install chibisafe-server put it in the docker network you create and change SERVE_UPLOADS_FROM variable to your IP example "http://192.168.0.100:24424"


    Yes, but wich other variable is involved? Wich port should be redirected to wich port?
     

    Quote

    3. Install chibisafe put it in the docker network you create


    Yes, but what about the template variables?
    The docker port 8000, redirected to 24424, how should be configured?
    Should the other variables be left alone?

     

    Quote

    4. Unraid CLI "wget -O /mnt/user/appdata/chibisafe/Caddyfile https://raw.githubusercontent.com/chibisafe/chibisafe/master/Caddyfile"

    Ok.
     

    Quote

    5. Install chibisafe-caddy and use it to access chibisafe


    So, i guess chibisafe-caddy doesn't need to be included in the custom network.
    I hope so, cause the "old" chibisafe is already included in a custom networek shared with SWAG (to be accessible through a domain from outside).
    Also, what is exactly the "BASE_URL:"?

    thanks.


     

  2. 23 hours ago, A75G said:

    Okay i have added Chibisafe requirement for 6.0 when running it you will require to install three containers

    chibisafe_server
    chibisafe-caddy

    chibisafe

     

     

    Thanks, but atm in CA the only chibisafe avaiable is the caddy:
    image.png.234c27d44fbcdd1772b9be0206e6e9ca.png

  3. Hi,

    Chibisafe after update to 6.0.0 (and 6.0.1) isn't working anymore with the current template.
    In the logs i see it makes itself avaiable in docker port 8001 (instead of 8000): redirecting a port to that 8001 loads a chibisafe page but seems to be unable to connecto to its server.

     

    In the official GIT it says that migration from 5.x.x to 6.x.x is handled automatically but it doesn't seems the case.


    Any idea?

     

    BTW: downgrading to previous 5.x.x version works.


    thanks,

     

  4. Tried to configure the container with the following variables (taken from https://github.com/zurdi15/romm/blob/release/examples/docker-compose.example.yml ):

    SCHEDULED_RESCAN_CRON value 30 13 * * *

    ENABLE_SCHEDULED_UPDATE_MAME_XML value 5 13 * * * 

     

    Starting the container it still reports default values:
    image.png.a8ed82e8b418d9b9bb7d984c01a8514d.png

    And after a while crashes.

    Removed them, it starts. I force a new scan, it starts finding some 3do roms then all it found dishappears, looks like it's till scanning (but it'sshowing it only if i check the logs), no files added to "library", quite a lot of those:

    ERROR:      [RomM][2023-12-24 21:30:36] 400 Client Error: Bad Request for url: https://api.igdb.com/v4/covers/
    ERROR:      [RomM][2023-12-24 21:30:37] 400 Client Error: Bad Request for url: https://api.igdb.com/v4/screenshots/
     

    I guess i'll keep it there until some problems have been ironed out.

     

    Thanks for the work so far.

     

  5. 29 minutes ago, ich777 said:

    This is really strange radeontop is just a binary and eventually loads the module on boot if it‘s not already loaded (which it should be).

     

    Do the fans start to spin when you visit the dashboard or when you call radeontop? Or when do the fans start spinning?

    The Dashboard also calls radeontop if you got GPUStatistics installed.


    starting with the computer turned on:

    -No fans.
    -Unraid prompt for selection (with or withour guy/safe mode).
    -After a while, during loading, the fans spin to max then stop immediately;
    -text on video switched from low res to high res;
    -Fans tun on after a while, and like, a minute after turn off.
    -Just before Unraid finishes loading (and showing prompt to login) fans start again at mid level;

    after this, they may turn off for a while and then start again (and stay on).

    (a little clarification: the internal of the computer isn't hot and the gfx card is doing basically nothing).

    -Loading a VM (with gfx card passthrough) ends this behaviour, until its stopped. Then the fan starts again.
    -Removing the radeontop, this behaviour ceases.

    Also, until yesterday (when i was stubbing the card in vfio) all of that wasn't happening (no fans spinning), so i guess it has also something to do with Unraid loading AMD gfx drivers.

    C.
     

  6. Hi there,
    After some months i'm "upping" this thread.
    Yesterday i went through a major "crysis" with my Unraid installation and having a progressive backup with my rsnapshot script would have been a life saver.
    But still, it requires lchown and i still didin't find a way to have the command running in my Unraid (in previous version was there).

    Any possibile solution?

    Thanks.

  7. Hi,
    I'm having one of those days, if there has ever been one.

    Basically, by mistake i've been setting one docker container (Transmission_VPN) to use HOST instead of bridge.
    Since then, i can't access unraid in any way except directly.

    Of course i've corrected the container, stopped it, removed it, stopped the docker service and so on.
    No way, i can't access the server anymore: http, https, SMB. SSH... restored a previous unraid backup... nothing works.
    And yes, the eth cable is connected.
    Any idea? I'm quite desperate :(
    Thanks.
     

    incubus-diagnostics-20231119-2359.zip

  8. So, card unbind.

    1st thing i can notice is the fans on the card spinning up like crazy.

    Seabios:

    char device redirected to /dev/pts/1 (label charserial0)
    2023-11-19T14:03:50.200337Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
    2023-11-19T14:03:50.205360Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
    2023-11-19T14:03:50.991547Z qemu-system-x86_64: VFIO_MAP_DMA failed: Bad address
    2023-11-19T14:03:50.991592Z qemu-system-x86_64: vfio_dma_map(0x147f946c2400, 0xd0000000, 0x10000000, 0x147f84200000) = -14 (Bad address)
    2023-11-19T14:03:50.992033Z qemu-system-x86_64: VFIO_MAP_DMA failed: Bad address
    2023-11-19T14:03:50.992051Z qemu-system-x86_64: vfio_dma_map(0x147f946c2400, 0xe0000000, 0x200000, 0x147f84000000) = -14 (Bad address)
    2023-11-19T14:03:50.992743Z qemu-system-x86_64: VFIO_MAP_DMA failed: Bad address
    2023-11-19T14:03:50.992761Z qemu-system-x86_64: vfio_dma_map(0x147f946c2400, 0xfe400000, 0x40000, 0x14809928c000) = -14 (Bad address)
    2023-11-19T14:03:50.993306Z qemu-system-x86_64: VFIO_MAP_DMA failed: Bad address
    2023-11-19T14:03:50.993323Z qemu-system-x86_64: vfio_dma_map(0x147f946c2400, 0xfe200000, 0x4000, 0x148099288000) = -14 (Bad address)
     

    OVMF.

     

    -msg timestamp=on
    char device redirected to /dev/pts/1 (label charserial0)
    2023-11-19T15:32:14.346058Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
    2023-11-19T15:32:14.362085Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.


    Thx.

  9. 5 minutes ago, ich777 said:

    Please unbind the card from VFIO because otherwise the plugin win‘t work properly anyways.


    I will try that now.
     

    Quote

    What card are you using?


    RX560.
     

    Quote

    Again, I can only assume that the VM templates where you see other values are created differently. Are you sure that you where using OVMF before or where you using SeaBIOS?


    Problem shows up with both SeaBIOS and OVMF (even if it manifests in different ways).

    Trying to unbinding and will let you know.

    THX

  10. Hi there,

    Since updating to 6.12.4, every VM i create fails to start, stating:
     

    char device redirected to /dev/pts/1 (label charserial0)
    2023-11-19T10:27:44.614155Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.
    2023-11-19T10:27:44.618203Z qemu-system-x86_64: vfio: Cannot reset device 0000:01:00.1, no available reset mechanism.


    VMd created before updating do work.

    So, i've been digging a bit into this.

    I uninstalled the AMD Vendor Reset plugin, reboot, started one of those new VM and it went on without any problem.

    Reinstalled the AMD Vendor Reset plugin, reboot, restarted the very same VM and it keeps working.

    Checking one of the "non working VMs" (one wich was NOT started previously without the plugin), i find that in the XML view of the definition of the VM, in the "os" part, there's this (from "Lakka" VM):
     

    <os>
        <type arch='x86_64' machine='pc-q35-7.1'>hvm</type>
      </os>


    "Libreelec" VM, wich was experiencing the same problem, starting it without the AMD Vendor Reset plugin, is now showing this:
     

    <os>
        <type arch='x86_64' machine='pc-q35-7.1'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/e56733f0-82df-31c5-ddfd-21b884fb67c7_VARS-pure-efi.fd</nvram>
      </os>


    Basically, with the plugin installed, if i create a new VM and start/it, there are no <loader> and <nvram> lines added, and also, the respective nvram file isn't created at all (if i look into /etc/libvirt/qemu/nvram/ ).

    Not sure if this is a problem with the plugin itself, but the fact that everything goes as it should with it uninstalled leads me to think so.

    Any ideas?

    Diagnostics attacched, problematic VM is "Lakka".

    Thanks.

    incubus-diagnostics-20231119-1401.zip

  11. Hi,


    I have a daily script doing a backup of various "sensible" Unraid folders using rsnapshot (from nerdtools).

    Everything has always working fine until i noticed, in the last times (i guess from 6.12) that the script isn't able to do its job anymore, sending a lot of warnings:

    Warning: Could not lchown() symlink (path to the file).

    i see online that the fix is usually to install Lchown wich isn't avaiable in default Unraid and either nerdtools.

    Any idea?

    Thanks.
     

  12. Rebuilt all the docker image after upgrading to 6.12 / 6.12.1.

    Now Sonarr can't connect with anything (both indexers and download clients).
    Indexer are under Jackett in torznab.
    Client is Transmission.

    When i test an indexer, for example, i get this:

    [v3.0.10.1567] System.Net.WebException: Unable to read data from the transport connection: Connection reset by peer.: 'http://10.0.1.25:9117/api/v2.0/indexers/1337x/results/torznab/api?t=caps&apikey=(removed) ---> System.Net.WebException: Unable to read data from the transport connection: Connection reset by peer. ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. ---> System.Net.Sockets.SocketException: Connection reset by peer
       --- End of inner exception stack trace ---
      at System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.ThrowException (System.Net.Sockets.SocketError error) [0x00000] in /build/mono/src/mono/external/corefx/src/System.Net.Sockets/src/System/Net/Sockets/Socket.Tasks.cs:1088 
      at System.Net.Sockets.Socket+AwaitableSocketAsyncEventArgs.GetResult (System.Int16 token) [0x00025] in /build/mono/src/mono/external/corefx/src/System.Net.Sockets/src/System/Net/Sockets/Socket.Tasks.cs:1062 
      at System.Threading.Tasks.ValueTask`1+ValueTaskSourceAsTask+<>c[TResult].<.cctor>b__4_0 (System.Object state) [0x00030] in /build/mono/src/mono/external/corefx/src/Common/src/CoreLib/System/Threading/Tasks/ValueTask.cs:655 
    --- End of stack trace from previous location where exception was thrown ---
    
      at System.Net.WebResponseStream.InitReadAsync (System.Threading.CancellationToken cancellationToken) [0x00091] in /build/mono/src/mono/mcs/class/System/System.Net/WebResponseStream.cs:452 
      at System.Net.WebOperation.Run () [0x0018f] in /build/mono/src/mono/mcs/class/System/System.Net/WebOperation.cs:283 
      at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x0008e] in /build/mono/src/mono/mcs/class/System/System.Net/WebCompletionSource.cs:111 
      at System.Net.HttpWebRequest.MyGetResponseAsync (System.Threading.CancellationToken cancellationToken) [0x00235] in /build/mono/src/mono/mcs/class/System/System.Net/HttpWebRequest.cs:1016 
       --- End of inner exception stack trace ---
      at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000e8] in /build/mono/src/mono/mcs/class/System/System.Net/HttpWebRequest.cs:956 
      at System.Net.HttpWebRequest.GetResponse () [0x0000f] in /build/mono/src/mono/mcs/class/System/System.Net/HttpWebRequest.cs:1218 
      at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x00123] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:81 
       --- End of inner exception stack trace ---
      at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x001c0] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:107 
      at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookieContainer) [0x00086] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Http\HttpClient.cs:126 
      at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00008] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Http\HttpClient.cs:59 
      at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Http\HttpClient.cs:281 
      at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x000a1] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:64 
      at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider+<>c__DisplayClass4_0.<GetCapabilities>b__0 () [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:36 
      at NzbDrone.Common.Cache.Cached`1[T].Get (System.String key, System.Func`1[TResult] function, System.Nullable`1[T] lifeTime) [0x000b1] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Cache\Cached.cs:104 
      at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.GetCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00020] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:36 
      at NzbDrone.Core.Indexers.Torznab.Torznab.get_PageSize () [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Torznab\Torznab.cs:23 
      at NzbDrone.Core.Indexers.Torznab.Torznab.GetRequestGenerator () [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Torznab\Torznab.cs:27 
      at NzbDrone.Core.Indexers.HttpIndexerBase`1[TSettings].TestConnection () [0x00007] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:336 
    
    2023-06-24 14:13:59.4|Warn|SonarrErrorPipeline|Invalid request Validation failed: 
     -- : Unable to connect to indexer, check the log for more details


    the very same indexer, configured in the same way, keep working no problem on radarr.
    all the dockers network are configured as bridge.

    Any idea?
    Thanks.

    EDIT: Solved: it was configured to use a proxy that for some reason isn't working correctly.

  13. On 9/23/2022 at 2:35 PM, alturismo said:

    ok, as your shown resolution is 624 x 352, which is pretty exact 16:9 and you see black bars in fullscreen mode on a 16:9 display, then the raw video is not fully 16:9, like real resolution would be 600 x 352.

     

    you can check if the black bars are hardcoded, search for ffmpeg crop detect ... next step would be to look why your encoded video is then left alligned and not centered anymore.


    It's doing it with any video i use as input, even the ones without any kind of bars on the sides: it just adds that black bar to the right. I guess it's something in the metadata it adds, dunno. :(

  14. 25 minutes ago, alturismo said:

    looking weird anyhow, Top (Original) black bar left & right (centered), Bottom (encoded) black bar right (left alligned).

     

    about the pixel aspect ratio, low quality ~ 16:9 .. what is the resolution on the encoded video ? if its similar its just weird looking on a mirrored VLC session, should be pretty fine on a 16:9 screen (fullscreen), only if the black bars are really hardcoded ... and not only "fillers" right now to match the windows screen. Or are those black bars really included in the video ?

     

    why its left alligned instead centered ... i cant imagine right now from your infos

     

    I doin't force a resolution, so the encoded one should be the same of the source.

    As far the bars, they are shown in every player i tried, including the one in my TV (16:9).

    So, i'm clueless.

  15. 5 hours ago, alturismo said:

     

     

    are you sure its added ? in your "snipplet" its looking ok as its filled top & bottom.

     

    what is the height and aspect ratio from your source and targets, may check with mediainfo to compare, or play them side by side with 2 VLC Instances ...


    Top and bottom are filled but on the right it adds that vertical black bar.

    Those are the properties of source file:
    image.png.95d5e0cc1c50e7dae091730b84685810.png


    As far as the comparison, original on top, converted on the bottom:
    image.thumb.png.341d372eb39913a9a159ed1a859b3a73.png


    In other cases (other video), i even squeezed the frame to make room for the right vertical bar.
     

×
×
  • Create New...