Help with error please - exec node chromium kiosk

Hi @Colin,
When I change this I get a red circle and an error code -2

Cheers.
Paul.

What is the text of the error. Show Full Message in the three debug nodes and expand the contents.

Hi @Colin,
Here it is.

image

The only message is in the return code.

Cheers.
Paul.

Odd, could you export that flow and paste it here please.

[Edit] Is there no message at all on output 1 or 2?

No other messages.
Sorry I can't remember how to format the code.

[{"id":"3665f925.450a76","type":"exec","z":"e5593c90.29dda","command":"DISPLAY=:0 chromium-browser --noerrdialogs --disable-infobars --kiosk http://localhost:1880/ui -start-fullscreen enable-logging --v=1","addpay":false,"append":"","useSpawn":"true","timer":"","oldrc":false,"name":"Kiosk Display","x":370,"y":70,"wires":[["c3c8d968.9e3898"],["9bc4ab56.ff2458"],["ae8236a8.de0d08"]]},{"id":"4ba01b75.94a9e4","type":"inject","z":"e5593c90.29dda","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":true,"onceDelay":"1","topic":"","payload":"","payloadType":"date","x":180,"y":70,"wires":[["3665f925.450a76"]]},{"id":"c3c8d968.9e3898","type":"debug","z":"e5593c90.29dda","name":"stdout","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":590,"y":40,"wires":},{"id":"9bc4ab56.ff2458","type":"debug","z":"e5593c90.29dda","name":"stderr","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":690,"y":70,"wires":},{"id":"ae8236a8.de0d08","type":"debug","z":"e5593c90.29dda","name":"ReturnCode","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":630,"y":130,"wires":}]

How to share code or flow json

Yes, you are right, I wonder about the error. I will try a few things. It seems likely that the fact that you are making it buffer the output is responsible for the buffer overflow.

@Colin, Thank you

Just to show I can do it!! :upside_down_face: :wink:

[{"id":"3665f925.450a76","type":"exec","z":"e5593c90.29dda","command":"DISPLAY=:0 chromium-browser --noerrdialogs --disable-infobars --kiosk http://localhost:1880/ui -start-fullscreen enable-logging --v=1","addpay":false,"append":"","useSpawn":"true","timer":"","oldrc":false,"name":"Kiosk Display","x":370,"y":70,"wires":[["c3c8d968.9e3898"],["9bc4ab56.ff2458"],["ae8236a8.de0d08"]]},{"id":"4ba01b75.94a9e4","type":"inject","z":"e5593c90.29dda","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":true,"onceDelay":"1","topic":"","payload":"","payloadType":"date","x":180,"y":70,"wires":[["3665f925.450a76"]]},{"id":"c3c8d968.9e3898","type":"debug","z":"e5593c90.29dda","name":"stdout","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":590,"y":40,"wires":[]},{"id":"9bc4ab56.ff2458","type":"debug","z":"e5593c90.29dda","name":"stderr","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":690,"y":70,"wires":[]},{"id":"ae8236a8.de0d08","type":"debug","z":"e5593c90.29dda","name":"ReturnCode","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":630,"y":130,"wires":[]}]

Try this as the command
bash -c "DISPLAY=:0 chromium-browser --noerrdialogs --disable-infobars --kiosk http://localhost:1880/ui -start-fullscreen enable-logging --v=1"

1 Like

Hi @Colin,
Using that in spawn mode seems to work
getting this repeatedly out of stderr. Is it actually an error?
it may be this message which is filling the buffer.

image

I'll reboot everything and let it run.

Thanks for your help.
Cheers.
Paul.

I think it should be -enable-logging if you need that option at all.
I can't test it on a pi as I haven't got one with a desktop version of rasbian, all mine are headless servers.

@Colin

I have removed that option.
Two of these msg's but the main bulk have stopped. There were many per second.
image

I've done some googling and the error is coming from chromium.

Thanks for your help.
I think we may be there.

Good progress you did with @Colin.

I checked the config in my environment and it looks like below. This script is executed when the desktop environment is started. The 5 seconds delay is to allow Node-RED to load the flows and have the dashboard ready.

#!/bin/bash
echo "Starting chromium in 5 seconds..."
sleep 5
chromium-browser   --noerrdialogs --disable-translate  --disable-session-crashed-bubble --start-fullscreen  http://127.0.0.1:1880/ui  &
1 Like

Hi @Andrei,

Is there something after the '&' in your codeline.

Cheers
Paul.

Not really. The & is there to force Chromium running in the background. This way Chrome will no longer be "attached" to the terminal that instantiated it.

Probably running chromium from a script has a similar effect to running it explicitly using bash.

Hi @Colin and @Andrei ,
Thank you both for taking the time to help me.
The system has now been running for over 3 and a half hours and it's nearly midnight.
I'll leave it running, and see what has happened when I come down in the morning, which is usually when I find it has failed.

There are still some error messages but hopefully now as they're not being buffered they will disappear into the ether.

The system parameters are stable, cpu utilisation at about 2-3% and memory in use is also stable at under 60% used, despite this message appearing about 4 or 5 times a minuit from the stderr output on the exec node.
image

We shall see.......

Cheers.
Paul.

1 Like

Quite interesting to learn that Chrome generate so many error messages. Maybe they could be disposed to /dev/null if that helps. I just don´t remember how to do that. I always get confused with the syntax.

Hi @Andrei,
I'm hoping that they are not now being buffered and will disappear into some bit bucket!

I'll know in the morning and will update.
I would like to get to the bottom of this though, and have posted on the google chromium help forum.

Try this small flow to see the errors.

[{"id":"3665f925.450a76","type":"exec","z":"e5593c90.29dda","command":"bash -c \"DISPLAY=:0 chromium-browser --noerrdialogs --disable-infobars --kiosk http://localhost:1880/ui -start-fullscreen\"","addpay":false,"append":"","useSpawn":"true","timer":"","oldrc":false,"name":"Kiosk Display","x":360,"y":80,"wires":[["c3c8d968.9e3898"],["9bc4ab56.ff2458"],["ae8236a8.de0d08"]]},{"id":"4ba01b75.94a9e4","type":"inject","z":"e5593c90.29dda","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":true,"onceDelay":"1","topic":"","payload":"","payloadType":"date","x":170,"y":80,"wires":[["3665f925.450a76"]]},{"id":"c3c8d968.9e3898","type":"debug","z":"e5593c90.29dda","name":"stdout","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":600,"y":40,"wires":[]},{"id":"9bc4ab56.ff2458","type":"debug","z":"e5593c90.29dda","name":"stderr","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":600,"y":80,"wires":[]},{"id":"ae8236a8.de0d08","type":"debug","z":"e5593c90.29dda","name":"ReturnCode","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":620,"y":120,"wires":[]}]

To really see the errors take off add this parameter "enable-logging --v=1"

Cheers.
Paul.

That should be --enable-logging. Without the -- it will try to open the url enable-logging. What does the --v=1 do?