Date: 2011/02
Affected NV Version:
OS Version: All
Plugin version: Report Plugin
Application version: N/A
Symptoms: “Failed to run reporting job. Failed when running job to produce output. Please see job log.�
Description: This error can occur when there is a resource or time out issue. In these situation, the following error messages appear in the binary log :
Error 2011/02/25 13:22:57 20138 Jobs FEKI1 Job manager lost message channel unexpectedly
Error 2011/02/25 13:22:57 20138 Jobs FEKI1 Fatal error: Report Lost Message Channel Unexpectedly
Error 2011/02/25 13:22:57 20138 Jobs FEKI1 Job Status: Report Failed
Job manager trace will show the same error:
Job manager lost message channel unexpectedly
The report plugin will not show much, but there should be a dump file generated. The dump itself does not hold useful information apart from the fact that a dump was created.
First, check what kind of report is this (i.e. Media report, job report etc.). Also check if other report are running fine and if this report ran successfully in the past.
We have noticed in one case that the error was occurring when running a report showing the last day's jobs which have completed with warning. In this case the fault was due to a lack of resource in processing a huge number of logs - kept for 120 days. In this type of report the plugin goes through the logs to pull jobs completed with warning. The larger the size of the logs directory the longer it can take - the more likely it can time out.
This error can occur when there is a resource or time out issue. In these situation, the following error messages appear in the binary log :
Error 2011/02/25 13:22:57 20138 Jobs FEKI1 Job manager lost message channel unexpectedly
Error 2011/02/25 13:22:57 20138 Jobs FEKI1 Fatal error: Report Lost Message Channel Unexpectedly
Error 2011/02/25 13:22:57 20138 Jobs FEKI1 Job Status: Report Failed
Job manager trace will show the same error:
Job manager lost message channel unexpectedly
The report plugin will not show much, but there should be a dump file generated. The dump itself does not hold useful information apart from the fact that a dump was created.
First, check what kind of report is this (i.e. Media report, job report etc.). Also check if other report are running fine and if this report ran successfully in the past.
We have noticed in one case that the error was occurring when running a report showing the last day's jobs which have completed with warning. In this case the fault was due to a lack of resource in processing a huge number of logs - kept for 120 days. In this type of report the plugin goes through the logs to pull jobs completed with warning. The larger the size of the logs directory the longer it can take - the more likely it can time out.
1. Open Netvault Configurator
2. Go to Loggin daemon
3. Decrease the " Auto-purge entries that are older than (days)" to something less than 120 days. 30 days is usually sufficient. If the Netvault Database is backed up. The logs are also backed up with it.
4. You can go to the Logs Module and use the Options pull down menu to purge log entries older than the desired date or,
5. You can manually purge the logs via command line. Open a command line and cd to netvault/util.
Purge the old logs with the following command:
nvlogpurge -purgetime "YYYYMMDDHHMMSS"
6. Stop and Restart the netvault service
7. Try running the report again.
If errors persist, it may be due to a corrupt plugin in which case the following Knowledge Base Article is useful : How to Readd Canned Reports and Reinstall Report Producing APM
BakBone SFDC Solution Number: 00006137
