Intermittent BJ errors

Rails
1

hi all

I’m running background tasks using BJ 1.0.1 (gem version). On some
requests, the tasks are executed as expected. On others, I get the
following error:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):

when it runs, it runs fine but does anyone know what could be causing
these errors?
I’m using ubuntu 7.10/nginix/mongrel/swiftiply

thanks
nic

full error message:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/util.rb:93:in
find_script' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/bj.rb:12 /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb: 43:ininstance_eval’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb:
43:in call' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb: 43:inattribute’
(eval):3:in call' (eval):3:inscript!’
(eval):4:in script' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:120:incommand’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:107:in
start' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:62:intickle’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/api.rb:66:in
submit' /app/controllers/uploads_controller.rb:7:increate’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/base.rb:1158:in send' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/base.rb:1158:inperform_action_without_filters’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/filters.rb:697:in call_filters' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/filters.rb:689:inperform_action_without_benchmark’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/benchmarking.rb:68:in
perform_action_without_rescue' /usr/local/lib/ruby/1.8/benchmark.rb:293:inmeasure’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/benchmarking.rb:68:in
perform_action_without_rescue' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/rescue.rb:199:inperform_action_without_caching’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/caching.rb:678:in perform_action' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/ active_record/connection_adapters/abstract/query_cache.rb:33:incache’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/
active_record/query_cache.rb:8:in cache' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/caching.rb:677:inperform_action’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/base.rb:524:in send' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/base.rb:524:inprocess_without_filters’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/filters.rb:685:in
process_without_session_management_support' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/session_management.rb:123:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/base.rb:388:in process' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/dispatcher.rb:171:inhandle_request’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/dispatcher.rb:115:in dispatch' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/dispatcher.rb:126:indispatch_cgi’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/dispatcher.rb:9:in dispatch' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/ rails.rb:76:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
rails.rb:74:in synchronize' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/ rails.rb:74:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
159:in process_client' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 158:ineach’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
158:in process_client' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 285:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
285:in initialize' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 285:innew’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
285:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 268:ininitialize’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
268:in new' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 268:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
configurator.rb:282:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/ configurator.rb:281:ineach’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
configurator.rb:281:in run' /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/ mongrel_rails:136:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
command.rb:212:in run' /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/ mongrel_rails:252 /usr/local/bin/mongrel_rails:19:inload’
/usr/local/bin/mongrel_rails:19

2

I’m experiencing similar problems on Ubuntu 8.04

it sucks big time… has anyone found the cause of this?

“no bj found in [”/var/www/oc/releases/20080713133248/script",
“/sbin”, “/bin”, “/usr/sbin”, “/usr/bin”]"

