Iceman24

Members
  • Posts

    107
  • Joined

  • Last visited

Posts posted by Iceman24

  1. 4 hours ago, SimonF said:

    If you click info on my IPMI entry in CA you should see this and click action to update.

     

    image.thumb.png.99a9977341c63076a8a5d7238c1bd4d6.png

    Thanks. It shows as if both versions are installed though, but only lists the old one in the plugins tab. It seems to work okay though.

  2. On 10/4/2022 at 4:09 PM, jlaning said:

    After some initial investigation, it seems that at least maybe dropping a custom script into the directory

    /boot/config/plugins/dynamix/notifications/agents/

    would work based on the code in

    /usr/local/emhttp/plugins/dynamix/scripts/notify

     

    but I haven't tested this. However, a UI way of doing this would be preferred.

     

    EDIT:

     

    Creating a script

    /boot/config/plugins/dynamix/notifications/agents/ntfy

     

    worked (as a temp solution). Here's my example for ntfy.sh

     

    #!/bin/bash
    curl -u "user:pass" \
      -H "Title: ${SUBJECT}" \
      -H "Tags: unRAID" \
      -d "Event: ${EVENT}
    Subject: ${SUBJECT}
    Description: ${DESCRIPTION}
    Importance: ${IMPORTANCE}
    Time: $(date '+%Y-%m-%d %H:%M:%S')
    
    ${CONTENT}" \
      https://ntfy.domain.tld/unRAID

     

    Are you saying that you got it working with that script?

  3. On 8/19/2022 at 3:28 PM, imagoodusername said:

    For those who are still struggling to get Compreface running with the internal database, I think this is a step by step on how to fix the issue.

     

    If you are starting fresh, skip the first three lines. If you installed this docker already, start from the beginning.

    1. On the Docker tab in the unRaid webgui, stop CompreFace if running.
    2. On the Docker tab in the unRaid webgui, delete CompreFace docker installation.
    3. THIS IS VERY IMPORTANT: delete the default compreface folder that was created in your appdata folder. IF YOU DON’T DO THIS, YOU WILL CONTINUE TO GET ERRORS NO MATTER WHAT YOU DO.
    4. Go back to the apps tab and install Compreface (I’ve only tested the CPU version — I don’t know about the GPU version).
    5. DO NOT JUST BLINDLY HIT APPLY AND START THE INSTALL WITH THE DEFAULT PARAMETERS Instead, toggle on Advanced View (top right of the Compreface docker installation page). THEN GO TO “SHOW MORE SETTINGS”. DELETE ALL FOUR OF THE CUSTOM SETTINGS THERE BY USING THE BUTTONS TO THE RIGHT OF THE TEXT BOX Those settings are for using an external database, but if you are trying to use the internal database it will create a series of errors.
    6. Hit apply on the docker install page, and let docker/unraid do its thing. Go get a cup of coffee and let compreface go through its installation.
    7. After successful installation, you should be able to access the webgui for compreface without issue.

    These fixes do appear in this thread already, but I had to read through the thread several times and do a bunch of trial-and-error to figure out that I needed to delete the docker and the appdata before trying to reinstall sans database parameters.

    This doesn't work for me, just complains about not being able to find a suitable jdbc url. It seems to need those lines. External database defaults to false, so I don't know why it would be a probably to leave. Once upon a time, it worked like that, but trying to use again after a hiatus and with or without, it still doesn't work for me.

  4. On 12/7/2016 at 10:20 AM, ClunkClunk said:

     

    I started this a few months ago, but never got around to really optimizing it and rotating out old listings or compressing them. But hopefully it'll give you a starting point!

     

     

    #!/bin/sh
    
    DISKS=8
    COUNTER=1
    THEDATE=`date +"%Y-%m-%d_%H-%M-%S"`
    LOCATION="/boot/trees"
    
    echo " "
    echo " "
    echo "Starting tree scanning"
    
    while [ $COUNTER -le $DISKS ]
    do
    echo "Scanning tree for disk$COUNTER/Movies"
    tree -h /mnt/disk$COUNTER/Movies >> "$LOCATION/$THEDATE.movies.log"
    echo "Scanning tree for disk$COUNTER/TV"
    tree -h /mnt/disk$COUNTER/TV >> "$LOCATION/$THEDATE.tv.log"
    echo "Incrementing disk counter"
    COUNTER=$[$COUNTER+1]
    done
    echo "Scanning tree for cache/Movies"
    tree -h /mnt/cache/Movies >> "$LOCATION/$THEDATE.movies.log"
    echo "Scanning tree for cache/TV"
    tree -h /mnt/cache/TV >> "$LOCATION/$THEDATE.tv.log"
    echo "All done scanning disks. Beginning scanning shares."
    echo "Scanning tree for user/Movies"
    tree -h /mnt/user/Movies >> "$LOCATION/$THEDATE.movies.log"
    echo "Scanning tree for user/TV"
    tree -h /mnt/user/TV >> "$LOCATION/$THEDATE.tv.log"
    echo " "
    echo " "
    echo "Complete! Logs stored in $LOCATION"
     

     

     

    Thanks for this, although I could use some help understanding how to modify it to use. I have 2 disks I want to do this to. I don't quite understand the COUNTER part. It seems to be going through all the disks, but only one disk is there for me and the other is the cache drive. Also, how it is saving I'm not quite sure about. I just want to let it run on disk1 and cache at directories of my choosing.

  5. 39 minutes ago, dlandon said:

    The disk is trying to use the Unraid password/passphrase to open that device.  Has it changed since the disk was formatted?

     

    You can enter the specific disk password in the UD settings if it is different from Unraid.

     

    The disk password cannot be recovered or changed.

    Thanks. That led me to finding the place to set the encrypted password, which I just used what I had originally set it as. It must've forgot it between updates or whatever.

  6. 11 minutes ago, dlandon said:

    When the Unraid api is used to open the luks device, it does not provide any feedback on whether or not it was successful.  The following line tells me that your credentials failed and the luks open did not create the /dev/mapper/ device.

     

     

    Thanks. I didn't change anything related to this, so not sure how this could be. How do I wipe the credentials and reenter them?

  7. On 9/23/2022 at 11:30 AM, Iceman24 said:

    I tried running a backup to my local external drive that I hadn't done since I starting having lockup issues due to macvlan docker network type. I upgraded from 6.9.3 to 6.10.3 and then enabled the ipvlan, that solved that issue, but that is all that I did besides some updates of this plugin that is since my last backup. Now, I get these errors. Drive is encrypted with LUKS that unRAID saves info for unlocking drive once I plug in. I use another drive in a similar fashion but without encryption and it does not have an issue.

     

    Sep 23 11:26:34 unRAID unassigned.devices: Adding partition 'Backup'...
    Sep 23 11:26:34 unRAID unassigned.devices: Mounting partition 'Backup' at mountpoint '/mnt/disks/Backup'...
    Sep 23 11:26:34 unRAID unassigned.devices: Using Unraid api to open the 'crypto_LUKS' device.
    Sep 23 11:26:34 unRAID unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/Backup' '/mnt/disks/Backup'
    Sep 23 11:26:34 unRAID kernel: /dev/mapper/Backup: Can't open blockdev
    Sep 23 11:26:34 unRAID unassigned.devices: Mount of 'Backup' failed: 'mount: /mnt/disks/Backup: special device /dev/mapper/Backup does not exist. '
    Sep 23 11:26:34 unRAID unassigned.devices: Partition 'Backup' cannot be mounted.

     

    Did I post this in the wrong place? Should I have started to different thread for this issue? I don't know if the issue is with this plugin or something else.

  8. I tried running a backup to my local external drive that I hadn't done since I starting having lockup issues due to macvlan docker network type. I upgraded from 6.9.3 to 6.10.3 and then enabled the ipvlan, that solved that issue, but that is all that I did besides some updates of this plugin that is since my last backup. Now, I get these errors. Drive is encrypted with LUKS that unRAID saves info for unlocking drive once I plug in. I use another drive in a similar fashion but without encryption and it does not have an issue.

     

    Sep 23 11:26:34 unRAID unassigned.devices: Adding partition 'Backup'...
    Sep 23 11:26:34 unRAID unassigned.devices: Mounting partition 'Backup' at mountpoint '/mnt/disks/Backup'...
    Sep 23 11:26:34 unRAID unassigned.devices: Using Unraid api to open the 'crypto_LUKS' device.
    Sep 23 11:26:34 unRAID unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/Backup' '/mnt/disks/Backup'
    Sep 23 11:26:34 unRAID kernel: /dev/mapper/Backup: Can't open blockdev
    Sep 23 11:26:34 unRAID unassigned.devices: Mount of 'Backup' failed: 'mount: /mnt/disks/Backup: special device /dev/mapper/Backup does not exist. '
    Sep 23 11:26:34 unRAID unassigned.devices: Partition 'Backup' cannot be mounted.

     

  9. 1 hour ago, Skylord123 said:

    Try deleting your MQTT database file and starting again. My db file got corrupted by improper shutdown (my UPS failed) and this was only way to fix it. May be your issue as well. 

    Thanks, but I already switched to mosquitto. Most of the way through redoing entities as that got all messed up. I had to delete and recreate, thought I was clear, but now I have Frigate issues where it doesn't work right with MQTT to HA anymore, but I'm so deep in the switch, not sure I want to reverse. Ugh.

  10. On 8/3/2022 at 9:47 AM, stlrox said:

    Suddenly MQTT container stopped working. There is no information in the logs. This container worked without any issues for the last two years. Recently I upgraded to OS 6.10.3.

    I verified directory path and there is no issue with the permissions.

    I tried to restart this several times but didn't produce any helpful information in the logs. I appreciate any tips for solving this issue. 

    Did you ever get this fixed? I just updated to 6.10.3 from 6.9.2 and it killed my MQTT.

  11. It happened again just now. More diagnostics and syslog attached. 20:11:30-20:13:15 time of lockup.

     

    I did notice the "rcu_sched self-detected stall on CPU" error, some other info I found on it, but I will leave that to someone more knowledgeable to advise me on how to move forward with my particular server. Thanks.

     

    I could update from 6.9.2, was hesitant due to some issues people had.

     

  12. Another thing is that every time now I have to turn off Docker service, go into network settings, modify DNS just to the point that after I put settings back, I apply. I didn't even change anything. Then restart Docker service, then I have proper DNS connectivity the way I have things setup. What issues I have varies, but sometimes it's as far as delays to ping anything on the Internet at all, but it's all good once I do what I just said.

  13. Thanks, JorgeB. I will try that now. I did notice the CompreFace container giving me issues again, this time not stopping. It was holding up almost everything else. I had to stop all other containers individually. I can't even kill the process. I had to hard reboot it again. Ugh. I've had this container for months, no recent update and like I said before, problem happens without it running. 

     

    Edit:

    I have had the option "-i br0" on WSD this whole time. I don't recall why, read about it years ago.

  14. Diagnostics and syslog that I mirrored to flash so that I had more data when/if it happened again. The lockup (as I'll call it) occurred between 18:14:30-18:16:50. I know as I have a monitor checking for a Docker app that runs that goes down just like everything else when it happens. I cannot even ping the server itself whatsoever once it happens, yet it was still logging for the 15 minutes or so until I hard rebooted it.

     

    It has happened about 5 times now over 2 weeks. It has been a few days, thought it may have been resolved. I reseated the memory and ran MemTest 9 until it said PASS after the 4 passes it does.

     

    Originally, unless unrelated, this problem started with something happening overnight, couldn't access anything, after reboot I couldn't see files on cache drive. After xfs repair, I could, everything okay. Then 2 days or so later the regular lockups occurred, maybe 2 days, 24 hours, 5 hours in between, very random, wasn't usually using server firsthand when it happens except once. Nothing stood out in syslog to me around lockup time, but it wasn't a log I am used to reading.

     

    I did see once I think that memory log showed 100% full on dashboard while it still kind of worked. I tried to reboot, wouldn't do it, had to hard reboot. I didn't see it seem to fill up quickly when monitoring it. At that time, CompreFace was pegging CPU, but even after keeping off, it still locked up once. I'd appreciate any help, please. This is driving me mad. I rely on this server so much. Thanks.

     

    just over 2.5 years old. No issues up until this.