Re: [IBMiOSS] Node troubleshooting for noobs?

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

*>I'm running Node in QP2TERM right now. *

Stop using QP2TERM and use SSH instead.  It will solve future heartache.
 Check out this link for more
info: krengel.tech/eight-reasons-to-embrace-ssh

Aaron Bartell
IBM i hosting, starting at $157/month.  litmis.com/spaces


On Tue, Oct 10, 2017 at 4:36 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

> I'm running Node in QP2TERM right now.  No errors appears in the shell,
> but I'll the logging statement and see what I get.
>
>
>
> -----Original Message-----
> From: Aaron Bartell [mailto:aaronbartell@xxxxxxxxx]
> Sent: Tuesday, October 10, 2017 12:47 PM
> To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
> Subject: Re: [IBMiOSS] Node troubleshooting for noobs?
>
> If you start the Node.js app in a shell and don't submit it to batch then
> you should see what is causing the error being output to the console.
>
> The example in the URL you cite has code that manufactures an HTTP 500
> response.  Add a console.log() to that area of the code.  For example...
>
>       file.on('error', function(err){
>         console.log('err:' +err);   // <------ line I added
>         res.writeHead(500, {'Content-Type': 'text/plain'});
>         res.end("500 Internal Server Error");
>       });
>
> Further on the debugging front...
>
> I have both an RFE(n1) and PMR with IBM concerning the step Node.js
> debugger not working on IBM i.  I submitted it back in April so I am hoping
> it's that they haven't had time to get to it and not actually something
> significantly hard to solve (i.e. IBM i missing something that Linux/Mac
> has).
>
> n1: krengel.tech/rfe-nodejs-inspector
>
> Aaron Bartell
> IBM i hosting, starting at $157/month.  litmis.com/spaces
>
>
>
> --
> This is the IBMi Open Source Roundtable (OpenSource) mailing list
> To post a message email: OpenSource@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/opensource
> or email: OpenSource-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/opensource.