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

Unable to start WRF4G #90

Open
donglx2018 opened this issue Dec 28, 2023 · 2 comments
Open

Unable to start WRF4G #90

donglx2018 opened this issue Dec 28, 2023 · 2 comments

Comments

@donglx2018
Copy link

donglx2018 commented Dec 28, 2023

I successfully installed WRF4G using 'pip3 install wrf4g', but when I entered the command 'wrf4g start' in the terminal, it prompted an error message: 'Error! Lock file ~/.drm4g/var/.lock exists.' May I know what could be the reason for this?

@fernanqv
Copy link
Contributor

fernanqv commented Dec 29, 2023

Hello:

Every time you start WRF4G, it automatically initiates DRM4G (a tool responsible for process management). If you attempt to start WRF4G and DRM4G has not been properly stopped, WRF4G will not initiate.

In this situation, you first have to check that the DRM4G process has been stopped (ps -ef| grep drm4g). If it has, you can manually delete ~/.drm4g/var/.lock and then run WRF4G start again.

Kind regards
Valva

@cofinoa
Copy link
Member

cofinoa commented Dec 30, 2023

@fernanqv, DRM4G has a mechanism to check if LOCK file it's valid, and if not, it removes it:
https://github.com/cofinoa/DRM4G/blob/ff72e7c544795a050027088caa64883200227c8c/drm4g/commands/__init__.py#L246-L247

Which version of DRM4G is using WRF4G? Or is using its own LOCK file check?

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

3 participants