poldim
-
Posts
69 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by poldim
-
-
On 9/24/2016 at 6:39 AM, Viaduct said:
ipmi.sh
Script for monitoring IPMI parameters.
** A working influxdb setup is required - see opening post **
**Disclaimer: I am not a programmer and thus please use the scripts at your own risk. Please read the script to understand what it is trying to achieve. There is no error trapping in it and no check to see if it is already running, so in theory if the script running time is longer than the crontab interval you could end up in a ever increasing system load and potentially crash the server.**
This requires ipmi-sensors to be installed. I use the excellent dmacias IPMI plugin which installs this.
You need to edit the script to add the devices you want measuring in the $tagsArray statement. Different motherboards will have different values. Run ipmi-sensors from the command line to see what yours are. I'm not clever enough to write a script that does it automatically. And you will need to change the parameters mentioned in the first post in the curl statement. You will need to use a unix type editor to do it e.g. Notepad++ such that the correct line endings are in the file. Save them somewhere that crontab can access them (mine are in /mnt/cache/appdata/myscripts/).
Note that the tagName cannot have spaces in, so I have had to add an extra line to remove the spaces from the string.
#!/usr/bin/php <?php $tagsArray = array( "CPU_FAN1", "REAR_FAN1", "REAR_FAN2", "MB Temp", "CPU Temp" ); //do system call $call = "ipmi-sensors"; $output = shell_exec($call); //parse output for tag and value foreach ($tagsArray as $tag) { preg_match("/".$tag.".*(\b\d+\b)\..*$/mi", $output, $match); //send measurement, tag and value to influx sendDB($match[1], $tag); } //end system call //send to influxdb function sendDB($val, $tagname) { $tagname2 = str_replace(' ', '', $tagname); $curl = "curl -i -XPOST 'http://influxDBIP:8086/write?db=telegraf' --data-binary 'IPMI,host=Tower,region=us-west " .$tagname2."=".$val."'"; $execsr = exec($curl); } ?>I run this script every 5 min in crontab:
*/5 * * * * /mnt/cache/appdata/myscripts/ipmi.sh &>/dev/null 2>&1
Grafana does not need any specific setup to show this metric since it is a simple value. The measurement IPMI will appear in the list of measurements to select.
To show fan speed and temp on the same graph, move the temps to the right axis and the fans to the left axis.
@Viaduct - Thanks for the script! I tweaked the. regex a bit to include the decimal places as my current draw was below 1. Seems to be working well.
Will the crontab settings save reboots or does it need to be added to the GO script?
preg_match("/".$tag.".*(\b\d+\b\.\d\d).*$/mi", $output, $match);
-
Anyone have any ideas why my LE docker cannot ping the unraid IP? I've got LE bound to a custom IP of 10.1.1.8 while my unraid is 10.1.1.10. Certs went through fine, but cannot successfully ping the unraid IP:
Trying to RP to my homeassistant docker and getting a `failed (113: Host is unreachable) while connecting to upstream` error
docker exec -it letsencrypt /bin/bash root@e01490db42ac:/$ curl http://10.1.1.10:8123/ curl: (7) Failed to connect to 10.1.1.10 port 8123: Host is unreachable root@e01490db42ac:/$ ping 10.1.1.10 PING 10.1.1.10 (10.1.1.10): 56 data bytes ^C --- 10.1.1.10 ping statistics --- 14 packets transmitted, 0 packets received, 100% packet loss root@e01490db42ac:/$ ping 10.1.1.1 PING 10.1.1.1 (10.1.1.1): 56 data bytes 64 bytes from 10.1.1.1: seq=0 ttl=64 time=0.475 ms 64 bytes from 10.1.1.1: seq=1 ttl=64 time=0.383 ms 64 bytes from 10.1.1.1: seq=2 ttl=64 time=0.391 ms 64 bytes from 10.1.1.1: seq=3 ttl=64 time=0.378 ms ^C --- 10.1.1.1 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 0.378/0.406/0.475 ms root@e01490db42ac:/$ ping 10.1.1.8 PING 10.1.1.8 (10.1.1.8): 56 data bytes 64 bytes from 10.1.1.8: seq=0 ttl=64 time=0.072 ms 64 bytes from 10.1.1.8: seq=1 ttl=64 time=0.063 ms ^C --- 10.1.1.8 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.063/0.067/0.072 ms -
5 hours ago, aptalca said:
Why not reverse proxy both on port 80?
I'd love to do that, but I can't seem to get it working. Basically it would be two services that come in on port 80 but would need to go to two different locations.
Do you have any hints/guides/examples?
-
Does anyone have LE running with a pihole (pi-hole) container?
I'm trying to get something like this https://hub.docker.com/r/diginc/pi-hole/ running but not sure how to setup LE / nginx config to prevent breaking my existing forwards. I have a wordpress site that externally hosted on 80 and also want to have the pihole
Quote- Port 80 is highly recommended because if you have another site/service using port 80 by default then the ads may not transform into blank ads correctly. To make sure docker-pi-hole plays nicely with an existing webserver you run you'll probably need a reverse proxy webserver config if you don't have one already. Pi-Hole has to be the default web app on said proxy e.g. if you goto your host by IP instead of domain then pi-hole is served out instead of any other sites hosted by the proxy. This is the 'default_server' in nginx or 'default' virtual host in Apache and is taken advantage of so any undefined ad domain can be directed to your webserver and get a 'blocked' response instead of ads.
-
You can still map other ports to pi-hole port 80 using docker's port forwarding like this
-p 8080:80, but again the ads won't render propertly. Changing the inner port 80 shouldn't be required unless you run docker host networking mode. -
Here is an example of running with jwilder/proxy (an nginx auto-configuring docker reverse proxy for docker) on my port 80 with pihole on another port. Pi-hole needs to be
DEFAULT_HOSTenv in jwilder/proxy and you need to set the matchingVIRTUAL_HOSTfor the pihole's container. Please read jwilder/proxy readme for more info if you have trouble. I tested this basic example which is based off what I run.
-
23 hours ago, CHBMB said:
OK, so what isn't working?
My setup:
-
192.168.2.0/24 - VLAN 20 - HOMELAB
-
192.168.3.0/24 - VLAN 30 - HOME AUTOMATION
-
192.168.4.0/24 - VLAN 40 - WLAN
-
192.168.5.0/24 - VLAN 50 - GUEST [Subnet routing only blocked for GUEST VLAN.]
What happens:
- 4G connection from cell -> nginx reverse proxy = works
- VM on HOMELAB VLAN -> nginx reverse proxy = works
- VM on HOME AUTOMATION VLAN -> nginx reverse proxy = does not work
- phone/laptop on WLAN VLAN -> nginx reverse proxy = does not work
- phone/laptop on WLAN VLAN -> IP of service on HOMELAB VLAN = works
The unraid server has the letsencrypt / nginx docker. The server sits on 192.168.2.100 VLAN 20 but is bridged to 192.168.3.100 VLAN 30 and 192.168.4.100 VLAN 40. I added the networking settings to the gdoc https://docs.google.com/document/d/1Cf8qLFcBVAen3yxqcOzA3kI_KbaRuS582b7yE7X7J1Q/edit?usp=sharing
What does not make sense to me:
- I can access the UniFi UI on 192.168.2.100 from my macbook or phone which are 192.168.4.1xx
- I can access my security cameras that are 192.168.3.xxx from the same macbook/phone and VM hosted on 192.168.2.xxx.
Doesn't this mean that subnet routing is, in fact, working correctly?
Is this correct while on WAN: unifi.mydomain.com
-
Phone > DNS lookup and send me to my router > router forwards 80 + 443 to 80 and 443 on my unraid server > letsencrypt is bound to those ports, receives the request, and forwards to the appropriate internal address based on config.
-
If I have hairpin NAT enabled, is the process the same? Does the lookup for unifi.mydomain.com not get routed by the router back to the unraid server?
-
-
1 hour ago, CHBMB said:
Post your complete config file. I'm confused..... First it was plex and now unifi. I need to be able to see the whole config file.
Here are all of the relevant settings that I can think of:
https://docs.google.com/document/d/1Cf8qLFcBVAen3yxqcOzA3kI_KbaRuS582b7yE7X7J1Q/edit?usp=sharing
-
On 6/19/2017 at 1:52 PM, CHBMB said:
Sounds like a routing issue, look for NAT reflection in your router setup. VLAN communication is nothing to do with nginx that's your network topology and routing rules.
Any ideas on anything else to check? I have no issues accessing the resources while on the LAN across subnets. Makes me think it's some kind of nginx setting...
-
17 hours ago, aptalca said:
I'm not sure what you're trying to accomplish, you have too many variables there that need to be validated, which makes troubleshooting very difficult.
Plus, the listed config above is only listening on port 443 with ssl, but you're trying to connect to http, which is port 80 with no ssl.
Why don't you start with the default config, see if you can access the welcome page so you can confirm the dns is correct? Then you can try the proxy.I discovered that my problem was appending the URL with the final destination. IE:
proxy_pass https://192.168.2.100:32400/web/index.html;does not work, but removing "/web/index.html" makes it happy:
proxy_pass https://192.168.2.100:8443;I've now got access to both my unifi and plex interface on my phone while on 4G. BUT, I'm still unable to connect while connected to the WIFI in the house.
Are there some kind of additional settings in nginx to allow it to route the connection between VLANs? My wifi is on a separate VLAN but I have no issues hitting the direct IP of the interfaces. When trying to access the subdomain.domain.com I get the following error: ERR_EMPTY_RESPONSE or ERR_CONNECTION_TIMED_OUT
-
On 6/13/2017 at 11:07 PM, poldim said:
Still having trouble with this.
THESE are my current domain settings. I've tried having both 'www' and '@' before .mydomain.com and still noting.
This is my default config:
server { listen 443 ssl; root /config/www/unifi; index index.html index.htm index.php; server_name unifi.*; ssl_certificate LOCATION_REDACTED; ssl_certificate_key LOCATION_REDACTED; ssl_dhparam LOCATION_REDACTED; ssl_ciphers 'CIPHER_REDACTED'; ssl_prefer_server_ciphers on; client_max_body_size 0; location = / { include /config/nginx/proxy.conf; proxy_pass https://192.168.2.100:8443/manage/account/login; } }
EDIT:So I added the CNAME records for www + unifi and sending them to @. I then pulled up http://unifi.mydomain.com/ on my mac and get nothing. I tried my phone on wifi and it timed out. I tried my phone on 4G and am getting THIS:
Outdated Browser You are using an outdated browser. Please upgrade your browser to improve your experience. {{toast.message}}Partial success as it's prompting to open the unifi app....now how do I get it to work?
Anyone have any recommendations on what I could look at to try to solve this?
-
Still having trouble with this.
THESE are my current domain settings. I've tried having both 'www' and '@' before .mydomain.com and still noting.
This is my default config:
server { listen 443 ssl; root /config/www/unifi; index index.html index.htm index.php; server_name unifi.*; ssl_certificate LOCATION_REDACTED; ssl_certificate_key LOCATION_REDACTED; ssl_dhparam LOCATION_REDACTED; ssl_ciphers 'CIPHER_REDACTED'; ssl_prefer_server_ciphers on; client_max_body_size 0; location = / { include /config/nginx/proxy.conf; proxy_pass https://192.168.2.100:8443/manage/account/login; } }
EDIT:So I added the CNAME records for www + unifi and sending them to @. I then pulled up http://unifi.mydomain.com/ on my mac and get nothing. I tried my phone on wifi and it timed out. I tried my phone on 4G and am getting THIS:
Outdated Browser You are using an outdated browser. Please upgrade your browser to improve your experience. {{toast.message}}Partial success as it's prompting to open the unifi app....now how do I get it to work?
-
Anyone have a breakdown on how to make a certificate for unifi that lives in this docker?
-
1 hour ago, DZMM said:
Thanks - that was driving me crazy
This is odd, when I restart my docker, the upload limit is 4.7 Mb/s and download is 9.7 Mb/s.
I havent changed my rtorrent.rc file which still states
download_rate = 10000 upload_rate = 5000 -
On 4/9/2017 at 0:52 PM, bobbintb said:
It should already since the config files aren't saved in the image. The issue I've had is with restarts, not necessarily updates. If so, shut down the docker, manually edit the config file, and start it again.
The upload rate is one of the few settings that is consistently getting wiped after each update.
Where is the upload rate set in the config manually?
-
How can I make the upload speed limit a persistent setting that survives docker updates?
-
On 3/13/2017 at 5:40 PM, trurl said:
Do you have an rutorrent folder within the appdata folder (that is how most people do it)? I would expect an rutorrent plugins folder to be within the rutorrent folder in appdata.
Do you really understand volume mapping?
yea, i get mapping. all of my dockers follow the standard appdata folder structure.
no plugins folder, and there isnt one in the sub folders either.
root@ChiRAID:/mnt/user/appdata/rutorrent# ls -l total 0 drwxr-xr-x 1 poldim users 44 Dec 15 00:09 log/ drwxr-xr-x 1 poldim users 20 Dec 15 00:09 nginx/ drwxr-xr-x 1 poldim users 14 Dec 15 00:09 php/ drwxr-xr-x 1 poldim users 48 Dec 15 19:12 rtorrent/ drwxr-xr-x 1 poldim users 32 Dec 15 19:12 rutorrent/ -
How can I change the permissions settings of the new files that ruTorrent makes?
It looks like it's currently making them as drwxr-xr-x which isn't giving couchpotato the ability to rename and move the files automatically. Can RU make the files with 777 file permissions?
-
On 3/14/2017 at 5:05 PM, kstile said:
I just have to unplug/replug after rebooting unraid.
Why do you have to do this?
-
11 hours ago, trurl said:
I don't use this but it sounds like there is supposed to already be a plugins folder in your appdata for rutorrent. Have you looked?
I have, no plugins folder in the appdata folder nor within the docker itself.
-
How can I use this, https://github.com/xombiemp/rutorrentMobile, which needs to be installed in the plugins directory? Is this a folder that I would need to map myself or does it need to exist elsewhere?
-
Feb 25 18:52:52 ChiRAID kernel: usb 5-1: USB disconnect, device number 7 Feb 25 18:54:44 ChiRAID kernel: usb 5-1: new full-speed USB device number 8 using uhci_hcd Feb 25 18:54:44 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 25 19:05:44 ChiRAID kernel: usb 5-1: USB disconnect, device number 8 Feb 25 19:05:48 ChiRAID kernel: usb 5-1: new full-speed USB device number 9 using uhci_hcd Feb 25 19:05:48 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 25 19:07:15 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 25 21:27:00 ChiRAID kernel: br0: port 3(vnet1) entered disabled state Feb 25 21:27:00 ChiRAID kernel: device vnet1 left promiscuous mode Feb 25 21:27:00 ChiRAID kernel: br0: port 3(vnet1) entered disabled state Feb 26 00:00:01 ChiRAID kernel: mdcmd (40): check Feb 26 00:00:01 ChiRAID kernel: md: recovery thread: check P ... Feb 26 00:00:01 ChiRAID kernel: md: using 1536k window, over a total of 4883770532 blocks. Feb 26 01:00:01 ChiRAID root: mover started Feb 26 01:00:01 ChiRAID root: mover finished Feb 26 09:08:55 ChiRAID kernel: md: sync done. time=32934sec Feb 26 09:08:55 ChiRAID kernel: md: recovery thread: completion status: 0 Feb 26 14:28:36 ChiRAID kernel: usb 5-1: USB disconnect, device number 9 Feb 26 14:28:44 ChiRAID kernel: usb 2-1: new high-speed USB device number 10 using ehci-pci Feb 26 14:28:44 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:28:44 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:29:27 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 11 using ehci-pci Feb 26 14:29:27 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:34:33 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 26 14:34:59 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 26 14:35:20 ChiRAID emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Feb 26 14:35:23 ChiRAID kernel: usb 2-1: USB disconnect, device number 10 Feb 26 14:35:23 ChiRAID kernel: usb 2-1.4: USB disconnect, device number 11 Feb 26 14:35:32 ChiRAID kernel: usb 2-1: new high-speed USB device number 12 using ehci-pci Feb 26 14:35:32 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:35:32 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:35:32 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 13 using ehci-pci Feb 26 14:35:32 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:41 ChiRAID kernel: usb 2-1: USB disconnect, device number 12 Feb 26 14:35:41 ChiRAID kernel: usb 2-1.4: USB disconnect, device number 13 Feb 26 14:35:44 ChiRAID kernel: usb 2-1: new high-speed USB device number 14 using ehci-pci Feb 26 14:35:45 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:35:45 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:35:45 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 15 using ehci-pci Feb 26 14:35:45 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:54 ChiRAID kernel: usb 2-1: USB disconnect, device number 14 Feb 26 14:35:54 ChiRAID kernel: usb 2-1.4: USB disconnect, device number 15 Feb 26 14:35:58 ChiRAID kernel: usb 2-1: new high-speed USB device number 16 using ehci-pci Feb 26 14:35:59 ChiRAID kernel: hub 2-1:1.0: USB hub found Feb 26 14:35:59 ChiRAID kernel: hub 2-1:1.0: 4 ports detected Feb 26 14:35:59 ChiRAID kernel: usb 2-1.4: new full-speed USB device number 17 using ehci-pci Feb 26 14:35:59 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device -
2 hours ago, saarg said:
I have not had the same experience with my Z-wave stick. For some reason your device disconnects. Check your log for any USB errors.
Here's the log:
root@ChiRAID:~# cat /var/log/syslog | grep ttyACM Feb 24 08:52:12 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM0: USB ACM device Feb 24 13:32:54 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 24 14:37:16 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM0: USB ACM device Feb 24 15:04:46 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM0: USB ACM device Feb 25 18:54:44 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 25 19:05:48 ChiRAID kernel: cdc_acm 5-1:1.0: ttyACM1: USB ACM device Feb 26 14:29:27 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:32 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:45 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 26 14:35:59 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Feb 28 02:30:02 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM1: USB ACM device Feb 28 09:55:06 ChiRAID root: home-assistant: Error response from daemon: linux runtime spec devices: error gathering device information while adding custom device "/dev/ttyACM0": lstat /dev/ttyACM0: no such file or directory Error: failed to start containers: home-assistantunifi: started succesfully! Mar 1 02:30:01 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device Mar 2 02:30:02 ChiRAID kernel: cdc_acm 2-1.4:1.0: ttyACM1: USB ACM deviceI think I know what it is:
I had HA initializing a soft reset based on the suggestion on their zwave config page (all the way at the bottom) that ran nightly at 2:30.
Any idea what's after cdc_acm in the log? Is it the USB bus/device/etc?
I'd still like to find a solution to permanently bind the device to a static mapping. I've got a separate thread HERE for it, but no responses.
-
Any takers here?
-
On 2/27/2017 at 1:21 PM, saarg said:
Probably is a way, but I don't know how.
The easy way is to not unplug it
I've now had the device change it's address from /dev/ttyACM0 to /dev/ttyACM1 and /dev/ttyACM1 to /dev/ttyACM0 at separate times completely on it's own. How do I stop this from happening?
-
I've tried to follow this guide for making a persistent path for my zwave stick and udevinfo doesn't appear to be recognized.
# udevinfo -bash: udevinfo: command not foundlsusb produces the device
# lsusb Bus 002 Device 019: ID 0658:0200 Sigma Designs, Inc.Any thoughts on what can be done to persistently link it to a fixed path?
[support] digiblur's Docker Template Repository
in Docker Containers
Posted
I'm getting a similar error:
[32m20-04-18 14:38:39 INFO (MainThread) [__main__] Initialize Hass.io setup[0m [32m20-04-18 14:38:39 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 200[0m [32m20-04-18 14:38:39 INFO (SyncWorker_0) [hassio.docker.supervisor] Connect Supervisor to Hass.io Network[0m [32m20-04-18 14:38:43 INFO (MainThread) [__main__] Setup HassIO[0m [33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.systemd] No systemd support on the host. Host control has been disabled.[0m [33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.hostname] No hostname support on the host. Hostname functions have been disabled.[0m [33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.[0m [33m20-04-18 14:38:43 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.[0m [32m20-04-18 14:38:43 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()[0m [32m20-04-18 14:38:43 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host[0m [32m20-04-18 14:38:43 INFO (MainThread) [hassio.dns] No CoreDNS plugin Docker image homeassistant/amd64-hassio-dns found.[0m [32m20-04-18 14:38:43 INFO (MainThread) [hassio.dns] Setup CoreDNS plugin[0m [32m20-04-18 14:38:43 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-dns tag 1.[0m [32m20-04-18 14:38:58 INFO (MainThread) [hassio.dns] CoreDNS plugin now installed[0m [32m20-04-18 14:38:58 INFO (MainThread) [hassio.dns] Start CoreDNS plugin[0m [32m20-04-18 14:38:58 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to 172.30.32.3[0m [32m20-04-18 14:39:10 INFO (SyncWorker_1) [hassio.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3[0m [32m20-04-18 14:39:10 INFO (MainThread) [hassio.homeassistant] No Home Assistant Docker image homeassistant/intel-nuc-homeassistant found.[0m [32m20-04-18 14:39:10 INFO (MainThread) [hassio.homeassistant] Setup HomeAssistant landingpage[0m [32m20-04-18 14:39:10 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/intel-nuc-homeassistant tag landingpage.[0m [32m20-04-18 14:39:27 INFO (MainThread) [hassio.homeassistant] Start HomeAssistant landingpage[0m [32m20-04-18 14:39:31 INFO (SyncWorker_9) [hassio.docker.homeassistant] Start homeassistant homeassistant/intel-nuc-homeassistant with version landingpage[0m [32m20-04-18 14:39:36 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.store] Load add-ons from store: 62 all - 62 new - 0 remove[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.addons] Found 0 installed add-ons[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.discovery] Load 0 messages[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.ingress] Load 0 ingress session[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 0[0m [32m20-04-18 14:39:37 INFO (MainThread) [__main__] Run Hass.io[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.api] Start API on 172.30.32.2[0m [32m20-04-18 14:39:37 INFO (MainThread) [hassio.supervisor] Update Supervisor to version 217[0m [32m20-04-18 14:39:37 INFO (SyncWorker_14) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:200 to homeassistant/amd64-hassio-supervisor:217[0m [32m20-04-18 14:39:37 INFO (SyncWorker_14) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 217.[0m [32m20-04-18 14:40:54 INFO (SyncWorker_14) [hassio.docker.interface] Tag image homeassistant/amd64-hassio-supervisor with version 217 as latest[0m [32m20-04-18 14:40:54 INFO (SyncWorker_14) [hassio.docker.interface] Stop hassio_supervisor application[0m [32m20-04-18 14:40:54 INFO (MainThread) [__main__] Stopping Hass.io[0m [32m20-04-18 14:40:54 INFO (MainThread) [hassio.api] Stop API on 172.30.32.2[0m [32m20-04-18 14:40:54 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding[0m [32m20-04-18 14:40:54 INFO (MainThread) [hassio.core] Hass.io is down[0m [32m20-04-18 14:40:54 INFO (MainThread) [__main__] Close Hass.io[0m