Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to debug the action of sending email #441

Closed
rjrodriguezalvarez97 opened this issue Jun 13, 2018 · 2 comments
Closed

Unable to debug the action of sending email #441

rjrodriguezalvarez97 opened this issue Jun 13, 2018 · 2 comments

Comments

@rjrodriguezalvarez97
Copy link

rjrodriguezalvarez97 commented Jun 13, 2018

Hi, I've been trying to debug Mailtrain but I'm unable to do it. The child Sender process is unable to start while debugging but it starts properly during running. This is the output from running:

info Using local auth
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
info sql Database check completed
info Express WWW server listening on port 3000
verb UTC Updating timezone offsets
info POSTFIXBOUNCE Server listening on port 5699
info Service All services started

And this is the output from debugging:

/usr/bin/node --inspect-brk=42835 /home/ricardo/mailtrain/index.js
Debugger listening on ws://127.0.0.1:42835/ecaafed2-45de-4622-bcd3-c4f8d8a7bc93
For help see https://nodejs.org/en/docs/inspector
Debugger attached.
info Using local auth
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
info sql Database check completed
info Express WWW server listening on port 3000
verb UTC Updating timezone offsets
info POSTFIXBOUNCE Server listening on port 5699
Starting inspector on 127.0.0.1:42835 failed: address already in use
info Service All services started
ERR! Child Sender process 8979 exited with 12

I think it might be caused because of child_process.fork() as explained here
nodejs/node#8495 (comment)

Any ideas or workaround?
Thanks.

@bures
Copy link
Member

bures commented Sep 3, 2018

Honestly, I thing it's close to impossible to debug a multi-process app with concurrently running co-routines. Just use log messages via console.out.

@talheim-it
Copy link
Collaborator

Close this issue. You are welcome to reopen a new issue on v2 if still required and you are welcome to participate on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants