Jump to content

PTRFRLL

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

8 Neutral

About PTRFRLL

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. PTRFRLL

    Docker Pull/Extract Slow

    Wow, I didn't realize it wasn't on the cache drive. I can already notice a huge difference. Thanks for the help!
  2. PTRFRLL

    Docker Pull/Extract Slow

    Oops! Sorry, forgot to attach to the OP vault-diagnostics-20190410-1242.zip
  3. PTRFRLL

    Docker Pull/Extract Slow

    Lately I've seen a noticeable slowness when updating/pulling docker containers. It appears to happen on the Extracting stage of the layers and it's directly correlated to the layer size (larger layer == longer extract time). It's gotten bad enough where I can't update some of my containers as the update just hangs forever. I'm not sure where to start for troubleshooting this. Nothing has changed on the hardware side and I haven't updated the Unraid OS recently (running 6.6.5).
  4. I haven't upgraded myself but if you try to manually start the service using: /etc/rc.d/rc.pulseway start it should point you in the direction of what is causing the error. Based on the release notes, it looks like they upgraded the one of the underlying libraries again. Most likely you'd have to update the symlink command to point to the new version.
  5. PTRFRLL

    [support] dlandon - Zoneminder 1.32

    Thanks for the help. Another issue I noticed is in the Montage view, there seem to be some failed AJAX calls when trying to get the camera state (FPS, Enabled, etc). Digging a little deeper it looks like the request is leaving off the port ZM is running on. So right now the request fires off to: http://<IP ADDRESS>/zm/index.php??view=request&request=stream&connkey=779378&command=99 (this fails) instead of: http://<IP ADDRESS>:<PORT NUM>/zm/index.php??view=request&request=stream&connkey=779378&command=99 if I copy the link and add the correct port, the response is good: { "result": "Ok", "status": { "type": 2, "monitor": 2, "state": 0, "fps": 30.31, "level": 0, "rate": 1, "delay": 0.04, "zoom": 1, "delayed": 0, "paused": 0, "enabled": 1, "forced": 0 } } Not sure if this is a docker issue or ZM thing
  6. PTRFRLL

    [support] dlandon - Zoneminder 1.32

    /dev/shm is sitting around 4%. Would anything regarding that have changed with the docker update?
  7. PTRFRLL

    [support] dlandon - Zoneminder 1.32

    Ever since upgrading my docker to zm 1.32, my monitors in the Montage view will occasionally freeze. Has anyone else experienced this? It didn't happen with previous versions and the log only states a generic error, "terminating". Seems like it may be related to a motion event but not 100% sure.
  8. According to this page: https://wiki.unraid.net/Files_on_v6_boot_drive, the extras folder is optional It looks like you'll just need to create the extras folder.
  9. PTRFRLL

    Not using all NICs on PCI card

    Now we're cooking! Looks like that was the issue. I'm guessing this is what was causing my LAG to fail as well. Thanks for the help!
  10. PTRFRLL

    Not using all NICs on PCI card

    Deleted and rebooted, still same issue. Looks like part of the problem is eth0/eth1 are assigned to the Ethernet ports on my motherboard, which are not connected. Is there a way to disable those and only use PCIe card?
  11. PTRFRLL

    Not using all NICs on PCI card

    Strange thing is, they both show as Up and that they are a member of the bond, here's eth1 for example
  12. PTRFRLL

    Not using all NICs on PCI card

    Understood but the links don't even show as connected whereas the 2nd, backup NIC does. Same as in mode 4, only 2 of the 4 NICs showed connected.
  13. PTRFRLL

    Not using all NICs on PCI card

    I believe I've done that:
  14. I have an Intel Pro/1000 Quad Port PCI adapter in my server. All 4 ports are connected to my managed switch via Ethernet. unRAID does not seem to be utilizing all 4 ports, just two. When the server boots I see link activity on all 4, so I believe the switch, cabling and adapter are all working just fine. unRAID recognizes all 4 ports but states that 2 of the 4 are down and never uses them. Currently my network bonding is in mode 1 (active/backup) but even if I switch to link aggregation (mode 4) it still only uses 2 links. Attached is my syslog. Any ideas? syslog.txt
  15. Pulseway is a great tool that allows you to remotely monitor servers from iOS, Android, and the web. I mainly use it on iOS for the notifications about loss of network, high CPU usage or my server being shutdown. It was one of the few things I missed when I switched my server to unRAID. Luckily, I figured out how to get it installed and working. Here's the steps I took: 1. Download the Pulseway Agent for Slackware from Pulseway's website 2. Copy the pulseway_x64.txz to /boot/extra (this is also the flash smb share so flash/extra) 3. Create a new folder,pulseway, in the /boot directory 4. Reboot unRAID 5. SSH into server and copy config.xml.sample to config.xml: cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml 6. Edit the config.xml file you just copied, you'll need to add your Pulseway username/password and setup any notifications you want to receive (change the Enabled flag from False to True). I enabled Network interface monitoring (change interface name to br0) as well as WhenOffline, HighCpuUsage and MemoryLow notifications. 7. Pulseway needs to be run to verify your config file works and to generate an id file. The Pulseway service looks for version 0.9.8 of libssl and libcrypto, unRAID includes version 1.0.0 so we need to create symlinks to the 1.0.0 files to trick Pulseway into using those: ln -s /lib64/libssl.so.1.0.0 /usr/lib64/libssl.so.0.9.8 ln -s /lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.0.9.8 8. Start Pulseway service: /etc/rc.d/rc.pulseway start 9. Copy the id file generated by Pulseway to the /boot/pulseway directory (if you don't do this, the server will show up as a new machine in Pulseway every time unRAID boots): cp /var/pulseway/pulseway.id /boot/pulseway/pulseway.id 10. Copy your config file to /boot/pulseway cp /etc/pulseway/config.xml /boot/pulseway/config.xml 11. Add the following lines to /boot/config/go cp /boot/pulseway/config.xml /etc/pulseway/config.xml cp /boot/pulseway/pulseway.id /var/pulseway/pulseway.id ln -s /lib64/libssl.so.1.0.0 /usr/lib64/libssl.so.0.9.8 ln -s /lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.0.9.8 # As of version 6.6, you also need one for libidn ln -s /usr/lib64/libidn.so.12 /usr/lib64/libidn.so.11 /etc/rc.d/rc.pulseway start 12. Reboot unRAID and make sure everything works! Explanation: unRAID's OS is stored in RAM so any changes you make do not persist after a reboot/shutdown. That's why we need to move everything to the /boot drive (the flash drive unRAID boots from). On startup, we're installing Pulseway, creating symlinks to libraries it needs, copying the config and id files to their respective locations and then starting the service. EDIT (9/26/2018): As of version 6.6, you also need to create a symlink for libidn like so: ln -s /usr/lib64/libidn.so.12 /usr/lib64/libidn.so.11