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
Cron email notifications not working in VyOS #183
Comments
Do you need any help reproducing this, or any more information about my environment? |
If you can, please try to:
|
This is the closest thing I'm able to get to a cron log with my docker install, I don't see any dedicated cron logs:
I may need to change some config |
This is the supervisor configuration for cron, I'm not entirely sure how the supervisor system works, but this suggests it's dropping cron logs?
Unless maxbytes=0 means infinite, but I'm not seeing much output in the supervisor logs for this, and I believe the supervisor logs match what podman displays when I show the container logs. I do see nginx logs, and that is also set to maxbytes=0, so I feel cron is logging nothing here? it says it is running, supervisor shows it and I'm able to see it in top. I'm not very familiar with this container environment, is there an editor I can use to create a cron file to test? I se this passbolt-ce-server script is set to run every minute, I'm thinking of making one that touches a file or spits something to the logs so I can be sure it's even running |
|
Can you confirm you're running this as www-data/nginx inside the cronjob? |
I'm not able to create or meaningfully modify the cron jobs because I don't know of an editor that exists in this container, I guess I could make one using echo or something, but I'd prefer to do this more cleanly if that is an option.
|
|
Could you also provide the permission for the files inside the |
|
I don't think this is related, and I still can't get cron to log anything, I would like to be able to just edit files in this environment without making new mounts or doing anything like that, do you know if any simple editor is included in this docker image? |
This image does not ship with an editor. But you can install one temporarily using Note that a fix is on its way to be shipped very soon, it will also include additional debug to help us understand issues relative to gpg. |
I have most internet traffic blocked to this container, it's mostly being used internally so I can't easily download packages. Should I be able to pull that image to my container environment soon? I may just wait to do that, I'm not in a particular rush to change lots of things if a fix is coming |
We have had call with a user, it was not related to SMTP settings, and the cron was not working. It was solved by commenting the module |
I'll check this now |
I've updated the file to contain the following:
|
I think that worked! |
I'd really like to know why this issue occurred, I'm not that familiar with PAM and have only messed around with it much. I'm assuming this modification is going to be applied to future images? |
We also do not know. We're trying to get to the bottom of this, we never had to touch pam before. |
Closing feel free to reopen if needed |
Crosspost from forums: https://community.passbolt.com/t/server-unable-to-send-emails-other-than-the-test-email/6126
I have the latest version of passbolt-ce running in docker. I’m able to send test emails, but no other emails seem to be going through. I’m not seeing any activity in the docker logs when the registration emails are requested, and nothing is being dropped in my firewall. I’m really not sure why it can send the test emails to any address, but it’s unable to send any of the other emails. It displays the page saying the emails were sent, and they aren’t going to spam.
Running tcpdump and looking for activity to that mail server, I can see activity instantly when I send a test email, but never see anything for the other emails.
I’m using VyOS for the container environment, is there a chance it’s not interfacing with cron correctly?
I’m seeing this in dmesg:
I’m not too familiar with this container environment, but it seems cron is running:
The text was updated successfully, but these errors were encountered: