I’m trying to debug why dashboard mail isn’t going out.
I had some errors in rt.log related to graphviz until I found the
undocumented disableGraphViz set command and used it. But now there
is no error … just nothing. No attempt to send mail. Funny enough
– if I delete a dashboard I do get e-mail saying that the dashboard
is no longer there. But never the dashboard mail.
Is there any way to get a dashboard e-mail done NOW instead of on a
given hour? Every attempt forces me to back off and wait another
hour to see what’s going wrong. I’d love to say “run my dashboard
RIGHT NOW” so I could use ktrace on it to determine what is failing.
Please clue me in.
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
I’m trying to debug why dashboard mail isn’t going out.
I had some errors in rt.log related to graphviz until I found the
undocumented disableGraphViz set command and used it. But now there
is no error … just nothing. No attempt to send mail. Funny enough
– if I delete a dashboard I do get e-mail saying that the dashboard
is no longer there. But never the dashboard mail.
Is there any way to get a dashboard e-mail done NOW instead of on a
given hour? Every attempt forces me to back off and wait another
hour to see what’s going wrong. I’d love to say “run my dashboard
RIGHT NOW” so I could use ktrace on it to determine what is failing.
Please clue me in.
rt-email-dashboards has an --all option to ignore subscription date/time
constraints. Invoke it with --help to get more information. The --debug
and --verbose options will be helpful for you.
This isn’t the first time I’ve heard of this failure mode so I’d be
happy to work with you to track it down. I wasn’t able to reproduce it
myself.
Shawn
I’m trying to debug why dashboard mail isn’t going out.
I had some errors in rt.log related to graphviz until I found the
undocumented disableGraphViz set command and used it. But now there
is no error … just nothing. No attempt to send mail. Funny enough
– if I delete a dashboard I do get e-mail saying that the
dashboard
is no longer there. But never the dashboard mail.
rt-email-dashboards has an --all option to ignore subscription date/
time
constraints. Invoke it with --help to get more information. The –
debug
and --verbose options will be helpful for you.
This isn’t the first time I’ve heard of this failure mode so I’d be
happy to work with you to track it down. I wasn’t able to reproduce it
myself.
doh! Sorry, I misread the --all syntax in help to mean something
different. Anyway, I did figure it out:
[Wed Feb 25 06:00:03 2009] [error]: Caught exception: mkdir /var/run/
rt38/mason_data/obj/3583890391: Permission denied at /usr/local/lib/
perl5/site_perl/5.8.8/HTML/Mason/Compiler/ToObject.pm line 107 (/usr/
local/sbin/rt-email-dashboards:119)
The problem was that the user I was running the dashboard under has no
ability to write to this directory. The directory is created as
www:www 640.
I know you guys just LOVE to run things as root, but I really prefer
to run with the most limited rights. And I hate running these
scripts as the web server too, but that’s all that seems to work given
the rights structure. When I have time I’ll be proposing some
alternatives to limit the necessary rights for RT 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
I’m trying to debug why dashboard mail isn’t going out.
I had some errors in rt.log related to graphviz until I found the
undocumented disableGraphViz set command and used it. But now there
is no error … just nothing. No attempt to send mail. Funny enough
– if I delete a dashboard I do get e-mail saying that the
dashboard
is no longer there. But never the dashboard mail.
rt-email-dashboards has an --all option to ignore subscription date/
time
constraints. Invoke it with --help to get more information. The –
debug
and --verbose options will be helpful for you.
This isn’t the first time I’ve heard of this failure mode so I’d be
happy to work with you to track it down. I wasn’t able to reproduce it
myself.
doh! Sorry, I misread the --all syntax in help to mean something
different. Anyway, I did figure it out:
[Wed Feb 25 06:00:03 2009] [error]: Caught exception: mkdir /var/run/
rt38/mason_data/obj/3583890391: Permission denied at /usr/local/lib/
perl5/site_perl/5.8.8/HTML/Mason/Compiler/ToObject.pm line 107 (/usr/
local/sbin/rt-email-dashboards:119)
The problem was that the user I was running the dashboard under has no
ability to write to this directory. The directory is created as
www:www 640.
I know you guys just LOVE to run things as root, but I really prefer
to run with the most limited rights. And I hate running these
scripts as the web server too, but that’s all that seems to work given
the rights structure. When I have time I’ll be proposing some
alternatives to limit the necessary rights for RT
dashboards mailer shouldn’t use object files at all, it can be fixed.
http://rt3.fsck.com/Ticket/Display.html?id=13233
–
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Best regards, Ruslan.
I’m trying to debug why dashboard mail isn’t going out.
I had some errors in rt.log related to graphviz until I found the
undocumented disableGraphViz set command and used it. But now there
is no error … just nothing. No attempt to send mail. Funny enough
– if I delete a dashboard I do get e-mail saying that the
dashboard
is no longer there. But never the dashboard mail.
rt-email-dashboards has an --all option to ignore subscription date/
time
constraints. Invoke it with --help to get more information. The –
debug
and --verbose options will be helpful for you.
This isn’t the first time I’ve heard of this failure mode so I’d be
happy to work with you to track it down. I wasn’t able to reproduce it
myself.
doh! Sorry, I misread the --all syntax in help to mean something
different. Anyway, I did figure it out:
[Wed Feb 25 06:00:03 2009] [error]: Caught exception: mkdir /var/run/
rt38/mason_data/obj/3583890391: Permission denied at /usr/local/lib/
perl5/site_perl/5.8.8/HTML/Mason/Compiler/ToObject.pm line 107 (/usr/
local/sbin/rt-email-dashboards:119)
The problem was that the user I was running the dashboard under has no
ability to write to this directory. The directory is created as
www:www 640.
I know you guys just LOVE to run things as root, but I really prefer
to run with the most limited rights. And I hate running these
scripts as the web server too, but that’s all that seems to work given
the rights structure. When I have time I’ll be proposing some
alternatives to limit the necessary rights for RT
Just for your information, the email-dashboard script needs access to
run Mason components to be able to generate the dashboards. The script
renders the “show dashboard” page and emails that to users.
The “show dashboard” page, originally “preview dashboard”, was actually
created only to render a dashboard for email, but then we realized that
it was pretty handy on its own.
Shawn
Just for your information, the email-dashboard script needs access to
run Mason components to be able to generate the dashboards. The script
renders the “show dashboard” page and emails that to users.
The “show dashboard” page, originally “preview dashboard”, was
actually
created only to render a dashboard for email, but then we realized
that
it was pretty handy on its own.
FWIW, it’s still not working and now there’s no log entry again 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
FWIW, it’s still not working and now there’s no log entry again
Gah. It’s running as root, but I hate that.
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness