Auto FetchMail Mail Account Management

[jnelson]

I'm setting up a brand new OTRS 5 on CentOS 7 and I'm getting this error from the mail configuration (it works just fine if run manually from the UI)

Code: Select all

OTRS-otrs.Console.pl-Maint::PostMaster::MailAccountFetch-93	There was an error executing Execute() in Kernel::System::Console::Command::Maint::PostMaster::MailAccountFetch: Error: Unable to register the process in the database. Is another instance still running?

[jnelson]

Sorry crythias!

[jnelson]

More info. Please let me know if there's any other data to help figure this error out that I can provide. I'm stumped

Server version: 5.6.28 MySQL Community Server (GPL)
CentOS Linux release 7.2.1511 (Core)
OTRS 5.0.4

The setting at Daemon::SchedulerCronTaskManager::Task###MailAccountFetch is at it's default


Checkmodules output:
o Apache::DBI......................ok (v1.12)
o Apache2::Reload..................ok (v0.13)
o Archive::Tar.....................ok (v1.92)
o Archive::Zip.....................ok (v1.30)
o Crypt::Eksblowfish::Bcrypt.......Not installed! Use: 'yum install "perl(Crypt::Eksblowfish::Bcrypt)"' (optional - For strong password hashing.)
o Crypt::SSLeay....................ok (v0.64)
o Date::Format.....................ok (v2.24)
o DBI..............................ok (v1.627)
o DBD::mysql.......................ok (v4.023)
o DBD::ODBC........................Not installed! (optional - Required to connect to a MS-SQL database.)
o DBD::Oracle......................Not installed! (optional - Required to connect to a Oracle database.)
o DBD::Pg..........................Not installed! Use: 'yum install "perl(DBD::Pg)"' (optional - Required to connect to a PostgreSQL database.)
o Encode::HanExtra.................Not installed! Use: 'yum install "perl(Encode::HanExtra)"' (optional - Required to handle mails with several Chinese character sets.)
o IO::Socket::SSL..................ok (v1.94)
o JSON::XS.........................ok (v3.01)
o List::Util::XS...................ok (v1.27)
o LWP::UserAgent...................ok (v6.13)
o Mail::IMAPClient.................ok (v3.37)
o IO::Socket::SSL................ok (v1.94)
o ModPerl::Util....................ok (v2.000009)
o Net::DNS.........................ok (v0.72)
o Net::LDAP........................ok (v0.56)
o Template.........................ok (v2.24)
o Template::Stash::XS..............ok (undef)
o Text::CSV_XS.....................ok (v1.00)
o Time::HiRes......................ok (v1.9725)
o Time::Piece......................ok (v1.20_01)
o XML::LibXML......................ok (v2.0018)
o XML::LibXSLT.....................ok (v1.80)
o XML::Parser......................ok (v2.41)
o YAML::XS.........................ok (v0.54)

[crythias]

The error log indicates that it thinks the process is still running, though, which means either it truly is and it's trying to download a lot of email, or large email, or it's in a state where the process ID/PID is still in the database and because such exists, it won't try to start again.

I believe that the process can be forced through the new console function.
There is another (German) post asking about the same thing: viewtopic.php?t=30898

[jnelson]

I added the --force-pid argument to the module in the cron task

Daemon::SchedulerCronTaskManager::Task###MailAccountFetch

Kernel::System::Console::Command::Maint::PostMaster::MailAccountFetch --force-pid

Seems to be working so far.