Cannot start dispacher, tcp_smtp_server, and job_controller

Question

IInstallation and configuration of JSMS 6.1 was done as a component of JES. First start right after the installation using �start-msg� was quite successful. But after the change of "service.http.port" to 2080 with "configutil" command any attempt to start-msg are failed with the "dispatcher" timeout and "job_controller" failed.
The log files (dispatcher.log, tcp_smtp_server.log, and job_controller.log) are of "0" length in spite of increasing verbosity with "DEBUG=-1 and/or DEBUG=5" in �dispatcher.cnf� and �job_controller.cnf�. The tracing shows the last error as ENOTTY (25), but the output has few preceding errors in system calls where I would never expect it. I also activated "local.autorestart=yes" which produced two "defunct" processes forked by the �watcher� from "msstart -r " program and which I need manually remove.
And I don't have the patch 116568-60.
Now, I think you know almost everything (quite messy). Please, help me. I need it ASAP.
Regards,
Peter Kinev

Answer 1

I've the same version (without the patch), and i've changed the port:bash-2.05# ./configutil -o service.http.port
80
bash-2.05# ./configutil -o service.http.port -v 2080
OK SET
bash-2.05# ./configutil -o service.http.port
2080
bash-2.05# ./imsimta chbuild
bash-2.05# ./imsimta cnbuild
bash-2.05# ./start-msg
Connecting to watcher ...
Launching watcher ...
Starting ens server .... 11151
Starting store server .... 11152
checking store server status .... ready
Starting imap server .......... 11154
Starting pop server ......... 11157
Starting http server ................ 11160
Starting sched server .... 11162
Starting dispatcher server .... 11164
Starting job_controller server .... 11168
bash-2.05# ./imsimta version
Sun Java(tm) System Messaging Server 6.1 (built Apr 28 2004)
libimta.so 6.1 (built 13:10:36, Apr 28 2004)
SunOS server.domain.com 5.9 Generic_117171-17 sun4u sparc SUNW,Ultra-250
bash-2.05#But, as you can see, i'm not able to reproduce the problem.
Anyway if you want to enable logging for the IMTA component you should add the keyword logging on the default channel definition in the imta.cnf file