Issue with Local Server on Parametric Analysis Tool (PAT) and Question on Unmet Hours

edit

Hi, Any new updates on this?

I tried PAT 3.8 and encountered the same problem.

This is the rails.log content:

C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/definition.rb:524:in `materialize': Could not find date-3.3.4, sassc-2.4.0, bson-4.14.1, msgpack-1.4.5, nio4r-2.5.9, websocket-driver-0.7.6, json-2.7.2 in locally installed gems (Bundler::GemNotFound)
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/definition.rb:197:in `specs'
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/definition.rb:254:in `specs_for'
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/runtime.rb:18:in `setup'
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler.rb:171:in `setup'
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/setup.rb:23:in `block in <top (required)>'
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/ui/shell.rb:159:in `with_level'
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/ui/shell.rb:111:in `silence'
from C:/ParametricAnalysisTool-3.8.0/pat/OpenStudio-server/gems/gems/bundler-2.4.10/lib/bundler/setup.rb:23:in `<top (required)>'
from <internal:C:/ParametricAnalysisTool-3.8.0/pat/ruby/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
from <internal:C:/ParametricAnalysisTool-3.8.0/pat/ruby/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
from C:/ParametricAnalysisTool-3.8.0/pat/ruby/lib/ruby/3.2.0/rubygems.rb:1370:in `<top (required)>'
from <internal:gem_prelude>:2:in `require'
from <internal:gem_prelude>:2:in `<internal:gem_prelude>'

Hi, Is there any update regarding this issue?

I tried to start the local server for a manual analysis using PAT 3.7.0, 3.8.0, and 3.9.0. I also followed all the instructions from other Q&A posts concerning this issue as well. I still cannot start the local server. Please advise.

C:\fakepath\PAT390-01.jpg

These are the error and warning messages received from starting the server via the command prompt:

System call will be: 'mongod.exe --port 27018 --logpath "D:/.../.../PAT380/logs/mongo.log" --dbpath "D:/.../.../PAT380/data/db"' in directory 'C:/ParametricAnalysisTool-3.9.0/pat/mongo/bin' {"t":{"$date":"2025-01-20T07:06:25.500Z"},"s":"I", "c":"CONTROL", "id":20697, "ctx":"main","msg":"Renamed existing log file","attr":{"oldLogPath":"D:/.../.../PAT380/logs/mongo.log","newLogPath":"D:/.../.../PAT380/logs/mongo.log.2025-01-20T07-06-25"}} E, [2025-01-20T14:06:41.761695 #6456] ERROR -- : Mongod failed to launch. Please refer to D:\...\...\PAT380/logs/mongod.log. W, [2025-01-20T14:06:42.171683 #6456] WARN -- : No process with PID 6060 exists, did not attempt to kill

This is from the mongo.log:

{"t":{"$date":"2025-01-20T14:06:25.863+07:00"},"s":"E", "c":"STORAGE", "id":20557, "ctx":"initandlisten","msg":"DBException in initAndListen, terminating","attr":{"error":"DBPathInUse: Unable to create/open the lock file: D:/.../.../PAT380/data/db\mongod.lock (The process cannot access the file because it is being used by another process.). Ensure the user executing mongod is the owner of the lock file and has the appropriate permissions. Also make sure that another mongod instance is not already running on the D:/.../.../PAT380/data/db directory"}}

Thank you.