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

WINDOWS - CAVE AWIPS fail to launch #285

Open
Meustache opened this issue Jan 5, 2020 · 11 comments
Open

WINDOWS - CAVE AWIPS fail to launch #285

Meustache opened this issue Jan 5, 2020 · 11 comments

Comments

@Meustache
Copy link

Meustache commented Jan 5, 2020

image
I have that error.

CAVE console output say:

"21:32:45.762 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'NcCore'
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG com.raytheon.uf.viz.spring.dm.OSGIXmlApplicationContext - Unable to locate LifecycleProcessor with name 'lifecycleProcessor': using default [org.springframework.context.support.DefaultLifecycleProcessor@17f2f0fd]
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'lifecycleProcessor'
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.core.env.PropertySourcesPropertyResolver - Searching for key 'spring.liveBeansView.mbeanDomain' in [systemProperties]
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.core.env.PropertySourcesPropertyResolver - Searching for key 'spring.liveBeansView.mbeanDomain' in [systemEnvironment]
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.core.env.PropertySourcesPropertyResolver - Could not find key 'spring.liveBeansView.mbeanDomain' in any property source. Returning [null]
Spring initialization took: 3469 ms
No component specified, defaulting to 'thinclient'"
@YoulSaden82
Copy link

image I have that error.

CAVE console output say:

"21:32:45.762 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Finished creating instance of bean 'NcCore'
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG com.raytheon.uf.viz.spring.dm.OSGIXmlApplicationContext - Unable to locate LifecycleProcessor with name 'lifecycleProcessor': using default [org.springframework.context.support.DefaultLifecycleProcessor@17f2f0fd]
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'lifecycleProcessor'
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.core.env.PropertySourcesPropertyResolver - Searching for key 'spring.liveBeansView.mbeanDomain' in [systemProperties]
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.core.env.PropertySourcesPropertyResolver - Searching for key 'spring.liveBeansView.mbeanDomain' in [systemEnvironment]
21:32:45.763 [Start Level: Equinox Container: 20d70885-fa2f-001a-1558-db5ce5f0bdfb] DEBUG org.springframework.core.env.PropertySourcesPropertyResolver - Could not find key 'spring.liveBeansView.mbeanDomain' in any property source. Returning [null]
Spring initialization took: 3469 ms
No component specified, defaulting to 'thinclient'"

I have the same problem

@srcarter3
Copy link
Contributor

What language are you using (English, Spanish, etc) on your machine, and what OS (Mac, Windows, etc) are you running?
Thanks.

@HarveyRichard2007
Copy link

I have the exact same problem. Did you guys find any solution in the end?

@srcarter3
Copy link
Contributor

@HarveyRichard2007 Couple of questions:

  • What OS are you running?
  • What language is your machine in (English, Spanish, etc)?

@HarveyRichard2007
Copy link

HarveyRichard2007 commented Aug 23, 2022 via email

@srcarter3
Copy link
Contributor

@HarveyRichard2007 That is the issue. It seems when CAVE is run on a system other than English, it can experience unresolvable errors.
The solutions are either to:

  • switch your system to English, when using CAVE
  • use our Virtual Machine option. This option allows your actual machine to stay in whichever language you use, while you can run CAVE in an environment in English. The VM option has one notable drawback at the moment -- it cannot render RGB satellite products.

Let us know if either of these options work for you?

@HarveyRichard2007
Copy link

HarveyRichard2007 commented Aug 24, 2022 via email

@srcarter3
Copy link
Contributor

Hi @HarveyRichard2007,
Can we have you try and remove caveData and then restarting Cave?
Also, I assume you're connecting to our edex (edex-cloud.unidata.ucar.edu)? Is that correct?
After attempting to load a dataset again, could you take a screenshot of how CAVE looks?
Also could you go to the CAVE menu > Open Alertview > and then either take a screenshot or copy and paste if there are any errors in there?

@HarveyRichard2007
Copy link

HarveyRichard2007 commented Aug 24, 2022 via email

@HarveyRichard2007
Copy link

HarveyRichard2007 commented Aug 25, 2022 via email

@srcarter3
Copy link
Contributor

Hi @HarveyRichard2007 ,

I don't think your screenshot came through, but that might not be super helpful from the sounds of it.

Do you think you could install the vm option and try loading the model data through that method?
I want to see if that makes any difference, and that will give us some more insight to what might be the problem.

We confirmed we are able to load both satellite and HRRR data on Windows, here, so we're fairly confident it isn't an general EDEX issue at this point, but running from the VM will give us some more information.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants