UNSOLVED Errors and not restart

vonarstonehelm

So I finally got it working the way I wanted with a few workarounds, however now it is throwing errors after a while and will disappear.

Here are the errors from pm2 logs:

/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm       | [20219:0213/125456.250611:ERROR:gles2_cmd_decoder.cc(10129)] [.DisplayCompositor-0x5a1c900]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
0|mm       | [20219:0213/125456.297244:ERROR:gles2_cmd_decoder.cc(18288)] [.DisplayCompositor-0x5a1c900]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
0|mm       | [20219:0213/125456.297506:ERROR:gles2_cmd_decoder.cc(10129)] [.DisplayCompositor-0x5a1c900]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
0|mm       | [20219:0213/125456.298002:ERROR:gles2_cmd_decoder.cc(18288)] [.DisplayCompositor-0x5a1c900]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
0|mm       | [20219:0213/125456.298138:ERROR:gles2_cmd_decoder.cc(10129)] [.DisplayCompositor-0x5a1c900]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
0|mm       | [20219:0213/125456.298485:ERROR:gles2_cmd_decoder.cc(18288)] [.DisplayCompositor-0x5a1c900]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
0|mm       | [20219:0213/125456.298619:ERROR:gles2_cmd_decoder.cc(18288)] [.DisplayCompositor-0x5a1c900]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
0|mm       | [20219:0213/125456.298699:ERROR:gles2_cmd_decoder.cc(18288)] [.DisplayCompositor-0x5a1c900]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
0|mm       | [20219:0213/125456.298815:ERROR:gles2_cmd_decoder.cc(10129)] [.DisplayCompositor-0x5a1c900]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
0|mm       | [20219:0213/125456.298880:ERROR:gles2_cmd_decoder.cc(10129)] [.DisplayCompositor-0x5a1c900]RENDER WARNING: texture bound to texture unit 2 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
0|mm       | [20219:0213/125456.298958:ERROR:gles2_cmd_decoder.cc(10129)] [.DisplayCompositor-0x5a1c900]RENDER WARNING: texture bound to texture unit 3 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
0|mm       | fatal: unable to access 'https://github.com/JonathanAndersonPE/MMM-inspirobot/': SSL connection timeout
0|mm       |
0|mm       | fatal: unable to access 'https://github.com/MichMich/MagicMirror.git/': SSL connection timeout

Edit: Here is more from the mm-errors.log:

libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
ATTENTION: default value of option force_s3tc_enable overridden by environment.
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
ATTENTION: default value of option force_s3tc_enable overridden by environment.
fatal: unable to access 'https://github.com/alberttwong/MMM-iFrame.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated.

Any ideas? Suggestions? This started after using iFrame module, so I wonder if that is causing it.

Mykle1

@vonarstonehelm said in Errors and not restart:

This started after using iFrame module, so I wonder if that is causing it.

Have you removed the iFrame module to see if that is the cause?

vonarstonehelm

@mykle1 No, however I did go in and changed the pi over to legacy non-GL drivers, and so far it has been stable for almost 5 hours now. If it crashes again tonight then I will go ahead and comment out the iframe module and see if that is in fact the root cause.

vonarstonehelm

@mykle1 So at some point my MM did go black again. I commented out my iframe module and then restarted it and now it has been stable for 6+ hours with no issues. This leads me to think it is something with iframe.

//      {
//              module: 'MMM-iFrame',
//              position: 'bottom_center',      // This can be any of the regions.
//              config: {
//                      // See 'Configuration options' for more information.
//                              url: ["http://192.168.1.132:81/livestream.htm?cam=Cam1"],  // as many URLs you want or you can just ["ENTER IN URL"] if single URL.
//                              updateInterval: 0.5 * 60 * 1000, // rotate URLs every 30 seconds
//                              width: "1280", // width of iframe
//                              height: "720", // height of iframe
//                              frameWidth: "640" // width of embedded iframe, height is beeing calculated by aspect ratio of iframe
//                      }
//              },

I am not sure what else could be causing it, or else I would try to do some more troubleshooting myself.