Upgrade to 5.5u1, stalls of server initialization iscsi up to 45 min.

Similar Questions

• A server error has occurred, the Profile Manager after upgrade to osX - 10.11.4 server 5.1

  After the Connection Manager profile with safari and firefox, I get this error message after my upgrade to el captian 10.11.4 and upgrade to Server 5.1.

  "A server error has occurred, please reload the page and try again.

  If this error " persists, please contact your administrator"

  Someone who could give me advice where to start troubleshooting?

  THE SERVER LOG

  PROFILEMANAGER

  Service log:

  ######################################################################

  ##############     START          ###########################################

  ######################################################################

  [738] [08/04/2016 17:48:56.170] I: completed in 232ms s (view: 1, DB: 62). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [733] [08/04/2016 18:51:53.312] I: treatment MagicController #admin_will_load (for 1.1.1.1 at 2016-04-08 18:51:53) [POST]

  [733] [08/04/2016 18:51:53.488] I: completed in 157ms (view: 1 DB: 9) | 200 OK [https://macserver.elcapitan.com/magic/admin_will_load]

  [734] [08/04/2016 18:51:54.555] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:54) [POST]

  [734] [08/04/2016 18:51:55.346] I: completed in 790ms (views: 0dB,: 92). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [735] [08/04/2016 18:51:55.476] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [737] [08/04/2016 18:51:55.712] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [738] [08/04/2016 18:51:55.741] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [735] [08/04/2016 18:51:55.773] I: completed in 296ms (view: 0, DB: 73). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [739] [08/04/2016 18:51:55.841] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [738] [08/04/2016 18:51:55.892] I: completed in 151ms (view: DB, 0: 18) | 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [737] [08/04/2016 18:51:55.943] I: completed in 230ms (view: 0, DB: 60). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [739] [08/04/2016 18:51:55.980] E: \253Magic#do_magic-> UserGroup.get_profiles\273 taken unsupported constant not initialized exception InactiveUserGroup to /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/dependencies.rb:469:in 'load_missing_constant '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/dependencies.rb:106:in "const_missing_with_dependencies".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_library_item_base.rb:22: in 'const_get '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_library_item_base.rb:22: in 'library_item_by_id '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/Mo dels / profile .rb: 276: in 'owner '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/Mo dels / profile .rb: 250: in "library_item_type".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/Mo dels / profile .rb: 257: in "modify_attributes".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_record_base.rb:184: in 'get_attributes.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/he FPL / user_group_helper.rb:85: in 'get_profiles '.

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:180: in ' block ' (5 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "block in ms.

  /Applications/server.app/Contents/ServerRoot/usr/lib/Ruby/1.9.1/benchmark.rb:29 5: in 'real time '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "ms."

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:180: in ' block ' (4 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstr act / database_statements.rb:136: in "transaction".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config /initializers/dm_rails_monkey_patches.rb:152:in "transaction".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in "transaction".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_utilities.rb:242: in 'process_in_transaction '.

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:163: in ' block ' (3 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:146: in 'each '.

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:146: in ' block ' (2 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:137: in 'each '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:137: in 'block in do_magic'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:127: in 'each '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:127: in 'do_magic '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in 'perform_action.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in "call_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:638:in 'block in run_before_filters'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / application_controller.rb:111: in 'give_session_to_models '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in "evaluate_method".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:186:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:635:in "run_before_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:615:in "call_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in "perform_action_with_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in 'block in perform_action_with_benchmark'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "block in ms.

  /Applications/server.app/Contents/ServerRoot/usr/lib/Ruby/1.9.1/benchmark.rb:29 5: in 'real time '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "ms."

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in "perform_action_with_benchmark".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in "perform_action_with_rescue".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in "perform_action_with_flash".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in "process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in "process_with_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in "process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:43 8: in 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:87:in 'send '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:121:in "_Appel".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:130:in 'block in build_middleware_stack'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/string_coercion.rb:25:i n 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/string_coercion.rb:25:i n 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/head.rb:9:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/methodoverride.rb:24:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/params_parser.rb:15:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/session/abstract_store. RB: 177: in 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in "call block".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstr act / query_cache.rb:34: in 'cache '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:9:in "cache".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:28:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstr act / connection_pool.rb:361: in "call".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/failsafe.rb:26:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/lock.rb:11:in "call block".

  < internal: Prelude >: 10: in 'synchronize '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/lock.rb:11:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:106:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/static.rb:31:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/log_tailer.rb:17:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:81:in "pre_process block."

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:79:in 'catch '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:79:in "pre_process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:54:in "process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:39:in "receive_data".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in "run_machine".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in 'run '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/backends/base.rb:63:in 'start '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/server.rb:159:in 'start '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/controllers/controller.rb:86:in 'start '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:187:in 'run_command.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:152:in 'run! '

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/thin:1 1: turnkey"< >".

  [739] [08/04/2016 18:51:55.991] F: NameError (uninitialized constant InactiveUserGroup):

  Vendor/Ruby/1.9.1/Gems/ActiveSupport-2.3.18/lib/active_support/Dependencies.RB: 469: in "load_missing_constant".

  Vendor/Ruby/1.9.1/Gems/ActiveSupport-2.3.18/lib/active_support/Dependencies.RB: 106: in "const_missing_with_dependencies".

  lib/mdm_library_item_base. RB:22: in 'const_get '.

  lib/mdm_library_item_base. RB:22: in 'library_item_by_id '.

  App/Models/Profile.RB:276:in 'owner '.

  App/Models/Profile.RB:250:in "library_item_type".

  App/Models/Profile.RB:257:in "modify_attributes".

  lib/mdm_record_base. RB:184: in 'get_attributes.

  App/helpers/user_group_helper. RB:85: in 'get_profiles '.

  App/Controllers/magic_controller. "RB:180: in ' block ' (5 levels) in do_magic.

  App/Controllers/magic_controller. "RB:180: in ' block ' (4 levels) in do_magic.

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/connection_adapter s/abstract/database_statements.rb:136:in "transaction".

  config/Initializers/dm_rails_monkey_patches. RB:152: in "transaction".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/transactions. RB:18 2: in the "transaction".

  lib/mdm_utilities. RB:242: in 'process_in_transaction '.

  App/Controllers/magic_controller. "RB:163: in ' block ' (3 levels) in do_magic.

  App/Controllers/magic_controller. RB:146: in 'each '.

  App/Controllers/magic_controller. "RB:146: in ' block ' (2 levels) in do_magic.

  App/Controllers/magic_controller. RB:137: in 'each '.

  App/Controllers/magic_controller. RB:137: in 'block in do_magic'

  App/Controllers/magic_controller. RB:127: in 'each '.

  App/Controllers/magic_controller. RB:127: in 'do_magic '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:1333: in 'perform_action.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:617:i 'call_filters '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:638:i n 'run_before_filters block '.

  App/Controllers/application_controller. RB:111: in 'give_session_to_models '.

  Vendor/Ruby/1.9.1/Gems/ActiveSupport-2.3.18/lib/active_support/callbacks. RB:178: in 'evaluate_method '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:186:i n 'call '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:635:i 'run_before_filters '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:615:i 'call_filters '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:610:i 'perform_action_with_filters '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/benchmarking. RB: 68: 'block in perform_action_with_benchmark'

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/benchmarking. RB: 68: in "perform_action_with_benchmark".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Rescue.RB:160:in "perform_action_with_rescue".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Flash.RB:151:in "perform_action_with_flash".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:532: in 'process '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:606:i 'process_with_filters '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:391: in 'process '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:386: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Routing/route_se t.rb:438: in "call".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:87: "send."

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:12 1: in "_Appel".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:13 0: in 'block in build_middleware_stack'

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/string_coercion. RB: 25: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/string_coercion. RB: 25: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/params_parser. RB: 15: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/session/abstract _store.rb:177: in "call".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/query_cache. RB:29: in "block in the call.

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/connection_adapter s/abstract/query_cache.rb:34:in "cache".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/query_cache. RB:9:i n "cache".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/query_cache. RB:28: in "call".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/connection_adapter s/abstract/connection_pool.rb:361:in «call»

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Failsafe.RB:26:i n 'call '.

  < internal: Prelude >: 10: in 'synchronize '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:10 6: in 'call '.

  Vendor/Ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/static. RB:31: in 'call '.

  Vendor/Ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/log_tailer. RB:17: in 'call '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:81:in 'block in pre_process ".

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:79:in 'catch '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:79:in "pre_process".

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:54:in 'process '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:39:in "receive_data".

  Vendor/Ruby/1.9.1/Gems/eventmachine-1.0.3/lib/eventmachine. RB:187: in 'run_machine '.

  Vendor/Ruby/1.9.1/Gems/eventmachine-1.0.3/lib/eventmachine. RB:187: in 'run '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/backends/base. RB:63: in 'start '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Server.RB:159:in 'start '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Controllers/Controller.RB:86:in 'start '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Runner.RB:187:in 'run_command.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Runner.RB:152:in 'run '!

  end: 11: in "< main >".

  [739] [08/04/2016 18:51:55.992] I: rendered /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/public 500.html (500 internal server error)

  [740] [08/04/2016 18:51:55.998] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [741] [08/04/2016 18:51:56.060] I: treatment MagicController #do_magic (for 1.1.1.1 at 2016-04-08 18:51:56) [POST]

  [740] [08/04/2016 18:51:56.278] I: completed in s 280ms (view: 1, DB: 115). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [741] [08/04/2016 18:51:56.368] I: completed in 307ms (views: 1, DB: 177). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  mpass1 kernel [0]: gfx: Surf 15ea9c9f: clientClose:

  8 April 18:52:14 macserver kernel [0]: gfx: Surf 15ea9c9f: SetIDMode: id = 330484187 mode = 0 x 24

  8 April 18:52:14 macserver kernel [0]: gfx: Surf 15ea9c9f: clientClose:

  ######################################################################

  ##############     END               ##########################################

  ######################################################################

  OS X Server: Troubleshooting with the Profile Manager

  How to reset the profile to its original State Manager

  Update Server 3.2.1 fail

• Is upgrading to the El Capitan crash Server Apple Application?

  Only Mini server - crash Server Application after an upgrade to El Capitan, or it doesn't work until a patch is installed?

  My experience is that the upgrade using the App store of 10.10.5 for a running Server 5.0.15 smoothly by stopping the server, and then performing the upgrade. You must then open the.app and he made some kind of update and then starts with the previous services and settings as they were. At this point, that I reboot, no particular reason, it seems just too good to be true.

  C.

• There will be an upgrade path to windows 8 Windows server 2008 r2 or the preview?

  I had windows vista and after a computer crash, I decided to build my own, but I used Windows Server 2008R2 for an operating system of DreamSpark...

  There will be a way to upgrade windows 8 for my situation? or at least of Windows 8 preview (at a discount)?

  I had windows vista and after a computer crash, I decided to build my own, but I used Windows Server 2008R2 for an operating system of DreamSpark...

  There will be a way to upgrade windows 8 for my situation? or at least of Windows 8 preview (at a discount)?

  Subject: No and Yes.

  Not for windows 8 Windows Serevr 2008 R2.  Do not upgrade a server with a consumer OS operating system.  Windows Server 2012 (also RTM'd yesterday, I think) would be this way.

  Yes since version 8 of preview Windows to Windows 8 Professional.  Sort of.  You can switch between preview release in full release, but it's just that the upgrade of XP you get just to keep your personal files - all installed applications and tastes are gone and you need to install fees.  Might as well save and install clean anyway - since that's what it does basically.

  Body of the message: View topic answer.

• How to upgrade the hardware on a VCenter Server

  In lab environment, two hosts, VCenter server, don't HA, storage etc. running share. I managed to upgrade hosts, using Crossover, but his declaration of errors when attempting to upgrade the hardware of server VCenter comments... I can see that it would be a problem, using VCenter to upgrade equipment on himself, when he needs to reboot the server to install. The question is, how to get around that? I tried to look for solutions, not found anything yet. Hope that makes sense.

  Latest versions of everything, as it is a laboratory under eval licenses. Thank you

  You must turn off the VM, connection to the ESXi host through vSphere client vCenter and right-click on the VM vCenter > virtual hardware upgrade.

  Make sure that you run VMware tools before do you.

• UNABLE TO DOWNLOAD CLOUD CREATIVE UPGRADE... TRY CONTACTING SERVER IS WHAT I'VE GOT ACE

  Two months my creative cloud to desktop to update itself. "" Every attempt the download stops at 2% and I got is: "TRY to CONNECT to THE SERVER"

  Since then, my creative office has no menu, suffice it to say that upgrade is available UNUSABLE

  First of all we will follow the basic steps:

  N ° 1)

  Exit the Office Adobe Creative Cloud application.

  Complete all Adobe processes like the creative cloud, CoreSync, Armsvc, AAMUpdater... etc from the Task Manager.

  Step 2)

  Temporarily disable anti-virus and firewall.

  If you use the following software security like Mcafee, AVG, norton, etc., be sure to turn off their smart firewall.

  Step 3)

  (1) open Control Panel and then click on the network and Internet"" option.

  2) click on Internet options, click on the tab "connections".

  (3) in the 'Connections' tab, select 'LAN' settings, you will be able to view the LAN settings box.

  (4) check the box-"automatically detect settings" and then "uncheck" all the other boxes as "configuration Script auto use", "Use a proxy server," proxy server ", then click on the ok button."

  5) click on the "Network settings" button once again, make sure that "Automatically detect settings" is the only option you select, the window of properties of LAN so clear.

  
  

  Step 4)

  
  Launch the Adobe Creative Cloud desktop application and try to update again.

  Always the same?

  1) go to C:\Windows\System32\drivers\etc and locate the file named hosts inside the folder etc.

  Copy 2) host of the file to the desktop and open the same thing with Notepad.

  Let me know if you can see all the entries as Adobe 127.0.0.1 activate.adobe.com... ... etc?

