Homeassistant docker logs show Pseudo-terminal will not be allocated because stdin is not a terminal

Installation Home Assistant OS
1

Hi,

I’m runnin home assistant on my Pi4 using docker.
I used the supervised installer i think 1 or 2 years ago.

but when i do:

sudo docker logs $(sudo docker ps -aqf "name=homeassistant") -f

i see a lot of these messages:

Pseudo-terminal will not be allocated because stdin is not a terminal.

Somebody knows why or how to fix it?

PS: Oh i see it happened after updating to 0.111.0 and supervisor logs are still working…

Thanks!
Bye

2

i’m getting the same thing nonstop

giygas@d4k:~$ docker logs --tail=10 homeassistant
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
3

Hello,

I’m using Home Assistant OS, evetyhing up-to-date :slight_smile:
OS : Home Assistant OS 5.13
Core : core-2021.5.4
Supervisor supervisor-2021.04.3

My Core Logs if full of lines like that :

Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.

How could I investigate and track the origin of these logs ?

Thanks,
David

4

Anyone having an idea about this ?
How could I find the integration or addon responsible for these logs ?
Do I have to stop each addon one by one and restart the Core ? Or is there a way to narrow down the origin of these logs ?

Thanks,
David