Bug 1216307

Summary: postfix cannot start up if ipV6 got disabled but address '::1' still remained in /etc/hosts
Product: [openSUSE] openSUSE Tumbleweed Reporter: Zaoliang Luo <zluo>
Component: BasesystemAssignee: Peter Varkoly <varkoly>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: amajer, miika.alikirri
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Zaoliang Luo 2023-10-17 07:43:22 UTC
Install Tumbleweed (ipV6 got disabled) and enable cockpit webUI.

I found there is error from postfix that cannot start up:

--
postfix
fatal: parameter inet_interfaces: no local interface found for ::1
PRIORITY
2
SYSLOG_FACILITY
2
SYSLOG_IDENTIFIER
postfix
SYSLOG_PID
8952
SYSLOG_TIMESTAMP
Oct 12 09:53:34
_BOOT_ID
1a1a57e1ddea4c91a80d0a8fec871673
_CAP_EFFECTIVE
1f3f5fcffff
_CMDLINE
/usr/sbin/postfix stop
_COMM
postfix
_EXE
/usr/sbin/postfix
_GID
0
_HOSTNAME
d4-123
_MACHINE_ID
1d71abea49394c9f91e030b83b716bd5
_PID
8952
_RUNTIME_SCOPE
system
_SOURCE_REALTIME_TIMESTAMP
1697097214641690
_SYSTEMD_CGROUP
/system.slice/postfix.service
_SYSTEMD_INVOCATION_ID
a34279f64b3e45f7bcdf6c517cc54ff7
_SYSTEMD_SLICE
system.slice
_SYSTEMD_UNIT
postfix.service
_TRANSPORT
syslog
_UID
0
__CURSOR
s=cd4431e0e4c14554b6fe9c75f02650f6;i=607d;b=1a1a57e1ddea4c91a80d0a8fec871673;m=d8f108981;t=607803ca0c61f;x=4cd8cb6e810c80c9
__MONOTONIC_TIMESTAMP
58234800513
__REALTIME_TIMESTAMP
1697097214641695
__SEQNUM
24701
__SEQNUM_ID
cd4431e0e4c14554b6fe9c75f02650f6

--

found out the problem is in /etc/hosts

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback


remove or comment this line with #, postfix can start up.
Comment 1 Miika Alikirri 2023-10-18 12:45:08 UTC
Hi!

Is your postfix configured to only support ipv4?

You can check it by running this:
```
# grep inet_protocols /etc/postfix/main.cf
```

If you see this, postfix is configured to use both ipv4 and ipv6:
```
inet_protocols = all
```

And you can fix it by changing the value to ipv4, like this:
```
inet_protocols = ipv4
```
Comment 2 Adam Majer 2023-10-18 12:56:36 UTC
To be honest, this sounds like a postfix configuration issue and it's unrelated to cockpit.

Re-assigning to postfix maintainer
Comment 3 Zaoliang Luo 2023-10-19 07:43:25 UTC
(In reply to Miika Alikirri from comment #1)
> Hi!
> 
> Is your postfix configured to only support ipv4?
> 
> You can check it by running this:
> ```
> # grep inet_protocols /etc/postfix/main.cf
> ```
> 
> If you see this, postfix is configured to use both ipv4 and ipv6:
> ```
> inet_protocols = all
> ```
> 
> And you can fix it by changing the value to ipv4, like this:
> ```
> inet_protocols = ipv4
> ```

I didn't realize this has to do with inet_protocols.

So it will be nice to check network setting (ipv4/6) before starting postfix?

Please feel free to close this report, thanks!
Comment 4 Peter Varkoly 2024-06-11 10:56:34 UTC
ok