# Fatal error in , line 0

**URL:** <https://discourse.nodered.org/t/fatal-error-in-line-0/69483>\
**Category:** General\
**Created:** [24 October 2022 10:46 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483 "2022-10-24T10:46:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![strbaknxp](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/strbaknxp/32/69628_2.png) [@strbaknxp](https://discourse.nodered.org/u/strbaknxp)\
**Post date:** [24 October 2022 10:46 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/1 "2022-10-24T10:46:39Z")

</div>

Hello,

I have a problem. The NR terminated with this error:

```auto
#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 01DDEE18

```

There is no more information even I have a debug mode on trace level.

I am using:  
Windows 10 and also Win 11,  
node -v: v16.13.2 (32bit)  
npm -v:8.5.4

I am not able to update the node version because I am using NR as a module with is bundled together and newer version is not supported.

Is there some possibility how to debug/fix this issue?  
I am using following modules:

1. node-red - 2.2.2
2. node-red-contrib-excel - 0.0.3
3. node-red-contrib-excelsheets - 1.1.1
4. node-red-contrib-file-function-ext - 1.5.0
5. node-red-contrib-freemaster - 1.1.2
6. node-red-contrib-gc - 0.0.1
7. node-red-contrib-nbrowser - 1.1.4
8. node-red-contrib-ui-actions - 0.1.8
9. node-red-contrib-ui-button\_state - 0.2.2
10. node-red-contrib-ui-multistate-switch - 1.2.3
11. node-red-dashboard - 3.1.5
12. node-red-node-serialport - 0.15.0
13. node-red-node-ui-list - 0.3.6
14. node-red-node-ui-table - 0.3.12

Thank you very much  
Pavol

---

<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:** [24 October 2022 11:37 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/2 "2022-10-24T11:37:45Z")

</div>

> [@strbaknxp](#):
>
> I am not able to update the node version because I am using NR as a module with is bundled together and newer version is not supported.

Why are you doing that?

Please post the full terminal output when you start node red.

---

<div class="post-metadata">

**Author:** ![strbaknxp](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/strbaknxp/32/69628_2.png) [@strbaknxp](https://discourse.nodered.org/u/strbaknxp)\
**Post date:** [24 October 2022 11:52 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/3 "2022-10-24T11:52:34Z")

</div>

Thank you for response.

I am using FreeMaster lite from NXP company. And node-red is part of the installation process. It means, To be able to use the FreeMaster extensions I need to use supported versions. and this is the newest version which I am able to use.

This is the whole log for INFO level of debug:

```auto
21 Oct 15:51:06 - [info] 

runtime.welcome
===================

21 Oct 15:51:06 - [info] runtime.version
21 Oct 15:51:06 - [info] runtime.version
21 Oct 15:51:06 - [info] Windows_NT 10.0.22000 ia32 LE
21 Oct 15:51:06 - [info] server.loading
21 Oct 15:51:07 - [info] Dashboard version 3.1.5 started at /red/ui
21 Oct 15:51:07 - [info] runtime.paths.settings
21 Oct 15:51:07 - [warn] server.deprecatedOption
21 Oct 15:51:07 - [info] context.log-store-init
21 Oct 15:51:07 - [info] storage.localfilesystem.user-dir
21 Oct 15:51:07 - [info] storage.localfilesystem.projects.projects-directory

FreeMASTER Lite server is running at
http://127.0.0.1:7001
====================================

21 Oct 15:51:07 - [info] storage.localfilesystem.projects.active-project
21 Oct 15:51:07 - [info] storage.localfilesystem.flows-file
21 Oct 15:51:07 - [info] nodes.flows.starting-flows
21 Oct 15:51:08 - [info] nodes.flows.started-flows
21 Oct 15:51:09 - [audit] {"event":"comms.open","level":98,"timestamp":1666360269185}
21 Oct 15:51:10 - [info] [debug:dd4aa348cf731788] 
{
  payload: 1666360270948,
  topic: 'DemoAvailability',
  _msgid: '404a1a38702aed36'
}
21 Oct 15:51:10 - [audit] {"event":"flows.get","level":98,"path":"/flows","ip":"127.0.0.1","timestamp":1666360270958}
21 Oct 15:51:10 - [info] [debug:8bbfcbdbd3ed82e6] 
{
  payload: 1666360270972,
  topic: 'DemoAvailability',
  _msgid: '9a2c3aea719bb17d'
}
21 Oct 15:51:11 - [info] [debug:be74763f5c74e4cb] 
{
  payload: 1666360271027,
  topic: 'DemoAvailability',
  _msgid: '2bfaf4171737abe8'
}
21 Oct 15:51:11 - [audit] {"event":"flows.get","level":98,"path":"/flows","ip":"127.0.0.1","timestamp":1666360271036}
21 Oct 15:51:11 - [audit] {"event":"flows.get","level":98,"path":"/flows","ip":"127.0.0.1","timestamp":1666360271052}
21 Oct 15:51:14 - [info] [debug:fa4bd621d811bbc5] 
{ payload: 'phase_1', _msgid: '404a1a38702aed36' }
21 Oct 15:51:14 - [info] [debug:aaaa0e82e0b48921] 
{ payload: 'phase_2', _msgid: '9a2c3aea719bb17d' }
21 Oct 15:51:14 - [info] [debug:3ef715febeb93ab9] 
{ payload: 'phase_3', _msgid: '2bfaf4171737abe8' }
21 Oct 15:51:45 - [audit] {"event":"flows.set","type":"nodes","level":98,"path":"/flows","ip":"10.12.206.150","timestamp":1666360305896}
21 Oct 15:51:46 - [info] nodes.flows.stopping-modified-nodes
21 Oct 15:51:46 - [info] nodes.flows.stopped-modified-nodes
21 Oct 15:51:46 - [info] nodes.flows.starting-modified-nodes
21 Oct 15:51:46 - [info] nodes.flows.started-modified-nodes

#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 01DDEE18

```

---

<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:** [24 October 2022 20:18 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/4 "2022-10-24T20:18:28Z")

</div>

This appears to be an internal node.js error related to how a package uses node.js. See [Check failed: result.second · Issue #32463 · nodejs/node · GitHub](https://github.com/nodejs/node/issues/32463)

However that was on nodejs 14 and you say you are using 16 so it may not be closely related. I think you may have to get back to the supplier to ask for help with this.

You said that the start that you could not use a later node version, but you are using v16 which is not an old version. Or did you mean that you cannot use a later node-red version?

---

<div class="post-metadata">

**Author:** ![strbaknxp](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/strbaknxp/32/69628_2.png) [@strbaknxp](https://discourse.nodered.org/u/strbaknxp)\
**Post date:** [25 October 2022 12:36 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/5 "2022-10-25T12:36:04Z")

</div>

Thank you,  
I already found this issue (32463) on github. But I am none the wiser.

I mean, that I am not able to use the lastest version.  
I am able to use: NODE\_MODULE\_VERSION:93

I am wondering, if is some possibility how to add more info about exception. I found a lot of similar errors. But all of them contained also source of error. At least name of module. I get nothing.  
Debug level, audit, trace not helped.  
It looks from my inexperienced point of view, that it is somewhere in core.  
often it happened when I clicked on deploy. But it is not a rule.

Thank you very much

---

<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:** [25 October 2022 14:07 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/7 "2022-10-25T14:07:30Z")

</div>

> [@strbaknxp](#):
>
> I mean, that I am not able to use the lastest version.  
> I am able to use: NODE\_MODULE\_VERSION:93

That is OK, that is node.js 16 which is what you are using.  
Why, then, are you not using the latest version of node-red?

---

<div class="post-metadata">

**Author:** ![strbaknxp](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/strbaknxp/32/69628_2.png) [@strbaknxp](https://discourse.nodered.org/u/strbaknxp)\
**Post date:** [25 October 2022 14:27 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/8 "2022-10-25T14:27:41Z")

</div>

I was using the 16.13.2 from past. I don't know exactly why. But I am using the project on github. And I have also project dependences on settings.js and node-modules.  
So I have to use on all execution machines the same version because compatibility of modules and when I was trying to actualize to newer version, then some problems occurred with supporting modules and update was not pass. It still crashed. (It's a few months ago. I don't remember exact problems)

But you right. I will try tomorrow actualize all machines. this is the first what should I do. 🙂

---

<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:** [24 December 2022 14:28 UTC](https://discourse.nodered.org/t/fatal-error-in-line-0/69483/9 "2022-12-24T14:28:35Z")

</div>

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