Got error when connecting to google smtp

[fxfred]

../src/node_crypto.cc:685: void node::crypto::Connection::ClearError(): Assertion `handle_->Get(String::New("error"))->BooleanValue() == false' failed.
And process dies.
Could it be a SSL error?
v0.6.14

[bnoordhuis]

Yes, possibly. Would it be possible for you to provide a test case? Failing that, can you post a backtrace? Here's how you obtain one:

$ gdb --args node script.js
> run
# wait for it to crash
> backtrace full
# copy/paste the backtrace

[fxfred]

It could be my own problem, since I'm running node in a jailed environment.
It's running fine when I created a small test case.
Does node need openssl lib to communicate with other SSL server? If so, how do I know which binary I shall copy to my jailed environment?

Thanks a lot.

[fxfred]

Never mind. In a jailed environment.

[bnoordhuis]

I would still like to resolve this issue if you're up to it. You should never see an assert, it's by its very definition an unhandled error situation.

[fxfred]

I used 'daemon' to chroot, and used 'nodemailer' to send email
throught gmail, then I got the error.
It's a big chunk of source code. If you need a small one to reproduce
the error, please let me know.
Thanks

On Mon, Apr 9, 2012 at 5:58 PM, Ben Noordhuis
reply@reply.github.com
wrote:

I would still like to resolve this issue if you're up to it. You should never see an assert, it's by its very definition an unhandled error situation.

---

Reply to this email directly or view it on GitHub:
#3073 (comment)

[bnoordhuis]

A small test case would help a lot but a backtrace is oftentimes enough to point me in the right direction.

[fxfred]

(gdb) backtrace full
#0 0x00000030f2435215 in raise () from /lib64/libc.so.6
No symbol table info available.
#1 0x00000030f2436b2b in abort () from /lib64/libc.so.6
No symbol table info available.
#2 0x00000030f242dc3e in assert_fail_base () from /lib64/libc.so.6
No symbol table info available.
#3 0x00000030f242dce2 in assert_fail () from /lib64/libc.so.6
No symbol table info available.
#4 0x000000000055e374 in ClearError (this=0xcc40b0) at
../src/node_crypto.cc:685
scope = {isolate = 0xc0d0d0, prev_next = 0xc45ec8,
prev_limit = 0xc47be0, is_closed = false}
#5 Unwrap (args=...) at ../src/node_crypto.h:165
No locals.
#6 node::crypto::Connection::ClearOut (args=...) at ../src/node_crypto.cc:1055
ss = 0xcc40b0
buffer_data =
buffer_length =
off =
len =
bytes_read =
scope = {isolate_ = 0xc0d0d0, prev_next_ = 0xc45ec8,
prev_limit_ = 0xc47be0, is_closed_ = false}
#7 0x0000000000594436 in
v8::internal::Builtin_HandleApiCall(v8::internal::(anonymous
namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>,
v8::internal::Isolate*) ()
No symbol table info available.
#8 0x00002c69996ba14e in ?? ()
No symbol table info available.
#9 0x00002c69996e0ef5 in ?? ()
No symbol table info available.
#10 0x00002c69996ba0c1 in ?? ()
No symbol table info available.
#11 0x00007fffffffdc10 in ?? ()
No symbol table info available.
#12 0x00007fffffffdc70 in ?? ()
No symbol table info available.
#13 0x00002c6999763019 in ?? ()
No symbol table info available.
---Type to continue, or q to quit---
#14 0x000007028ebf4b71 in ?? ()
No symbol table info available.
#15 0x0001000000000000 in ?? ()
No symbol table info available.
#16 0x0000000000000000 in ?? ()
No symbol table info available.

On Tue, Apr 10, 2012 at 2:06 PM, Ben Noordhuis
reply@reply.github.com
wrote:

A small test case would help a lot but a backtrace is oftentimes enough to point me in the right direction.

---

Reply to this email directly or view it on GitHub:
#3073 (comment)

Fred Xiang

[bnoordhuis]

Thanks. Now I know where it's happening and where it's coming from but admittedly I don't understand why it's happening. If you have a test case, that would be much appreciated!

[fxfred]

var daemon, nodemailer, transport;

daemon = require('daemon');

nodemailer = require('nodemailer');

daemon.chroot("/tmp");

transport = nodemailer.createTransport('SMTP', {
service: "Gmail",
auth: {
user: "xxxxxxx@gmail.com",
pass: "xxxxxxx"
}
});

transport.sendMail({
from: 'xxxxxxx@gmail.com',
to: 'xxxxxxx@gmail.com',
subject: 'test',
text: 'test'
}, function(err) {
return console.log(err);
});

On Mon, Apr 16, 2012 at 5:13 PM, Ben Noordhuis
reply@reply.github.com
wrote:

Thanks. Now I know where it's happening and where it's coming from but admittedly I don't understand why it's happening. If you have a test case, that would be much appreciated!

---

Reply to this email directly or view it on GitHub:
#3073 (comment)

Fred Xiang