# Unusual log startup following upgrade to 3.1.3/node20

**URL:** <https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868>\
**Category:** General\
**Created:** [20 December 2023 11:21 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868 "2023-12-20T11:21:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [20 December 2023 11:21 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/1 "2023-12-20T11:21:33Z")

</div>

Just upgraded my main Pi NR instance to 3.1.3 and node 20 and noticed that I don't get the normal start-up info (Welcome to NR and port info stuff)

```auto
pi@pi128gb:~/.node-red $ node-red
20 Dec 11:16:01 - [warn] Projects disabled : editorTheme.projects.enabled=false
20 Dec 11:16:04 - [warn] ttsultimate-config abf536dfafd7b1dd: Polly service not used.
20 Dec 11:16:04 - [warn] ttsultimate-config abf536dfafd7b1dd: Google TTS service not used.
20 Dec 11:16:04 - [warn] ttsultimate-config abf536dfafd7b1dd: Microsoft AzureTTS service not used. 
20 Dec 11:16:05 - [warn] Unknown context store 'memory' specified. Using default store.
20 Dec 11:16:12 - [error] [alexa-remote-routine:Speak to Flex2] Account not initialised!
20 Dec 11:16:35 - [warn] Context f20fcb163d371c8f:4040409aae3a5015 contains a circular reference that cannot be persisted

```

Now it might have been like that for a while and I just haven't noticed - is there something in the settings that needs changing?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [20 December 2023 11:54 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/2 "2023-12-20T11:54:28Z")

</div>

Not that I am aware of. I might expect that if you were running as a service and the log viewer only attached a little bit late - but not if you are running node-red directly...  
Will check my node v20 version when I get home later.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [20 December 2023 12:02 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/3 "2023-12-20T12:02:10Z")

</div>

I just looked at my Win11 instance and that's been doing the same for at least a month!  
(and I only upgraded it to node 20 today (from 18) so it's not due to that

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/9/a9e4b3fb67cdaa8e2bb4b321d096052188591767.png)

And just checked my @TotallyInformation alternate install on the same Pi and that's still giving traditional info

```auto
pi@pi128gb:~/.nr1881/data $ npm start

> node-red-userdir@3.0.2 start
> cd .. && node node_modules/node-red/red.js --userDir ./data

20 Dec 11:17:07 - [info] 

Welcome to Node-RED
===================

20 Dec 11:17:07 - [info] Node-RED version: v3.1.0
20 Dec 11:17:07 - [info] Node.js version: v20.10.0
20 Dec 11:17:07 - [info] Linux 6.1.21-v7+ arm LE
20 Dec 11:17:11 - [info] Loading palette nodes
20 Dec 11:17:19 - [info] Settings file : /home/pi/.nr1881/data/settings.js
20 Dec 11:17:19 - [info] Context store : 'default' [module=memory]
20 Dec 11:17:19 - [info] User directory : /home/pi/.nr1881/data
20 Dec 11:17:19 - [warn] Projects disabled : editorTheme.projects.enabled=false
20 Dec 11:17:19 - [info] Flows file : /home/pi/.nr1881/data/flows.json
20 Dec 11:17:19 - [info] Server now running at http://127.0.0.1:1881/
20 Dec 11:17:19 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials

```

[edit] And my Win11 is still on 3.1.0 so it's not a 3.1.0-\>3.1.3 issue

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [20 December 2023 12:14 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/4 "2023-12-20T12:14:28Z")

</div>

My Ubuntu system with 3.1.3 and nodejs 20, which uses the same setup as a Pi is showing the welcome message ok.

What does `which node-red` show (on the pi)? It should be /usr/bin/node-red

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [20 December 2023 12:22 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/5 "2023-12-20T12:22:16Z")

</div>

/usr/bin/node-red

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [20 December 2023 13:05 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/6 "2023-12-20T13:05:12Z")

</div>

It seems to be the logging level setting

I tried to think what could be common to my Pi and Win setups and I remembered changing logging levels on them

So the pi was on warn - changed it back to info (like the alternate instance was using) and the startup info has come back

Sorry for noise 🙂

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [20 December 2023 17:08 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/7 "2023-12-20T17:08:33Z")

</div>

> [@cymplecy](#):
>
> And just checked my @TotallyInformation alternate install on the same Pi and that's still giving traditional info

Perhaps you wisely used my enhanced settings file as well. 🕶

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [3 January 2024 17:09 UTC](https://discourse.nodered.org/t/unusual-log-startup-following-upgrade-to-3-1-3-node20/83868/8 "2024-01-03T17:09:13Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
