0

I have a traditional rails stack(mysql,ubuntu) that uses delayed_job for processing background tasks.

today started seeing ssl_connect errors, but only from our background processes.

Have also tried using the ssl_tools/doctor from @mislav and have no errors.

For reference error is:

OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
- 17 non-project frames
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/net/http.rb" line 923 in connect
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/net/http.rb" line 923 in block in connect
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/timeout.rb" line 90 in block in timeout
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/timeout.rb" line 100 in call
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/timeout.rb" line 100 in timeout
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/net/http.rb" line 923 in connect
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/net/http.rb" line 863 in do_start
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/net/http.rb" line 852 in start
File "/home/deploy/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/net/http.rb" line 1375 in request
Community
  • 1
  • 1
Blair Anderson
  • 19,463
  • 8
  • 77
  • 114

1 Answers1

-1

Wow.

PID stands for process ID, which is the strategy that computers use to keep track internal programs that are running. each process gets a PID. Delayed jobs allows you to configure the PID directory.

IF you are having trouble with delayed jobs, check the pids and make sure you don't have random DJ processes running on old code. That was my problem above. anytime a bug came up, someone would manually restart DJ without specifying PIDs and it would create NEW PIDs. YIKES.

Old DJ processes running old/outdated code.

Blair Anderson
  • 19,463
  • 8
  • 77
  • 114