I understand that. Once again Rene, thank you for your time and patience!
I’ll keep trying to find solution to this problem. 
i feel sad that we couldnt find the answer.
i hope you figure it out at 1 point.
and no thanks, your welcome.
1 Like
I’ve just read through this thread, a couple of linux commands may help if the os supports them.
$ find / -name robots.txt
This is a recursive find. You will see a lot of “permission denied” after directory entries, don’t worry about those. It will show any files named “robots.txt” and the full path.
This is the end of the file when I run the command on my system.
find: ‘/var/cache/ldconfig’: Permission denied
find: ‘/var/cache/lightdm’: Permission denied
find: ‘/var/cache/apt/archives/partial’: Permission denied
find: ‘/run/udisks2’: Permission denied
find: ‘/run/lightdm’: Permission denied
find: ‘/run/samba/ncalrpc/np’: Permission denied
find: ‘/run/systemd/ask-password-block’: Permission denied
find: ‘/run/systemd/inaccessible’: Permission denied
find: ‘/media/pi/SETTINGS/lost+found’: Permission denied
find: ‘/sys/kernel/debug’: Permission denied
find: ‘/tmp/systemd-private-a58b1924e2ad43fb9eaae34254bf7a1a-systemd-timesyncd.service-VCFiB4’: Permission denied
find: ‘/home/homeassistant/.cache’: Permission denied
find: ‘/lost+found’: Permission denied
/srv/homeassistant/lib/python3.5/site-packages/hass_frontend/robots.txt
/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/frontend/www_static/robots.txt
pi@annabell:~ $
look though your list and see if there is a robots.txt file there.
Sometime I think of things after I have posted. My brain takes some time to extract these things from the cobwebs in my memory
If you redirect STDERR to /dev/null it will remove all the errors from sight
pi@annabell:~ $ find / -name robots.txt 2> /dev/null
/srv/homeassistant/lib/python3.5/site-packages/hass_frontend/robots.txt
/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/frontend/www_static/robots.txt
pi@annabell:~ $
thx for showing that.
i found a robots.txt in hass now also and it seems that that is a file to disallow user-agents.
but somehow that turns up in the dashboard section.
it can only be that paths have been wrong at some point, and at that moment there where files compiled because off that.
the compiled dir is at an unknown place for hassio and deleting what is inside is not possible because of that.
i think hassio has a central place for temp dirs and they placed it there. and even deleting and reinstalling addons doesnt clear that dir.
maybe that @frenck has a solution for it.
I’m not familiar with the file layout with hassio so I need to explore
what is the result of this command?
ls -al /config/appdaemon/compiled
I’m running Hassio. In my case, if i use find / -name robots.txt 2> /dev/null accessing HA from SSL i get no results. If I use the same command accessing Hassio/ResinOS (port 22222) i get the following:
root@hassio:~# find / -name robots.txt 2> /dev/null
/mnt/data/docker/aufs/diff/14419231acb3ce4114a8bd9088734f61958051b63ff3e7ee3613413657358150/usr/lib/python3.6/site-packages/hass_frontend/robots.txt
/mnt/data/docker/aufs/diff/6f64a5090852e2dd004979d9dbc4f8d35c44b29db1fa919ad38d4b46ad666277/usr/share/grafana/public/robots.txt
/var/lib/docker/aufs/diff/14419231acb3ce4114a8bd9088734f61958051b63ff3e7ee3613413657358150/usr/lib/python3.6/site-packages/hass_frontend/robots.txt
/var/lib/docker/aufs/diff/6f64a5090852e2dd004979d9dbc4f8d35c44b29db1fa919ad38d4b46ad666277/usr/share/grafana/public/robots.txt
/var/volatile/lib/docker/aufs/diff/14419231acb3ce4114a8bd9088734f61958051b63ff3e7ee3613413657358150/usr/lib/python3.6/site-packages/hass_frontend/robots.txt
/var/volatile/lib/docker/aufs/diff/6f64a5090852e2dd004979d9dbc4f8d35c44b29db1fa919ad38d4b46ad666277/usr/share/grafana/public/robots.txtOn HA:
core-ssh:~# ls -al /config/appdaemon/compiled
lrwxrwxrwx 1 root root 14 Mar 8 23:16 /config/appdaemon/compiled -> /data/compiled
On Hassio/ResinOS:
root@hassio:~# ls -al /config/appdaemon/compiled
ls: cannot access '/config/appdaemon/compiled': No such file or directory
can you somehow access the dir /data/compiled?
If i knew where /data/compiled was i could…
root@hassio:~# cd /
root@hassio:/# ls -la
total 383
drwxr-xr-x 20 root root 1024 Mar 6 23:28 .
drwxr-xr-x 20 root root 1024 Mar 6 23:28 ..
-rwxr-xr-x 1 root root 0 Mar 6 23:28 .dockerenv
drwxr-xr-x 2 root root 5120 Mar 6 23:28 bin
drwxr-xr-x 2 root root 1024 Mar 6 23:28 boot
drwxr-xr-x 15 root root 13660 Mar 13 12:23 dev
drwxr-xr-x 33 root root 3072 Mar 6 23:29 etc
drwxr-xr-x 3 root root 1024 Mar 6 23:28 home
drwxr-xr-x 9 root root 4096 Mar 6 23:28 lib
drwx------ 2 root root 12288 Mar 6 23:28 lost+found
drwxr-xr-x 2 root root 1024 Mar 6 23:28 media
drwxr-xr-x 5 root root 1024 Mar 6 23:28 mnt
dr-xr-xr-x 208 root root 0 Jan 1 1970 proc
drwxr-xr-x 8 root root 4096 Sep 27 15:42 resin-data
-rw-r--r-- 1 root root 347587 Mar 6 23:28 resinos.fingerprint
drwxr-xr-x 16 root root 500 Mar 13 12:23 run
drwxr-xr-x 2 root root 3072 Mar 6 23:28 sbin
drwxr-xr-x 2 root root 1024 Mar 6 23:28 srv
dr-xr-xr-x 12 root root 0 Jan 1 1970 sys
drwxrwxrwt 8 root root 160 Mar 12 23:04 tmp
drwxr-xr-x 10 root root 1024 Mar 6 23:29 usr
drwxr-xr-x 8 root root 1024 Mar 6 23:28 var
There is no folder with that name.
root@hassio:/# cd /data
-sh: cd: /data: No such file or directory
maybe inside the tmp dir?
or try searching for robots.txt_head.html
Just to be clear, i’m accessing Hassio/ResinOS directly, not any Docker container.
Nothing inside /tmp
root@hassio:/# cd tmp
root@hassio:/tmp# ls
systemd-private-02138a0d96df4144b24add121af0b06e-systemd-timesyncd.service-1iobPK
root@hassio:/tmp# ls -la
total 1
drwxrwxrwt 8 root root 160 Mar 12 23:04 .
drwxr-xr-x 20 root root 1024 Mar 6 23:28 ..
drwxrwxrwt 2 root root 40 Sep 17 13:49 .ICE-unix
drwxrwxrwt 2 root root 40 Sep 17 13:49 .Test-unix
drwxrwxrwt 2 root root 40 Sep 17 13:49 .X11-unix
drwxrwxrwt 2 root root 40 Sep 17 13:49 .XIM-unix
drwxrwxrwt 2 root root 40 Sep 17 13:49 .font-unix
drwx------ 3 root root 60 Sep 17 13:49 systemd-private-02138a0d96df4144b24add121af0b06e-systemd-timesyncd.service-1iobPK
And no robots.txt_head.html file
root@hassio:~# find / -name robots.txt_head.html 2> /dev/null
root@hassio:~#and searching for data?
(by the way i noticed that you searched outside the dockers, and thats exactly where i expect the stuff to be. it would be strange in my eyes if they relocated stuff inside a docker)
i think they use 1 central point for all editable files and temp files
if you find config, it could very well be tht the other dir is near.
How abou this?
root@hassio:~# find / -name compiled 2> /dev/null
/resin-data/homeassistant/compiled
/resin-data/homeassistant/appdaemon/compiled
/resin-data/addons/data/a0d7b954_appdaemon3/compiled
/mnt/data/resin-data/homeassistant/compiled
/mnt/data/resin-data/homeassistant/appdaemon/compiled
/mnt/data/resin-data/addons/data/a0d7b954_appdaemon3/compiledlol thats a lot of compiled dirs.
i would look in them all and if they have a subdir html, js and css, they must be from appdaemon and i would clear those subdirs.
Got it!
root@hassio:/resin-data/addons/data/a0d7b954_appdaemon3/compiled# ls -la
total 20
drwxr-xr-x 5 root root 4096 Mar 8 12:02 .
drwxr-xr-x 3 root root 4096 Mar 8 12:02 ..
drwxr-xr-x 4 root root 4096 Mar 8 16:13 css
drwxr-xr-x 4 root root 4096 Mar 8 16:13 html
drwxr-xr-x 4 root root 4096 Mar 8 16:13 javascripti would still check the others too, but if you find anything about roboto.txt in those subdirs you must be in the right place.
I have to leave to work now. I’ll search for it later. Thank you
1 Like
Only /resin-data/addons/data/a0d7b954_appdaemon3/compiled and /mnt/data/resin-data/addons/data/a0d7b954_appdaemon3/compiled have html, js and css folders.
Should i delete the folders or just the content of the folders?
to be sure just the content