Ho cercato questo file per un po 'e non riesco a trovare nulla che sembra applicabile alla mia situazione. Sono stato a fissare questi registri e non riesco a vedere quale sia il problema.Codice Heroku = H10 desc = "Arresto anomalo dell'app" - Impossibile capire perché si arresta in modo anomalo
Questo è successo durante le distribuzioni precedenti, ma sembrava sempre risolvere se stesso. Ora questo è appena successo da solo (nessuna distribuzione) e non posso uscirne. Ho provato a tornare a una versione precedente dell'app, ma sembra che io sia bloccato. Ho resettato il banco e ho anche fatto un rake db: migrate.
Ci sono alcune cose ripetitive nel registro, ma non so cosa leggerne. Qualcuno ha idea di dove sia il problema? Qualsiasi suggerimento sarebbe davvero apprezzato. Vedi i log qui sotto.
Jun 18 15:51:54 snapclass-production app/heroku-postgres: source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99981 measure.table-cache-hit-rate=0.99349
Jun 18 15:52:06 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="46.165.195.139" dyno= connect= service= status=503 bytes=
Jun 18 15:52:07 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="178.255.152.2" dyno= connect= service= status=503 bytes=
Jun 18 15:52:12 snapclass-production app/postgres: [47-1] [] LOG: checkpoint starting: time
Jun 18 15:52:13 snapclass-production app/postgres: [48-1] [] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.000 s, sync=0.000 s, total=0.334 s; sync files=0, longest=0.000 s, average=0.000 s
Jun 18 15:52:51 snapclass-production app/heroku-postgres: source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99994 measure.table-cache-hit-rate=0.99997
Jun 18 15:53:06 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="95.141.32.46" dyno= connect= service= status=503 bytes=
Jun 18 15:53:48 snapclass-production app/heroku-postgres: source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.97826 measure.table-cache-hit-rate=0.99999
Jun 18 15:54:06 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="95.211.217.68" dyno= connect= service= status=503 bytes=
Jun 18 15:54:17 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="205.197.158.210" dyno= connect= service= status=503 bytes=
Jun 18 15:54:17 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=www.snapclass.com fwd="205.197.158.210" dyno= connect= service= status=503 bytes=
Jun 18 15:54:25 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=demosidney.snapclass.com fwd="202.46.61.33" dyno= connect= service= status=503 bytes=
Jun 18 15:54:44 snapclass-production heroku/web.1: State changed from crashed to starting
Jun 18 15:54:44 snapclass-production app/heroku-postgres: source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.98897 measure.table-cache-hit-rate=0.99087
Jun 18 15:54:48 snapclass-production heroku/web.1: Starting process with command `bundle exec thin start -R config.ru -e $RAILS_ENV -p 50180`
Jun 18 15:55:40 snapclass-production app/heroku-postgres: source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99926 measure.table-cache-hit-rate=0.99996
Jun 18 15:55:50 snapclass-production heroku/web.1: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
Jun 18 15:55:50 snapclass-production heroku/web.1: Stopping process with SIGKILL
Jun 18 15:55:51 snapclass-production heroku/web.1: Process exited with status 137
Jun 18 15:55:51 snapclass-production heroku/web.1: State changed from starting to crashed
Jun 18 15:55:52 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=demosidney.snapclass.com fwd="119.63.193.130" dyno= connect= service= status=503 bytes=
Jun 18 15:55:52 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/snapclasses/sat-prep-math/register host=www.snapclass.com fwd="173.199.115.115" dyno= connect= service= status=503 bytes=
Jun 18 15:55:53 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="23.21.36.78" dyno= connect= service= status=503 bytes=
Jun 18 15:55:54 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="23.22.98.102" dyno= connect= service= status=503 bytes=
Jun 18 15:55:54 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="91.109.115.41" dyno= connect= service= status=503 bytes=
Jun 18 15:56:06 snapclass-production heroku/router: at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="174.34.224.167" dyno= connect= service= status=503 bytes=
Hai provato a contattare l'assistenza di Heroku? – mor
Non sembra che ci sia un buon modo per raggiungere il proprio team di supporto. Vedo solo una pagina per un [Servizio di supporto critico] (https://www.heroku.com/critical). La maggior parte di tutto riporta ai loro [Help] (https://help.heroku.com/) documenti. Un tempo era possibile inviare un ticket, ma non sembra che il Supporto critico sia un servizio aggiunto. Quindi ho esaminato i loro documenti per un po 'di aiuto e sono uscito vuoto, ma non ho contattato il loro supporto critico. – mgreich