Several issues after upgrading to V8

[Trulli]

We run PMG as a container on Promox 8.
After the update to PMG 8 the local DNS resolution was broken, the local dns server installed was "gone". (all resolves failed).
Manually re-installing unbound kicked me out of the local console...

2023-06-29T20:30:51.148399+02:00 mx01 pmg-smtp-filter[428]: WARNING: dns: sendto() to [127.0.0.1]:53 failed: Connection refused, failing over to [127.0.0.1]:53
2023-06-29T20:30:51.151281+02:00 mx01 pmg-smtp-filter[428]: WARNING: dns: sendto() to [127.0.0.1]:53 failed: Connection refused, failing over to [127.0.0.1]:53
2023-06-29T20:30:51.153055+02:00 mx01 pmg-smtp-filter[428]: WARNING: dns: sendto() to [127.0.0.1]:53 failed: Connection refused, failing over to [127.0.0.1]:53


resolv.conf only had 127.0.0.1 as entry (added 8.8.8.8 to be start apt-get update).

I rolled back, so no further analysis possible.

Transcript of session follows.

Out: 220 mx01.proximilan.at ESMTP mx01.proximilan.at
In: EHLO smtpout01.proximilan.at
Out: 250-mx01.proximilan.at
Out: 250-PIPELINING
Out: 250-SIZE 10485760
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-SMTPUTF8
Out: 250 CHUNKING
In: STARTTLS
Out: 220 2.0.0 Ready to start TLS
In: EHLO smtpout01.proximilan.at
Out: 250-mx01.proximilan.at
Out: 250-PIPELINING
Out: 250-SIZE 10485760
Out: 250-VRFY
Out: 250-ETRN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-SMTPUTF8
Out: 250 CHUNKING
In: MAIL FROM:<Trulli@proximilan.at> SIZE=778
Out: 250 2.1.0 Ok
In: RCPT TO:<Trulli@proximilan.at>
Out: 250 2.1.5 Ok
In: DATA
Out: 354 End data with <CR><LF>.<CR><LF>
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye

 

[dcsapak]

were there

After the update to PMG 8 the local DNS resolution was broken, the local dns server installed was "gone". (all resolves failed).

was there any message about the pacakge is to be removed during the upgrade?
any other error during upgrade?

Manually re-installing unbound kicked me out of the local console...

that shouldn't happen.. how did you install unbound exactly?

resolv.conf only had 127.0.0.1 as entry (added 8.8.8.8 to be start apt-get update).

that was probably normaly when you have configured unbound (so the local host just uses the local unbound on 127.0.0.1)

Out: 220 mx01.proximilan.at ESMTP mx01.proximilan.at
In: EHLO smtpout01.proximilan.at
Out: 250-mx01.proximilan.at
Out: 250-PIPELINING
Out: 250-SIZE 10485760
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-SMTPUTF8
Out: 250 CHUNKING
In: STARTTLS
Out: 220 2.0.0 Ready to start TLS
In: EHLO smtpout01.proximilan.at
Out: 250-mx01.proximilan.at
Out: 250-PIPELINING
Out: 250-SIZE 10485760
Out: 250-VRFY
Out: 250-ETRN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-SMTPUTF8
Out: 250 CHUNKING
In: MAIL FROM:<Trulli@proximilan.at> SIZE=778
Out: 250 2.1.0 Ok
In: RCPT TO:<Trulli@proximilan.at>
Out: 250 2.1.5 Ok
In: DATA
Out: 354 End data with <CR><LF>.<CR><LF>
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye

to debug that, we would have to have access to the journal/syslog during that time...