nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

web deamon not starting after 7.3.1

ranjeeth

I have installed 7.3.1(TS) on the RHEL.Installation was smooth and i could see bring up the UI.But suddenly today when i reset the Teamsite services i found that web deamon is not ablt to start and thwoing some errors in the iwserver.log as
iwuiboot: ---------- STOPPING: Wed May 23 10:28:54 EDT 2012
/data/TeamSite/iw-webd/bin/iw.webd stop: iwwebd (no pid file) not running
iwuiboot: ---------- STOPPED: Wed May 23 10:28:59 EDT 2012
iwuiboot: ---------- STARTING: Wed May 23 10:33:02 EDT 2012
iwuiboot: Error: Web Daemon FAILED: Wed May 23 10:33:05 EDT 2012.
I tried manually stopping it but it says /data/TeamSite/iw-webd/bin/iw.webd stop: iwwebd (no pid file) not running.
During the installation i gave a different path for the log files other than the default.But when i went beneath the iwui directory i cannot find the access and error.log.I figured out from the iwwebd.conf file that the pid file is not getting created in the directory mentioned in the iwwebd.conf file.
Any ideas folks?

Find more posts tagged with

Comments

nipper

Check the iwjboss.log and server.log in ....../ApplicationContainer/server/default/log/

Rick Poulin

But when i went beneath the iwui directory i cannot find the access and error.log. I figured out from the iwwebd.conf file that the pid file is not getting created in the directory mentioned in the iwwebd.conf file.
Any ideas folks?

Make sure that the iwui user has sufficient permissions to write to that directory. Same with the logs.

mart2001

Did you stop the TeamSite services with /etc/init.d/iw.server stop or just ran iwreset -a (-ui)?

ranjeeth

I assume that during the installation the Permissions on the IWUI folder were set to the iwui user but i found that they were changed to the root somehow and was not able to write to the logs and as well as the directory changing the Permissions and re-booting the box fixed the issue.