When a user creates/starts a Review, an email notification isn't being sent to the reviewers. I confirmed that the users Review Settings are configured to send the Notifications Immediately. I noticed that there aren't any entries in either the Fisheye Error log or Fisheye Mail log... so it appears the Notification isn't getting triggered at all (???).
Any help with this would be greatly appreciated... thanks!
I have the similar issue.
The Test Email sends fine, but notification emails are not being sent. I enabled debugging but other than see the mail system restarted and a line about setDebug: JavaMail, I don't see anything in the logs. I do see lots of output when I send the test email, which is successful.
I run the query, the status column contain only 0 , which mean "Do not send notification".
I have verified the repository, user setting, the user should receive the email notification when there is review comment, etc.
I'm seeing similar issues. The Test Email sends fine, but notification emails are not being sent. I enabled debugging but other than see the mail system restarted and a line about setDebug: JavaMail, I don't see anything in the logs. I do see lots of output when I send the test email, which is successful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
I too have cru_recipient/cru_notification tables full of data , and no crucible review emails being sent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guac,
Please ensure the "Send Test Email" test completes successfully from:
http://<FISHEYE_BASE_URL>/admin/sendTestEmail-default.do
Having ensured that, test whether the commit notifications are working as expected:
https://confluence.atlassian.com/display/FISHEYE/Watches
If none of the above helps, you may enable debug logging for SMTP configuration via:
http://<FISHEYE_BASE_URL>/admin/editSmtpConfig-default.do
by setting "Enable debug" to "YES".
Then replicate the issue and check for any related errors in the {{<FISHEYE_INST>/var/log}} folder.
In some cases, this can even be due to a mis-configured NTP server where the servers are out of sync for some reason. If you use a NTP server, please ensure the system clocks are synced across all configured servers.
If the issue persists, I'd suggest lodging a support request with Atlassian at https://support.atlassan.com with the above troubleshooting information included for further investigation.
Thanks,
Gurleen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Apparently there's a message queue in Crucible -- cru_recipient/cru_notification tables in database, but since database schema is completely undocumented, it's hard to say what to look for in there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It sounds like it could be similar to this issue I had: Crucible Not Sending Email Notificaitons. Unfortunately, the way we finally solved it was to port the install from a Windows Server running MS SQL 2008 to a Linux Server running MySQL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make sure the user's email clien isn't filtering incoming mail from Crucible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.