Read the statement by Michael Teeuw here.
Calendar not updating
-
@sdetweil ok it’s a big one…
pi@magicmirror:~/MagicMirror $ npm start > magicmirror@2.26.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js [01.01.2024 20:09.38.801] [LOG] Starting MagicMirror: v2.26.0 [01.01.2024 20:09.38.814] [LOG] Loading config ... [01.01.2024 20:09.38.823] [DEBUG] config template file not exists, no envsubst [01.01.2024 20:09.38.834] [LOG] Loading module helpers ... [01.01.2024 20:09.38.840] [LOG] No helper found for module: alert. [01.01.2024 20:09.38.947] [LOG] Initializing new module helper ... [01.01.2024 20:09.38.949] [LOG] Module helper loaded: updatenotification [01.01.2024 20:09.38.951] [LOG] No helper found for module: clock. [01.01.2024 20:09.39.477] [LOG] Initializing new module helper ... [01.01.2024 20:09.39.480] [LOG] Module helper loaded: calendar [01.01.2024 20:09.40.633] [LOG] Initializing new module helper ... [01.01.2024 20:09.40.636] [LOG] Module helper loaded: MMM-UKNationalRail [01.01.2024 20:09.41.573] [LOG] Module helper loaded: MMM-Sonos [01.01.2024 20:09.41.575] [LOG] No helper found for module: weather. [01.01.2024 20:09.41.585] [LOG] Initializing new module helper ... [01.01.2024 20:09.41.587] [LOG] Module helper loaded: MMM-MoonPhase [01.01.2024 20:09.42.084] [LOG] Initializing new module helper ... [01.01.2024 20:09.42.085] [LOG] Module helper loaded: newsfeed [01.01.2024 20:09.42.088] [LOG] No helper found for module: MMM-WiFiPassword. [01.01.2024 20:09.43.354] [LOG] Initializing new module helper ... [01.01.2024 20:09.43.355] [LOG] Module helper loaded: MMM-MyCommute [01.01.2024 20:09.43.357] [LOG] No helper found for module: MMM-EyeCandy. [01.01.2024 20:09.43.469] [LOG] Initializing new module helper ... [01.01.2024 20:09.43.469] [LOG] Module helper loaded: mmm-hue-lights [01.01.2024 20:09.44.432] [LOG] Initializing new module helper ... [01.01.2024 20:09.44.433] [LOG] Module helper loaded: MMM-HASS [01.01.2024 20:09.44.439] [LOG] Initializing new module helper ... [01.01.2024 20:09.44.440] [LOG] Check MagicMirror² version for node helper 'MMM-ip' - Minimum version: 2.15.0 - Current version: 2.26.0 [01.01.2024 20:09.44.443] [LOG] Version is ok! [01.01.2024 20:09.44.444] [LOG] Module helper loaded: MMM-ip [01.01.2024 20:09.44.445] [LOG] All module helpers loaded. [01.01.2024 20:09.44.466] [LOG] Starting server on port 8080 ... [01.01.2024 20:09.44.489] [WARN] You're using a full whitelist configuration to allow for all IPs [01.01.2024 20:09.44.518] [ERROR] Whoops! There was an uncaught exception... [01.01.2024 20:09.44.521] [ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:8080 at Server.setupListenHandle [as _listen2] (node:net:1751:16) at listenInCluster (node:net:1799:12) at doListen (node:net:1948:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '0.0.0.0', port: 8080 } [01.01.2024 20:09.44.522] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? [01.01.2024 20:09.44.523] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues Warning: vkCreateInstance: Found no drivers! Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88) at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458) at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344) at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266) at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) -
@matt216 pm2 stop all
then npm start again
no idea on the Vulcan driver issue…
what os are u running on what hardware…
uname -a
lsb_release -a -
A avano referenced this topic on
-
pi@magicmirror:~ $ uname -a Linux magicmirror 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux pi@magicmirror:~ $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseyeStopped and re-started npm… the npm start seems to generate a rolling log output (with some sensitive info), so I’ve selected what I think is relevant to the calendar for my reply. There are no errors/warning this time :)
[02.01.2024 09:15.55.833] [LOG] Module helper loaded: calendar ... [02.01.2024 09:15.58.013] [LOG] Connecting socket for: calendar [02.01.2024 09:15.58.014] [LOG] Starting node helper for: calendar ... [02.01.2024 09:16.02.605] [LOG] Create new calendarfetcher for url: https://my.cal.url - Interval: 120000 ... [02.01.2024 09:16.27.480] [INFO] Calendar-Fetcher: Broadcasting 380 events from https://my.cal.url. [02.01.2024 09:16.47.441] [LOG] Use existing calendarfetcher for url: https://my.cal.url [02.01.2024 09:16.47.442] [INFO] Calendar-Fetcher: Broadcasting 380 events from https://my.cal.url. ... [02.01.2024 09:17.12.085] [INFO] Calendar-Fetcher: Broadcasting 380 events from https://my.cal.url.Mostly looks ok, but the “use existing calendarfetcher for url:…” concerns me.
Still, I have an event upcoming soon that should be displaying in my 5 entries that isn’t.
Thanks
-
I can also see in pm2 logs:
0|MagicMir | [02.01.2024 10:11.33.120] [ERROR] Calendar Error. Could not fetch calendar: https://my.cal.url TypeError: fetch failedI wonder why.
Getting the calendar to show in the first place was achieved by changing my baikal calendar WebDAV authentication type to ‘basic’ and setting the same in the calendar module. I’ve confirmed this is still set. -
@matt216 well the type error is the problem.
the calendar.module doesn’t recover after the error.can you open an issue on the mm GitHub page, with that info
are there any errors above that?
-
@sdetweil None that I can see.
pi@magicmirror:~/.pm2/logs $ tail --lines=1000 MagicMirror-error.log | grep calendar [02.01.2024 10:29.43.758] [ERROR] Calendar Error. Could not fetch calendar: https://my.cal.url TypeError: fetch failed [02.01.2024 10:31.53.769] [ERROR] Calendar Error. Could not fetch calendar: https://my.cal.url TypeError: fetch failedWill open an issue. Thanks for assisting. I might have a play with a couple of the other calendar modules there are out there…
-
@matt216 generally there is a more specific error earlier in the log.
if you clear it
pm2 flush
the restart
pm2 restart allyou will have the smallest output to look at
-
@sdetweil Can’t see any calendar errors in error.log now! :grinning_squinting_face:
But still my new events are not showing up when they should… -
-
@matt216 thank you… i posted a an additional grep thru the log to the issue
