aptalca
-
Posts
3,064 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by aptalca
-
-
I got Zoneminder up and running with one monitor. I would like to get push notifications to our phones for certain alarms.
I found this add-on https://github.com/pliablepixels/zmeventserver but I'm not sure how to add it to zoneminder the way it runs in docker and all...
Can you help or suggest a better way to get push notifications?
Thanks!
github page says to put the script in /usr/bin and modify a couple of scripts in there. That location is within the container.
You can get into the container by typing the following in unraid terminal:
docker exec -it Zoneminder-1_29 bash
(I'm assuming you are using the 1.29 version)
You can retrieve the script from github using wget and copy into /usr/bin
You can edit the other scripts with nano (just install nano with apt-get install and then do "export TERM=xterm")
Keep in mind thatif you edit or reinstall the container, those changes you made will be lost
Good luck
Do you think it would be wiser to run zoneminder in a VM since I want to mess around with it so much?
I just got my VT-x working on my p8z77-v LK... updating the BIOS fixed the bug where it wasn't working.
If you're gonna mess with something too much, it's always better to custom install yourself from scratch.
If you just want a working version of zoneminder that is super easy to install, then this is the container for you [emoji6]
-
Hey, any chance of making a docker for the .net version of PlexRequests?
https://github.com/tidusjar/PlexRequests.Net
This version is getting different features than the meteor version even though the two de v s work together.
I'll look into it
It seems there is already a container for this in CA. It is by Bjonness
-
Hey, any chance of making a docker for the .net version of PlexRequests?
https://github.com/tidusjar/PlexRequests.Net
This version is getting different features than the meteor version even though the two de v s work together.
I'll look into it
-
I got Zoneminder up and running with one monitor. I would like to get push notifications to our phones for certain alarms.
I found this add-on https://github.com/pliablepixels/zmeventserver but I'm not sure how to add it to zoneminder the way it runs in docker and all...
Can you help or suggest a better way to get push notifications?
Thanks!
github page says to put the script in /usr/bin and modify a couple of scripts in there. That location is within the container.
You can get into the container by typing the following in unraid terminal:
docker exec -it Zoneminder-1_29 bash
(I'm assuming you are using the 1.29 version)
You can retrieve the script from github using wget and copy into /usr/bin
You can edit the other scripts with nano (just install nano with apt-get install and then do "export TERM=xterm")
Keep in mind thatif you edit or reinstall the container, those changes you made will be lost
Good luck
-
What if you're in hell and you get mad at someone? Where do you tell them to go?
Enhanced: Notifications now sent when applications autoupdate themselves
Changed: CA now defaults to autoupdate. (All other applications still default to not autoupdate)
Added: Optional appdata backup
The appdata backup / restore feature can be found under Settings (Community Applications Section).
In a nutshell it allows you to either manually or via a scheduled job to backup your appdata folder to your Array
http://i46.photobucket.com/albums/f109/squidaz/Untitled_zpsgayo2aji.png[/img]
Appdata share Select whatever share is storing the appdata for your docker /plugin apps. Only shares which are cache-only or mounted with Unassigned Devices will be listed. If your appdata share isn't listed (ie: your appdata is already stored on the redundant array), then this module will not function for you.
Destination Share This is whatever share you want the backup to go to. DO NOT use a share that already contains any other files, as part of the process of the backup is keeping everything in sync, which ultimately means that if the file/folder does not exist in the appdata share, CA will delete it from the destination share. In other words, if you decide to backup the appdata to your "Movies" share, I will be the first to laugh.
Save To Disk Because most docker applications use hardlinks / symlinks in their appdata, the destination share HAS to be written directly to a disk share in order for the backup / restore process to work. Set this in conjunction with the Destination Share. Note that if you happen to set any split levels, include/exclude disks, etc they are automatically overridden by this setting
Path to Custom Stop / Start Script Prior to issuing the Docker Stop (and after the Docker Start) command, the backup / restore scripts will call the scripts if this is filled out. Use this to perform any custom shutdown procedures (ie: stop plugins).
Rsync Options If you don't know what you're doing here, just leave it at the defaults
Run scripts in place of rsync or in addition to Setting this to in place of has the effect of disabling CA's rsync command to backup, so that the custom scripts can handle everything
Scheduled Backup Frequency Daily / Weekly / Monthly / Custom
The temporary log file is stored within the docker.img file and upon completion is copied to the flash drive (in a DOS format). This is primarily because the log files (especially on the initial backup) has the potential to completely fill the space allocated to /var/log, I didn't want to force anyone to have to increase their allocation for the logfiles - My initial backup log file size is ~400Meg. Logs are not rolling, and are deleted at the start of each new backup / restore set.
Scheduled backups? What kind of sorcery is this? [emoji14]
I can't wait to try it
-
I was wanting to try your jDownloader Docker. I was just wondering, will jDownloader update itself?
Yep, it does
-
I am using one, I seem to recall that it won't turnoff the UPS after the server has been shutdown.
It should shut down the UPS completely. The way it is supposed to work is that before UNRAID shuts down, the APCUPSD software issues a kill-power command to the UPS which also has a time setting (maybe 60 seconds). This allows for UNRAID to complete its shutdown before power is removed completely by the UPS shutting down to prevent excessive discharge of its batteries.
The other thing for anyone to remember is to adjust the APCUPSD setting so that the shutdown process begins with enough battery power left for it to run to completion. It's also normal to set the PC's BIOS to allow an automatic start up when mains power is restored.
I don't think the ups shutdown works on the cyber power ones. It certainly doesn't work on mine and others reported the same.
All other features work, though.
-
Any luck on a Blue Iris docker?
Isn't that Windows only?
-
Hi,
I've installed aptalca's dolphin docker and really like the look of it.
However, I can't get it to do anything other than browse directories. It's probably really obvious to most of you here but I just can't figure out how to make it do things like moving files and deleting.
I think it's something to do with permissions and that by default it's set up as "nobody". I've looked through all the settings and can't find a way to change anything. I've searched google and not been able to find anything. I've even searched the forums. This makes me think it's so obvious and I'm just not getting it.
I'd really appreciate it if someone could please help me understand what is going on and how to fix it in layman's terms.
Thanks,
Graham
By default, it runs as user nobody and group users, which should have write access to your user shares in unraid.
Some config folders of certain docker containers may not provide write access for the user nobody or the group users.
If that's the issue, you can set the environment variables USER_ID and GROUP_ID to 0 when you install/edit the container in unraid gui so it will run as root. It's explained in the container description
-
Thank you so much for the Home-Automation-Bridge. I didn't know about it until 2 days ago. I can now have Alexa turn on my media center!!
Yeah the echo ended up becoming one of my best purchases. I integrated that thing with my lights, media center and everything. My friend's kids especially love chatting with Alexa lol
-
I'm installing the Zoneminder-1.29 and after I set everything up, I get a broken image in the monitor view. And this err in the logs:
ERR [getStreamCmdResponse stream error: socket_sendto( /var/run/zm/zms-607652s.sock ) failed: No such file or directory - checkStreamForErrors()]
This is a clean install. I followed the directions on this topic and got no where: https://forums.zoneminder.com/viewtopic.php?t=24499
EDIT: I fixed it. In the Setting/Paths page, change PATH_ZMS from /cgi-bin/nph-zms to /zm/cgi-bin/nph-zms
That forum post refers to the older version. I probably should update it to reflect that. The correct directions for ver 1.29 are on the docker hub page as well as the github page
-
You probably used a/mnt/user location for the config folder. Change it to /mnt/cache or /mnt/disk and it should work
If I change my Dockers to use /mnt/cache/ how do back them up? I've got my Dockers running from /mnt/user/AppData so that everything is protected in the Array. It's one of the questions I've had about Dockers and unRAID, but I haven't been able to find a definitive answer.
Look into cache pooling. That way you can have multiple disks as part of a single cache share and every piece of data exists on two separate disks (more of a mirroring approach rather than a parity protected system, but unlike traditional raid mirroring, this system uses bttrfs's builtin feature and it is very flexible in terms of showing disks of different sizes)
Or you can periodically back up the cache drive contents on a user share via a simple copy operation or rsync.
The reasons most people use cache shares for dockers are:
1. There is a bug that affects some containers and breaks them when they are on a user share (may be related to use of symlinks)
2. Writes to the protected array are much slower due to the parity calculation. Whereas if you use an ssd as a cache drive it can be much much faster so you get better performance in most dockers
3. Having the containers on a user share may put too much stress on the parity drive in the long run
-
Could your docker image file be full by any chance?
Also try the following in unraid terminal docker logs PlexRequests
That might show more info on any potential errors
Here's the Unraid logs from restarting it. How do you check if the docker image is full? I highly doubt it is, since it's 10GB and I saw this same issue when it was the only docker app installed, but I can check.
Apr 12 08:52:44 Media php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'restart' 'PlexRequests' Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: veth27e6fc1: renamed from eth0 Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth27e6fc1. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for vethca05738. Apr 12 08:52:44 Media kernel: device vethca05738 left promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: device vethfcc4630 entered promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: nf_conntrack: falling back to vmalloc. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth04d6a32. Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered disabled state Apr 12 08:52:44 Media kernel: eth0: renamed from veth04d6a32 Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:58 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f PlexRequests Apr 12 08:52:59 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state
I actually needed the logs for the container (by typing the command I posted in terminal), but. . . those messages in the unraid log don't seem right. Perhaps jonp or limetech can elaborate as there may be an issue with your network settings
-
I am attempting to install Nginx-letsencrypt. I cannot get the container to install, I click create and nothing happens.
I set the config path to /mnt/cache/nginx/config. http port is 81, https is 443. Nothing happens.
I have installed the following containers successfully:
owncloud and apache.
Is anyone else having this problem? Any ideas what I could do to get around this issue?
I really appreciate you taking your time to help.
Bill
Click on advanced view
-
Could your docker image file be full by any chance?
Also try the following in unraid terminal docker logs PlexRequests
That might show more info on any potential errors
-
Attached. Thanks!
Reposting my reply, as I think it got missed since it was last on the previous page.
Looks like you updated the log to be more verbose? It started for me again, but I came back in the morning and it wasn't running, and it won't start again. Here's the log from my last two restarts:
<--------------------------------------> Starting container on Fri Apr 8 08:24:12 PDT 2016 Updating repository Selecting the desired branch Using the master branch Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 08:24:17 0e4ab8704a53 syslog-ng[48]: syslog-ng starting up; version='3.5.3' <--------------------------------------> <--------------------------------------> Starting container on Fri Apr 8 16:39:19 PDT 2016 Updating repository Selecting the desired branch Using the master branch Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 16:39:23 0e4ab8704a53 syslog-ng[46]: syslog-ng starting up; version='3.5.3' Apr 8 17:17:01 0e4ab8704a53 /USR/SBIN/CRON[70]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 18:17:01 0e4ab8704a53 /USR/SBIN/CRON[73]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 19:17:01 0e4ab8704a53 /USR/SBIN/CRON[76]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 20:17:01 0e4ab8704a53 /USR/SBIN/CRON[79]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 21:17:01 0e4ab8704a53 /USR/SBIN/CRON[82]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 22:17:01 0e4ab8704a53 /USR/SBIN/CRON[85]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 23:17:01 0e4ab8704a53 /USR/SBIN/CRON[88]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 00:17:01 0e4ab8704a53 /USR/SBIN/CRON[91]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 01:17:01 0e4ab8704a53 /USR/SBIN/CRON[94]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 02:17:01 0e4ab8704a53 /USR/SBIN/CRON[97]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 03:17:01 0e4ab8704a53 /USR/SBIN/CRON[100]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 04:17:01 0e4ab8704a53 /USR/SBIN/CRON[103]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 05:17:01 0e4ab8704a53 /USR/SBIN/CRON[106]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:17:01 0e4ab8704a53 /USR/SBIN/CRON[109]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:25:01 0e4ab8704a53 /USR/SBIN/CRON[112]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Can you post a screenshot of your container settings?
The issue is not obvious to me. Is this a new install?
I would recommend deleting the local folder and reinstalling it from scratch.
-
Reposting my reply, as I think it got missed since it was last on the previous page.
Looks like you updated the log to be more verbose? It started for me again, but I came back in the morning and it wasn't running, and it won't start again. Here's the log from my last two restarts:
<--------------------------------------> Starting container on Fri Apr 8 08:24:12 PDT 2016 Updating repository Selecting the desired branch Using the master branch Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 08:24:17 0e4ab8704a53 syslog-ng[48]: syslog-ng starting up; version='3.5.3' <--------------------------------------> <--------------------------------------> Starting container on Fri Apr 8 16:39:19 PDT 2016 Updating repository Selecting the desired branch Using the master branch Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 16:39:23 0e4ab8704a53 syslog-ng[46]: syslog-ng starting up; version='3.5.3' Apr 8 17:17:01 0e4ab8704a53 /USR/SBIN/CRON[70]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 18:17:01 0e4ab8704a53 /USR/SBIN/CRON[73]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 19:17:01 0e4ab8704a53 /USR/SBIN/CRON[76]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 20:17:01 0e4ab8704a53 /USR/SBIN/CRON[79]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 21:17:01 0e4ab8704a53 /USR/SBIN/CRON[82]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 22:17:01 0e4ab8704a53 /USR/SBIN/CRON[85]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 23:17:01 0e4ab8704a53 /USR/SBIN/CRON[88]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 00:17:01 0e4ab8704a53 /USR/SBIN/CRON[91]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 01:17:01 0e4ab8704a53 /USR/SBIN/CRON[94]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 02:17:01 0e4ab8704a53 /USR/SBIN/CRON[97]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 03:17:01 0e4ab8704a53 /USR/SBIN/CRON[100]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 04:17:01 0e4ab8704a53 /USR/SBIN/CRON[103]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 05:17:01 0e4ab8704a53 /USR/SBIN/CRON[106]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:17:01 0e4ab8704a53 /USR/SBIN/CRON[109]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:25:01 0e4ab8704a53 /USR/SBIN/CRON[112]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Can you post a screenshot of your container settings?
-
I did a fresh install of PlexRequests yesterday, but it doesn't appear to be working. The Docker starts, but I'm never able to connect to the Web UI (http://towerip:3000). Any thoughts?
Here's the log
<--------------------------------------><-------------------------------------->
Starting container on Fri Apr 8 15:12:10 EDT 2016
First install detected, cloning repository
Selecting the desired branch
Using the master branch
Your branch is up-to-date with 'origin/master'.
Fixing permissions
Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting
npm-container: updating npm dependencies -- winston...
Changes to your project's package version selections from updating the release:
accounts-base upgraded from 1.2.2 to 1.2.5
accounts-password upgraded from 1.1.4 to 1.1.7
allow-deny added, version 1.0.3
autoupdate upgraded from 1.2.4 to 1.2.7
babel-compiler* upgraded from 5.8.24_1 to 6.6.1
babel-runtime upgraded from 0.1.4 to 0.1.7
base64 upgraded from 1.0.4 to 1.0.7
binary-heap upgraded from 1.0.4 to 1.0.7
blaze upgraded from 2.1.3 to 2.1.6
blaze-html-templates upgraded from 1.0.1 to 1.0.3
blaze-tools upgraded from 1.0.4 to 1.0.7
boilerplate-generator upgraded from 1.0.4 to 1.0.7
caching-compiler upgraded from 1.0.0 to 1.0.3
caching-html-compiler upgraded from 1.0.2 to 1.0.5
callback-hook upgraded from 1.0.4 to 1.0.7
check upgraded from 1.1.0 to 1.1.3
coffeescript upgraded from 1.0.11 to 1.0.16
ddp upgraded from 1.2.2 to 1.2.4
ddp-client upgraded from 1.2.1 to 1.2.4
ddp-common upgraded from 1.2.2 to 1.2.4
ddp-rate-limiter upgraded from 1.0.0 to 1.0.3
ddp-server upgraded from 1.2.2 to 1.2.5
deps upgraded from 1.0.9 to 1.0.11
diff-sequence upgraded from 1.0.1 to 1.0.4
ecmascript upgraded from 0.1.6 to 0.4.2
ecmascript-runtime upgraded from 0.2.6 to 0.2.9
ejson upgraded from 1.0.7 to 1.0.10
email upgraded from 1.0.8 to 1.0.11
fastclick upgraded from 1.0.7 to 1.0.10
geojson-utils upgraded from 1.0.4 to 1.0.7
hot-code-push upgraded from 1.0.0 to 1.0.3
html-tools upgraded from 1.0.5 to 1.0.8
htmljs upgraded from 1.0.5 to 1.0.8
http upgraded from 1.1.1 to 1.1.4
id-map upgraded from 1.0.4 to 1.0.6
jquery upgraded from 1.11.4 to 1.11.7
launch-screen upgraded from 1.0.4 to 1.0.10
less upgraded from 2.5.1 to 2.5.7
livedata upgraded from 1.0.15 to 1.0.17
localstorage upgraded from 1.0.5 to 1.0.8
logging upgraded from 1.0.8 to 1.0.11
meteor upgraded from 1.1.10 to 1.1.13
meteor-base upgraded from 1.0.1 to 1.0.3
minifier-css added, version 1.1.10
minifier-js added, version 1.1.10
minifiers removed from your project
minimongo upgraded from 1.0.10 to 1.0.13
mobile-experience upgraded from 1.0.1 to 1.0.3
mobile-status-bar upgraded from 1.0.6 to 1.0.11
modules added, version 0.5.2
modules-runtime added, version 0.6.2
mongo upgraded from 1.1.3 to 1.1.6
mongo-id upgraded from 1.0.1 to 1.0.3
npm-mongo upgraded from 1.4.39_1 to 1.4.42
observe-sequence upgraded from 1.0.7 to 1.0.10
ordered-dict upgraded from 1.0.4 to 1.0.6
promise upgraded from 0.5.1 to 0.6.6
random upgraded from 1.0.5 to 1.0.8
rate-limit upgraded from 1.0.0 to 1.0.3
reactive-dict upgraded from 1.1.3 to 1.1.6
reactive-var upgraded from 1.0.6 to 1.0.8
reload upgraded from 1.1.4 to 1.1.7
retry upgraded from 1.0.4 to 1.0.6
routepolicy upgraded from 1.0.6 to 1.0.9
service-configuration upgraded from 1.0.5 to 1.0.8
session upgraded from 1.1.1 to 1.1.4
sha upgraded from 1.0.4 to 1.0.6
spacebars upgraded from 1.0.7 to 1.0.10
spacebars-compiler upgraded from 1.0.7 to 1.0.10
srp upgraded from 1.0.4 to 1.0.7
standard-minifier-css added, version 1.0.5
standard-minifier-js added, version 1.0.5
standard-minifiers upgraded from 1.0.2 to 1.0.5
templating upgraded from 1.1.5 to 1.1.8
templating-tools upgraded from 1.0.0 to 1.0.3
tracker upgraded from 1.0.9 to 1.0.12
ui upgraded from 1.0.8 to 1.0.10
underscore upgraded from 1.0.4 to 1.0.7
url upgraded from 1.0.5 to 1.0.8
webapp upgraded from 1.2.3 to 1.2.7
webapp-hashing upgraded from 1.0.5 to 1.0.8
* These packages have been updated to new versions that are not backwards
compatible.
plexrequests-meteor: updated to Meteor 1.3.1.
Changes to your project's package version selections from updating package
versions:
alanning:roles upgraded from 1.2.14 to 1.2.15
aldeed:autoform upgraded from 5.7.1 to 5.8.1
aldeed:collection2 upgraded from 2.5.0 to 2.9.1
aldeed:collection2-core added, version 1.1.1
aldeed:schema-deny added, version 1.0.1
aldeed:schema-index added, version 1.0.1
aldeed:simple-schema upgraded from 1.3.3 to 1.5.3
aslagle:reactive-table upgraded from 0.8.18 to 0.8.28
fortawesome:fontawesome upgraded from 4.4.0 to 4.5.0
mdg:validation-error added, version 0.2.0
momentjs:moment upgraded from 2.10.6 to 2.12.0
percolate:synced-cron upgraded from 1.3.0 to 1.3.2
raix:eventemitter added, version 0.1.3
softwarerero:accounts-t9n upgraded from 1.1.6 to 1.1.7
standard-minifiers removed from your project
useraccounts:bootstrap upgraded from 1.12.4 to 1.13.1
useraccounts:core upgraded from 1.12.4 to 1.13.1
The following top-level dependencies were not updated to the very latest
version available:
* ongoworks:security 1.3.0 (2.0.1 is available)
* twbs:bootstrap 4.0.0-alpha (4.0.0-alpha2 is available)
Newer versions of the following indirect dependencies are available:
* mdg:validation-error 0.2.0 (0.5.1 is available)
* softwarerero:accounts-t9n 1.1.7 (1.3.3 is available)
To update one or more of these packages, pass their names to `meteor update`.
Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed
Apr 8 15:14:04 5e4a1c6e673d syslog-ng[99]: syslog-ng starting up; version='3.5.3'
[[[[[ /config/plexrequests-meteor ]]]]]
=> Started proxy.
Unexpected mongo exit code 14. Restarting.
Unexpected mongo exit code 14. Restarting.
Unexpected mongo exit code 14. Restarting.
Can't start Mongo server.
Unspecified unrecoverable error. Exit was not clean
Apr 8 15:17:01 5e4a1c6e673d /USR/SBIN/CRON[138]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 16:17:01 5e4a1c6e673d /USR/SBIN/CRON[141]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 17:17:01 5e4a1c6e673d /USR/SBIN/CRON[144]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 18:17:01 5e4a1c6e673d /USR/SBIN/CRON[147]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 19:17:01 5e4a1c6e673d /USR/SBIN/CRON[150]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 20:17:01 5e4a1c6e673d /USR/SBIN/CRON[153]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 21:17:01 5e4a1c6e673d /USR/SBIN/CRON[156]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 22:17:01 5e4a1c6e673d /USR/SBIN/CRON[159]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 8 23:17:01 5e4a1c6e673d /USR/SBIN/CRON[162]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 00:17:01 5e4a1c6e673d /USR/SBIN/CRON[165]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 01:17:01 5e4a1c6e673d /USR/SBIN/CRON[168]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 02:17:01 5e4a1c6e673d /USR/SBIN/CRON[171]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 03:17:01 5e4a1c6e673d /USR/SBIN/CRON[174]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 04:17:01 5e4a1c6e673d /USR/SBIN/CRON[177]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 05:17:01 5e4a1c6e673d /USR/SBIN/CRON[180]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 06:17:01 5e4a1c6e673d /USR/SBIN/CRON[183]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 9 06:25:01 5e4a1c6e673d /USR/SBIN/CRON[186]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Apr 9 07:17:01 5e4a1c6e673d /USR/SBIN/CRON[273]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
You probably used a/mnt/user location for the config folder. Change it to /mnt/cache or /mnt/disk and it should work
-
Looks like Zoneminder 1.29.1 is out, what is the best way to upgrade ? Wasn't sure if I need to wait until you updated the docker, or if there was another way.
Thanks.
Wanted to thank you for making the changes. Seems to be working well, will need to mess with it a bit more, but so far so good.
Thanks again.
Zoneminder is now fixed, update pushed
Great to hear is working. Let me know if you find any other bugs
It seems it was premature (they accidentally changed the version number in their github). It has now been reverted. No version 1.29.1 yet :-)
I believe the internal updater should update in the case of incremental updates (versions 1.29.X) but honestly, ever since I created the first zoneminder container, I don't think there has been any incremental updates, so that has not been tested. Worst case, I'll push an update to the container.
-
I need to see the full log
*UPDATE: Just did it and this time I get: "/defaults/letsencrypt.sh: line 11: ./letsencrypt-auto: No such file or directory"
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/firstrun.sh... Setting the correct time Current default time zone: 'Europe/Berlin' Local time is now: Fri Apr 8 19:07:24 CEST 2016. Universal Time is now: Fri Apr 8 17:07:24 UTC 2016. Using existing nginx.conf Using existing nginx-fpm.conf Using existing site config Using existing landing page Using existing jail.local Using existing fail2ban filters Using existing letsencrypt installation rm: cannot remove ‘/etc/letsencrypt’: No such file or directory SUBDOMAINS entered, processing Sub-domains processed are: -d XXXX.XXXX.XX -d XXXX.XXXX.XX -d XXXX.XXXX.XX -d XXXX.XXXX.XX -d XXXX.XXXX.XX Using existing DH parameters <-------------------------------------------------> <-------------------------------------------------> cronjob running at Fri Apr 8 19:07:24 CEST 2016 domains.conf: line 1: -d: command not found URL is XXXX.XX Subdomains are XXXX,XXXX,XXXX,XXXX,XXXX letting the script update itself; help info may be displayed, you can ignore that :-) /defaults/letsencrypt.sh: line 11: ./letsencrypt-auto: No such file or directory deciding whether to renew the cert(s) Existing certificate is still valid for another 75 day(s); skipping renewal. * Starting authentication failure monitor fail2ban ...done. *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 121 Apr 8 19:07:24 88d529fcdb60 syslog-ng[128]: syslog-ng starting up; version='3.5.3'
Oops, that second issue was my bad. I accidentally removed a line in the last update. The next version is being pushed and it should work.
-
@aptalca
Are you going to include the new Plexrequests fork on your docker?
Check it out here: https://github.com/tidusjar/PlexRequests.Net
I wasn't aware of that. I'll look into it.
But isn't .net a Windows thing??
-
I need to see the full log
-
Nice to see regularly updated container
I applied your LetsEncrypt Update for the "nightly pulls"
I saw the following in the logs, is that "normal" or did something go wrong?
error: Your local changes to the following files would be overwritten by merge: letsencrypt-auto Please, commit your changes or stash them before you can merge. Aborting
Creating virtual environment... ./letsencrypt-auto: 460: ./letsencrypt-auto: virtualenv: not found
I dont think that I saw that other versions.
I got the first one in my log last night as well. Funny enough, that's because letsencrypt updated the auto script itself the night before (v0.4.2 to v0.5.0). Not sure if that was a mistake on their part or not. I'll investigate.
For the second one, I'm assuming that your certs were renewed last night, is that correct? If so that error always happens during renewal and it never caused any issues
-
Hi there,
Thanks for the great work. I've gotten the calibre-rdp running, but I've been having a lot of trouble with plex requests. At first I couldn't access the WebGUI, but randomly it started working. It then crashed in the middle of the night, and I haven't been able to get it working again for a few weeks. In docker it shows running, but the WebGUI cannot be reached. The logs show as follows:
Updating repository
Using the master branch
The latest version of Meteor, 1.3, is already installed on this computer. Run
'meteor update' inside of a particular project directory to update that project
to Meteor 1.3
Apr 5 22:39:26 666ed119ae26 syslog-ng[60]: syslog-ng starting up; version='3.5.3'
I've set the config folder as well as the port. Anything else I'm missing?
When you first start it, it updates meteor, which can take a while depending on how slow meteor servers are (it took me over an hour once). Just let it run for a while
As for the crash, I have no idea without seeing a log or something
I'll make it more verbose so the user can see why it hasn't started yet in the logs
LSI Controller FW updates IR/IT modes
in Storage Devices and Controllers
Posted
Try this thread if you haven't already. They have newer versions of the firmware: http://forums.laptopvideo2go.com/topic/29059-sas2008-lsi92409211-firmware-files