iwwebd could not be started

System

Hi,

We are setting up a new TS 6.5 SP3 installation on Solaris 9. When we perform iwreset -a, it throws the following errror:

-------------------------------
2008] [warn] module mod_fastcgi.c is already added, skipping
Syntax error on line 510 of /opt/iw-home/iw-webd/conf/httpd.conf:
SSLPassPhraseDialog not allowed here
/opt/iw-home/iw-webd/bin/iw.webd start: iwwebd could not be started
-------------------------------

When i checked the httpd.conf file, in line#491 there was no closing tag for Location. So i edited the file and i restarted iw-webd and it started successfully after which i started servletd and it started successfully as well.

When i perform iw.server stop/start the problem persists again. Everytime httpd.conf is getting generated without the closing tag for Location.

I tried using iwwebd_conf.ipl from a working server and it didn't help.

Attached is the httpd.conf file for reference.

Any pointers on this issue.

Thanks,
Arun.

Adam Stoller

Hi, We are setting up a new TS 6.5 SP3 installation on Solaris 9. When we perform iwreset -a, it throws the following errror: ------------------------------- 2008] [warn] module mod_fastcgi.c is already added, skipping Syntax error on line 510 of /opt/iw-home/iw-webd/conf/httpd.conf: SSLPassPhraseDialog not allowed here /opt/iw-home/iw-webd/bin/iw.webd start: iwwebd could not be started ------------------------------- When i checked the httpd.conf file, in line#491 there was no closing tag for Location. So i edited the file and i restarted iw-webd and it started successfully after which i started servletd and it started successfully as well. When i perform iw.server stop/start the problem persists again. Everytime httpd.conf is getting generated without the closing tag for Location. I tried using iwwebd_conf.ipl from a working server and it didn't help. Attached is the httpd.conf file for reference. Any pointers on this issue. Thanks, Arun.

You need to edit the httpd.conf.template file - which is used to regenerated the httpd.conf file everytime you restart the UI - and hence the reason why the problem returned after you did so.