• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Can't find nodejs logs

macmee

New Pleskian
I have my nodejs app working perfectly with the nodejs that uses passthrough in plesk!

My only issue though is sadly I can't see the logs of my running app. Meaning, console.log/error or any stdout or stderr from node does not seem to get logged anywhere I can find.

In the log viewer I tried choosing nodejs in the dropdown but this file is empty. The passthrough log file is also empty.

I was wondering if anyone could shed some light on this before I go digging deeper into how nginx works with passthrough.

Thank you!
 
What about /var/log/passenger/passenger.log ?

It is also possible to troubleshoot the application using the Debugging Guide. However, this isn't supported by Plesk and has to run only from CLI (stopping the web server beforehand).
 
What about /var/log/passenger/passenger.log ?

It is also possible to troubleshoot the application using the Debugging Guide. However, this isn't supported by Plesk and has to run only from CLI (stopping the web server beforehand).
I don't see my application logs in there either, just this repeated:

[ D 2022-11-29 06:40:35.0002 199117/T3 age/Cor/App/Poo/AnalyticsCollection.cpp:116 ]: Analytics collection time...
[ D 2022-11-29 06:40:35.0002 199117/T3 age/Cor/App/Poo/AnalyticsCollection.cpp:143 ]: Collecting process metrics
[ D 2022-11-29 06:40:35.0003 199117/T3 age/Cor/App/Poo/AnalyticsCollection.cpp:151 ]: Collecting system metrics
[ D 2022-11-29 06:40:35.0004 199117/T3 age/Cor/App/Poo/AnalyticsCollection.cpp:67 ]: Analytics collection done; next analytics collection in 5.000 sec
[ D 2022-11-29 06:40:35.0005 206476/T5 Ser/Server.h:691 ]: [WatchdogApiServer] Updating statistics
[ D 2022-11-29 06:40:35.0006 206479/Ta age/Cor/Con/TurboCaching.h:246 ]: Clearing turbocache
[ D 2022-11-29 06:40:35.0001 199117/Td Ser/Server.h:691 ]: [ApiServer] Updating statistics
[ D 2022-11-29 06:40:35.0007 199117/T9 age/Cor/Con/TurboCaching.h:246 ]: Clearing turbocache
[ D 2022-11-29 06:40:35.0007 199117/T9 Ser/Server.h:691 ]: [ServerThr.1] Updating statistics
[ D 2022-11-29 06:40:35.0001 199114/T5 Ser/Server.h:691 ]: [WatchdogApiServer] Updating statistics
[ D 2022-11-29 06:40:35.0006 206479/Ta Ser/Server.h:691 ]: [ServerThr.2] Updating statistics
[ D 2022-11-29 06:40:35.0006 206479/T9 age/Cor/Con/TurboCaching.h:246 ]: Clearing turbocache
[ D 2022-11-29 06:40:35.0008 206479/T9 Ser/Server.h:691 ]: [ServerThr.1] Updating statistics
[ D 2022-11-29 06:40:35.0006 206479/T7 age/Cor/App/Poo/AnalyticsCollection.cpp:116 ]: Analytics collection time...
[ D 2022-11-29 06:40:35.0007 206479/Td Ser/Server.h:691 ]: [ApiServer] Updating statistics
[ D 2022-11-29 06:40:35.0008 206479/T7 age/Cor/App/Poo/AnalyticsCollection.cpp:143 ]: Collecting process metrics
[ D 2022-11-29 06:40:35.0134 206479/T7 age/Cor/App/Poo/AnalyticsCollection.cpp:151 ]: Collecting system metrics
[ D 2022-11-29 06:40:35.0136 206479/T7 age/Cor/App/Poo/AnalyticsCollection.cpp:67 ]: Analytics collection done; next analytics collection in 4.986 sec
 
Back
Top