hrue / r-inla

This is the public repository for the r-inla project
GNU General Public License v2.0
81 stars 23 forks source link

Issues with running R-INLA on Redhat linux 8 Server #94

Open WateryDave opened 5 months ago

WateryDave commented 5 months ago

The servers that we were running an R script for INLA on were recently updated to Redhat Enterprise Linux 8, and now were having issues running the INLA package. We are able to run all the functions for running a model but when we run the inla function in R we get the following error.

results4 <- inla(formula4,

  • family = 'binomial',
  • control.family = list(link = 'logit'),
  • data = inla.stack.data(stack),
  • control.predictor = list(
  • A = inla.stack.A(stack),
  • compute = T, link = 1 # compute = T enables the fitted.values calculation, link = 1
  • ),
  • control.inla = list(int.strategy = 'eb'),
  • verbose = T,
  • control.compute = list(dic = T,cpo = T)) crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE

*** inla.core.safe: The inla program failed, but will rerun in case better initial values may help. try=1/1 crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE Error in inla.core.safe(formula = formula, family = family, contrasts = contrasts, : The inla-program exited with an error. Unless you interupted it yourself, please rerun with verbose=TRUE and check the output carefully. If this does not help, please contact the developers at help@r-inla.org. The inla program failed and the maximum number of tries has been reached. Calls: inla -> inla.core.safe Execution halted

I am not sure if the issues stem from on of the other steps that we took when installing the INLA package. We installed INLA. library (INLA) inla.binary.install()

After that in the server we deleted some of the Lib files in 64bit since they were conflicts.

Any help would be appreciated.

hrue commented 5 months ago

inla.binary.install()

chose Rocky8

let me know if that does not work

On Thu, 2024-04-04 at 14:39 -0700, WateryDave wrote:

The servers that we were running an R script for INLA on were recently updated to Redhat Enterprise Linux 8, and now were having issues running the INLA package. We are able to run all the functions for running a model but when we run the inla function in R we get the following error.

results4 <- inla(formula4,                   family = 'binomial',                   control.family = list(link = 'logit'),                   data = inla.stack.data(stack),                   control.predictor = list(                     A = inla.stack.A(stack),                     compute = T, link = 1 # compute = T enables the fitted.values calculation, link = 1                   ),                   control.inla = list(int.strategy = 'eb'),                   verbose = T,                   control.compute = list(dic = T,cpo = T)) crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE inla.core.safe: The inla program failed, but will rerun in case better initial values may help. try=1/1 crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE Error in inla.core.safe(formula = formula, family = family, contrasts = contrasts, : The inla-program exited with an error. Unless you interupted it yourself, please rerun with verbose=TRUE and check the output carefully. If this does not help, please contact the developers at @. The inla program failed and the maximum number of tries has been reached. Calls: inla -> inla.core.safe Execution halted I am not sure if the issues stem from on of the other steps that we took when installing the INLA package. We installed INLA. library (INLA) inla.binary.install() After that in the server we deleted some of the Lib files in 64bit since they were conflicts. Any help would be appreciated. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Håvard Rue Professor of Statistics Chair of the Statistics Program CEMSE Division King Abdullah University of Science and Technology Thuwal 23955-6900 Kingdom of Saudi Arabia

@.*** Office: +966 (0)12 808 0640   Mobile: +966 (0)54 470 0421 Research group: bayescomp.kaust.edu.sa   R-INLA project: www.r-inla.org Zoom: kaust.zoom.us/my/haavard.rue

--

This message and its contents, including attachments are intended solely for the original recipient. If you are not the intended recipient or have received this message in error, please notify me immediately and delete this message from your computer system. Any unauthorized use or distribution is prohibited. Please consider the environment before printing this email.

hrue commented 5 months ago

you can just retry as each new 'binary.install()' will overwrite that whole directory

On Fri, 2024-04-05 at 00:45 +0300, Haavard Rue wrote:

I am not sure if the issues stem from on of the other steps that we took when installing the INLA package.  We installed INLA. library (INLA) inla.binary.install() After that in the server we deleted some of the Lib files in 64bit since they were conflicts.

-- Håvard Rue Professor of Statistics Chair of the Statistics Program CEMSE Division King Abdullah University of Science and Technology Thuwal 23955-6900 Kingdom of Saudi Arabia

@.*** Office: +966 (0)12 808 0640   Mobile: +966 (0)54 470 0421 Research group: bayescomp.kaust.edu.sa   R-INLA project: www.r-inla.org Zoom: kaust.zoom.us/my/haavard.rue

--

This message and its contents, including attachments are intended solely for the original recipient. If you are not the intended recipient or have received this message in error, please notify me immediately and delete this message from your computer system. Any unauthorized use or distribution is prohibited. Please consider the environment before printing this email.

WateryDave commented 5 months ago

Thanks I will give that a try.