Logging is only as good or as bad as the logging you build in. If your
application crashes then of course you will get a healthly amount of info in
stderr (or stdout) to examine. There are node debuggers but AFAIK nothing
works too well on the IBMi just yet.
-----Original Message-----
From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: 10 October 2017 18:37
To: OpenSource-Midrange. com (opensource@xxxxxxxxxxxx)
<opensource@xxxxxxxxxxxx>
Subject: [IBMiOSS] Node troubleshooting for noobs?
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-n
odejs/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.
midrange.com
