Sentry unable to run on PCF

I tried to deploy sentry on PCF, but I got the following errors that don’t look like errors. Any idea what does these means?

2017-02-24T19:24:15.53+0800 [APP/0] ERR *** Starting uWSGI 2.0.14 (64bit) on [Fri Feb 24 11:24:15 2017] ***
2017-02-24T19:24:15.53+0800 [APP/0] ERR compiled with version: 4.8.4 on 24 February 2017 00:36:48
2017-02-24T19:24:15.53+0800 [APP/0] ERR os: Linux-4.4.0-53-generic #74~14.04.1-Ubuntu SMP Fri Dec 2 03:43:31 UTC 2016
2017-02-24T19:24:15.53+0800 [APP/0] ERR nodename: 65aaab92-c2a1-4bba-77bb-29c8698c9c9e
2017-02-24T19:24:15.53+0800 [APP/0] ERR machine: x86_64
2017-02-24T19:24:15.53+0800 [APP/0] ERR clock source: unix
2017-02-24T19:24:15.53+0800 [APP/0] ERR pcre jit disabled
2017-02-24T19:24:15.53+0800 [APP/0] ERR detected number of CPU cores: 8
2017-02-24T19:24:15.53+0800 [APP/0] ERR current working directory: /home/vcap/app
2017-02-24T19:24:15.53+0800 [APP/0] ERR detected binary path: /home/vcap/app/.heroku/python/bin/uwsgi
2017-02-24T19:24:15.53+0800 [APP/0] ERR your processes number limit is 128604
2017-02-24T19:24:15.53+0800 [APP/0] ERR your memory page size is 4096 bytes
2017-02-24T19:24:15.53+0800 [APP/0] ERR detected max file descriptor number: 16384
2017-02-24T19:24:15.53+0800 [APP/0] ERR lock engine: pthread robust mutexes
2017-02-24T19:24:15.53+0800 [APP/0] ERR thunder lock: enabled
2017-02-24T19:24:15.53+0800 [APP/0] ERR uwsgi socket 0 bound to TCP address 0.0.0.0:9000 fd 3
2017-02-24T19:24:15.53+0800 [APP/0] ERR Python version: 2.7.13 (default, Dec 20 2016, 22:26:45) [GCC 4.8.4]
2017-02-24T19:24:15.53+0800 [APP/0] ERR Set PythonHome to /app/.heroku/python
2017-02-24T19:24:15.56+0800 [APP/0] ERR Python main interpreter initialized at 0x162f2b0
2017-02-24T19:24:15.56+0800 [APP/0] ERR python threads support enabled
2017-02-24T19:24:15.56+0800 [APP/0] ERR your server socket listen backlog is limited to 100 connections
2017-02-24T19:24:15.56+0800 [APP/0] ERR your mercy for graceful operations on workers is 60 seconds
2017-02-24T19:24:15.56+0800 [APP/0] ERR setting request body buffering size to 65536 bytes
2017-02-24T19:24:15.56+0800 [APP/0] ERR mapped 1922048 bytes (1877 KB) for 12 cores
2017-02-24T19:24:15.56+0800 [APP/0] ERR *** Operational MODE: preforking+threaded ***
2017-02-24T19:24:15.56+0800 [APP/0] ERR spawned uWSGI master process (pid: 46)
2017-02-24T19:24:15.56+0800 [APP/0] ERR spawned uWSGI worker 1 (pid: 50, cores: 4)
2017-02-24T19:24:15.56+0800 [APP/0] ERR spawned uWSGI worker 2 (pid: 51, cores: 4)
2017-02-24T19:24:15.56+0800 [APP/0] ERR spawned uWSGI worker 3 (pid: 52, cores: 4)
2017-02-24T19:24:17.64+0800 [APP/0] ERR WSGI app 0 (mountpoint=’’) ready in 2 seconds on interpreter 0x162f2b0 pid: 50 (default app)
2017-02-24T19:24:17.80+0800 [APP/0] ERR WSGI app 0 (mountpoint=’’) ready in 2 seconds on interpreter 0x162f2b0 pid: 51 (default app)
2017-02-24T19:24:17.82+0800 [APP/0] ERR WSGI app 0 (mountpoint=’’) ready in 2 seconds on interpreter 0x162f2b0 pid: 52 (default app)

However you set this up, it looks like Django → stderr → something. And the something assumes everything on stderr to be an ERR. Stupid something. :wink:

Same thing on journalctl:

Feb 17 14:46:19 vm-jessie bash[4300]: WSGI app 0 (mountpoint=’’) ready in 4 seconds …

In a nutshell, your server is very likely up and running.

Yeah, all of that output is normal. Everything is working fine.