Jump to content

Spiritreader

Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by Spiritreader

  1. I think I am too dumb to figure out how to change the order of containers?

     

    If I drag a container  in the "start order" section to the right, and then hit save and reload the page, it's at the old position again.

    Is there any additional step or save button that I am missing?

     

    container order in the config.json is empty

    "containerOrder": []

     

    I thought that I might be able to set it manually but I don't know if it's a list of strings or some internal ids

     

    The configuration file is also missing some of my containers, and I cannot change their individual configuration or save that.

     

    The config ends at tika:

     

           "Tika": {
                "skip": "no",
                "group": "",
                "backupExtVolumes": "no",
                "updateContainer": "",
                "exclude": "",
                "skipBackup": "no",
                "verifyBackup": "",
                "ignoreBackupErrors": ""
            }
        },
        "containerOrder": []

    image.png.9b2705f308a64bf85f8cce004ccb6042.pngBut there are more containers

     

    Here's a gif of trying to change order

    oplJ01v.gif

    • Like 1
  2. 58 minutes ago, bonienl said:

     

    Yes, configuration is always opened in basic mode.

     

     

    Ah I realized that template authoring mode got disabled for some reason.

    Probably had to do with me restoring a bunch of settiings from backup due to fixing another issue.

     

    Thanks for the replay nonetheless!

  3. When editing a docker container, Unraid does not remember that I picked the "Advanced View" anymore.

    Instead it always shows me the basic view.

    Is this intentional?
     

    It's a bit cumbersome, having to click this every time, as I regularily use/modify the fields that are hidden in basic view.

     

    image.thumb.png.66347dd06880eaeadde7a5fbfa2fc813.png

  4. On 5/28/2022 at 2:30 AM, limetech said:

     

    Issue was introduced at the beginning of 6.10-rc series when we introduced code to require a root password and add brute-force mitigations.  Does not have to do with sanitizing input from a form but rather server-side extraction of the record from /etc/shadow file.  You can examine the one-line fix here.

     

    Oh wow I didn't know the WebGUI source was inspectable. That's awesome!

    If I had known, I could've reported the bug way faster than I did!

     

    In any case, thanks for fixing it so quickly! Appreciate the team always being on the lookout in the forums! 😃

    • Thanks 1
  5. I figured it out. 

     

    There seems to be an issue with how the WebGUI matches usernames.

    I have a user called "rootshare" which exposes all shares via a custom smb config.

    When this user account exists, unraid's WebUI attempts to match the password for "rootshare" instead of "root".

    Using the password for the "rootshare" user then works for the "root" user.

     

    Seems like an oversight? (username.startsWith() / username.Contains() or something?)

    • Like 1
    • Haha 1
  6. Hey everyone,

     

    all the way back when RC-1 came out, I tried upgrading, but it was stopped in its tracks because I was unable to log in with my correct credentials.

     

    I rolled back to 6.9.2 and everything worked fine again.

     

    Now that 6.10 is released as stable, I tried again, and I still cannot log in with the WebGUI.

    I tried downgrading to 6.9.2, setting the password to only letters, upgrading again, it still doesn't work.

     

    I tried removing/renaming the shadow file, which prompts me to set a new password.

    I set the password, press "logout", and I can not log back in again.

     

    The shadow file is written to, there's a new hash in there, so this seems to have worked.

    But it just won't let me access the WebUI?

    SSH works fine.

     

    The flash drive is fine, permissions are fine, there don't seem to be any corrupted files.

    I have no idea how to proceed here.

     

    This is the only thing that shows up in the log (I stay logged in after resetting the password until I log out again)

    May 26 04:47:09 UMS webGUI: Unsuccessful login user root from 192.168.178.84

     

  7. Using version-1.4.0 results in the following error message:

     

    Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.4.0".

     

    Is that an issue on my end or is the used php version outdated?

    What do I need to do?

     

    UPDATE: fixed in latest container version

  8. 2 minutes ago, ich777 said:

    Thank you for the quick answer. ;)

    When installing the beta35 on my server I got a similar problem.

    I got a Cine C/T v6.5 with an addon card Cine C/T v6.5 and only the first Cine C/T (2 tuner instead of 4) showed up. I had to shutdown the server completely and waited for a minute and then turned back on the server. After that it picked up all of the 4 Tuners.

     

    Is a little bit weired but not the first time that I got such a problem.

     

    ddbrige isn't actually the driver itself can you give me the output of 'lsmod'?

    The drivers for the cards tuners should be updated to that version number that you see on github.

    I also build with the latest driver version.

     

    Can I contact you a little bit later on this, I'm currently not at home, in which timezone are you?

    Hmm, that is indeed very weird.
    Good to know it's not the driver version, must be something else then.

    Before trying 6.9b35, I also wasn't able to get the card working on 6.8.3 with the custom-kernel-helper builder. That kernel however, also picked up the S2 C6 fine.

     

    Here's the output of lsmod, I put it in a pastebin so it doesn't spam the forum.

    https://pastebin.com/5RkQRr74

     

    Yes you can contact me, in fact I would be very glad to!

    My timezone is Europe/Berlin, GMT+1.

    Thank you for trying to help me out!

    • Like 1
  9. 15 minutes ago, ich777 said:

    Can you tell me which package shows up on the DVB Plugin page, LibreELEC or DigitalDevices?

    Have you rebooted after selecting the digitaldevices package?

    The digitaldevices package is compiled with the latest available drivers from digitaldevices from their github.

    Of course! Thank you!

     

    First, sanity check: The tuner is showing up.

    [dd01:000b] 25:00.0 Multimedia controller: Digital Devices GmbH Device 000b

     

    Then, to answer your questions:

    - Package that shows up is "digitaldevices".

    - I have performed a reboot after selecting download.

     

    Driver version shows as 0.9.33-integrated, while the latest digitaldevices drivers seem to be 0.9.37.

    The syslog also reports loading an out of date driver (c 2017)

    Nov 15 11:39:37 UMS kernel: ddbridge: Digital Devices PCIE bridge driver 0.9.33-integrated, Copyright (C) 2010-17 Digital Devices GmbH

     

    Since the DigitalDevices S8 series requires extra configuration, I have added this to the syslinux config

    kernel /bzimage
    append initrd=/bzroot ddbridge.fmode=3 ddbridge.msi=1

    However, this used to be part of the documentation of the Unraid DVB post that was removed.

    This config step seems to be mandatory, although I am unsure whether not configuring that prevents the drivers from picking up the card at all.

     

    In case the syslinux config change isn't working anymore, what would be necessary is to create a config file in /etc/modprobe.d/ddbridge.conf which must persist between reboots.

    http://support.digital-devices.eu/index.php?article=151

    I'm also unsure how to achieve this with the new dvb infrastructure

     

    Here's a screenshot of the page (Cine S2 V6 there, Max S8X not there)

    image.thumb.png.973ffd6a3e0fe66fd0a1b35cb4d1a36f.png

    • Thanks 1
  10. For the Unraid DVB plugin, Is there an option to select a newer driver version than 0.9.33-integrated?

    We have a DigitalDevices Max S8X basic and it is not picked up.

    The DigitalDevices Cine S6 V6 is picked up, not the S8X though.
    I'm assuming I need newer drivers. How do I accomplish this?

    root@UMS:~# dmesg | grep -i ddbridge
    [    0.000000] Command line: BOOT_IMAGE=/bzimage initrd=/bzroot ddbridge.fmode=1 ddbridge.msi=1
    [    0.000000] Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot ddbridge.fmode=1 ddbridge.msi=1
    [   65.506126] ddbridge: Digital Devices PCIE bridge driver 0.9.33-integrated, Copyright (C) 2010-17 Digital Devices GmbH
    [   65.506213] ddbridge 0000:21:00.0: enabling device (0000 -> 0002)
    [   65.506322] ddbridge 0000:21:00.0: detected Digital Devices Cine S2 V6 DVB adapter
    [   65.506344] ddbridge 0000:21:00.0: HW 0001000b REGMAP 00010004
    [   65.506422] ddbridge 0000:21:00.0: using 2 MSI interrupt(s)
    [   65.507558] ddbridge 0000:21:00.0: Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2
    [   65.508574] ddbridge 0000:21:00.0: Port 1: Link 0, Link Port 1 (TAB 2): NO MODULE
    [   65.509582] ddbridge 0000:21:00.0: Port 2: Link 0, Link Port 2 (TAB 3): NO MODULE
    [   65.509955] dvbdev: DVB: registering new adapter (DDBridge)
    [   65.509957] dvbdev: DVB: registering new adapter (DDBridge)
    [   65.691770] ddbridge 0000:21:00.0: attach tuner input 0 adr 60
    [   65.691774] ddbridge 0000:21:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
    [   65.734287] ddbridge 0000:21:00.0: attach tuner input 1 adr 63
    [   65.734291] ddbridge 0000:21:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...

     

  11. Unfortunately nothing shows up.

     

    I omitted the unlink to check what else samba was logging, and there's nothing there except for when the daemon is restarted due to config changes

     

    root@Tower:~# cat /var/log/samba/log.smbd
    
    [2020/10/04 21:45:16.282004,  0] ../../source3/smbd/server.c:1775(main)
      smbd version 4.11.4 started.
      Copyright Andrew Tridgell and the Samba Team 1992-2019

     

  12. 22 hours ago, dlandon said:

    I think your additions to the smb-extra.conf file is causing some issues.

    I have removed the extra configuration. Now it's just unassigned devices and the recycle bin.

    #unassigned_devices_start
    #Unassigned devices share includes
       include = /tmp/unassigned.devices/smb-settings.conf
    #unassigned_devices_end
    #vfs_recycle_start
    #Recycle bin configuration
    [global]
       syslog only = No
       syslog = 0
       logging = 0
       log level = 0 vfs:0
    #vfs_recycle_end

    Still no logging when deleting files unfortunately.

  13. I seem to have an issue where the deleted files log no longer works.

    This issue seems to have started some time around July.

     

    On two separate Unraid systems, despite the "Log Deleted Files" flag being enabled, it no longer tracks them.

    When I delete a file, it correctly ends up in the recycle bin. But upon clicking "empty trash" or waiting for the automated schedule to execute, it no longer shows an 

    Jul 19 02:26:13  unlink => xyz

    entry.

     

    This is what the recycle bin configuration looks like under smb config

    #vfs_recycle_start
    #Recycle bin configuration
    [global]
       syslog only = No
       syslog = 0
       logging = 0
       log level = 0 vfs:0
    #vfs_recycle_end

     

  14. linuxdvb: Montage Technology M88DS3103 poll TIMEOUT

    Getting this since upgrading to Unraid 6.8.0 (stable) with LibreELEC 1.4.0 and Linux kernel 4.19.88 using a DVBSky S952.

    Tuner is recognized but can't open a stream.

    I've read that there was a kernel bug with the driver that has been introduced in ~kernel 4.18.xx but some people reported that it got fixed(?).

     

    The tuner was working fine with the latest available 6.7.2 LibreELEC build and V1.3.1 drivers.

     

    Anyone has any idea why this isn't working anymore in 6.8.0?

     

    Update: Seems to be working again now after rebooting unraid. Gonna monitor if this happens again.

×
×
  • Create New...