I actually ran into this in 4.1, but at the time didn’t really get a chance to look into it:
I can’t get the web service on Pulse to run. Regardless what I configure in the repository options, I can’t get any connections going. The configured port never shows as open in netstat either.
System info:
Fedora
i386
Firewall disabled
SELinux disabled
Deadline 5.0 beta 1
Mono 2.6.7
Cheers!
-Matt
Hey Matt,
What value do you have for the Web Service Connection Limit in the Repository Options? If it’s set to 0 (which it is by default), the feature is disabled.
If it’s greater than 0, can you restart Pulse and then after it starts up, can you grab the most recent Pulse log from the machine? You can find the log folder from the Pulse UI by selecting Help -> Explore Log Folder. Pulse should print out a bit of info about the web service, so we can take a look at the log to see if anything appears suspect.
Thanks!
Hey Matt,
I just tested it here, and the web service is working fine on Linux. So hopefully it’s just a matter of the feature being disabled on your setup (see my response above for more info).
Cheers,
I have the connection limit set to 5. I don’t actually have the Pulse gui running, I’m running it as a daemon, capturing it’s stdout to a log file. The X server isn’t even running on that server (it boots to runlevel 3 by default, instead of 5).
Here’s the init.d script I use that starts Pulse on startup:
[code]#! /bin/bash
#deadlinepulsed This is the init script for starting and stoping Deadline Pulse on linux as a (semi) daemon
for thinkbox software
Source function library
. /etc/rc.d/init.d/functions
DLCLIENTBIN="/usr/local/Thinkbox/Deadline/bin"
LOGDIR="/var/log/Thinkbox/Deadline"
LOGFILE="$LOGDIR/deadlinepulsed.log"
PULSEUSER=mech
start(){
pid=ps auwx | grep mono | grep deadlinepulse |grep -v start | grep -v grep | awk '{print $2}'
if [ -n “$pid” ]; then
echo “Deadline Pulse already running”
echo
echo_failure
exit 1
else
if [ -x $DLCLIENTBIN/deadlinepulse ]; then
su -l $PULSEUSER -s /bin/bash -c "$DLCLIENTBIN/deadlinepulse -nogui &" >> "$LOGFILE" 2>&1 < /dev/null
success "Deadline Pulse started as a daemon"
echo
else
failure "Could not start Deadline Pulse"
echo
fi
fi
}
stop(){
pid=ps auwx | grep mono | grep deadlinepulse |grep -v start | grep -v grep | awk '{print $2}'
if [ -n “$pid” ]; then
kill $pid
success “Deadline Pulse stopped”
echo
else
failure “Deadline Pulse not running”
echo
fi
}
See how we were called.
case “$1” in
start)
start
;;
stop)
stop
;;
restart)
stop
start
;;
*)
echo $“Usage: $0 {start|stop|restart}”
exit 2
esac
[/code]
Cheers!
-Matt
Could you post the log file that Pulse creates?
Thanks!
Sure! I’ve attached it.
Cheers!
-Matt
deadlinepulsed.log (643 KB)
Thanks for the log! It’s not showing any information about the web service though. If it was enabled, you should see something like this near the top:
2011-01-24 14:52:59: Web Service - Web Service is using Basic Authentication.
2011-01-24 14:52:59: Web Service - Web Service listening for connections on port 8080...
If it’s not enabled, nothing gets printed out, so your Pulse must think the connection limit is set to 0. In beta 3, we’ll add a line of output to say if it’s disabled, just to make it more obvious when this is the case.
What happens if you stop the Pulse daemon and then restart it manually? Do the lines I showed above appear in the log?
Cheers,
Hmm, that’s odd. I restarted just the daemon, and that didn’t do it. However, after rebooting the server, it the web service works!
As a side note, it might be nice if deadline timestamped it’s log lines.
Cheers!
-Matt
Glad to hear a reboot fixed it!
I overlooked the fact that you were redirecting Pulse’s stdout to a log file. Pulse already writes to a log file of its own, which can be found in your Deadline Client installation folder (ie: /usr/local/Thinkbox/Deadline/logs). A new log is created for each session, and these logs include timestamps for each line of output, which you can actually see in the two log lines I posted above.
Cheers,
I was wondering about that. Cool! Is there a way to define the output location of the log files? (Not that big of a deal as I can always sym link the logs folder). If not, it might be a useful feature to add.
Cheers!
-Matt