1. 11 Dec, 2018 1 commit
  2. 10 Dec, 2018 6 commits
  3. 07 Dec, 2018 12 commits
  4. 04 Dec, 2018 3 commits
  5. 02 Dec, 2018 1 commit
  6. 30 Nov, 2018 1 commit
  7. 28 Nov, 2018 12 commits
  8. 25 Nov, 2018 2 commits
  9. 23 Nov, 2018 2 commits
    • Chris Lamb's avatar
      Don't treat unsupported protocols as fatal errors · fbff3514
      Chris Lamb authored
      If we encounter an unsupported protocol in the "bind" list, don't
      ipso-facto consider it a fatal error. We continue to abort startup if
      there are no listening sockets at all.
      
      This ensures that the lack of IPv6 support does not prevent Redis from
      starting on Debian where we try to bind to the ::1 interface by default
      (via "bind 127.0.0.1 ::1"). A machine with IPv6 disabled (such as some
      container systems) would simply fail to start Redis after the initiall
      call to apt(8).
      
      This is similar to the case for where "bind" is not specified:
      
        https://github.com/antirez/redis/issues/3894
      
      ... and was based on the corresponding PR:
      
        https://github.com/antirez/redis/pull/4108
      
      ... but also adds EADDRNOTAVAIL to the list of errors to catch which I
      believe is missing from there.
      
      This issue was raised in Debian as both <https://bugs.debian.org/900284>
      & <https://bugs.debian.org/914354>.
      fbff3514
    • Chris Lamb's avatar
      Clarify the "Creating Server TCP listening socket" error. · 9cfcf379
      Chris Lamb authored
      This really helps spot it in the logs, otherwise it does not look like a
      warning/error. For example:
      
        Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address
      
      ... is not nearly as clear as:
      
        Could not create server TCP listening listening socket ::1:6379: bind: Cannot assign requested address
      9cfcf379