MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. scottwalsh
    3. Posts
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    S
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 21
    • Groups 0

    Posts

    Recent Best Controversial
    • MM Screen goes blank 5-20min after starting (was stable on 2.31) - Pi Zero 2W running MagicMirrorOS

      MM Screen goes blank 5-20min after starting (was stable on 2.31) - Pi Zero 2W running MagicMirrorOS

      Have recently reimaged my MM, and since the rebuild, the MM screen goes blank 5-20min after starting. Is intermittent though, sometimes stays up for a while.

      Am using MagicMirrorOS, which uses Khassel’s docker implementation on a lightweight OS build. Running this on a Pi Zero 2W.

      To isolate the cause, reimaged it again, and progressively configured it until the issue started to reoccur.
      (I store my configuration files in a private git repo that have a script to pull them on starting MM - so can roll configuration back and forth).

      With the below config.js file, electron crashes - about 5-30min after docker is started. If I remove the calendar & CalendarExt3 module config block - then it stays up longer (hours) but still crashes (sometimes does still crash on first start).

      Any suggestions on where to next to troubleshoot this was would be appreciated.

      config.js

      /* Config Sample
       *
       * For more information on how you can configure this file
       * see https://docs.magicmirror.builders/configuration/introduction.html
       * and https://docs.magicmirror.builders/modules/configuration.html
       *
       * You can use environment variables using a `config.js.template` file instead of `config.js`
       * which will be converted to `config.js` while starting. For more information
       * see https://docs.magicmirror.builders/configuration/introduction.html#enviromnent-variables
       */
      let config = {
      	address: "0.0.0.0",	// Address to listen on, can be:
      							// - "localhost", "127.0.0.1", "::1" to listen on loopback interface
      							// - another specific IPv4/6 to listen on a specific interface
      							// - "0.0.0.0", "::" to listen on any interface
      							// Default, when address config is left out or empty, is "localhost"
      	port: 8080,
      	basePath: "/",	// The URL path where MagicMirror² is hosted. If you are using a Reverse proxy
      									// you must set the sub path here. basePath must end with a /
      	ipWhitelist: [],	// Set [] to allow all IP addresses
      									// or add a specific IPv4 of 192.168.1.5 :
      									// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
      									// or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
      									// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],
      
      	useHttps: false,			// Support HTTPS or not, default "false" will use HTTP
      	httpsPrivateKey: "",	// HTTPS private key path, only require when useHttps is true
      	httpsCertificate: "",	// HTTPS Certificate path, only require when useHttps is true
      
      	language: "en",
      	locale: "en-US",   // this variable is provided as a consistent location
      			   // it is currently only used by 3rd party modules. no MagicMirror code uses this value
      			   // as we have no usage, we  have no constraints on what this field holds
      			   // see https://en.wikipedia.org/wiki/Locale_(computer_software) for the possibilities
      
      	logLevel: ["INFO", "LOG", "WARN", "ERROR"], // Add "DEBUG" for even more logging
      	timeFormat: 24,
      	units: "metric",
      
      	modules: [{ module: "MMM-mmpm" },
      		{
      			module: "alert",
      		},
      
      
      
      
      		{
      			module: "calendar",
      			header: "Family Calendar",
      			//position: "fullscreen_above",
      			config: {
      				broadcastPastEvents: true,
      		                maximumNumberOfDays: 28,
      		                pastDaysCount: 13,
      		                maximumEntries: 300,
      				fetchInterval: 960000,
      				calendars: [
      					{
      					url: "https://calendar.google.com/calendar/ical/[Redacted]/basic.ics",
      			                name: "Scott",
      					color: "ForestGreen",
      					},
      					{
      					url: "https://calendar.google.com/calendar/ical/[Redacted]/basic.ics",
      			                name: "Sarah",
      					color: "deeppink",
      					},
      					{
      					url: "https://calendar.google.com/calendar/ical/[Redacted]/basic.ics",
      			                name: "Skyla",
      					color: "Gold",
      					},
      					{
      					url: "https://calendar.google.com/calendar/ical/[Redacted]/basic.ics",
      			                name: "Willow",
      					color: "Gold",
      					},
      					{
      					url: "https://calendar.google.com/calendar/ical/[Redacted]/basic.ics",
      		                        name: "Family",
      					color: "Gold",
      					},
      				]
      			}
      		},
      		  
      
      
      		{
      			module: "MMM-CalendarExt3",
                  		//position: "fullscreen_above",
                          position: "top_bar",
                 		title: "Family Calendar",
                  		config: {
      		                instanceId: "familyCalendar",
      		                mode: "week",
      		                weekIndex: 0,
      		                weeksInView: 4,
      		                displayEndTime: true,
      				useSymbol: false,
      		                locale: 'en-NZ',
      				refreshInterval: 660000,
      		                eventTimeOptions: {timeStyle: 'short', hour12: false},
      		                maxEventLines: 8,
      		                firstDayOfWeek: 1,
      		                fontSize: '20px',
      		                eventHeight: '20px',
      		                calendarSet: ['Scott','Sarah','Skyla','Willow','Family'],
                  		}
              	},
      
      		  
      	
      		  
      		  
      		{
      			module: "clock",
      			position: "bottom_left"
      		},
      
      		{
      			module: "MMM-AVStock",
      			position: "bottom_center",
      			config: {
      				mode: "grid",
      				classes: "xsmall",
                  			maxTableRows: 5,
      				symbols : ["NZDUSD=X", "NZDAUD=X", "NZDEUR=X", "NZDJPY=X", "^NZ50", "^GSPC", "^AXJO", "^STOXX", "^N225", "IBM", "BRK-B", "RKLB"],
          				alias: ["USD", "AUD", "EUR", "YEN", "NZX50", "S&P 500", "ASX 200", "STXE 600", "Nikkei 225"],
      				showChart: false,
                  			showVolume: false,
      				decimals: 3,
      			}
      		},
      
      		{
      			module: "weather",
      			position: "bottom_right",
      			config: {
      				weatherProvider: "openmeteo",
      				type: "current",
      				lat: -41.323407,
      				lon: 174.7984817
      			},
      		},
      
      		{
      			module: "updatenotification",
      			//position: "bottom_bar"
      		},
      
      
      	] };
      
      /*************** DO NOT EDIT THE LINE BELOW ***************/
      if (typeof module !== "undefined") { module.exports = config; }
      

      Error log extracts

      scottwalsh@calendar:~ $ docker logs mm
      [entrypoint 08:10:08.796] [INFO]   copy default modules
      
      > magicmirror@2.32.0 start
      > node --run start:x11
      
      [2025-07-19 08:11:20.897] [LOG]   Starting MagicMirror: v2.32.0 
      [2025-07-19 08:11:22.511] [LOG]   Loading config ... 
      [2025-07-19 08:11:22.530] [LOG]   config template file not exists, no envsubst 
      
      [Snip]
      
      [2025-07-19 08:13:26.838] [INFO]  Checking git for module: MagicMirror 
      [2025-07-19 08:13:27.494] [ERROR] We expected a redirect to guce.yahoo.com, but got https://finance.yahoo.com/quote/AAPL/ 
      [2025-07-19 08:13:27.497] [ERROR] We'll try to continue anyway - you can safely ignore this if the request succeeds 
      [2025-07-19 08:13:27.508] [LOG]   Success. Cookie expires on Sun Jul 19 2026 14:13:26 GMT+1200 (New Zealand Standard Time) 
      [2025-07-19 08:13:27.547] [LOG]   fetch https://query1.finance.yahoo.com/v1/test/getcrumb 
      [2025-07-19 08:13:30.595] [LOG]   New crumb: WxlJ.T9HZVG 
      [30:0719/132347.804243:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:78] Fatal Wayland communication error: Broken pipe.
      [30:0719/132347.898470:FATAL:electron/shell/browser/electron_browser_main_parts.cc:502] Failed to shutdown.
      scottwalsh@calendar:~ $ 
      scottwalsh@calendar:~ $ docker logs labwc
      00:00:00.009 [INFO] [seatd/seat.c:48] Created VT-bound seat seat0
      00:00:00.010 [INFO] [seatd/seatd.c:194] seatd started
      failed to connect to display
      failed to connect to display
      failed to connect to display
      00:00:02.888 [INFO] [seatd/server.c:145] New client connected (pid: 1, uid: 1000, gid: 1000)
      00:00:02.889 [INFO] [seatd/seat.c:239] Added client 1 to seat0
      00:00:02.889 [INFO] [seatd/seat.c:563] Opened client 1 on seat0
      failed to connect to display
      failed to connect to display
      failed to connect to display
      HDMI-A-1 "Stargate Technology 1560FX (HDMI-A-1)"
        Make: Stargate Technology
        Model: 1560FX
        Serial: (null)
        Physical size: 330x220 mm
        Enabled: yes
        Modes:
          1920x1080 px, 60.000000 Hz (preferred, current)
          1920x1080 px, 60.000000 Hz
          1920x1080 px, 59.939999 Hz
          1680x1050 px, 59.882999 Hz
          1400x1050 px, 59.948002 Hz
          1280x1024 px, 60.020000 Hz
          1440x900 px, 59.901001 Hz
          1280x960 px, 60.000000 Hz
          1366x768 px, 59.999001 Hz
          1280x720 px, 60.000000 Hz
          1280x720 px, 60.000000 Hz
          1280x720 px, 59.939999 Hz
          1024x768 px, 60.004002 Hz
          800x600 px, 60.317001 Hz
          800x600 px, 59.863998 Hz
          800x600 px, 56.250000 Hz
          640x480 px, 60.000000 Hz
          640x480 px, 59.939999 Hz
          640x480 px, 59.971001 Hz
        Position: 0,0
        Transform: normal
        Scale: 1.000000
        Adaptive Sync: disabled
      Fri Jul 18 20:11:10 UTC 2025
      wlr-randr errors "failed to connect to display" so killing container.
      00:01:08.126 [INFO] [seatd/seat.c:158] No clients on seat0 to activate
      00:01:08.190 [INFO] [seatd/seat.c:290] Removed client 1 from seat0
      00:01:08.195 [INFO] [seatd/client.c:496] Client disconnected
      00:00:00.000 [INFO] [seatd/seatd.c:167] Removing leftover socket at /run/seatd.sock
      00:00:00.000 [INFO] [seatd/seat.c:48] Created VT-bound seat seat0
      00:00:00.000 [INFO] [seatd/seatd.c:194] seatd started
      failed to connect to display
      00:00:00.818 [INFO] [seatd/server.c:145] New client connected (pid: 1, uid: 1000, gid: 1000)
      00:00:00.819 [INFO] [seatd/seat.c:239] Added client 1 to seat0
      00:00:00.819 [INFO] [seatd/seat.c:563] Opened client 1 on seat0
      failed to connect to display
      failed to connect to display
      failed to connect to display
      HDMI-A-1 "Stargate Technology 1560FX (HDMI-A-1)"
        Make: Stargate Technology
        Model: 1560FX
        Serial: (null)
        Physical size: 330x220 mm
        Enabled: yes
        Modes:
          1920x1080 px, 60.000000 Hz (preferred, current)
          1920x1080 px, 60.000000 Hz
          1920x1080 px, 59.939999 Hz
          1680x1050 px, 59.882999 Hz
          1400x1050 px, 59.948002 Hz
          1280x1024 px, 60.020000 Hz
          1440x900 px, 59.901001 Hz
          1280x960 px, 60.000000 Hz
          1366x768 px, 59.999001 Hz
          1280x720 px, 60.000000 Hz
          1280x720 px, 60.000000 Hz
          1280x720 px, 59.939999 Hz
          1024x768 px, 60.004002 Hz
          800x600 px, 60.317001 Hz
          800x600 px, 59.863998 Hz
          800x600 px, 56.250000 Hz
          640x480 px, 60.000000 Hz
          640x480 px, 59.939999 Hz
          640x480 px, 59.971001 Hz
        Position: 0,0
        Transform: normal
        Scale: 1.000000
        Adaptive Sync: disabled
      Sat Jul 19 01:23:47 UTC 2025
      wlr-randr errors "failed to connect to display" so killing container.
      05:12:15.325 [INFO] [seatd/seat.c:158] No clients on seat0 to activate
      05:12:15.379 [INFO] [seatd/seat.c:290] Removed client 1 from seat0
      05:12:15.380 [INFO] [seatd/client.c:496] Client disconnected
      00:00:00.000 [INFO] [seatd/seatd.c:167] Removing leftover socket at /run/seatd.sock
      00:00:00.000 [INFO] [seatd/seat.c:48] Created VT-bound seat seat0
      00:00:00.000 [INFO] [seatd/seatd.c:194] seatd started
      failed to connect to display
      00:00:00.881 [INFO] [seatd/server.c:145] New client connected (pid: 1, uid: 1000, gid: 1000)
      00:00:00.881 [INFO] [seatd/seat.c:239] Added client 1 to seat0
      00:00:00.882 [INFO] [seatd/seat.c:563] Opened client 1 on seat0
      failed to connect to display
      failed to connect to display
      HDMI-A-1 "Stargate Technology 1560FX (HDMI-A-1)"
        Make: Stargate Technology
        Model: 1560FX
        Serial: (null)
        Physical size: 330x220 mm
        Enabled: yes
        Modes:
          1920x1080 px, 60.000000 Hz (preferred, current)
          1920x1080 px, 60.000000 Hz
          1920x1080 px, 59.939999 Hz
          1680x1050 px, 59.882999 Hz
          1400x1050 px, 59.948002 Hz
          1280x1024 px, 60.020000 Hz
          1440x900 px, 59.901001 Hz
          1280x960 px, 60.000000 Hz
          1366x768 px, 59.999001 Hz
          1280x720 px, 60.000000 Hz
          1280x720 px, 60.000000 Hz
          1280x720 px, 59.939999 Hz
          1024x768 px, 60.004002 Hz
          800x600 px, 60.317001 Hz
          800x600 px, 59.863998 Hz
          800x600 px, 56.250000 Hz
          640x480 px, 60.000000 Hz
          640x480 px, 59.939999 Hz
          640x480 px, 59.971001 Hz
        Position: 0,0
        Transform: normal
        Scale: 1.000000
        Adaptive Sync: disabled
      scottwalsh@calendar:~ $ 
      scottwalsh@calendar:~ $ 
      
      
      posted in Troubleshooting
      S
      scottwalsh
    • Issue with latest build of Karsten’s docker labwc container?

      Apologies if the title is an incorrect conclusion.

      As using MagicMirrorOs that uses Karsten’s docker build.

      Noticed my screen at a tty login prompt instead of displaying my configuration that has been running a couple of weeks.

      After investigating a little, I can see the labwc container keeps restarting with the below error messages in the logs.

      It looks like it did pull of the latest version of the container ~3 hours ago, and I see that is when a new version of the content was published.

      • Is there an issue with th*e latest version of the labwc container?
      • Or any suggestions on troubleshooting?
      scottwalsh@calendar:/opt/mm/run $ docker images
      REPOSITORY              TAG       IMAGE ID       CREATED         SIZE
      karsten13/labwc         latest    8e88d2ea284a   3 hours ago     475MB
      karsten13/magicmirror   fat       4e817d6adb5a   2 days ago      1.59GB
      karsten13/magicmirror   latest    1d9d652de531   2 days ago      1.01GB
      karsten13/mmpm          latest    44cfa75bf098   5 days ago      841MB
      containrrr/watchtower   latest    a157fa84f431   15 months ago   14MB
      scottwalsh@calendar:/opt/mm/run $ docker logs labwc
      sudo: seatd: command not found
      00:00:00.523 [ERROR] [libseat] [libseat/backend/logind.c:621] Could not get primary session for user: No data available
      00:00:00.601 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
      00:00:00.602 [ERROR] [libseat] [seatd/seat.c:70] Could not open tty0 to update VT: Permission denied
      00:00:00.602 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
      00:00:00.602 [ERROR] [libseat] [seatd/seat.c:80] Could not open terminal for VT 0: Permission denied
      00:00:00.602 [ERROR] [libseat] [seatd/seat.c:544] Could not open VT for client
      00:00:00.602 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
      00:00:00.602 [ERROR] [libseat] [seatd/seat.c:94] Could not open terminal to clean up VT 0: Permission denied
      00:00:10.606 [ERROR] [backend/backend.c:105] Timeout waiting session to become active
      00:00:10.606 [ERROR] [backend/backend.c:407] Failed to start a DRM session
      00:00:10.652 [ERROR] [../src/server.c:463] unable to create backend
      
      Some friendly trouble-shooting help
      ===================================
      
      If a seat could not be created, this may be caused by lack of permission to the
      seat, input and video groups. If you are using a systemd setup, try installing
      polkit (sometimes called policykit-1). For other setups, search your OS/Distro's
      documentation on how to use seatd, elogind or similar. This is likely to involve
      manually adding users to groups.
      
      If the above does not work, try running with `WLR_RENDERER=pixman labwc` in
      order to use the software rendering fallback
      00:00:11.825 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
      00:00:11.825 [ERROR] [libseat] [seatd/seat.c:94] Could not open terminal to clean up VT 0: Permission denied
      sudo: seatd: command not found
      00:00:00.038 [ERROR] [libseat] [libseat/backend/logind.c:621] Could not get primary session for user: No data available
      00:00:00.044 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
      00:00:00.044 [ERROR] [libseat] [seatd/seat.c:70] Could not open tty0 to update VT: Permission denied
      00:00:00.044 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
      00:00:00.044 [ERROR] [libseat] [seatd/seat.c:80] Could not open terminal for VT 0: Permission denied
      00:00:00.044 [ERROR] [libseat] [seatd/seat.c:544] Could not open VT for client
      00:00:00.045 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
      00:00:00.045 [ERROR] [libseat] [seatd/seat.c:94] Could not open terminal to clean up VT 0: Permission denied
      00:00:10.054 [ERROR] [backend/backend.c:105] Timeout waiting session to become active
      00:00:10.054 [ERROR] [backend/backend.c:407] Failed to start a DRM session
      00:00:10.061 [ERROR] [../src/server.c:463] unable to create backend
      
      posted in Troubleshooting
      S
      scottwalsh
    • Family Calendar (non Mirror currently)

      Family calendar, went for a custom framed screen as opposed to a mirror surface, may at a mirror surface later.

      IMG_0811 (1).jpeg

      Hardware
      Hardware is a Pi Zero 2W with a cheap portable monitor (Firebat).

      MM Configuration
      Modules is a simple set up of a CalendarExt3 with the default weather and time pulling five ics calendars from google (a calendar for each person plus a shared one).

      OS
      Used the MagicMirrorOS for the build, had some intermittent issues as noted in a troubleshooting thread that @KARSTEN13 and @SDETWEIL gave some good pointers on so could put in a workaround.

      Server Side
      On the google side, have written two Google Scripts to transform the calendar entries a little.

      Script 1
      Events are prefixed by “[CalendarName]” so clear which calendar the event belongs to without colour coding.

      Script 2
      Also a script that takes a calendar and copies the events to another, optionally padding the times for travel times (hardcoded) and rewriting the the title so that the original time is included. This allows me to consolidate several calendars into one.
      End result is (for example) my calendar for display (SW), has copied into two ics feeds, one of any gym classes I have booked (padded with travel time) and one from Tripit unpadded. Similar with my wife’s calendar with her gym bookings.

      posted in Show your Mirror
      S
      scottwalsh
    • RE: MagicMirrorOS build intermittently not starting mm container (Version 2.30)

      As an update, based on the pointers from @KARSTEN13 and @SDETWEIL, have a workaround.

      Had three issues going on.

      1:
      I found that on a graceful reboot (shutdown -r now) that it would generally start fine, but not on an ungraceful reboot (power cycle the machine).

      Looks like when it was ungraceful reboot, the labwc container would show with uptime of (for example) five hours when ‘docker ps’, even though the machine was rebooted 20min ago after ‘docker compose up’ was executed by install.sh. Whereas the magicmirror container would have recently started.

      I assume kind of lock file confusing things?

      Workaround was to change the first ‘docker compose up’ install.sh to ‘docker compose up -d --force-recreate’

      2:
      I’d also included a pause and --force-recreate at the end of the install.sh and noted it was never executing as per @KARSTEN13’s suggestion.
      Looked like the install.sh script was hanging at docker compose pull.
      Commented that out.

      3:
      Lastly, the initial ‘docker compose up -d --force-recreate’ in install.sh would still fail often with the mm container restarting with logs as per the original post.

      With a 7 min pause and then second ‘docker compose up -d --force-recreate’ it seems to start the second time well (3min wasn’t enough, 5min was better, 7min seems to work).

      Workaround is a bit on the slow side, at some point will see if can refactor it a bit so that a pull for updates occurs.

      Extract of resulting install.sh below.

      _info "--> Pulling docker images and starting magicmirror"
      # need sudo for docker here if docker was installed with this script
      
      # use up so mm can start if there are already local images
      _info "--> Pre Start Pause for 2min"
      sleep 120
      
      _info "--> Start and recreate"
      $_sudo docker compose up -d --force-recreate
      
      #_info "--> Pull Pause for 1 min"
      #sleep 60
      # pull new images
      #_info "--> Image Pull"
      #$_sudo docker compose pull
      
      #_info "--> Restart Pause for 1 min"
      #sleep 60
      # restart (only if new images pulled)
      #_info "--> Restart stopped"
      #$_sudo docker compose up -d
      
      _info "--> Final Pause for 7 min"
      sleep 720
      
      _info "--> Final  start and recreate"
      $_sudo docker compose up -d --force-recreate
      
      if [[ "$_sudo" == "sudo" ]]; then
        _info "--> Reboot needed, starting in 120 sec. (use ctrl-c to skip)"
        sleep 120
        sudo reboot now
      fi
      
      # cleanup
      $_sudo docker image prune -f
      
      posted in Troubleshooting
      S
      scottwalsh
    • RE: MagicMirrorOS build intermittently not starting mm container (Version 2.30)

      @karsten13 said in MagicMirrorOS build intermittently not starting mm container (Version 2.30):

      the script /opt/mm/install/install.sh is executed with every reboot.

      As workaround you could add

      Is that executed on the OS boot, or by one of the containers as they start?

      I was thinking of a workaround like that to introduce a pause. Given the low machine spec, it seems to be busy for about 5min after sshd starts, so will just try a 300 sec sleep.

      posted in Troubleshooting
      S
      scottwalsh
    • RE: MagicMirrorOS build intermittently not starting mm container (Version 2.30)

      @sdetweil said in MagicMirrorOS build intermittently not starting mm container (Version 2.30):

      @scottwalsh can you show w MagicMirror running…

      scottwalsh@calendar:/opt/mm/run $ 
      scottwalsh@calendar:/opt/mm/run $ docker compose up -d --force-recreate
      [+] Running 5/5
       ✔ Container watchtower  Started                                                                                                                                                                        42.0s 
       ✔ Container labwc       Started                                                                                                                                                                        41.9s 
       ✔ Container init        Started                                                                                                                                                                        42.2s 
       ✔ Container mmpm        Started                                                                                                                                                                        42.4s 
       ✔ Container mm          Started                                                                                                                                                                         5.3s 
      scottwalsh@calendar:/opt/mm/run $ 
      scottwalsh@calendar:/opt/mm/run $ docker ps
      CONTAINER ID   IMAGE                          COMMAND                  CREATED         STATUS                   PORTS                                                                                                                                                 NAMES
      a1cb1b400de1   karsten13/mmpm:latest          "/home/node/entrypoi…"   3 minutes ago   Up 2 minutes             0.0.0.0:6789->6789/tcp, :::6789->6789/tcp, 0.0.0.0:7890-7891->7890-7891/tcp, :::7890-7891->7890-7891/tcp, 0.0.0.0:8907->8907/tcp, :::8907->8907/tcp   mmpm
      f7ec5d32f0bd   karsten13/magicmirror:latest   "/usr/bin/tini -- ./…"   3 minutes ago   Up About a minute                                                                                                                                                              mm
      74193ae14fbf   karsten13/labwc:latest         "/entrypoint.sh"         3 minutes ago   Up 2 minutes                                                                                                                                                                   labwc
      bcf30cd7bb10   containrrr/watchtower:latest   "/watchtower --inter…"   3 minutes ago   Up 2 minutes (healthy)   8080/tcp                                                                                                                                              watchtower
      scottwalsh@calendar:/opt/mm/run $ 
      scottwalsh@calendar:/opt/mm/run $ free -m
                     total        used        free      shared  buff/cache   available
      Mem:             425         236         134          36         141         189
      Swap:           1023         296         727
      scottwalsh@calendar:/opt/mm/run $
      
      posted in Troubleshooting
      S
      scottwalsh
    • RE: MagicMirrorOS build intermittently not starting mm container (Version 2.30)

      An observation, if I power cycle the pi, there is a good chance of it not starting up with the errors in the original post.

      Once leave it for five min for all the processes to start (and fail), then run docker compose up -d --force-recreate, it seems to be stable from then on and works well.

      posted in Troubleshooting
      S
      scottwalsh
    • RE: MagicMirrorOS build intermittently not starting mm container (Version 2.30)

      @sdetweil said in MagicMirrorOS build intermittently not starting mm container (Version 2.30):

      @scottwalsh how big is the swap file?

      free -m

      scottwalsh@calendar:~ $ free -m
                     total        used        free      shared  buff/cache   available
      Mem:             425         210          66           0         204         214
      Swap:           1023         203         820
      scottwalsh@calendar:~ $
      
      posted in Troubleshooting
      S
      scottwalsh
    • RE: MagicMirrorOS build intermittently not starting mm container (Version 2.30)

      @sdetweil said in MagicMirrorOS build intermittently not starting mm container (Version 2.30):

      @scottwalsh please dont double post

      Apologies, user error.

      posted in Troubleshooting
      S
      scottwalsh
    • RE: MagicMirrorOS build intermittently not starting mm container (Version 2.30)

      @sdetweil
      The host is a pi zero 2w - so is on the low spec side.

      posted in Troubleshooting
      S
      scottwalsh
    • 1 / 1