Loading ...
Sorry, an error occurred while loading the content.

Postfix has a bizarre dependency and does not start

Expand Messages
  • James Moe
    ... Hash: SHA1 opensuse 13.1 postfix 2.9.6-7.4.1 I recently upgraded a server from 12.3 to 13.1. Postfix worked correctly in v12.3. Postfix fails to start with
    Message 1 of 9 , Jun 3, 2014
    • 0 Attachment
      -----BEGIN PGP SIGNED MESSAGE-----
      Hash: SHA1


      opensuse 13.1
      postfix 2.9.6-7.4.1

      I recently upgraded a server from 12.3 to 13.1. Postfix worked
      correctly in v12.3.

      Postfix fails to start with this message:

      Code:
      - -- Unit postfix.service has failed.
      - --
      - -- The result is dependency.
      Jun 03 10:59:24 sma-server3 systemd[1]: t2.mount mount process exited,
      code=exited status=32
      Jun 03 10:59:24 sma-server3 systemd[1]: Failed to mount /t2.

      While annoying that mount point /t2 no longer starts (yet another
      upgrade problem), I see no reason for postfix to be fixated on its
      presence.

      Where are such dependencies defined?


      - --
      James Moe
      moe dot james at sohnen-moe dot com
      520.743.3936
      -----BEGIN PGP SIGNATURE-----
      Version: GnuPG v2.0.22 (GNU/Linux)
      Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

      iEYEARECAAYFAlOOYzoACgkQzTcr8Prq0ZNycwCgi8RnDVbKrUg1kMBjqbM5DsTL
      wnkAnjJCedZPmCQCNyOqAwMAWksRLz3r
      =tbtm
      -----END PGP SIGNATURE-----
    • Wietse Venema
      ... To view Postfix built-in file system depencencies: $ postconf | egrep _(directory|path) = Maybe that causes the coint to drop. Wietse
      Message 2 of 9 , Jun 3, 2014
      • 0 Attachment
        James Moe:
        > opensuse 13.1
        > postfix 2.9.6-7.4.1
        >
        > I recently upgraded a server from 12.3 to 13.1. Postfix worked
        > correctly in v12.3.
        >
        > Postfix fails to start with this message:
        >
        > Code:
        > -- Unit postfix.service has failed.
        > --
        > -- The result is dependency.
        > Jun 03 10:59:24 sma-server3 systemd[1]: t2.mount mount process exited,
        > code=exited status=32
        > Jun 03 10:59:24 sma-server3 systemd[1]: Failed to mount /t2.
        >
        > While annoying that mount point /t2 no longer starts (yet another
        > upgrade problem), I see no reason for postfix to be fixated on its
        > presence.
        >
        > Where are such dependencies defined?

        To view Postfix built-in file system depencencies:

        $ postconf | egrep '_(directory|path) ='

        Maybe that causes the coint to drop.

        Wietse
      • James Moe
        ... Hash: SHA1 ... No, that did not show /t2 anywhere as a dependency. postconf | egrep t2 produced no results, either. - -- James Moe moe dot james at
        Message 3 of 9 , Jun 3, 2014
        • 0 Attachment
          -----BEGIN PGP SIGNED MESSAGE-----
          Hash: SHA1

          On 06/03/2014 05:33 PM, Wietse Venema wrote:
          >
          > $ postconf | egrep '_(directory|path) ='
          >
          > Maybe that causes the coin to drop.
          >
          No, that did not show "/t2" anywhere as a dependency.
          "postconf | egrep 't2'" produced no results, either.


          - --
          James Moe
          moe dot james at sohnen-moe dot com
          520.743.3936
          -----BEGIN PGP SIGNATURE-----
          Version: GnuPG v2.0.22 (GNU/Linux)
          Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

          iEYEARECAAYFAlOOdJAACgkQzTcr8Prq0ZN2VACfYShZzwxB+LDJ/mRbK6af9nok
          uK4AoI1B3bZT/uZvRIPGJPKHIHDt2J1n
          =u32Q
          -----END PGP SIGNATURE-----
        • Viktor Dukhovni
          ... How is anyone on the list supposed to know about configuration details of your systemd environment. ... Nothing in Postfix itself knows anything about
          Message 4 of 9 , Jun 3, 2014
          • 0 Attachment
            On Tue, Jun 03, 2014 at 05:07:22PM -0700, James Moe wrote:

            > Postfix fails to start with this message:
            >
            > Code:
            > - -- Unit postfix.service has failed.
            > - --
            > - -- The result is dependency.
            > Jun 03 10:59:24 sma-server3 systemd[1]: t2.mount mount process exited,
            > code=exited status=32
            > Jun 03 10:59:24 sma-server3 systemd[1]: Failed to mount /t2.

            How is anyone on the list supposed to know about configuration
            details of your systemd environment.

            > While annoying that mount point /t2 no longer starts (yet another
            > upgrade problem), I see no reason for postfix to be fixated on its
            > presence.

            Nothing in Postfix itself knows anything about mount points.

            > Where are such dependencies defined?

            In the systemd configuration.

            --
            Viktor.
          • jdebert
            On Tue, 03 Jun 2014 17:07:22 -0700 ... Was that message produced by systemd? What happens if you do as root: postfix check and postfix start ? What does the
            Message 5 of 9 , Jun 3, 2014
            • 0 Attachment
              On Tue, 03 Jun 2014 17:07:22 -0700
              James Moe <jimoe@...> wrote:

              > -----BEGIN PGP SIGNED MESSAGE-----
              > Hash: SHA1
              >
              >
              > opensuse 13.1
              > postfix 2.9.6-7.4.1
              >
              > I recently upgraded a server from 12.3 to 13.1. Postfix worked
              > correctly in v12.3.
              >
              > Postfix fails to start with this message:
              >
              > Code:
              > - -- Unit postfix.service has failed.
              > - --
              > - -- The result is dependency.
              > Jun 03 10:59:24 sma-server3 systemd[1]: t2.mount mount process exited,
              > code=exited status=32
              > Jun 03 10:59:24 sma-server3 systemd[1]: Failed to mount /t2.
              >

              Was that message produced by systemd?

              What happens if you do as root: 'postfix check' and 'postfix start'?

              What does the system log tell you?

              jd
            • James Moe
              ... Hash: SHA1 ... The mount errors are spurious for loading Postfix, as some have noted. I finally found a place where postfix errors show up (journalctl
              Message 6 of 9 , Jun 3, 2014
              • 0 Attachment
                -----BEGIN PGP SIGNED MESSAGE-----
                Hash: SHA1

                On 06/03/2014 05:07 PM, James Moe wrote:
                > opensuse 13.1 postfix 2.9.6-7.4.1
                >
                > I recently upgraded a server from 12.3 to 13.1. Postfix worked
                > correctly in v12.3.
                >
                The mount errors are spurious for loading Postfix, as some have noted.
                I finally found a place where postfix errors show up (journalctl -xn).

                Jun 03 23:20:10 sma-server3 postfix[10741]: name_mask: all
                Jun 03 23:20:10 sma-server3 postfix[10741]: inet_addr_local:
                configured 2 IPv4 addresses
                Jun 03 23:20:10 sma-server3 postfix[10741]: inet_addr_local:
                configured 2 IPv6 addresses
                Jun 03 23:20:10 sma-server3 postfix/postfix-script[10810]: starting
                the Postfix mail system
                Jun 03 23:20:10 sma-server3 postfix/master[10811]: fatal: bind
                2002:c0a8:45f6::c0a8:45f6 port 126: Cannot assign requested address

                Port 126 is defined since port 25 is used by the main MTA. I am
                using postfix as a local transport.
                The port bind seems to be a IPv6 issue. Is there some way to prevent
                that?

                - --
                James Moe
                moe dot james at sohnen-moe dot com
                520.743.3936
                -----BEGIN PGP SIGNATURE-----
                Version: GnuPG v2.0.22 (GNU/Linux)
                Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

                iEYEARECAAYFAlOOwGQACgkQzTcr8Prq0ZMzqQCcDJWTG/hN/+bty1j0mxw8qB2s
                /SkAnAr1b4ld3MGM9KVKL/MW1k2/2IJJ
                =ccCp
                -----END PGP SIGNATURE-----
              • M. Rodrigo Monteiro
                ... inet_protocols = ipv4 - --
                Message 7 of 9 , Jun 4, 2014
                • 0 Attachment



                  2014-06-04 3:44 GMT-03:00 James Moe <jimoe@...>:
                  -----BEGIN PGP SIGNED MESSAGE-----
                  Hash: SHA1


                    Port 126 is defined since port 25 is used by the main MTA. I am
                  using postfix as a local transport.
                    The port bind seems to be a IPv6 issue. Is there some way to prevent
                  that?


                  inet_protocols = ipv4

                  - --
                  James Moe
                  moe dot james at sohnen-moe dot com
                  520.743.3936
                  -----BEGIN PGP SIGNATURE-----
                  Version: GnuPG v2.0.22 (GNU/Linux)
                  Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

                  iEYEARECAAYFAlOOwGQACgkQzTcr8Prq0ZMzqQCcDJWTG/hN/+bty1j0mxw8qB2s
                  /SkAnAr1b4ld3MGM9KVKL/MW1k2/2IJJ
                  =ccCp
                  -----END PGP SIGNATURE-----

                • Wietse Venema
                  ... Are they running Postfix with verbose mode turned on? That will totally destroy performance. ... Look for SeLinux or similar configuration. Wietse
                  Message 8 of 9 , Jun 4, 2014
                  • 0 Attachment
                    James Moe:
                    > Jun 03 23:20:10 sma-server3 postfix[10741]: name_mask: all
                    > Jun 03 23:20:10 sma-server3 postfix[10741]: inet_addr_local:
                    > configured 2 IPv4 addresses
                    > Jun 03 23:20:10 sma-server3 postfix[10741]: inet_addr_local:
                    > configured 2 IPv6 addresses

                    Are they running Postfix with verbose mode turned on?
                    That will totally destroy performance.

                    > Jun 03 23:20:10 sma-server3 postfix/master[10811]: fatal: bind
                    > 2002:c0a8:45f6::c0a8:45f6 port 126: Cannot assign requested address
                    >
                    > Port 126 is defined since port 25 is used by the main MTA. I am
                    > using postfix as a local transport.
                    > The port bind seems to be a IPv6 issue. Is there some way to prevent
                    > that?

                    Look for SeLinux or similar configuration.

                    Wietse
                  • James Moe
                    ... Hash: SHA1 ... Thank you. That has allowed Postfix to start. - -- James Moe moe dot james at sohnen-moe dot com 520.743.3936 ... Version: GnuPG v2.0.22
                    Message 9 of 9 , Jun 4, 2014
                    • 0 Attachment
                      -----BEGIN PGP SIGNED MESSAGE-----
                      Hash: SHA1

                      On 06/04/2014 04:38 AM, M. Rodrigo Monteiro wrote:
                      > The port bind seems to be a IPv6 issue. Is there some way to
                      > prevent that?
                      >
                      > inet_protocols = ipv4
                      >
                      Thank you. That has allowed Postfix to start.

                      - --
                      James Moe
                      moe dot james at sohnen-moe dot com
                      520.743.3936
                      -----BEGIN PGP SIGNATURE-----
                      Version: GnuPG v2.0.22 (GNU/Linux)
                      Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

                      iEYEARECAAYFAlOPfmgACgkQzTcr8Prq0ZNSSwCfU0ggDBCOr/eaDlRVoIsCkvzh
                      qzEAoKmMZc75kb4ZojX9pn/GS+E8Lorw
                      =djiP
                      -----END PGP SIGNATURE-----
                    Your message has been successfully submitted and would be delivered to recipients shortly.