/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/util.rb:93:in
find_script' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/bj.rb:12 /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb:43:ininstance_eval’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb:43:in
call' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb:43:inattribute’
(eval):3:in call' (eval):3:inscript!’
(eval):4:in script' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:120:incommand’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:107:in
start' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:62:intickle’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/api.rb:66:in submit' [RAILS_ROOT]/app/models/user_observer.rb:4:inafter_create’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/observer.rb:171:in
send' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/observer.rb:171:inupdate’
/usr/local/lib/ruby/1.8/observer.rb:185:in notify_observers' /usr/local/lib/ruby/1.8/observer.rb:184:ineach’
/usr/local/lib/ruby/1.8/observer.rb:184:in notify_observers' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/callbacks.rb:309:innotify’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/callbacks.rb:296:in
callback' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/callbacks.rb:221:increate_without_timestamps’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/timestamp.rb:29:in
create' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/base.rb:2472:increate_or_update_without_callbacks’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/callbacks.rb:207:in
create_or_update' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/base.rb:2200:insave_without_validation’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.1.0/lib/active_record/validations.rb:901:in
`save_without_dirty’

Nic Deakins wrote:

hi all

I’m running background tasks using BJ 1.0.1 (gem version). On some
requests, the tasks are executed as expected. On others, I get the
following error:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):

when it runs, it runs fine but does anyone know what could be causing
these errors?
I’m using ubuntu 7.10/nginix/mongrel/swiftiply

thanks
nic

full error message:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/util.rb:93:in
find_script' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/bj.rb:12 /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb: 43:ininstance_eval’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb:
43:in call' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/attributes.rb: 43:inattribute’
(eval):3:in call' (eval):3:inscript!’
(eval):4:in script' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:120:incommand’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:107:in
start' /usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/runner.rb:62:intickle’
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/api.rb:66:in
submit' /app/controllers/uploads_controller.rb:7:increate’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/base.rb:1158:in send' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/base.rb:1158:inperform_action_without_filters’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/filters.rb:697:in call_filters' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/filters.rb:689:inperform_action_without_benchmark’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/benchmarking.rb:68:in
perform_action_without_rescue' /usr/local/lib/ruby/1.8/benchmark.rb:293:inmeasure’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/benchmarking.rb:68:in
perform_action_without_rescue' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/rescue.rb:199:inperform_action_without_caching’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/caching.rb:678:in perform_action' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/ active_record/connection_adapters/abstract/query_cache.rb:33:incache’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/
active_record/query_cache.rb:8:in cache' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/caching.rb:677:inperform_action’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/base.rb:524:in send' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/base.rb:524:inprocess_without_filters’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/filters.rb:685:in
process_without_session_management_support' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/session_management.rb:123:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/base.rb:388:in process' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/dispatcher.rb:171:inhandle_request’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/dispatcher.rb:115:in dispatch' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/ action_controller/dispatcher.rb:126:indispatch_cgi’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/
action_controller/dispatcher.rb:9:in dispatch' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/ rails.rb:76:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
rails.rb:74:in synchronize' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/ rails.rb:74:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
159:in process_client' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 158:ineach’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
158:in process_client' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 285:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
285:in initialize' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 285:innew’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
285:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 268:ininitialize’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:
268:in new' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb: 268:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
configurator.rb:282:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/ configurator.rb:281:ineach’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
configurator.rb:281:in run' /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/ mongrel_rails:136:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/
command.rb:212:in run' /usr/local/lib/ruby/gems/1.8/gems/swiftiply-0.6.1.1/bin/ mongrel_rails:252 /usr/local/bin/mongrel_rails:19:inload’
/usr/local/bin/mongrel_rails:19

3

Nic Deakins wrote:

hi all

I’m running background tasks using BJ 1.0.1 (gem version). On some
requests, the tasks are executed as expected. On others, I get the
following error:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):

when it runs, it runs fine but does anyone know what could be causing
these errors?
I’m using ubuntu 7.10/nginix/mongrel/swiftiply

thanks
nic

full error message:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/util.rb:93:in
`find_script’

bj is telling you what the problem is, if you look at those lines of
util you’ll see

  def find_script basename
    path = ENV["PATH"] || ENV["path"] || Bj.default_path
    raise "no env PATH" unless path
    path = path.split File::PATH_SEPARATOR
    path.unshift File.join(Bj.rails_root, "script")
    path.each do |directory|
      script = File.join directory, basename
      return File.expand_path(script) if(test(?s, script) and

test(?r, script))
end
raise “no #{ basename } found in #{ path.inspect }”
end

and your path is list in the error message. so, the question is

  1. is bj on one of those paths above?
  2. if it is, is it readable by the user running the rails app?

i suspect this is an installation or path/environment issue, however,
even if it is, you can always just set the path to bj manually in you
configuration

Bj.script = ‘/full/path/to/bin/bj’

and even set your path

Bj.default_path = %w[ /usr/bin /usr/local/bin ]

so it should be very simple to rememdy

have a look at lib/bj/api.rb and lib/bj/bj.rb

from the look of your error message i’d guess the cap deploy has a
different environment that another you may be running rails as.

cheers.

-a

4

D. Krmpotic wrote:

Sorry for late reply, but the problem is rather curious…! The catch is
in the word ‘intermittent’… we had a lot of these errors in the last 2
weeks (when I was away :frowning: ) and users couldn’t signup up!

I ‘solved’ the problem, by restarting THIN servers !?

Could you suggest a possible explanation? So it is not (an obvious) path
problem it seems… because now it works… until it stops again…

Thank you!
david

it seems perfectly obvious to me - you are starting your servers under
two environments: one has bj in the and one does not. a likely scenario
is starting from init scripts (machine boot)and from the console. in
both cases you have to make sure you path is setup correctly.

-a

5

Ara, thank you for the answer… but I don’t quite get it… are you
saying that two Thins are somehow running in different environments? I
have to say that I don’t see how this could be happening, because it’s a
Thin cluster and thus all/both instances stem from the same
configuration. Please elaborate your thinking a little bit. Thanx again

Ara Howard wrote:

D. Krmpotic wrote:

Sorry for late reply, but the problem is rather curious…! The catch is
in the word ‘intermittent’… we had a lot of these errors in the last 2
weeks (when I was away :frowning: ) and users couldn’t signup up!

I ‘solved’ the problem, by restarting THIN servers !?

Could you suggest a possible explanation? So it is not (an obvious) path
problem it seems… because now it works… until it stops again…

Thank you!
david

it seems perfectly obvious to me - you are starting your servers under
two environments: one has bj in the and one does not. a likely scenario
is starting from init scripts (machine boot)and from the console. in
both cases you have to make sure you path is setup correctly.

-a

6

D. Krmpotic wrote:

Ara, thank you for the answer… but I don’t quite get it… are you
saying that two Thins are somehow running in different environments? I
have to say that I don’t see how this could be happening, because it’s a
Thin cluster and thus all/both instances stem from the same
configuration. Please elaborate your thinking a little bit. Thanx again

i’m not saying the two are running under different environments, i’m
saying that when you re-started them by hand, perhaps at the console,
you may have had a different environment than they were originally
started under - for instance cron or init.d on system boot. may not be
the case - but worth inventigating.

-a

7

Sorry for late reply, but the problem is rather curious…! The catch is
in the word ‘intermittent’… we had a lot of these errors in the last 2
weeks (when I was away :frowning: ) and users couldn’t signup up!

I ‘solved’ the problem, by restarting THIN servers !?

Could you suggest a possible explanation? So it is not (an obvious) path
problem it seems… because now it works… until it stops again…

Thank you!
david

Ara Howard wrote:

Nic Deakins wrote:

hi all

I’m running background tasks using BJ 1.0.1 (gem version). On some
requests, the tasks are executed as expected. On others, I get the
following error:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):

when it runs, it runs fine but does anyone know what could be causing
these errors?
I’m using ubuntu 7.10/nginix/mongrel/swiftiply

thanks
nic

full error message:

RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/
script", “/bin”, “/usr/bin”, “/sbin”, “/usr/sbin”]):
/usr/local/lib/ruby/gems/1.8/gems/bj-1.0.1/lib/bj/util.rb:93:in
`find_script’

bj is telling you what the problem is, if you look at those lines of
util you’ll see

  def find_script basename
    path = ENV["PATH"] || ENV["path"] || Bj.default_path
    raise "no env PATH" unless path
    path = path.split File::PATH_SEPARATOR
    path.unshift File.join(Bj.rails_root, "script")
    path.each do |directory|
      script = File.join directory, basename
      return File.expand_path(script) if(test(?s, script) and

test(?r, script))
end
raise “no #{ basename } found in #{ path.inspect }”
end

and your path is list in the error message. so, the question is

  1. is bj on one of those paths above?
  2. if it is, is it readable by the user running the rails app?

i suspect this is an installation or path/environment issue, however,
even if it is, you can always just set the path to bj manually in you
configuration

Bj.script = ‘/full/path/to/bin/bj’

and even set your path

Bj.default_path = %w[ /usr/bin /usr/local/bin ]

so it should be very simple to rememdy

have a look at lib/bj/api.rb and lib/bj/bj.rb

from the look of your error message i’d guess the cap deploy has a
different environment that another you may be running rails as.

cheers.

-a

8

Sorry for late response… You were right…
After adding

export PATH=/usr/local/bin:$PATH

on top of /etc/init.d/thin script, BJ works fine after server restart.

Thank you.
david

Ara Howard wrote:

D. Krmpotic wrote:

Ara, thank you for the answer… but I don’t quite get it… are you
saying that two Thins are somehow running in different environments? I
have to say that I don’t see how this could be happening, because it’s a
Thin cluster and thus all/both instances stem from the same
configuration. Please elaborate your thinking a little bit. Thanx again

i’m not saying the two are running under different environments, i’m
saying that when you re-started them by hand, perhaps at the console,
you may have had a different environment than they were originally
started under - for instance cron or init.d on system boot. may not be
the case - but worth inventigating.

-a