Bigfix LMT DB2 Restore

Hi,

I’ve installed Bigfix/LMT on a new Redhat server (Redhat 6 to 7). Both servers (currect and new) have the same Bigfix version:
BESRootServer-9.5.12.68-rhel.x86_64
BESWebReportsServer-9.5.12.68-rhel.x86_64
BESAgent-9.5.12.68-rhe6.x86_64
I’m able to login for the first time and the default reports etc. were configured as expected.

After restoring the DB2 DB from the currect installation to the new server without any errors I get the error as shown below when I’m trying to acces the LMT login page (https://:9081). Any suggestions?
Thanks!

Internal Server Error (500)
Request Method: GET
Request URL: https://ota5651.management.dmz.finl.fortis:9081/sam
Applied migration files not in file system: 1480689548_dune_hpux_platform_fix.rb, 1487251774_eastwood_add_product_version_to_import.rb, 1492686770_fahrenheit_computer_group_type.rb, 1496667189_fahrenheit_fix_null_computer_created_at.rb, 1500020831_ghost_reprocess_missing_scans.rb from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.6369d34f70988ff5e2d4489b876d1cc303accdc9/lib/sequel/extensions/migration.rb:684:in get_applied_migrations' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.6369d34f70988ff5e2d4489b876d1cc303accdc9/lib/sequel/extensions/migration.rb:640:ininitialize’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/database.rb:928:in get_platform_migrator' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/database.rb:787:inschema_current?’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.6369d34f70988ff5e2d4489b876d1cc303accdc9/lib/sequel/database/connecting.rb:68:in connect' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.6369d34f70988ff5e2d4489b876d1cc303accdc9/lib/sequel/core.rb:106:inconnect’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/database.rb:309:in connect_internal' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/database.rb:321:inconnect’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/database.rb:786:in schema_current?' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/database.rb:34:insetup?’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/domains/sam/domain.rb:683:in Domain' from org/jruby/RubyBasicObject.java:1623:ininstance_exec’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/railties-4.2.6/lib/rails/initializable.rb:30:in run' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/railties-4.2.6/lib/rails/initializable.rb:55:inrun_initializers’ from classpath:/META-INF/jruby.home/lib/ruby/1.9/tsort.rb:150:in tsort_each' from classpath:/META-INF/jruby.home/lib/ruby/1.9/tsort.rb:183:ineach_strongly_connected_component’ from classpath:/META-INF/jruby.home/lib/ruby/1.9/tsort.rb:219:in each_strongly_connected_component_from' from classpath:/META-INF/jruby.home/lib/ruby/1.9/tsort.rb:182:ineach_strongly_connected_component’ from org/jruby/RubyArray.java:1613:in each' from classpath:/META-INF/jruby.home/lib/ruby/1.9/tsort.rb:180:ineach_strongly_connected_component’ from classpath:/META-INF/jruby.home/lib/ruby/1.9/tsort.rb:148:in tsort_each' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/railties-4.2.6/lib/rails/initializable.rb:54:inrun_initializers’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/railties-4.2.6/lib/rails/application.rb:352:in initialize!' from org/jruby/RubyKernel.java:1930:inpublic_send’ from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/railties-4.2.6/lib/rails/railtie.rb:194:in method_missing' from /opt/lmt/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/config/environment.rb:7:in(root)’ from org/jruby/RubyKernel.java:1040:in require' from classpath:/jruby/rack/rails/environment3.rb:1:in(root)’ from classpath:/jruby/rack/rails/environment3.rb:25:in load_environment' from classpath:/jruby/rack/rails_booter.rb:83:inload_environment’
You’re seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus.

Hi,

I’ve solved this issue: besides the Bigfix server versions, LMT should have the same version as well on both servers. After upgrading both servers (current- and new server) to the latest LMT version, I was able to migrate the current TEMADB to the new server.

Regards, Chiel