Hi there,
About a year ago we migrated from OTRS 4.x to OTRS 5. Since that time the system has been working ok, but I have been receiving a lot of error messages on System Log. Specifically, the errors are:
- There was an error executing Execute() in Kernel::System::Console::Command::Maint::Ticket::EscalationCheck
- There was an error executing Execute() in Kernel::System::Console::Command::Maint::PostMaster::MailAccountFetch
- There was an error executing Execute() in Kernel::System::Console::Command::Maint::Ticket::PendingCheck
I have already manually executed these procedures using the otrs.Console.pl and every single procedure run just fine. I have tried to disable the EscalationCheck daemon (since we are not using this feature) but nothing changed.
I may add that "ticket pending" and "mail account fetch" features are working as they should.
Any clues on why I keep receiving these error messages?
Regards,
Daniel Caetano
System Log Errors
Moderator: crythias
Re: System Log Errors
Hi,
is it the right user doing it?
is your $HOME correct?
Florian
is it the right user doing it?
is your $HOME correct?
Florian
OTRS 8 SILVER (Prod)
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
-
- Znuny newbie
- Posts: 17
- Joined: 31 May 2016, 16:19
- Znuny Version: 5.0.19
- Real Name: Daniel Caetano
- Company: Universidade de São Paulo
Re: System Log Errors
How can I check the user used to run those daemons?wurzel wrote:Hi,
is it the right user doing it?
is your $HOME correct?
Anyway, the home for OTRS user is set to /opt/otrs .
-
- Znuny newbie
- Posts: 17
- Joined: 31 May 2016, 16:19
- Znuny Version: 5.0.19
- Real Name: Daniel Caetano
- Company: Universidade de São Paulo
Re: System Log Errors
In the case you are talking about the cron user, it is on "otrs" user's crontab:
# check OTRS daemon status
*/5 * * * * $HOME/bin/otrs.Daemon.pl start >> /dev/null
# check OTRS daemon status
*/5 * * * * $HOME/bin/otrs.Daemon.pl start >> /dev/null
-
- Administrator
- Posts: 3955
- Joined: 18 Dec 2007, 12:23
- Znuny Version: Znuny and Znuny LTS
- Real Name: Roy Kaldung
- Company: Znuny
- Contact:
Re: System Log Errors
Hi,
Die you configured var/cron/aaa_base and set an appropriate e-mail address where output is send?
Check which crontab contains the jobs withdjcaetano wrote: How can I check the user used to run those daemons?
This show you the otrs user's crontab.crontab -l otrs
Looks good.djcaetano wrote: Anyway, the home for OTRS user is set to /opt/otrs .
Die you configured var/cron/aaa_base and set an appropriate e-mail address where output is send?
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?
-
- Znuny newbie
- Posts: 17
- Joined: 31 May 2016, 16:19
- Znuny Version: 5.0.19
- Real Name: Daniel Caetano
- Company: Universidade de São Paulo
Re: System Log Errors
It was configured to send mails to root@localhost. I configured it to send them to my e-mail, and now I am receiving messages about the errors, but no extra information to help me identify the real problem.root wrote: Looks good.
Die you configured var/cron/aaa_base and set an appropriate e-mail address where output is send?
-
- Administrator
- Posts: 3955
- Joined: 18 Dec 2007, 12:23
- Znuny Version: Znuny and Znuny LTS
- Real Name: Roy Kaldung
- Company: Znuny
- Contact:
Re: System Log Errors
Hi,
Did you checked the OTRS log on the time the error is generated? Maybe there are some hints. I recommend to configure the highest available log level (pls keep an eye on your disk space)
- Roy
Did you checked the OTRS log on the time the error is generated? Maybe there are some hints. I recommend to configure the highest available log level (pls keep an eye on your disk space)
- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?
-
- Znuny newbie
- Posts: 17
- Joined: 31 May 2016, 16:19
- Znuny Version: 5.0.19
- Real Name: Daniel Caetano
- Company: Universidade de São Paulo
Re: System Log Errors
Hi there,
After a long winter I had time to dig out the reason behind this problem.
It seems that the Daemon worker is not acting as it was supposed to regarding error logging.
There are NO errors at all on those cases, but de Daemon worker was acting as if "Debug" messages were errors (that is: the debug message showed as "priority: error" on System Event log).
I have totally disabled debug function using Config.pm (for some strange reason, it was enabled) and restarted the daemon... and after these two steps, there are no more fake errors being reported on my System Event log (nor email).
After a long winter I had time to dig out the reason behind this problem.
It seems that the Daemon worker is not acting as it was supposed to regarding error logging.
There are NO errors at all on those cases, but de Daemon worker was acting as if "Debug" messages were errors (that is: the debug message showed as "priority: error" on System Event log).
I have totally disabled debug function using Config.pm (for some strange reason, it was enabled) and restarted the daemon... and after these two steps, there are no more fake errors being reported on my System Event log (nor email).