× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

I was updating my node from 14 to 16, then saw 18 was out too.

When I use 18 I got errors like this in PM2:
PM2 | Error caught while calling pidusage
PM2 | Error: os400 is not supported yet, please open an
issue (https://github.com/soyuka/pidusage)
PM2 | at get
PM2 | at pidusage
PM2 | at Object.getMonitorData
PM2 | at tasks
PM2 | at Domain.<anonymous>
PM2 | at Domain.run (node:domain:382:15)
PM2 | at Timeout.wrappedTasks [as _onTimeout]
PM2 | at listOnTimeout (node:internal/timers:564:17)
PM2 | at process.processTimers

Then I changed my profile to use version 16.. ended SSHD, started up a new
session, checked the node version (it was 16) and started my app again.

I am still getting the same error in the log... and it's reporting
nodejs18, not nodejs16. I even deleted all my apps from PM2 and restarted
them, but I can't get it to not report about node 18.

Should I stick with version 14? When I change it back to 14 I don't get the

Bradley V. Stone
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any Cloud

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.