ElBurrito

Members
  • Posts

    17
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    OKC, OK

Recent Profile Visitors

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

ElBurrito's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Haven't messed with InfluxDB for a while but if I remember right you should be able to set retention policies. Does this help with what you are looking for? https://docs.influxdata.com/influxdb/v2.0/reference/api/influxdb-1x/dbrp/#default-retention-policies
  2. Sorry for the delay. This worked on mine using GUS just fine.
  3. No problem, glad to help. I’d be happy to test it.
  4. @testdasi Any idea on getting the World Map and Pie Chart plugins this new dashboard uses to show up in GUS? I have installed them in the plugin directory and changed file permissions, but so far still not able to get them to show up.
  5. I just rebuilt mine with new hardware, I am running AMD though, but I saw something in one of the guides where I had to enable that CSM for it to work. Not sure if that was just for ryzen devices or not. I had an issue like you had after my previous upgrade, I was running dual Xeons on super micro MB, and I had an issue with a couple of sticks of memory being the issue. It was running something like 96G and failed pretty far into the memtest. i finally isolated it down to the sticks and replaced them to resolve the issue. Side note, i have had some weird behavior like that also running a PCIe sata expansion card. If i remember correctly, it didn't like my drives over 2TB being on there and caused some weird crashing stuff.
  6. @RockDawgI think i saw you're the GUS docker for your Grafana? I believe when I setup Grafana on my server to test a while back, i used the standalone docker and those I had to manually configure the paths i wanted (/mnt/user or /mnt/user0 or /) for the container. When I started messing with this dashboard, I installed the GUS docker and in that / is mapped to /rootfs/ for the container. Not sure if that kinda of answers/helps you with anything but I can say, you aren't alone. The array stats didn't work for me either I had to go in and adjust the panels to point to "/rootfs/mnt/user0"
  7. Have you gotten this figured out? If not, what is the IP range of your home network(s) and the IP range that OpenVPN is handing out?
  8. Is it possible to get the v1.5 development json to mess around with?
  9. Yeah, I did have that problem. I think it was an issue with recognizing that I had extracted the Easy-RSA files in the folder, I believe it was installed in appdata on my cache drives. I reinstalled the app, pointed the folder location for the certs to "/boot/openvpn/", downloaded on of the easy-rsa files, sftp-ed it to my server, unzipped it in "boot/openvpn/" and then renamed the resulting folder "easy-rsa-3.x.x" to "easy-rsa". Once I did that, the "Install RSA Key" button worked and then the generate button worked again. As far as my other problem I just did a user script to restart the app after booting. At least as a work around for now.
  10. I did have it installed prior to upgrading but I accidentally deleted the config files for it and had issues trying to get it to regenerate certs and client profiles. I ended up removing the app entirely and doing fresh reinstall saved in a new location.
  11. I am running 6.6.7, not sure about 6.7.0-rc5, but I have his app set up and running on mine. I am only having 1 issue. OpenVPN app starts with the array on boot up, shows successfully, but I am not able to get a client to connect. It is like the server doesn't respond. I have to manually restart the application and then everything works just fine. But, if unRAID reboots openVPN comes back up but connections don't work again until I manually restart the app. Has anyone run into this before? This is my first time encountering this problem.
  12. My controller is stuck starting up and I am seeing the same thing as you. I found this in another log file, be curious to see if you are seeing the same thing. Here are the errors I see: /usr/lib/unifi-video/data/db/WiredTiger.wt: handle-open: open: Operation not permitted Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 277 This chuck keeps repeating. Guessing the DB can't come up or something. tail -f /var/log/unifi-video/mongod.log 2019-02-06T13:49:07.008-0600 I CONTROL [main] ***** SERVER RESTARTED ***** 2019-02-06T13:49:07.012-0600 I CONTROL [initandlisten] MongoDB starting : pid=8183 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=cbc8a953dbae 2019-02-06T13:49:07.012-0600 I CONTROL [initandlisten] db version v3.4.18 2019-02-06T13:49:07.012-0600 I CONTROL [initandlisten] git version: 4410706bef6463369ea2f42399e9843903b31923 2019-02-06T13:49:07.012-0600 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2n 7 Dec 2017 2019-02-06T13:49:07.012-0600 I CONTROL [initandlisten] allocator: tcmalloc 2019-02-06T13:49:07.012-0600 I CONTROL [initandlisten] modules: none 2019-02-06T13:49:07.013-0600 I CONTROL [initandlisten] build environment: 2019-02-06T13:49:07.013-0600 I CONTROL [initandlisten] distmod: ubuntu1604 2019-02-06T13:49:07.013-0600 I CONTROL [initandlisten] distarch: x86_64 2019-02-06T13:49:07.013-0600 I CONTROL [initandlisten] target_arch: x86_64 2019-02-06T13:49:07.013-0600 I CONTROL [initandlisten] options: { net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", journal: { enabled: true }, mmapv1: { smallFiles: true } }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } } 2019-02-06T13:49:07.048-0600 I - [initandlisten] Detected data files in /usr/lib/unifi-video/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2019-02-06T13:49:07.048-0600 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=15039M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress), 2019-02-06T13:49:07.060-0600 E STORAGE [initandlisten] WiredTiger error (1) [1549482547:60504][8183:0x14b2e30cf180], file:WiredTiger.wt, connection: /usr/lib/unifi-video/data/db/WiredTiger.wt: handle-open: open: Operation not permitted 2019-02-06T13:49:07.061-0600 I - [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 277 2019-02-06T13:49:07.062-0600 I STORAGE [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating 2019-02-06T13:49:07.062-0600 I NETWORK [initandlisten] shutdown: going to close listening sockets... 2019-02-06T13:49:07.062-0600 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-7441.sock 2019-02-06T13:49:07.062-0600 I NETWORK [initandlisten] shutdown: going to flush diaglog... 2019-02-06T13:49:07.062-0600 I CONTROL [initandlisten] now exiting 2019-02-06T13:49:07.062-0600 I CONTROL [initandlisten] shutting down with code:100
  13. Hello, I've installed the docker and was having issues getting it to install and run with 'latest/latest_beta' specified in the config file. Based on other responses I've seen, I changed the version to '17.8.31' and it installed fine. I then updated the config file to version '17.11.24' and this installed fine. But once I try to move past this version it failes. Has anyone been able to succesffully use the latest version of this software with this docker? [Apr 07 11:13:20 AM] Processing config file *** Running /etc/my_init.d/40_install_xeoma.sh... [Apr 07 11:13:20 AM] Using Xeoma version 17.8.31 (a user-specified version) [Apr 07 11:13:20 AM] Deleting files in /config/downloads to reclaim space... Deleting /config/downloads/xeoma_*.tgz [Apr 07 11:13:20 AM] Downloading from http://felenasoft.com/xeoma/downloads/xeoma_previous_versions/?get=xeoma_linux64_17.8.31.tgz into /config/downloads [Apr 07 11:13:25 AM] Downloaded /config/downloads/xeoma_17.8.31.tgz... [Apr 07 11:13:25 AM] Installing Xeoma from /config/downloads/xeoma_17.8.31.tgz [Apr 07 11:13:25 AM] Installation complete *** Running /etc/my_init.d/50_configure_xeoma.sh... [Apr 07 11:13:25 AM] Setting the password Password set successfull [Apr 07 11:13:25 AM] Downloaded /config/downloads/xeoma_17.8.31.tgz... [Apr 07 11:13:25 AM] Installing Xeoma from /config/downloads/xeoma_17.8.31.tgz [Apr 07 11:13:25 AM] Installation complete *** Running /etc/my_init.d/50_configure_xeoma.sh... [Apr 07 11:13:25 AM] Setting the password Password set successfull *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 66 [Apr 07 11:13:25 AM] Starting the server in 5 seconds. See the log directory in your config directory for server logs. Apr 7 11:13:26 585d08292200 syslog-ng[73]: syslog-ng starting up; version='3.5.6' -------------------------------------------------------------------------------------------------------------------------------------------------------------- [Apr 07 11:24:20 AM] Processing config file *** Running /etc/my_init.d/40_install_xeoma.sh... [Apr 07 11:24:20 AM] Using Xeoma version 17.11.24 (a user-specified version) [Apr 07 11:24:20 AM] Deleting files in /config/downloads to reclaim space... Deleting /config/downloads/xeoma_*.tgz [Apr 07 11:24:20 AM] Downloading from http://felenasoft.com/xeoma/downloads/xeoma_previous_versions/?get=xeoma_linux64_17.11.24.tgz into /config/downloads [Apr 07 11:24:25 AM] Downloaded /config/downloads/xeoma_17.11.24.tgz... [Apr 07 11:24:25 AM] Skipping installation because the currently installed version is the correct one *** Running /etc/my_init.d/50_configure_xeoma.sh... [Apr 07 11:24:25 AM] Setting the password Password set successfull *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 61 [Apr 07 11:24:25 AM] Starting the server in 5 seconds. See the log directory in your config directory for server logs. Apr 7 11:24:26 585d08292200 syslog-ng[68]: syslog-ng starting up; version='3.5.6' -------------------------------------------------------------------------------------------------------------------------------------------------------------- [Apr 07 11:16:08 AM] Processing config file *** Running /etc/my_init.d/40_install_xeoma.sh... [Apr 07 11:16:08 AM] Using Xeoma version 18.2.2 (a user-specified version) [Apr 07 11:16:08 AM] Deleting files in /config/downloads to reclaim space... Deleting /config/downloads/xeoma_17.11.24.tgz [Apr 07 11:16:08 AM] Downloading from http://felenasoft.com/xeoma/downloads/xeoma_previous_versions/?get=xeoma_linux64_18.2.2.tgz into /config/downloads [Apr 07 11:16:09 AM] ERROR: Could not download from http://felenasoft.com/xeoma/downloads/xeoma_previous_versions/?get=xeoma_linux64_18.2.2.tgz md5sum: /config/downloads/xeoma_18.2.2.tgz: No such file or directory [Apr 07 11:16:09 AM] Installing Xeoma from /config/downloads/xeoma_18.2.2.tgz tar (child): /config/downloads/xeoma_18.2.2.tgz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now *** /etc/my_init.d/40_install_xeoma.sh failed with status 2 *** Killing all processes...
  14. Okay, so after putting the drive in my windows laptop and scanning, once the server booted back up, I am no longer seeing the errors in the log. Thanks for the help.
  15. Gotcha. I shutdown my server and put the flash drive in my windows laptop. When I initially inserted it, it prompted me with message that stated "errors where found on drive, click to repair". When I click to scan it, it then completed and told me no errors.