-
Notifications
You must be signed in to change notification settings - Fork 252
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
Undefined method ord
for nil class
#266
Comments
Bump? Anyone aware of what could be triggering this? |
This code has changed in master https://github.com/ruby-ldap/ruby-net-ldap/blob/master/lib/net/ldap/connection.rb#L33 might be worth upgrading and see if issue persists. |
So, I think what is happening, is that |
Should be fixed by #306 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there,
I am currently seeing intermittent issues with this gem; every once a while, our connection with ldap will drop and fail with this backtrace:
"/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/connection.rb:33:in
getbyte'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ber/ber_parser.rb:169:in
read_ber'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/connection.rb:178:inblock in read'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/instrumentation.rb:19:in
instrument'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/connection.rb:177:inread'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/connection.rb:143:in
queued_read'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/connection.rb:253:inbind_simple'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/connection.rb:222:in
block in bind'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/instrumentation.rb:19:ininstrument'", "/opt/shared/bundle/ruby/2.2.0/gems/net-ldap-0.11/lib/net/ldap/connection.rb:219:in
bind'"As far as I can tell, this works flawlessly most of the time since I have a couple of cron jobs that reuse the same piece of code over and over again and this only happens (very consistently) every week or may be a bit more frequently than that. The steps to reproduce this issue are literally attempting to bind. I am tempted to say perhaps that when the connection times out, either a nil object is returned to the calling function which then attempts to send it the ord command which then fails, but again, I haven't taken a look at the source code as of now.
The text was updated successfully, but these errors were encountered: