Advertisement
Guest User

Untitled

a guest
Jan 18th, 2018
76
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.39 KB | None | 0 0
  1. Attaching to radiofm20_postgres_1, radiofm20_redis_1, radiofm20_web_1
  2. postgres_1 | LOG: database system was shut down at 2018-01-18 18:03:38 UTC
  3. redis_1 | 1:C 18 Jan 18:04:36.379 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
  4. redis_1 | 1:C 18 Jan 18:04:36.379 # Redis version=4.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
  5. redis_1 | 1:C 18 Jan 18:04:36.379 # Configuration loaded
  6. redis_1 | 1:M 18 Jan 18:04:36.381 * Running mode=standalone, port=6379.
  7. redis_1 | 1:M 18 Jan 18:04:36.381 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
  8. redis_1 | 1:M 18 Jan 18:04:36.381 # Server initialized
  9. redis_1 | 1:M 18 Jan 18:04:36.381 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
  10. redis_1 | 1:M 18 Jan 18:04:36.381 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
  11. redis_1 | 1:M 18 Jan 18:04:36.382 * DB loaded from append only file: 0.000 seconds
  12. redis_1 | 1:M 18 Jan 18:04:36.382 * Ready to accept connections
  13. postgres_1 | LOG: MultiXact member wraparound protections are now enabled
  14. postgres_1 | LOG: database system is ready to accept connections
  15. postgres_1 | LOG: autovacuum launcher started
  16. web_1 | 18:04:37 web.1 | started with pid 8
  17. web_1 | 18:04:43 web.1 | => Booting Puma
  18. web_1 | 18:04:43 web.1 | => Rails 5.1.4 application starting in development
  19. web_1 | 18:04:43 web.1 | => Run `rails server -h` for more startup options
  20. web_1 | 18:04:43 web.1 | Puma starting in single mode...
  21. web_1 | 18:04:43 web.1 | * Version 3.11.0 (ruby 2.4.3-p205), codename: Love Song
  22. web_1 | 18:04:43 web.1 | * Min threads: 5, max threads: 5
  23. web_1 | 18:04:43 web.1 | * Environment: development
  24. web_1 | 18:04:43 web.1 | * Listening on tcp://localhost:5000
  25. web_1 | 18:04:43 web.1 | Use Ctrl-C to stop
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement