-
Notifications
You must be signed in to change notification settings - Fork 28
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
mod_md error: error loading staged set #223
Comments
Thanks for the details. First of all, the error reported by mod_md is not preventing your Apache from running. This cannot be the cause of your Apache "shutting down accidentally". Second, the error happens when a new certificate is activated, e.g. the directory from 'staging' is moved to 'domains'. The existing from 'domains' is moved to 'archive'. Just to explain what is happening. If you can reproduce this, you can configure Since you are running under Windows, the obligatory question is: do you have a virus scanner installed? Thanks for you help. |
Hi icing! Thanks for your reply. Let me clarify. I am not trying to start or stop Apache. Apache stops accidentally and cannot run back again. Meanwhile, my mod_md.bat file starts sending me tons of emails (this but bile have a line to send email just one). It means that .bat files runs in a loop. This situation can be over only manually, but httpd process termination via Task Manager. All of these things pointing to mod_md. I can reproduce this error even when I change MDRenewWindow to 89 or something. Just to force Apache to update certificates in day or something. I don't know how to force cert renewal including MDNotifyCmd execution. I will add LogLevel md:trace2, it's not a problem. But I don't know when certs renewal procedure will be attempted. I have no any AV software active in background, but I scan this machine on demand. So, AV software cannot control (scan, move, delete, lock, etc.) any files / processes. |
The same errors appears when Apache restarts normally (no freezes, restart initiated by sysop):
Maybe I need to clean some MD files manually? Because /md/ subfolders content is a bit different. E.g. /md/staging/ folder contains only subfolder domain.dom, but not dev.domain.dom. Meanwhile, /tmp/dev.domain.dom contains only job.json file, when /tmp/domain.dom contais 4 files (2 .json and 2 .pem files). Could it be a reason of errors? |
Problem was solved! It was write permission issue for mod_md files and folders:
It was a read / list or something. I added write and full, and problem has gone. |
Hi Stefan!
Could you please help me again?
I played with Apache config files and got STARGING RE LE certificate by mistake. It is not trusted on the most of browsers and it’s a problem for me now.
How can I replace it with production (normal) one?
I tried to play with
MDRenewWindow 88d
MDRenewWindow 89d
and Apache restart, but no luck.
How can I force certs renewal?
I run Windows and using mod_md. I cannot run certbot, because there is no such file on my PC.
Can I just delete some files from md folder?
Thanks in advance!
…--
Regards,
Art
From: Stefan Eissing ***@***.***
Sent: 10 August 2020 10:27 AM
To: icing/mod_md ***@***.***>
Cc: EIKAInc ***@***.***>; Author ***@***.***>
Subject: Re: [icing/mod_md] mod_md error: error loading staged set (#223)
Thanks for the details.
First of all, the error reported by mod_md is not preventing your Apache from running. This cannot be the cause of your Apache "shutting down accidentally".
Second, the error happens when a new certificate is activated, e.g. the directory from 'staging' is moved to 'domains'. The existing from 'domains' is moved to 'archive'. Just to explain what is happening.
If you can reproduce this, you can configure LogLevel md:trace2 to get more information in your error log where we can see what exactly is going wrong.
Since you are running under Windows, the obligatory question is: do you have a virus scanner installed?
Thanks for you help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#223 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIAEJZQNKN7AITNQK5N4LPTR76ON7ANCNFSM4PYQM35Q> . <https://github.com/notifications/beacon/AIAEJZTJTILZ6MGCA4WH5HTR76ON7A5CNFSM4PYQM352YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFAA4DPI.gif>
|
Yes, if you delete the files in |
Thanks a lot, it helped!
…--
Regards,
Art
From: Stefan Eissing ***@***.***
Sent: 06 April 2021 20:44 PM
To: icing/mod_md ***@***.***>
Cc: EIKAInc ***@***.***>; State change ***@***.***>
Subject: Re: [icing/mod_md] mod_md error: error loading staged set (#223)
Yes, if you delete the files in md/domains/<yourdomain> and reload the server, the module will renew immediately.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub <#223 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIAEJZSEWBPCUBMN3ET2RFDTHNB7LANCNFSM4PYQM35Q> . <https://github.com/notifications/beacon/AIAEJZTWVAFDUYMIGQJB5XDTHNB7LA5CNFSM4PYQM352YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGCEV6MI.gif>
|
I'm going to leave a comment here mostly for myself because I've hit this error message a couple of times before and this page comes up first in a search. I tried a couple of things to get it "unstuck." (Including deleting |
Dear author and community! Thanks for all your work. I really appreciate it! But sadly I come across with new issue. From time to time Apache shut down accidentally. And I can't run it again.
In error_log I see:
The problem is definitely caused by mod_md, and related error_log record is:
AH10069: domain.dom: error loading staged set
I Googled for it, and found only mod_md source code:
I am not sure that it does matter, but I have HTTP2 disabled (all lines are commended out):
And my SSL config is:
Any ideas what can cause this issue? I am not programmer and can't understand all the logic. But I want to solve this issue.
Please advise!
The text was updated successfully, but these errors were encountered: