Does anybody know how to change listen address and TCP port for ENS. SUN docs tell to use configutil and set following parameters as below:
local.store.notifyplugin.enshost = 10.132.18.253
local.store.notifyplugin.ensport = 5500
It does not work although log messages indicate that parameters are read and recognized by iBiff.
Enpd process still listens on localhost and default port 7997.
Thanks
Mark
There was certainly work during the long run of 5.2. Was it 5.2, 5.dp1, 5.2p2, or some other hotfix?
Please understand, 5.2 is on the road to End Of Support Life. It's already been removed from the download site.
6.2 is current, and 6.3 is in beta, now.
Now, for your answer . . .
5.2 ENS didn't work well, initially.You may have indeed run across one of the many early bugs. That's why I ask for version, which you only partially answered.
Please do, as I suggest at the top of the forum, and run
imsimta version
and post the results. Perhaps I can help you, then.
Well, you are actually running the original bits.
I strongly recommend that you:
1. visit the Sun download site, and get 5.2p2. That's the most recent publically available version. If you have a support contract, you should contact Support for 5.2hf2.14
2. Begin the process of examinig your upgrade to 6.2 or 6.3.
I would do this before attempting to use ENS.
Hello Jay,
We are in the process of contacting SUN Support for the new hf as you suggested. Have few Qns about this hot fix:
1. Is 5.2hf2.14 available as a full install or can we have just the hf2.14 as a patch?
2. Is the ENS issue we are talking about in this thread, resolved in this hf?
3. Also, we tried to change the value for "service.http.smtpport" from 25 to some other value and it din't work. Still port 25 is responding.
-arun
> Hello Jay,
>
> We are in the process of contacting SUN Support for
> the new hf as you suggested. Have few Qns about this
> hot fix:
>
> 1. Is 5.2hf2.14 available as a full install or can we
> have just the hf2.14 as a patch?
It's what we call a "sparse patch". All you get is an installer that replaces files.
If you have customized your webmail, you will need to customize it again. The html/js files will be replaced. Some of the fixes involve changes to those files.
>
> 2. Is the ENS issue we are talking about in this
> thread, resolved in this hf?
I believe so.
>
> 3. Also, we tried to change the value for
> "service.http.smtpport" from 25 to some other value
> and it din't work. Still port 25 is responding.
I'm not surprised. the setting, "service.http.smtpport" changes where webmail sends messages, not where the MTA listens.
Edit the dispatcher.cnf file for that. . . .
then run:
imsimta cnbuild
imsimta restart dispatcher
to get it to take effect.
If anybody uses the webmail interface, make sure that service.http.smtpport matches where the server listens. You have to restart webmail to get changes here to take effect:
stop-msg http
start-msg http
>
> -arun
Hi Arun,
2. Is the ENS issue we are talking about in this thread, resolved in this hf?
No. local.store.notifyplugin.ensHost and local.store.notifyplugin.ensPort are ibiff configuration parameters. They control which ens server and port ibiff connects to. They do not affect how the ens server is started on a server.
There is no parameter in 5.2 which sets the host/port for the ens service. This was fixed in 6.1 onwards with the provision of the local.ens.port option.
If you want to run enpd on a different port, try the following:
# Disable ens
configutil -o local.ens.enable -v 0
# Start enpd manually with -p [ip:]port option (make sure to do this before running ./start-msg
./enpd -p 10.132.18.253:5500 &
I tried this and it seems to work.
bash-2.05$ netstat -an | grep 5500
10.15.10.33.5500*.*00 491520 LISTEN
You may need to update the local.store.notifyplugin.ensHost and local.store.notifyplugin.ensPort commands so that messaging server uses the correct ENS server.
Regards,
Shane.
p.s. I would still upgrade to hf2.14 as there are literally hundreds of fixes from your current release.
Shane,
Thanks for the response.
Without the hotfix,
1. starting enpd directly as root or mailsrv doesn't work in 5.2. Its complaining about loading some libraries. Same thing even after taking care of the PATH etc.
2. But, we are able to share the calendar enpd with the messaging server. The only problem is that when we bring down Messaging server it also pulls down the enpd of the calendar(don't want to change the enpd port in calendar), even after Disabling the ens in messaging by the cmd "configutil -o local.ens.enable -v 0 "
Will try again after implementing the hotfix2
-arun
Hi Arun,
I had the same issue with the library path's:
as user mailsrv:
bash-2.05$ pwd
/usr/iplanet/server5/bin/msg/admin/bin
bash-2.05$ ./enpd
ld.so.1: enpd: fatal: libservicebus.so: open failed: No such file or directory
Killed
bash-2.05$ export LD_LIBRARY_PATH=/usr/iplanet/server5/bin/msg/lib/
bash-2.05$ ./enpd &
[1] 5389
Regards,
Shane.
