After pushing on heroku my #Messages(value) are not interpreted:
--> value is display instead of the translation present in conf/Messages file.
I use play framework 2.2.1.
Here is the log of a start and a first display of a page containning #Messsages() use.
2014-10-12T05:37:14.320052+00:00 heroku[web.1]: State changed from down to starting
2014-10-12T05:37:14.320052+00:00 heroku[web.1]: Unidling
2014-10-12T05:37:24.363328+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/kosh -Dhttp.port=41328 -DapplyEvolutions.default=true`
2014-10-12T05:37:25.260260+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Djava.rmi.server.useCodebaseOnly=true
2014-10-12T05:37:25.672105+00:00 app[web.1]: Play server process ID is 2
2014-10-12T05:37:27.084724+00:00 app[web.1]: [←[37minfo←[0m] play - database [default] connected at jdbc:h2:mem:play
2014-10-12T05:37:27.660047+00:00 app[web.1]: [←[37minfo←[0m] play - Application started (Prod)
2014-10-12T06:39:14.765169+00:00 heroku[router]: at=info method=GET path="/" host=mmmm.herokuapp.com request_id=31eeed7d-0b4d-43ac-b2df-3d142f6db4ba fwd="-" dyno=web.1 connect=1ms service=16ms status=200 bytes=34657
2014-10-12T06:39:14.939740+00:00 heroku[router]: at=info method=GET path="/assets/stylesheets/bootstrap.min.css" host=mmmm.herokuapp.com request_id=7ffe7b15-d521-481fb9f1-fba1c146fbf0 fwd="-" dyno=web.1 connect=1ms service=7ms status=304 bytes=173
2014-10-12T06:39:14.949590+00:00 heroku[router]: at=info method=GET path="/assets/stylesheets/normalize.css" host=mmmm.herokuapp.com request_id=4616036b-d3d3-4891-bc69-8c3461d69e26 fwd="-" dyno=web.1 connect=1ms service=8ms status=304 bytes=1732
2014-10-12T06:47:05.367842+00:00 heroku[router]: at=info method=GET path="/webjars/jquery/1.9.1/jquery.min.js" host=mmmm.herokuapp.com request_id=2938c0d1-62ad-4e43-acdb-1dc23588754f fwd="-" dyno=web.1 connect=1ms service=5ms status=304 bytes=173
My Procfile contains :
web: target/universal/stage/bin/kosh -Dhttp.port=$PORT -DapplyEvolutions.default=true
Changing the name of the file from "Messages" to "messages" (with a lowercase m) had fix the problem. On my Windows side file was case insensitive, on heroku side, in an Unix world, file names were case sensitives. Play framework seem to look for file in lower case at heroku.
Related
I was trying to deploy my dashboard on heroku but after I finished I got Request timeout error
I got an Application error and search a lot but still have the same problem of time out and quota memory exceeded
Here is the error from the activity log:
2022-05-02T19:12:39.725777+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=ukraineinvasion.herokuapp.com request_id=fc485f9
6-0c39-416e-914a-93a3c9e1b6e8 fwd="41.46.189.30" dyno=web.1 connect=0ms service=30004ms status=503 bytes=0 protocol=https
2022-05-02T19:12:40.714784+00:00 app[web.1]: Dash is running on http://127.0.0.1:59351/
I deployed this app on Heroku for the first time 6 months ago and it was running fine. Its still running fine on localhost but now when I try to use the same heroku link its showing application error.
Here are my logs:
heroku logs --tail
2021-11-22T21:25:37.247493+00:00 heroku[web.1]: Restarting
2021-11-22T21:25:37.291674+00:00 heroku[web.1]: State changed from up to starting
2021-11-22T21:25:38.213115+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2021-11-22T21:25:38.434284+00:00 heroku[web.1]: Process exited with status 143
2021-11-22T21:25:39.432521+00:00 heroku[web.1]: Starting process with command `node app.js`
2021-11-22T21:25:40.721334+00:00 app[web.1]: Database_URL undefined
2021-11-22T21:25:40.722187+00:00 app[web.1]: Server has started
2021-11-22T21:25:41.145424+00:00 heroku[web.1]: State changed from starting to up
2021-11-22T21:26:10.715356+00:00 app[web.1]: connect ECONNREFUSED 127.0.0.1:27017
2021-11-22T21:26:20.762822+00:00 heroku[router]: at=info method=GET path="/" host=sleepy-basin-23202.herokuapp.com request_id=9145c837-b0b8-409e-af04-38431cef02a5 fwd="47.15.8.93" dyno=web.1 connect=0ms service=12ms status=304 bytes=151 protocol=https
2021-11-22T21:26:21.119967+00:00 heroku[router]: at=info method=GET path="/style.css" host=sleepy-basin-23202.herokuapp.com request_id=7cd5ff7a-a627-4f97-a28f-b4f73b08b463
fwd="47.15.8.93" dyno=web.1 connect=0ms service=9ms status=200 bytes=4543 protocol=https
2021-11-22T21:26:21.123105+00:00 heroku[router]: at=info method=GET path="/script.js" host=sleepy-basin-23202.herokuapp.com request_id=3176b0d8-80b4-4c6c-a389-cc786bbd0e0f
fwd="47.15.8.93" dyno=web.1 connect=0ms service=7ms status=404 bytes=392 protocol=https
2021-11-22T21:26:21.452457+00:00 heroku[router]: at=info method=GET path="/script.js" host=sleepy-basin-23202.herokuapp.com request_id=cbdc660f-90e1-443b-8b2d-2f255018b63d
fwd="47.15.8.93" dyno=web.1 connect=0ms service=2ms status=404 bytes=392 protocol=https
2021-11-22T21:26:22.904249+00:00 heroku[router]: at=info method=POST path="/view" host=sleepy-basin-23202.herokuapp.com request_id=3a4c38b1-5798-490e-bc1b-73338fc18cf5 fwd="47.15.8.93" dyno=web.1 connect=0ms service=13ms status=302 bytes=246 protocol=https
2021-11-22T21:26:33.202949+00:00 app[web.1]: (node:4) UnhandledPromiseRejectionWarning: MongooseError: Operation `users.find()` buffering timed out after 10000ms
2021-11-22T21:26:33.202957+00:00 app[web.1]: at Timeout.<anonymous> (/app/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:185:20)
2021-11-22T21:26:33.202958+00:00 app[web.1]: at listOnTimeout (internal/timers.js:554:17)
2021-11-22T21:26:33.202959+00:00 app[web.1]: at processTimers (internal/timers.js:497:7)
2021-11-22T21:26:33.202960+00:00 app[web.1]: (Use `node --trace-warnings ...` to show where the warning was created)
2021-11-22T21:26:33.203001+00:00 app[web.1]: (node:4) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
2021-11-22T21:26:33.203100+00:00 app[web.1]: (node:4) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are
not handled will terminate the Node.js process with a non-zero exit code.
2021-11-22T21:26:53.190725+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/view" host=sleepy-basin-23202.herokuapp.com request_id=23595d4a-6e69-48cf-a1ce-2ef12ce13815 fwd="47.15.8.93" dyno=web.1 connect=0ms service=30000ms status=503 bytes=0 protocol=https
There isn't much information here, but I see
Database_URL undefined
in your logs. Assuming you are using a Heroku database addon like Heroku Postgres, your database URL will be defined in a variable called DATABASE_URL. Case is important: DATABASE_URL and Database_URL are different things.
Please update your code to use DATABASE_URL.
Note that environment variable names are not case-sensitive on Windows. If you are using Windows for local development that's one reason this might work locally and not work on Heroku.
It can't find you database Url check your env configuration
I have a problem with deploying Strapi application on Heroku. Both local and Heroku Strapi setups are using Postgres database.
Can't see any errors in Heroku logs, just a blank page in browser. Brpwser's console has these two errors:
Uncaught SyntaxError: Unexpected token '<' runtime~main.8073a043.js:1
Uncaught SyntaxError: Unexpected token '<' main.abbe0ac9.chunk.js:1
Heroku logs:
2020-12-11T15:26:03.986177+00:00 heroku[web.1]: State changed from starting to up
2020-12-11T15:26:03.916838+00:00 app[web.1]: INFO: Accepting connections at http://localhost:58777
2020-12-11T15:26:04.470749+00:00 heroku[router]: at=info method=GET path="/" host=john-strapi-postgres.herokuapp.com request_id=8783501f-3d9f-4986-bb44-6648a93d8105 fwd="68.82.27.99" dyno=web.1 connect=1ms service=24ms status=304 bytes=85 protocol=https
2020-12-11T15:26:04.561029+00:00 heroku[router]: at=info method=GET path="/admin/runtime~main.8073a043.js" host=john-strapi-postgres.herokuapp.com request_id=008157f5-a2ff-4738-9a8c-8ef4ac76a2d8 fwd="68.82.27.99" dyno=web.1 connect=1ms service=3ms status=304 bytes=85 protocol=https
2020-12-11T15:26:04.558537+00:00 heroku[router]: at=info method=GET path="/admin/main.abbe0ac9.chunk.js" host=john-strapi-postgres.herokuapp.com request_id=aa2e15a8-e001-4333-a195-f669ddcaac74 fwd="68.82.27.99" dyno=web.1 connect=1ms service=5ms status=304 bytes=85 protocol=https
2020-12-11T15:26:04.666249+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=john-strapi-postgres.herokuapp.com request_id=f2342dac-0347-4b0b-a4e4-89f0a425a98a fwd="68.82.27.99" dyno=web.1 connect=0ms service=6ms status=304 bytes=85 protocol=https
Local Strapi application runs perfectly fine.
Node v. 14.5.1
NPM v. 6.14.8
Strapi v. 3.3.4
Windows 10
I'm developing an college project to read data from an sensor remotely.
I made an application with node-red to be served by Heroku. It has runned perfectly but from times to times the "flow" goes away and the aplication resets the SENSOR DATA.
So how can i made Heroku stops from reseting my application?
I couldn't found any configuration on Heroku manager's interface. In one deployment test, i fixed the "flow" import, but the config data and the sensors data still be loosing by Heroku.
Heroku's log file after an reset:
2018-06-23T15:53:51.688394+00:00 app[web.1]: 23 Jun 15:53:51 - [info] [mqtt-broker:mqttConnection] Connected to broker: Node-RED from smartcampus#mqtt://networkserver.maua.br:1883
2018-06-23T15:53:53.877683+00:00 heroku[router]: at=info method=GET path="/ui/dashboard.appcache" host=node-red-tcc.herokuapp.com request_id=9d830325-8753-4ce4-ac3f-e87710ef81e2 fwd="201.83.101.163" dyno=web.1 connect=1ms service=2ms status=200 bytes=765 protocol=https
2018-06-23T15:53:54.495634+00:00 heroku[router]: at=info method=GET path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWby" host=node-red-tcc.herokuapp.com request_id=64c87bcc-88f6-4a9a-b77c-0f413b5f99a1 fwd="201.83.101.163" dyno=web.1 connect=0ms service=2ms status=200 bytes=324 protocol=https
2018-06-23T15:53:54.663602+00:00 heroku[router]: at=info method=GET path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWeS&sid=yOGzHE-Gl54e7SKDAAAB" host=node-red-tcc.herokuapp.com request_id=7c9aef48-be2b-4a1b-b830-2d09e57f9856 fwd="201.83.101.163" dyno=web.1 connect=0ms service=6ms status=200 bytes=1867 protocol=https
2018-06-23T15:53:54.887141+00:00 heroku[router]: at=info method=GET path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWhA&sid=yOGzHE-Gl54e7SKDAAAB" host=node-red-tcc.herokuapp.com request_id=70e4ddae-93fd-4de6-a43b-f06da32154ef fwd="201.83.101.163" dyno=web.1 connect=0ms service=58ms status=200 bytes=269 protocol=https
2018-06-23T15:53:54.884760+00:00 heroku[router]: at=info method=POST path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWi0&sid=yOGzHE-Gl54e7SKDAAAB" host=node-red-tcc.herokuapp.com request_id=c2fb0ab8-4be9-41a4-ac22-a57b04beeb57 fwd="201.83.101.163" dyno=web.1 connect=0ms service=2ms status=200 bytes=281 protocol=https
2018-06-23T15:53:55.039176+00:00 heroku[router]: at=info method=POST path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWkQ&sid=yOGzHE-Gl54e7SKDAAAB" host=node-red-tcc.herokuapp.com request_id=3c5b9515-a8e8-461f-8500-8298618ddc4a fwd="201.83.101.163" dyno=web.1 connect=0ms service=1ms status=200 bytes=281 protocol=https
2018-06-23T15:53:55.040980+00:00 heroku[router]: at=info method=GET path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWkS&sid=yOGzHE-Gl54e7SKDAAAB" host=node-red-tcc.herokuapp.com request_id=7ceb0806-a510-4c2d-be9f-ac6f96c89ca0 fwd="201.83.101.163" dyno=web.1 connect=1ms service=1ms status=200 bytes=246 protocol=https
2018-06-23T15:53:55.193537+00:00 heroku[router]: at=info method=GET path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWms&sid=yOGzHE-Gl54e7SKDAAAB" host=node-red-tcc.herokuapp.com request_id=a7d5c82a-454c-48e6-933e-fbe1d14c8e88 fwd="201.83.101.163" dyno=web.1 connect=0ms service=1ms status=200 bytes=327 protocol=https
2018-06-23T15:53:55.537788+00:00 heroku[router]: at=info method=GET path="/ui/socket.io/?EIO=3&transport=polling&t=MGjMWql&sid=yOGzHE-Gl54e7SKDAAAB" host=node-red-tcc.herokuapp.com request_id=ed2a473d-2478-41ec-bc17-26567c4b44fa fwd="201.83.101.163" dyno=web.1 connect=0ms service=93ms status=200 bytes=225 protocol=https
Interface after reset:
Interface before reset:
Project Client Interface link:
https://node-red-tcc.herokuapp.com/ui/
PS: I didn't include node-red's project files to not pollute this Question. But I will when asked to do it.
Thank you in advance!
The Heroku's support said that the free services has an sleeping mode. And the sleeping mode resets some files, so there is no way to solve this problem in the free mode.
I was trying to deploy my first web-app ( back end - Spring, front end - Angular2 ) to Heroku, but the front end doesn't work properly. This is what I see in logs.
2016-11-08T16:53:10.634253+00:00 heroku[router]: at=info method=GET path="/login.html" host=organazi.herokuapp.com request_id=86ff1936-97be-4cd1-abea-6553163c834f fwd="91.196.192.37" dyno=web.1 connect=1ms service=209ms status=200 bytes=1772
2016-11-08T16:53:11.003293+00:00 heroku[router]: at=info method=GET path="/node_modules/core-js/client/shim.min.js" host=organazi.herokuapp.com request_id=8ae3afe7-5721-41ef-9d80-d853ede55e07 fwd="91.196.192.37" dyno=web.1 connect=2ms service=231ms status=404 bytes=548
2016-11-08T16:53:11.110401+00:00 heroku[router]: at=info method=GET path="/systemjs.config.js" host=organazi.herokuapp.com request_id=ee743412-a577-4b4e-b5a0-1a6ed9cd5391 fwd="91.196.192.37" dyno=web.1 connect=1ms service=88ms status=200 bytes=2077
2016-11-08T16:53:11.096089+00:00 heroku[router]: at=info method=GET path="/node_modules/reflect-metadata/Reflect.js" host=organazi.herokuapp.com request_id=4954cbe7-832a-4e86-a37f-beb82fc3d567 fwd="91.196.192.37" dyno=web.1 connect=1ms service=70ms status=404 bytes=549
2016-11-08T16:53:11.116841+00:00 heroku[router]: at=info method=GET path="/node_modules/zone.js/dist/zone.js" host=organazi.herokuapp.com request_id=facea6c9-0c5c-4b68-8b7d-88347054bbd6 fwd="91.196.192.37" dyno=web.1 connect=1ms service=100ms status=404 bytes=542
2016-11-08T16:53:11.113024+00:00 heroku[router]: at=info method=GET path="/node_modules/systemjs/dist/system.src.js" host=organazi.herokuapp.com request_id=5605b488-0a21-49d8-8d71-ef3fd06288e4 fwd="91.196.192.37" dyno=web.1 connect=2ms service=93ms status=404 bytes=549
2016-11-08T16:53:11.271432+00:00 heroku[router]: at=info method=GET path="/node_modules/reflect-metadata/Reflect.js" host=organazi.herokuapp.com request_id=c4c5d13d-3311-4d8e-a46a-c14c59b03899 fwd="91.196.192.37" dyno=web.1 connect=6ms service=27ms status=404 bytes=549
2016-11-08T16:53:11.430986+00:00 heroku[router]: at=info method=GET path="/node_modules/systemjs/dist/system.src.js" host=organazi.herokuapp.com request_id=d8f8a2ba-5e10-4d55-8cd1-0c6b5388de26 fwd="91.196.192.37" dyno=web.1 connect=1ms service=38ms status=404 bytes=549
2016-11-08T16:53:11.613146+00:00 heroku[router]: at=info method=GET path="/systemjs.config.js" host=organazi.herokuapp.com request_id=1440d389-ecc9-4537-bcd2-19cc6146e453 fwd="91.196.192.37" dyno=web.1 connect=6ms service=21ms status=200 bytes=2077
2016-11-08T16:53:11.778848+00:00 heroku[router]: at=info method=GET path="/login/blue-sky-hd-wallpaper-2.jpg" host=organazi.herokuapp.com request_id=cd6a19c8-dbd0-4b68-926a-4c760bc9c3a9 fwd="91.196.192.37" dyno=web.1 connect=1ms service=17ms status=200 bytes=52476
Files like systemjs.config.js and image /login/blue-sky-hd-wallpaper-2.jpg loads fine, but there are some problems with loading node_modules. Sitting for 2 weeks with this problem.
My project - https://github.com/BarexaS/Constructed.git
In my Spring Boot and Angular2 setup I have similar issues. Unfortunately I have no solution yet. If you did not add the (generated) node_modules to your VCS (which you should not do anyway) heroku won't be able to detect automatically that your project also contains Node.js dependencies, even if your package.json is checked in. Consequently node_modules won't be available. There is the possiblity to tell heroku that your project is also Node.js based (by specifying it in the Procfile) but in the description heroku will expect that the package.json file is located in the root folder of the Spring Boot app. In my setup it is located in resources/static/js/ so I do not really know how to tell heroku that it first must install the dependencies by calling npm install in this folder.