Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors 500 #66

Closed
maitrey0da opened this issue Apr 27, 2016 · 9 comments · Fixed by #71
Closed

Errors 500 #66

maitrey0da opened this issue Apr 27, 2016 · 9 comments · Fixed by #71

Comments

@maitrey0da
Copy link

Hello,

I use the latest version of Cachet or docker-cachet. With sandalone or docker installation, I have definitely errors 500.
I tried rm -rf bootstrap/cache/* and chmod -R 777 storage

Before my last checkout, docker-cachet was working.

@GrahamCampbell
Copy link
Contributor

We're going to need more information please.

@maitrey0da
Copy link
Author

Ok,

I followed this with docker-compose. No error during the setup and installation.

# docker-compose version
docker-compose version 1.7.0, build 0d7bf73
docker-py version: 1.8.0
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013

# docker version
Client:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:17:17 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:17:17 2016
 OS/Arch:      linux/amd64
# docker logs cachetdocker_cachet_1
.....
Running composer as root/super user is highly discouraged as packages, plugins and scripts cannot always be trusted
Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postInstall
> php artisan optimize --force
Generating optimized class loader
Compiling common classes
> php artisan config:cache
Configuration cache cleared!
Configuration cached successfully!
> php artisan route:cache
Route cache cleared!
Routes cached successfully!
Application key [base64:o5MZqKpR0wOG2vUBiLD01Pvr2jS8DA/XQywLEPmxTDU=] set successfully.
Copied Directory [/vendor/roumen/feed/src/views] To [/resources/views/vendor/feed]
Publishing complete for tag []!
Migration table created successfully.
Migrated: 2015_01_05_201324_CreateComponentGroupsTable
Migrated: 2015_01_05_201444_CreateComponentsTable
Migrated: 2015_01_05_202446_CreateIncidentTemplatesTable
Migrated: 2015_01_05_202609_CreateIncidentsTable
Migrated: 2015_01_05_202730_CreateMetricPointsTable
Migrated: 2015_01_05_202826_CreateMetricsTable
Migrated: 2015_01_05_203014_CreateSettingsTable
Migrated: 2015_01_05_203235_CreateSubscribersTable
Migrated: 2015_01_05_203341_CreateUsersTable
Migrated: 2015_01_09_083419_AlterTableUsersAdd2FA
Migrated: 2015_01_16_083825_CreateTagsTable
Migrated: 2015_01_16_084030_CreateComponentTagTable
Migrated: 2015_02_28_214642_UpdateIncidentsAddScheduledAt
Migrated: 2015_05_19_214534_AlterTableComponentGroupsAddOrder
Migrated: 2015_05_20_073041_AlterTableIncidentsAddVisibileColumn
Migrated: 2015_05_24_210939_create_jobs_table
Migrated: 2015_05_24_210948_create_failed_jobs_table
Migrated: 2015_06_10_122216_AlterTableComponentsDropUserIdColumn
Migrated: 2015_06_10_122229_AlterTableIncidentsDropUserIdColumn
Migrated: 2015_08_02_120436_AlterTableSubscribersRemoveDeletedAt
Migrated: 2015_08_13_214123_AlterTableMetricsAddDecimalPlacesColumn
Migrated: 2015_10_31_211944_CreateInvitesTable
Migrated: 2015_11_03_211049_AlterTableComponentsAddEnabledColumn
Migrated: 2015_12_26_162258_AlterTableMetricsAddDefaultViewColumn
Migrated: 2016_01_09_141852_CreateSubscriptionsTable
Migrated: 2016_01_29_154937_AlterTableComponentGroupsAddCollapsedColumn
Migrated: 2016_02_18_085210_AlterTableMetricPointsChangeValueColumn
Migrated: 2016_03_01_174858_AlterTableMetricPointsAddCounterColumn
Migrated: 2016_03_10_144613_AlterTableComponentGroupsMakeColumnInteger
Migrated: 2016_04_05_142933_create_sessions_table
Clearing cache...
Application cache cleared!
Cache cleared!

Starting Cachet
Configuration cache cleared!
Configuration cached successfully!
2016-04-26 15:30:16,609 CRIT Supervisor running as root (no user in config file)
2016-04-26 15:30:16,625 INFO RPC interface 'supervisor' initialized
2016-04-26 15:30:16,626 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2016-04-26 15:30:16,627 INFO supervisord started with pid 1
2016-04-26 15:30:17,630 INFO spawned: 'cron' with pid 122
2016-04-26 15:30:17,633 INFO spawned: 'php-fpm7.0' with pid 123
2016-04-26 15:30:18,690 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-26 15:30:18,692 INFO success: php-fpm7.0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-26 15:45:43,153 WARN received SIGTERM indicating exit request
2016-04-26 15:45:43,189 INFO waiting for cron, php-fpm7.0 to die
2016-04-26 15:45:43,208 INFO stopped: php-fpm7.0 (exit status 0)
2016-04-26 15:45:43,211 INFO stopped: cron (terminated by SIGTERM)

Starting Cachet
Configuration cache cleared!
Configuration cached successfully!
2016-04-26 15:51:07,003 CRIT Supervisor running as root (no user in config file)
2016-04-26 15:51:07,018 INFO RPC interface 'supervisor' initialized
2016-04-26 15:51:07,019 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2016-04-26 15:51:07,019 INFO supervisord started with pid 1
2016-04-26 15:51:08,023 INFO spawned: 'cron' with pid 17
2016-04-26 15:51:08,026 INFO spawned: 'php-fpm7.0' with pid 18
2016-04-26 15:51:09,085 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-26 15:51:09,086 INFO success: php-fpm7.0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

@djdefi
Copy link
Contributor

djdefi commented Apr 27, 2016

@maitrey0da are you still getting 500 after using docker-compose?

#46 changed the architecture to include an external nginx container for serving the front end, which allows users to customize the nginx configurations if needed.

@jrabbit
Copy link

jrabbit commented Apr 29, 2016

I can replicate.

@gimler
Copy link

gimler commented May 3, 2016

I get also a 500 with 2.2.1 not with 2.2.0 see also my bug report here cachethq/cachet#1743.

The problem is that in the 2.2.1 version the key:generate doesn't write into .env

@irneh-pl
Copy link

irneh-pl commented May 4, 2016

I followed the Cachet on Docker documentation to the letter, today, with v2.2.1 and am getting the 500 error. Ubuntu 14.04.4 on EC2. In addition I started a new EC2 instance and

# git checkout v2.2.0
HEAD is now at 97886ea... Cachet v2.0.4 release

and followed the docs to the end I get a working system but if I reboot the server I only get the 500 errors.

root@ip-172-30-0-191:/home/ubuntu/cachet-docker# docker-compose up
Starting cachetdocker_postgres_1
Starting cachetdocker_cachet_1
Starting cachetdocker_nginx_1
Attaching to cachetdocker_postgres_1, cachetdocker_cachet_1, cachetdocker_nginx_1
postgres_1  | LOG:  database system was shut down at 2016-05-04 21:50:45 UTC
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
postgres_1  | LOG:  database system is ready to accept connections
postgres_1  | LOG:  autovacuum launcher started
cachet_1    | Running composer as root/super user is highly discouraged as packages, plugins and scripts cannot always be trusted
cachet_1    | Loading composer repositories with package information
cachet_1    | Installing dependencies from lock file
cachet_1    | Nothing to install or update
cachet_1    | Generating optimized autoload files
cachet_1    | > Illuminate\Foundation\ComposerScripts::postInstall
cachet_1    | > php artisan optimize --force
cachet_1    | Generating optimized class loader
cachet_1    | Compiling common classes
cachet_1    | > php artisan config:cache
cachet_1    | Configuration cache cleared!
cachet_1    | Configuration cached successfully!
cachet_1    | > php artisan route:cache
cachet_1    | Route cache cleared!
cachet_1    | Routes cached successfully!
cachet_1    | Starting supervisord...
cachet_1    | 2016-05-04 21:51:21,932 CRIT Supervisor running as root (no user in config file)
cachet_1    | 2016-05-04 21:51:21,940 INFO RPC interface 'supervisor' initialized
cachet_1    | 2016-05-04 21:51:21,941 CRIT Server 'unix_http_server' running without any HTTP authentication checking
cachet_1    | 2016-05-04 21:51:21,941 INFO supervisord started with pid 1
cachet_1    | 2016-05-04 21:51:22,944 INFO spawned: 'cron' with pid 63
cachet_1    | 2016-05-04 21:51:22,946 INFO spawned: 'php-fpm7.0' with pid 64
cachet_1    | 2016-05-04 21:51:23,979 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
cachet_1    | 2016-05-04 21:51:23,980 INFO success: php-fpm7.0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
nginx_1     | 206.169.223.194 - - [04/May/2016:21:51:29 +0000] "GET / HTTP/1.1" 500 3165 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36" "-"
nginx_1     | 206.169.223.194 - - [04/May/2016:21:51:29 +0000] "GET /favicon.ico HTTP/1.1" 200 1034 "http://52.91.172.70/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36" "-"

Did it twice (new instance, clean install, v2.2.0) and same result: works until a reboot and then only 500 errors.

@5um1th
Copy link

5um1th commented May 7, 2016

Yep I can replicate the problem too as indicated by @irneh-pl

@fdhex
Copy link

fdhex commented May 10, 2016

Same. Will try previous versions.
Edit: v2.2.0 works until a reboot.

@fdhex
Copy link

fdhex commented May 12, 2016

@GrahamCampbell any suggestion which version should be used to avoid these issues?

The 500 error on reboot is applicable to 2.1.2 as well as 2.2.0+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants