#16 dispyscheduler -httpd not clearly documented

[Anonymous]

Hi, could you expand on the documentation for the dispyscheduler --httpd option ? I've tried to use it but without success (browsing to 192.168.16.69:8181 shows nothing). Log attached:

--httpd if given, HTTP server is created so clusters can be
monitored and managed
bmduser@lubuntu-box:~$ dispyscheduler.py -d -i hostname -I --max_file_size 2G --httpd
2015-09-21 09:48:58,134 - dispyscheduler - dispyscheduler version 4.5
2015-09-21 09:48:58,135 - asyncoro - poller: epoll
2015-09-21 09:48:58,136 - dispy - Started HTTP server at ('0.0.0.0', 8181)
2015-09-21 09:48:58,136 - dispy - Started HTTP server at ('0.0.0.0', 8181)
2015-09-21 09:48:58,137 - dispyscheduler - tcp server at 192.168.16.69:51347
2015-09-21 09:48:58,137 - dispyscheduler - scheduler at 192.168.16.69:51349
2015-09-21 09:48:58,137 - dispyscheduler - Pending jobs: 0
2015-09-21 09:48:58,139 - dispyscheduler - Discovered 192.168.16.104:51348 (LubuntuVM) with 1 cpus
2015-09-21 09:50:50,963 - dispyscheduler - New computation 1442792938136: compute, /tmp/dispy/scheduler/192.168.16.19/compute_nbUpWE
2015-09-21 09:50:50,969 - dispyscheduler - Copying file job.tar to /tmp/dispy/scheduler/192.168.16.19/compute_nbUpWE/job.tar (145776640)
2015-09-21 09:50:52,302 - dispyscheduler - Copied file /tmp/dispy/scheduler/192.168.16.19/compute_nbUpWE/job.tar
2015-09-21 09:50:52,307 - dispyscheduler - Pending jobs: 1
2015-09-21 09:50:53,803 - dispyscheduler - Pending jobs: 1
2015-09-21 09:50:53,803 - dispyscheduler - Pending jobs: 0
2015-09-21 09:50:53,805 - dispyscheduler - Running job 140527567618608 on 192.168.16.104 (busy: 1 / 1)

[Giridhar Pemmasani]

By any chance you have client (program that uses cluster) and dispyscheduler are both on same computer and you create httpd server in the client program? (It is probably why 'Started HTTP server' appears twice in the log above.) If so, the status you see in the browser is the client, not the scheduler. Either don't use httpd in the client, or use different port.

[Anonymous]

Thank you for your fast response!
No, the client runs on 192.168.16.19 and dispyscheduler runs on 192.168.16.69
The client does not try to create an httpd server, it is invoked like this:

cluster = dispy.SharedJobCluster(compute, depends = [make, getwns, "job.tar"], scheduler_node="192.168.16.69")

[Giridhar Pemmasani]

I don't see the issue with httpd and dispyscheduler as you mention. I see cluster / nodes / jobs as expected.