• After the upgrade to 754035, cannot access the server

  In Edit-preferences-shared VMs, workstation server settings is enabled, but I get the error (even when of WS running as root):

  Unable to connect to the server of workstation. Please ensure that the server is running and that you are allowed to connect.

  -It is true that I have not test this before the upgrade.

  WS Server uses the default port 443, nothing else should be listening on it.

  # netstat - nalp | grep 443
  TCP 0 0 0.0.0.0:443 0.0.0.0: * LISTEN 16082/vmware-pass
  TCP 0 0 127.0.0.1:41675 127.0.0.1:443 ESTABLISHED 16130/vmware
  TCP 0 0 127.0.0.1:443 ESTABLISHED 16082/vmware-pass 127.0.0.1:41675
  TCP 0 0 192.168.2.54:33662 74.125.227.117:443 ESTABLISHED 15280/firefox
  tcp6 0 0: 443: * LISTEN 16082/vmware-pass

  The host is running a new installation of Linux Mint 13, core 3.2.0 - 23-generic #36 - Ubuntu SMP Linux 64-bit

  Note: I use the session X as user "dave" and vmware workstation will be started as "dave2":

  Dave ~ $ "sudo knew dave2 vmware."

  Hello

  are there updates after your last post?

• The upgrade of the connection to the server to 64-bit

  We have a server to connect to version 4.0.1.  We are upgrading to 4.6, but it's on a 32-bit server, so we will need to migrate to a 64-bit server.  I see 2 ways to do this...

  1 put level 32 bit to 4.6, can create a replica of 64-bit.  If I do this, it will bring over our definitions of pool?

  2. use the vdmexport utility, but this backup pool definitions?

  Or is there a better way to do the migration?

  Hello

  You must follow the methods explained in VMware View4.6 upgrade Guide (page 25).

  https://www.VMware.com/PDF/view-46-upgrades.PDF

  -noble

