{"id":163452,"date":"2021-10-27T15:15:11","date_gmt":"2021-10-27T15:15:11","guid":{"rendered":"\/forum\/forums\/topic\/lumerical-fdtd-engine-failing-quickly-with-hangup-error-on-linux\/"},"modified":"2021-11-01T16:40:15","modified_gmt":"2021-11-01T16:40:15","slug":"lumerical-fdtd-engine-failing-quickly-with-hangup-error-on-linux","status":"closed","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/lumerical-fdtd-engine-failing-quickly-with-hangup-error-on-linux\/","title":{"rendered":"Lumerical fdtd-engine failing quickly with Hangup error on Linux"},"content":{"rendered":"
\n
\n

I've been asked to look into getting Lumerical up and running on our local cluster (Lumerical v212 on CentOS 7.6) and I'm seeing my initial tests fail very quickly.<\/p>\n

I started with the cpi-mpich2nem test first, and the following works correctly from the command line:<\/p>\n

\/usr\/shared_apps\/packages\/lumerical\/v212\/mpich2\/nemesis\/bin\/mpiexec -n 4 \/usr\/shared_apps\/packages\/lumerical\/v212\/mpitest\/cpi-mpich2nem<\/p>\n

I then proceed to try fdtd-engine using what I think is the right syntax based on the examples at Running simulations using terminal in Linux – Lumerical Support<\/a> :<\/p>\n

\/usr\/shared_apps\/packages\/lumerical\/v212\/mpich2\/nemesis\/bin\/mpiexec -n 1 \/usr\/shared_apps\/packages\/lumerical\/v212\/bin\/fdtd-engine-mpich2nem -t 1 \/storage\/hpc\/54\/pacey\/lumerical\/Lumerical_Test_RM.fsp<\/p>\n

The command returns very quickly with the error message:<\/p>\n

APPLICATION TERMINATED WITH THE EXIT STRING: Hangup (signal 1)<\/p>\n

There's no other output on the screen, and no new files created in that directory. Can anyone advise how I can troubleshoot this?<\/p>\n","protected":false},"template":"","class_list":["post-163452","topic","type-topic","status-closed","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t