Re: [IBMiOSS] Node troubleshooting for noobs?

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

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


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

> I've been watching Node for a while, and even poked at it a couple of
> times, but I've never tried to actually make something with it.  I have
> something to use it for now, so I installed it (v6.9.1 on 7.3) and am
> working thru the IBM samples (https://www.ibm.com/
> developerworks/ibmi/library/i-native-js-app-ibmi-with-nodejs/index.html).
> That's all well and good until I hit a "500 Internal Server Error".  I'm
> sure I could go back and double-check my typing, but I think this is a good
> time to learn about troubleshooting.
>
> Where do you start with troubleshooting?  Is there a debugger?  How about
> log files?
>
> TIA
> --
> 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.