Hi Everyone, I have been leaving my Pi running for longer periods and I'm seeing that the browser Chromium is crashing. Node Red itself is still up and running and if I point an external browser at it all is good. The only clue I have is this: [Chromium Error] the line of code inside the exec no…

Hi @Colin & @Andrei I believe I have solved the problem by using the switch --log-level It sets the minimum log level. Valid values are from 0 to 3: INFO = 0, WARNING = 1, LOG_ERROR = 2, LOG_FATAL = 3 So I used it like this --log-level=3 and all error messages have stopped! So the cmd line is …

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] [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":""…

[image] FatPilot: Sorry I can't remember how to format the code. 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,"appen…

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"

[image] Colin: bash -c "DISPLAY=:0 chromium-browser --noerrdialogs --disable-infobars --kiosk http://localhost:1880/ui -start-fullscreen enable-logging --v=1" 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 me…

Node-RED

Node-RED Forum

Help with error please - exec node chromium kiosk

General

Colin 4 March 2021 16:36 12

How to share code or flow json

Topic		Replies	Views
Running a script using the exec node to reboot chromium!! General	2	1434	1 December 2018
How to not have to manually refresh a dashboard ui on startup Dashboard	35	4332	2 July 2020
Open Chromium from EXEC node General	0	695	5 June 2021
How to not display refresh page in kiosk mode when i want to see dashboard nodered? Dashboard	8	1591	6 April 2021
Blank web page starting Node-Red General	11	320	25 July 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Help with error please - exec node chromium kiosk

Related topics