• Process of upgrading 3.5 host with vCenter server Virtual

  Hi I have recently updated my old server from client to vCenter 4.1 virtualized VI, sitting on my 3.5 cluster.  I intend to use the Update Manager to upgrade my guests, but I don't know how the virtual vCenter server is going to face?  The plan was: 1. move all the virtual machines off-host 1.  2 put the host in maintenance mode 1. 3. on the vCenter server, create a base, then line at host level 1 to 4.1. 4. now - at this point add this host in the cluster? And migrate the server vCenter top, so I can upgrade the other two hosts?  If the works above, then it should be quite a nice update, if you cannot add the new version of the host of back in, how you vMotion the vCenter server off so you can keep control of the cluster.

  IMO, it should work. To upgrade from 3.5 to 4.1, your ESX host must be in 5 update (see http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf) already.

  If VMotion or migrate the server vCenter Server - for some reason-does not work, you can delete vCenter Server of the inventory of the old host and add to the inventory of the new host.

  André

• ESX 3.5 to ESX 4.0 upgrade fails on IBM x 346 server

  Hi all,

  I try to improve ESX 3.5 to ESX 4.0 on IBM x 346 server using vSphere Host Update Utility 4.0 and upgrade constantly fails. In the ESX Server log, I found the following strings which I think are related with upgrade failure:

  NfcFileRawOpen: could not open: the file is not found.

  NfcFile_Open: Open failed:

  NfcStartFileSend: could not open the file

  NfcServerLoop: receive failed, quit smoking

  Nfc_AuthdServerLoop saw the error: no file exists for given path - file open failed: the file is not found

  Any ideas? What's wrong?

  TIA.

  ARO

  Danas

  IBM x 346 is not supported for ESX 4

• Upgrading ESX 3.5U1 to 3.5U3 by using Update Manager

  I'm almost finished upgrading all our servers ESX 3.02 to 3.5 update 1 more a few patches.

  This was done by booting from the CD to update 1 3.5 to perform the upgrade.

  I had a basleine created in the update manager that includes all fixes releaed in June 2008 or earlier. This base was also used on all of our ESX servers.

  I now want to use the Update Manager to upgrade all servers to 3.5.0 update 3 and the latest patches.

  If I have a base line that includes all the updates that are never out, can I just clean up the hosts on this base? The upgrade process will be "smart" enough to just install update 3 and latest patches or will be installed all the patches in sequence include the update 2 which I suppose is not necessary if the update 3 is also being installed?

  Should I create a baseline containing the 3 updated and any update since then. Update 3 includes other updates also published November 6?

  Note that I'm under 104215 virtual Center version but will be upgrading to update 3 before upgrading the hosts.

  Our Update Manager database was created when the Update Manager is out and includes all updates, including ESX Server 3.5.0 Update 2 updated with the question of the "ticking time bomb".

  Any advice will be appreciated.

  Craig

  Hello

  I'm never live from 3.0.1 to U1 and U3. Always fresh, I installed 3.5 and then improved from there. However your approach should work perfectly as well. I wouldn't get to frustrated with VUM as him starts and stops and the issue of sanitation occur due to the circles of interesting dependence and bugs squarely in the process of upgrading some of the improvements. I often force ESX in Maintenance mode to install the updates. It depends usually if VMware HA is enabled, or VMS must be evacuated. I tend to evacuate all virtual machines running by hand, then perform upgrades.

  Best regards

  Edward L. Haletky

  VMware communities user moderator

  ====

  Author of the book "VMWare ESX Server in the enterprise: planning and securing virtualization servers, Copyright 2008 Pearson Education.»

  Blue gears and SearchVMware Pro Articles: http://www.astroarch.com/wiki/index.php/Blog_Roll

  Security Virtualization top of page links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

• Performing a Firmware Upgrade using the built-in Web server

  This video provides step by step instructions to perform a firmware update using the integrated Web (EWS) server for single function of HP LaserJet and multifunction printers.

  For other helpful videos, go to hp.com/supportvideos or youtube.com/hpsupport. Several support options for your printer are available at hp.com support.

  This video was produced by HP.

  I hope you find this information useful.

• Upgrade to 5.5U1

  Hello

  I have a 5.5 test patched the host running. I just tried to pass this to U01. I used the method esxcli on the host via SSH. All patches are ignored and the host not changed them.

  However, I have 12 showing in my Update Manager. What are those contained in the U01 update.

  Puzzled?

  Tony

  Hello

  Here is the file. Maybe the original installation was a picture of HP as its on a server of the G8? Although updates in December were very good

  Tony

• VMWare ESX3i without VirtualCenter server initialization after help stop!

  Hello!

  I have a problem. Recently, I have server shutdown an ESX3i using customer Infrastructure. Now, I can not connect to the server. Ping does not work.

  When I make a stop a server of ESX3i, the machine is turned off or only the OS VMware ESX3i?

  How can I turn on the server after doing a stop an ESX3i Server?

  THX!

  Please mark my answer as "useful" or "correct", so that I will get a few points

• Upgrade to EclipseLink in Embedded WebLogic Server (JDeveloper 11.1.1.2.0)

  Currently I use JDeveloper 11.1.1.2.0 for my project, which comes with pre-installed v1.2 EclipseLink. However, my project requires using EclipseLink latest version 2.0. I added EclipseLink 2.0 in the libraries and Classpath setting in the ownership of the project. However, when I run my application using the embedded WebLogic Server, my application still uses the old v1.2 EclipseLink. I tried to copy the jar EclipseLink 2.0 file in DefaultDomain/lib directory and directory of library of ear. But server weblogic shipped still using the old version of the directory modules. Could someone tell me how I might solve this problem. Thank you!

  Supplied preconfigured WebLogic EclipseLink TopLink library as a module of the system. You can't pass this 2.0 in a mode of support. The next version of WebLogic will include EclipseLink 2.0(.x).

  If you want to test your use of EclipseLink 2.0 application application using JPA 1.0 managed by EntityManagers you can bundle the library 2.0 in your EAR and use of configuration config of classloader filtered in the weblogic - application.xml to ensure packed library is used instead of the system module.

  Doug