Jump to content

csrihari

Members
 View Profile  See their activity

  • Posts

    21

  • Joined

  • Last visited

 Content Type 

Posts posted by csrihari

    Unraid.net Account Upgrades

    in Announcements

    Posted

    3 minutes ago, ljm42 said:

     

    Please try signing in again. We are fixing these as we see them, working on automating the fix.

    Thanks. This worked now(obviously!!). Not sure what to do with that temp account. Will it be purged if I do not use it again?

    [Plugin] Parity Check Tuning

    in Plugin Support

    Posted · Edited by csrihari

    1 hour ago, itimpi said:

    I have just pushed a new release that should fix the permission issues reported as introduced in the last release.  In would welcome confirmation that this issue really IS fixed.

    Quote

    plugin: downloading: https://raw.githubusercontent.com/itimpi/parity.check.tuning/master/archives/parity.check.tuning-2023.02.10.txz ... failed (Invalid URL / Server error response)

     

    Same here

    • Upvote 1

    [Plugin] Parity Check Tuning

    in Plugin Support

    Posted

    root@Bebbuli:/# cd /usr/local/
    root@Bebbuli:/usr/local# ls -l
    total 0
    drwxr-xr-x 2 root   root   60 Feb  2 18:31 bin/
    drwxrwxrwx 4 nobody users 320 Feb 18  2019 emhttp/
    drwxr-xr-x 2 root   root   40 Nov 24  1993 etc/
    drwxr-xr-x 2 root   root   40 Mar 15  1994 lib/
    drwxr-xr-x 3 root   root   60 Jul 25  2022 lib64/
    drwxr-xr-x 2 root   root  700 Feb 10 08:17 sbin/
    drwxr-xr-x 3 root   root   60 Jul 25  2022 share/
    drwxr-xr-x 2 root   root   80 Nov 20 16:27 src/
    root@Bebbuli:/usr/local#

    [Plugin] Parity Check Tuning

    in Plugin Support

    Posted

    First one at / level

    root@Bebbuli:/# pwd
    /
    root@Bebbuli:/# ls -l
    total 8
    drwxr-xr-x   2 root   root  3820 Feb  2 18:32 bin/
    drwx------  11 root   root  8192 Dec 31  1969 boot/
    drwxr-xr-x  16 root   root  4020 Feb  8 09:49 dev/
    drwxr-xr-x  63 root   root  3300 Feb 10 08:17 etc/
    drwxr-xr-x   2 root   root    40 Nov 20 16:27 home/
    drwxr-xr-x   3 root   root     0 Feb  2 18:34 hugetlbfs/
    lrwxrwxrwx   1 root   root    10 Nov 20 16:27 init -> /sbin/init*
    drwxr-xr-x   8 root   root   160 Jan 19 14:13 lib/
    drwxr-xr-x   7 root   root  3940 Nov 20 16:27 lib64/
    drwxr-xr-x  16 root   root   320 Feb  7 07:55 mnt/
    drwx--x--x   3 root   root    60 Feb  2 18:34 opt/
    dr-xr-xr-x 838 root   root     0 Feb  2 18:31 proc/
    drwx--x---   3 root   root   180 Feb  3 12:35 root/
    drwxr-xr-x  20 root   root  1040 Feb 10 09:00 run/
    drwxr-xr-x   2 root   root  5380 Feb  2 18:32 sbin/
    dr-xr-xr-x  13 root   root     0 Feb  2 18:31 sys/
    drwxrwxrwt  14 root   root   360 Feb 10 15:44 tmp/
    drwxrwxrwx  14 nobody users  340 Feb 18  2019 usr/
    drwxr-xr-x  14 root   root   340 Jan  9  2017 var/

    [Plugin] Parity Check Tuning

    in Plugin Support

    Posted · Edited by csrihari

    After updating, my passwordless ssh broke and I see this in syslog

    Authentication refused: bad ownership or modes for directory /

     

    This happened on an earlier update of this plugin as well. I read the discussion of this in another thread and it has something to do with /usr permissions of this plugin?

    [Plugin] LXC Plugin

    in Plugin Support

    Posted

    10 hours ago, ich777 said:

    A little bit more context would be nice.

    What container are you using? The config would be also helpful. What do you want to do with the container?

     

    Your error is right here:

    LXC on Unraid is built without AppArmor because Unraid uses SELinux.

    Sorry nevermind. I was overthinking my docker setup. Disabled this and it works fine.

    • Like 1

    [Plugin] LXC Plugin

    in Plugin Support

    Posted

    Enabling nesting gives an error

    lxc-start: debtest: ../src/lxc/confile.c: set_config_apparmor_profile: 1651 Invalid argument - Built without AppArmor support
    lxc-start: debtest: ../src/lxc/parse.c: lxc_file_for_each_line_mmap: 129 Failed to parse config file "/usr/share/lxc/config/nesting.conf" at line "lxc.apparmor.profile = lxc-container-default-with-nesting"

    Is this expected?

    [Plugin] LXC Plugin

    in Plugin Support

    Posted

    7 hours ago, ich777 said:

    This containers should all run privileged.

     

    If you create a container check the owner from /proc, if it's root:root then it is privileged.

    Got it. Thank you for this. I see that it is privileged 👍

    • Like 1

    [Plugin] LXC Plugin

    in Plugin Support

    Posted · Edited by csrihari

    12 hours ago, ich777 said:

    Certain file paths are perhaps too long but it will create the tar file anyways. Have you yet tried the integrated snapshot feature?

    I did not try snapshots but will do. I am just playing around at this time to see how it all works. By the way, tar in backup script works without a problem if verbose is enabled. Weird. 

    [Plugin] LXC Plugin

    in Plugin Support

    Posted · Edited by csrihari

    Thank you for creating this plugin. First time trying LXC and it is awesome. Created default DebianLXC and it worked fine. It starts in 1 or 2 seconds which is amazing. Tried your backup script and ran into this error. Not a big deal but just wanted to let you know

    tar: ./rootfs/var/lib/apt/lists/deb.debian.org_debian-security_dists_bullseye-security_main_i18n_Translation-en: file name is too long (max 99); not dumped

    tar: Exiting with failure status due to previous errors
    Backup Failed!

    Edit: Though it says Backup Failed, it did create tar file. Did not attempt restoring.

     

    [DEPRECATED] Linuxserver.io - Rutorrent

    in Docker Containers

    Posted

    On 4/29/2020 at 9:57 PM, Xaero said:

    Would it be possible to implement the fix depicted here:
    https://github.com/rakshasa/rtorrent/issues/861

    Currently, the bug presented in that thread is present in this container. I've been having to screen -r my docker and manually stop and start torrents because I still cannot seem to stop getting the errors in regard to the getplugins.php (my previously implemented resolution stopped working, after a couple of months and incidental docker updates... This seems to be a constant struggle with rtorrent on unraid. Regardless of the number of active torrents.)

    EDIT:

    I'm at a loss. I'm back to square one basically. I'm going to backup my rutorrent config folder; and try starting over but I'm back to the abysmal 20-30kb/s and unresponsive (or not even loading) webui. Nothing in the logs seems of relevance. I've read through logs and even enabled advanced logging. There's no "errors" so to speak, just the rtorrent application sitting at 99.99% IOWAIT. I'm wondering if it doesn't like the merged filesystem that unraid uses? I'm downloading to an NVME SSD and the only application with this issue is rtorrent. I'll post back with what I figure out.

    Thank you for researching on this. I am having the exact same issue for months now to the point rtorrent is unusable. Changing ioscheduler to bfq (from Auto) did nothing to help. However, changing it to mq-deadline showed immediate results. IOWAIT fell back from 99% to under 10%. The speeds are still not great but atleast the torrents are downloading again. I too have NVMe(over a PCI adapter) for cache. It does look like I may have to move this to a dedicated unassigned drive but first need to figure out a way to move completed downloads to array and keep them seeding in th client. I am also thinking if NVMe drive is contributing to this as not everyone seems to have this issue.
    Please update if you find a good solution.

×
×
  • Create New...