Error In /var/adm/messages - IMTA-W-BADCONFIG, Attempt To Map New Configuration Failed
(Doc ID 2174013.1)
Last updated on NOVEMBER 22, 2017
Applies to:Oracle Communications Messaging Server - Version 8.0.1 and later
Information in this document applies to any platform.
Using: Oracle Communications Messaging Server 18.104.22.168.0 64bit (built Jun 15 2016)
libimta.so 22.214.171.124.0 64bit (built 21:00:45, Jun 15 2016)
Using /opt/sun/comms/messaging64/config/config.xml (not compiled)
When deploying new systems using Messaging Server 126.96.36.199 and Unified Config, the first time it starts, we see the following errors in the /var/adm/messages file:
Aug 17 13:15:01 server1 dispatcher: [ID 977949 user.error] %IMTA-W-BADCONFIG, Attempt to map new configuration failed.
Aug 17 13:15:01 server1 tcp_smtp_server: [ID 977949 user.error] %IMTA-W-BADCONFIG, Attempt to map new configuration failed.
We have seen this error on nearly (maybe every) system we have deployed.
After restarting the MTA, it never happens again.
We are running "not compiled", so it is not like there could be a compiled config file being changed. We have also ruled out a sequence-of-events problem.
It never happens again after restart -- unless everything is wiped out and a completely new install is performed.
Brand new installation is performed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document