Heroku deployment problem: no web processes running?

[Tom Williams]

Alright. I'm getting closer to Heroku working. I'm now successfully pushing to Heroku. But when I try to visit the URL given by $heroku domains (http://shielded-springs-77514.herokuapp.com/) it shows an application error. Going into my log, I see the following. :/

=============

2019-06-11T15:51:46.000000+00:00 app[api]: Build started by user twil...@mines.edu
2019-06-11T15:52:46.968686+00:00 app[api]: Release v12 created by user twil...@mines.edu
2019-06-11T15:52:46.968686+00:00 app[api]: Deploy 60f0a2d3 by user twil...@mines.edu
2019-06-11T15:52:58.000000+00:00 app[api]: Build succeeded
2019-06-11T15:54:35.644288+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=shielded-springs-77514.herokuapp.com request_id=### fwd="###" dyno= connect= service= status=503 bytes= protocol=http

=============

Config file:

[HIT Configuration]
title = ###
description = ###
amt_keywords = ###
lifetime = 24
us_only = true
approve_requirement = 80
contact_email_on_error = twil...@mines.edu
ad_group = ###
psiturk_keywords = ###
organization_name = ###
browser_exclude_rule = MSIE, mobile, tablet
allow_repeats = false

[Database Parameters]
database_url = postgres://###.amazonaws.com:5432/###
table_name = ###

[Server Parameters]
host = 0.0.0.0
port = 22362
cutoff_time = 60
logfile = server.log
loglevel = 2
debug = false
login_username = examplename
login_pw = examplepassword
threads = 1
secret_key = 'this is my secret key which is hard to guess, i should change this'
#certfile = <path_to.crt>
#keyfile = <path_to.key>
#adserver_revproxy_host = www.location.of.your.revproxy.sans.protocol.com
#adserver_revproxy_port = 80 # defaults to 80

[Task Parameters]
experiment_code_version = 6.0
num_conds = 16
num_counters = 1

[Shell Parameters]
launch_in_sandbox_mode = true

use_psiturk_ad_server = false
ad_location = shielded-springs-77514.herokuapp.com

[Dave Eargle]

1. ad_location needs to be https;//<domain>/pub

2. I assume you are skipping `psiturk-setup-example`. This readthedocs docs don't make this clear, but see https://github.com/NYUCCL/psiTurk/issues/254#issuecomment-282907137

I think you're missing a Procfile, and I bet you're also missing a herokuapp.py

Run `psiturk-setup-example` in another directory and copy `Procfile` and `herokuapp.py` into your directory.

--
You received this message because you are subscribed to the Google Groups "PsiTurk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to psiturk+u...@googlegroups.com.
To post to this group, send email to psi...@googlegroups.com.
Visit this group at https://groups.google.com/group/psiturk.
To view this discussion on the web visit https://groups.google.com/d/msgid/psiturk/b9802284-d6aa-434a-8ead-ab49ebd451b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Williams]

No dice :/
Fixed the URL! The Procfile and python file were already there, and verified to be identical to those generated using the setup command.

My heroku log after this push shows the same error as before, i.e.,

2019-06-12T16:09:03.000000+00:00 app[api]: Build started by user twil...@mines.edu
2019-06-12T16:10:03.438913+00:00 app[api]: Deploy 03900da1 by user twil...@mines.edu
2019-06-12T16:10:03.438913+00:00 app[api]: Release v14 created by user twil...@mines.edu
2019-06-12T16:10:15.000000+00:00 app[api]: Build succeeded
2019-06-12T16:11:23.452392+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/pub?mode=live&assignmentId=3GGAI1SQEWCGFZW7T6N0OTO38FFCMC&hitId=3K8CQCU3KEFTPVQIWWXZOIPH2HFNWB&workerId=AXKTYKCT9NGHS&turkSubmitTo=https%3A%2F%2Fwww.mturk.com" host=shielded-springs-77514.herokuapp.com request_id=a822e1eb-d489-42d0-9d77-57cd189352e1 fwd="141.126.131.90" dyno= connect= service= status=503 bytes= protocol=https
(with copies of that error being added periodically)

> To unsubscribe from this group and stop receiving emails from it, send an email to psi...@googlegroups.com.

[Tom Williams]

Thanks to Dave for the assistance! Turned out the problem lay in our faulty assumption that the appropriate psiturk directory structure was to have a single psiturk repo with subdirectory for all of our projects (wrong!) which didn't cause problems until now (because, of course, the full repo was being pushed to heroku rather than just the appropriate subdirectory).

[ENES AVCU]

Hi Tom and Dave,

Can you pls tell me how did you solve this problem? So when we have two experiment folders in Psiturk folder, how can we push that to heroku so that it will not give this error?

[Tom Williams]

I fixed this problem by abandoning the multiple studies in one repo model. I need most use one repository per project and everything works fine :)

Tom

You received this message because you are subscribed to a topic in the Google Groups "PsiTurk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/psiturk/_UK2LUohTTo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to psiturk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/psiturk/24aef0da-09e6-429b-a5a6-92dc167ea6bao%40googlegroups.com.