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; } } }

IWAT command trigger stops working

ChuckM

We have a command trigger that sends out an e-mail when content is submitted. About a month ago, this trigger stopped working every weekend. We have to do a "/etc/init.d/iw.local start" every Monday morning to get it working again. So far I have not found any clues pointing to the culprit. Could anyone suggest a log file to look in to or suggest possibilities? We are running 5.5.2 on Solaris.

Thanks.

Find more posts tagged with

Comments

nipper

Is the command still running ? ps -ef | grep <triggername> will
tell you.

If not, you may want to redirect STDOUT and STDERR to a file and see if anything is sent.

Andy

Bowker

you should also do an "iwlsat" to list the installed triggers that teamsite knows about. If it's not there - put it back.

mmb

It could also be down to the user who is running /etc/init.d/iw.local start command. If this user is logged in as root (on the console, or directly into the box) when they exit, it can kill the iwlocal process as it was spawned from their login shell. maybe someone is logged in all week, exits out on a friday afternoon & kills the process..?