Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WISE crashing in Azure Container Instances #52

Open
3 tasks
RobJago opened this issue Jun 5, 2023 · 1 comment
Open
3 tasks

WISE crashing in Azure Container Instances #52

RobJago opened this issue Jun 5, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@RobJago
Copy link

RobJago commented Jun 5, 2023

Contact Details

robert.jagodzinski@nrcan-rncan.gc.ca

What happened?

WISE executable fails in Azure in container instance. std:bad_alloc when trying to assign LD_LIBRARY_PATH. This happens in both the validation or just a straight model execution with the fgmj.

  1. The model container was built from a Dockerfile which runs both locally and in Azure web apps. The same container built from the Dockerfile does not work in Azure container instances.
  2. Copying the fgmj to the local environment from the Azure container instance: validating with WISE locally works.
  3. Copying a locally produced and working/validated fgmj to the Azure container instance: validating with WISE in the container instance does not work.

Version

(Ubuntu 2020) v1.0.0-beta

What component are you seeing the problem on?

WISE Binary

Relevant log output

[info]    2023-06-05T15:40:11.349Z . Executing WISE Directly, job_20230605094010485 
[info]    2023-06-05T15:40:11.431Z . error: Command failed: /usr/bin/wise --validate /usr/src/app/WISE_data/dipjobs/job_20230605094010485/job.fgmj
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
/usr/bin/wise: line 2:   287 Aborted                 LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/wise /usr/lib/wise/wise "$@"

[info]    2023-06-05T15:40:11.431Z . stderr: terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
/usr/bin/wise: line 2:   287 Aborted                 LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/wise /usr/lib/wise/wise "$@"

[info]    2023-06-05T15:40:11.431Z . stderr: terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
/usr/bin/wise: line 2:   287 Aborted                 LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/wise /usr/lib/wise/wise "$@"

[info]    2023-06-05T15:40:11.526Z . error: Command failed: /usr/bin/wise /usr/src/app/WISE_data/dipjobs/job_20230605094010485/job.fgmj
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
/usr/bin/wise: line 2:   290 Aborted                 LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/wise /usr/lib/wise/wise "$@"

[info]    2023-06-05T15:40:11.526Z . stderr: terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
/usr/bin/wise: line 2:   290 Aborted                 LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/wise /usr/lib/wise/wise "$@"

Approvals Process

  • Testing For Issue
  • Executive Approval
  • Merge
@RobJago RobJago added the bug Something isn't working label Jun 5, 2023
@spydmobile
Copy link
Contributor

@RobBryce does this not pertain to the switches you created for running in azure?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants