Issues with Form Player

63 views
Skip to first unread message

Cameron Grundy

unread,
Sep 5, 2017, 3:49:51 PM9/5/17
to CommCare Developers
Hey everyone, I'm a web development student at Purdue University and I'm using the open source CommCare application template for one of my senior projects. I followed all of the directions as stated on the site, but when I attempt to run one of my web apps, I'm told that im "unable to connect to form playing service, please report an issue if you continue to see this message". I'm not sure what I've done incorrectly as I've run through each of the provided steps twice. Any possible tips or things to check for that may help me understand whats going wrong with the formplayer? I'm able to provide any additional information about my project as needed.

My primary objective is really just to learn more about how software such as this operates from the inside, and how I can utilize many of the methods used here to create my own applications.

If anyone would prefer to assist me privately, I can be contacted at cgr...@purdue.edu

Thanks you guys so much, any help is appreciated

William Pride

unread,
Sep 5, 2017, 7:58:59 PM9/5/17
to CommCare Developers
Hi Cameron,

Have you setup and run the Formplayer process as described here?

Cheers,
Will

--

---
You received this message because you are subscribed to the Google Groups "CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-developers+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Cameron Grundy

unread,
Sep 6, 2017, 11:08:58 AM9/6/17
to CommCare Developers
Yes I have! There were no errors when building, but it still doesnt work.

William Pride

unread,
Sep 6, 2017, 11:20:52 AM9/6/17
to CommCare Developers
Interesting - a few ideas:
  • have you set the FORMPLAYER_URL variable in your localsettings.py file to be the url and port running Formplayer?
  • when you open the terminal running Formplayer can you see any errors in the logs?
  • when you open the dev console in your browser likewise can you see any error messages?
Cheers,
Will

To unsubscribe from this group and stop receiving emails from it, send an email to commcare-developers+unsubscribe...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Cameron Grundy

unread,
Sep 6, 2017, 2:01:27 PM9/6/17
to CommCare Developers
Thanks will,

I looked into the documents that you pointed out but no issues are coming up.  I did see on the formplayer.readme that the commcarehq build
must be aligned with what I have running.  Commcare build 2.0 is listed as unstable so I updated the build to the latest version 2.34.
do I have to do something to the formplayer to align these?  This is not a forked install so i am trying to eliminate any connections to the original source.

William Pride

unread,
Sep 6, 2017, 3:17:44 PM9/6/17
to CommCare Developers
I don't think that would be causing the issue you're seeing. Could you share the content of your Formplayer spring logs as well as the browser console output? It will be hard to diagnose this issue without.

Thanks,
Will

--
Message has been deleted

Cameron Grundy

unread,
Sep 18, 2017, 10:34:13 PM9/18/17
to CommCare Developers
Hello Will, I apologize for the delay. 

The formplayer-spring.log is here
supervisor: couldn't chdir to /home/commcarehq/commcare-hq//formplayer: ENOENT
supervisor: child process was not spawned
supervisor: couldn't chdir to /home/commcarehq/commcare-hq//formplayer: ENOENT
supervisor: child process was not spawned
supervisor: couldn't chdir to /home/commcarehq/commcare-hq//formplayer: ENOENT
supervisor: child process was not spawned
supervisor: couldn't chdir to /home/commcarehq/commcare-hq//formplayer: ENOENT
supervisor: child process was not spawned


The browser input is below

less-1.7.3.min.js:13 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
r @ less-1.7.3.min.js:13
less-1.7.3.min.js:13 less: css for http://192.168.56.101/static/style/less/bootstrap.debug.less generated in 938ms
less-1.7.3.min.js:13 less: css for http://192.168.56.101/static/font-awesome/less/font-awesome.less generated in 155ms
less-1.7.3.min.js:13 less: css for http://192.168.56.101/static/style/less/font-commcare.less generated in 13ms
less-1.7.3.min.js:13 less: css for http://192.168.56.101/static/style/less/style.debug.less generated in 163ms
less-1.7.3.min.js:13 less: css for http://192.168.56.101/static/cloudcare/less/font-formplayer.less generated in 15ms
less-1.7.3.min.js:13 less: css for http://192.168.56.101/static/cloudcare/less/formplayer-common.debug.less generated in 121ms
less-1.7.3.min.js:13 less: css for http://192.168.56.101/static/cloudcare/less/formplayer-webapp.debug.less generated in 80ms
less-1.7.3.min.js:13 less: less has finished. css generated in 1487ms)
middleware.js:19 User navigated to listApps
middleware.js:19 User navigated to selectApp
localhost:8080/navigate_menu Failed to load resource: net::ERR_CONNECTION_REFUSED
middleware.js:19 User navigated to listApps
Reply all
Reply to author
Forward
0 new messages