SOLVED [CPANEL-23903] tailwatchd warnings logged when enabling more than one alternate Exim port

kernow

Well-Known Member
Jul 23, 2004
970
35
178
cPanel Access Level
Root Administrator
Been getting these error messages for a while now despite a couple of cPanel updates which I thought might fix it. Their no problem, more of an annoyance:
/usr/local/cpanel/logs/error_log:
[2018-11-12 07:03:11 +0000] warn [tailwatchd] [exim-ports] doesn't look like a service name at /usr/local/cpanel/Cpanel/Services/Installed.pm line 221.
Cpanel::Services::Installed::service_is_installed("exim-ports") called at /usr/local/cpanel/Cpanel/Services/Enabled.pm line 240
Cpanel::Services::Enabled::is_enabled("exim-ports") called at /usr/local/cpanel/Cpanel/TailWatch/ChkServd.pm line 618
Cpanel::TailWatch::ChkServd::_load_config(Cpanel::TailWatch::ChkServd=HASH(0x2540ad8)) called at /usr/local/cpanel/Cpanel/TailWatch/ChkServd.pm line 265
Cpanel::TailWatch::ChkServd::_run_checks(Cpanel::TailWatch::ChkServd=HASH(0x2540ad8), Cpanel::TailWatch=HASH(0x1812480), 1542006191) called at /usr/local/cpanel/Cpanel/TailWatch/ChkServd.pm line 208
Cpanel::TailWatch::ChkServd::run(Cpanel::TailWatch::ChkServd=HASH(0x2540ad8), Cpanel::TailWatch=HASH(0x1812480), 1542006191) called at /usr/local/cpanel/Cpanel/TailWatch.pm line 748
Cpanel::TailWatch::tail_logs(Cpanel::TailWatch=HASH(0x1812480)) called at /usr/local/cpanel/Cpanel/TailWatch.pm line 648
eval {...} called at /usr/local/cpanel/Cpanel/TailWatch.pm line 616
Cpanel::TailWatch::run(Cpanel::TailWatch=HASH(0x1812480)) called at libexec/tailwatch/tailwatchd.pl line 58
main::run("--start") called at libexec/tailwatch/tailwatchd.pl line 35
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,911
2,234
363
[tailwatchd] [exim-ports] doesn't look like a service name
Hello @kernow,

Do you have a custom service configured for exim-ports in the /etc/chkserv.d/ directory? If so, can you post the contents of that file?

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,911
2,234
363
Hello @kernow,

Can you open a support ticket so we can take a closer look? You can post the ticket number here and we'll update this thread with the outcome.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,911
2,234
363
Oh I see what you you mean now, we edited the error message " [exim-ports]" to remove the ports listed as we have opened more ports than the default.
Can you let me know the specific files you modified, and the specific changes you made?

Thanks!
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,911
2,234
363
Hello @kernow,

I've confirmed that enabling Exim Mail Server (on another port) with more than one alternate port via WHM >> Service Manager results in output like this from tailwatchd in /usr/local/cpanel/logs/error_log on version 76:

Code:
[2018-11-12 14:43:11 -0600] warn [tailwatchd] [exim-26,99] doesn't look like a service name at /usr/local/cpanel/Cpanel/Services/Installed.pm line 221.
This is now reported under internal case CPANEL-23903. I'll monitor this case and update this thread with more information as it becomes available.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,911
2,234
363
Hello,

This is fixed in cPanel & WHM version 76.0.11:

Fixed case CPANEL-23903: Add backwards compatibility for exim-altport service names in chkservd.

You can learn more about our release tiers by clicking here and see which build is published to each release tier by clicking here.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,911
2,234
363
email from server says "The service “exim-xx,xx,xxx” appears to be down."
Hello @kernow,

Can you verify if any particular entries appear in /usr/local/cpanel/logs/error_log when this happens?

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,911
2,234
363
We couldn't find anything relevant in the log, we got an email from cPanel monitoring a few minutes later saying it had successfully restarted. That was several hours ago so perhaps its fixed.
This is unrelated to the issue originally reported on this thread, as in that case the error message persisted. Let us know if you encounter any additional problems with Chkservd, or if the failures persist.

Thank you.