Book Image

Redmine Cookbook

By : Pavic
Book Image

Redmine Cookbook

By: Pavic

Overview of this book

In a variety of online project management tools, Redmine markets itself as offering flexibility. Choosing the right management tool can mean the difference between the success and failure of a project. Flexible project management tools bend themselves to fit your needs, whether that’s communication regarding a simple project, or collaboration, or more complex project methodology such as SCRUM, or an issue-code relationship, or the need of different methodology for your project. Whether you are project manager or system administrator, this book provides valuable recipes to get the best possible performance out of your team, organization, infrastructure, and Redmine itself. Through a series of carefully crafted recipes covering the nitty-gritty of Redmine, you’ll be guided through the installation of Redmine, as well as how to fine-tune and customize your Redmine installation. Finally, we walk you through integrating Redmine with other softwares and databases like Tortoise SVN and Visual Studio and troubleshooting Redmine.
Table of Contents (12 chapters)
11
Index

Incoming e-mail parsing issues


Redmine can accept e-mails sent to it through a rake task (client pull) or through a web service (server push). Troubleshooting, in this case, can apply to configuration problems and runtime problems.

How to do it…

To troubleshoot configuration problems, first make sure that your configuration works by testing it manually from the console prior to configuring cron job or scheduled tasks. Scheduled tasks and cron jobs need to execute proper environment (production) and perform as expected.

An example problem would be, as follows:

rake redmine:email:receive_imap RAILS_ENV="production" host=demo.redminegit.com username=redmine.demo password=redmine
rake aborted!
Net::IMAP::NoResponseError:  Authentication failed.

It is clear from the console that our credentials are not good.

Tip

In order to view potential errors with cron jobs, you can always log them in /var, or somewhere else, instead of pointing output to /dev/null.

The second part of potential trouble is a case when...