# Nodered Blows on Upload

**URL:** <https://discourse.nodered.org/t/nodered-blows-on-upload/75498>\
**Category:** General\
**Created:** [21 February 2023 05:13 UTC](https://discourse.nodered.org/t/nodered-blows-on-upload/75498 "2023-02-21T05:13:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nodeautomata](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodeautomata/32/106678_2.png) [@nodeautomata](https://discourse.nodered.org/u/nodeautomata)\
**Post date:** [21 February 2023 05:13 UTC](https://discourse.nodered.org/t/nodered-blows-on-upload/75498/1 "2023-02-21T05:13:56Z")

</div>

I'm uploading files with Nodered. Works fine but blows chunks when the files go above a certain size, for example 30MB. I'm using HTTP input node. Is this normal, is there an easy workaround? I'm running on an AWS instance so memory costs. I can recode that section in PHP but I really want to keep the moving pieces at a minimum.

Any ideas why this happens? upload\_ui is not an option for various reasons.

Nodered says this when it goes boom..  
nodered.service: Main process exited, code=killed, status=9/KILL  
nodered.service: Failed with result 'signal'.

Works just fine with small files. Big files HTTP node goes boom.

---

<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:** [21 February 2023 07:13 UTC](https://discourse.nodered.org/t/nodered-blows-on-upload/75498/2 "2023-02-21T07:13:40Z")

</div>

Check the node red log, that is the one with the 'Welcome to node red' message.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [21 February 2023 09:53 UTC](https://discourse.nodered.org/t/nodered-blows-on-upload/75498/3 "2023-02-21T09:53:03Z")

</div>

> [@nodeautomata](#):
>
> code=killed, status=9/KILL

Using that as a google search term shows a lot of out of memory issues. The fact that it works for smaller files and you seem to indicate you have a memory limit, it would seem to point in that direction.

I'm not an AWS user, but if you can temporary upgrade the memory do you still have the issue?

> <https://serverfault.com/questions/1008479/what-killed-my-tomcat-service-and-how-can-i-restart-it-automatically>

---

<div class="post-metadata">

**Author:** ![nodeautomata](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodeautomata/32/106678_2.png) [@nodeautomata](https://discourse.nodered.org/u/nodeautomata)\
**Post date:** [21 February 2023 16:53 UTC](https://discourse.nodered.org/t/nodered-blows-on-upload/75498/4 "2023-02-21T16:53:42Z")

</div>

More digging and large uploads work fine on other copies of node-red I'm running.

Has to be something to do with this server. Now I guess endless hours of fun playing why ain't this like the others.

Increasing instance size worked yet other instance that works is small size.

So, server/config problem of some sort.

---

<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:** [7 March 2023 16:53 UTC](https://discourse.nodered.org/t/nodered-blows-on-upload/75498/5 "2023-03-07T16:53:58Z")

</div>

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