Your message dated Tue, 27 Jun 2006 22:49:00 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ERROR: relation "generic_agent_jobs" does not exist
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: otrs
Severity: normal
I recently upgraded my system and a new OTRS was installed along with
all the other updates. I now have 1.3.2p01-5; I'm not sure what I had
before but it was installed late last summer.
Although OTRS seems to function normally, its cron job suffers this
error every ten minutes:
DBD::Pg::st execute failed: ERROR: relation "generic_agent_jobs" does
not existERROR: OTRS-GenericAgent-10 Perl: 5.8.4 OS: linux Time: Fri Jul
1 23:10:21 2005
Message: ERROR: relation "generic_agent_jobs" does not exist
, SQL: 'SELECT job_name FROM generic_agent_jobs'
Traceback (6180):
Module: Kernel::System::GenericAgent::JobList (v1.7 ) Line: 602
Module: /usr/share/otrs/bin/GenericAgent.pl (v1.33) Line: 120
DBD::Pg::st fetchrow_array failed: no statement executing
This gets emailed to "otrs", and I only noticed it because the mail
spool had grown to 250k! Until I saw that I didn't even know that OTRS
had been upgraded.
I now see that there are some instructions in
/usr/share/doc/otrs/UPGRADE, and presumably running the "database
update" script in there will fix it. But it would have been really good
if this had happened automatically when it upgraded, or if it had told
me that I needed to do it manually.
Trying to follow those instructions, I fail at point one. I don't think
I have "rcotrs". Any suggestions?
Cheers, --Phil.
--- End Message ---
--- Begin Message ---
Hi,
I have to close this bug report, since OTRS 1.2 has never been
available in stable and the error message in the report cannot be
explained if the SQL commands have really been executed as the
postgres admin.
Regards,
Torsten
--
http://www.twerner42.de/
--- End Message ---
