Question Update Obsidian 18.0.44 from Debian 9.13 to 10 or 11

[straddi]

Server operating system version

debian 9.13

Plesk version and microupdate number

18.0.44

Hallo,
I want to update from Debian 9.13. Is it better to upgrade from 9 to 10 and then from 10 to 11 or can I upgrade from 9 to 11 straight away?
The next question is how do I best update my server?
With dist-upgrade or with the Plesk Migration Tool?
Does anyone have experience with it and can give me a tip?
Thank you
Straddi

 

[IgorG]

Try to perform dist-upgrade with this instruction: https://support.plesk.com/hc/en-us/...upgrade-procedure-on-Linux-server-with-Plesk-

 

[straddi]

Many thanks for the answer.

I have the following problem:

Update source.list file and configure the repository for the OS release that is going to upgrade to:

my file looks like this:

deb Index of /debian stretch main contrib non-free
deb Index of /debian stretch-updates main contrib non-free
deb Debian -- Security Information stretch/updates main contrib non-free

## deb Atomicorp stretch main

The instructions say: Only the highlighted line is to be updated/edited
the line deb http://autoinstall.plesk.com/PSA_18.0.37/ buster all is highlighted

I don't have this line

 

[straddi]

Ok, I think I misunderstood something. My source.list is to be replaced by the one listed and the line is to be updated. I had overlooked the "replaced".

 

[straddi]

I tried to update debian from 9 to 10. I got the following error at the end after apt-get dist-upgrade.

bind9-resolvconf.service is a disabled or a static unit not running, not starting it./etc/network/if-up.d/bind9Job for bind9.service failed because a timeout was exceeded.
See "systemctl status bind9.service" and "journalctl -xe" for details.
invoke-rc.d: initscript bind9, action "restart" failed.
● bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; disabled; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2022-07-26 11:01:39 CEST; 19ms ago
Docs: man:named(8)
Process: 26685 ExecStart=/usr/sbin/named $OPTIONS (code=exited, status=0/SUCCESS)

Jul 26 11:00:09 server1.xxxxx.de named[26685]: running
Jul 26 11:01:39 server1.xxxxx.de systemd[1]: bind9.service: Start operation timed out. terminating.
Jul 26 11:01:39 server1.xxxxx.de named[26685]: shutting down
Jul 26 11:01:39 server1.xxxxx.de named[26685]: stopping command channel on 127.0.0.1#953
Jul 26 11:01:39 server1.xxxxx.de named[26685]: no longer listening on ::#53
Jul 26 11:01:39 server1.xxxxx.de named[26685]: no longer listening on 127.0.0.1#53
Jul 26 11:01:39 server1.xxxxx.de named[26685]: no longer listening on 89.xxxxxx.xxx#53
Jul 26 11:01:39 server1.xxxxx.de named[26685]: exiting
Jul 26 11:01:39 server1.xxxxx.de systemd[1]: bind9.service: Failed with result 'timeout'.
Jul 26 11:01:39 server1.xxxxx.de systemd[1]: Failed to start BIND Domain Name Server.
dpkg: error processing package bind9 (--configure):
installed bind9 package post-installation script subprocess returned error exit status 1
Setting up libxml-parser-perl (2.44-4) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-21-amd64
I: The initramfs will attempt to resume from /dev/null
I: Set the RESUME variable to override this.
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libapache2-mod-php7.1 (7.1.33-45+0~20220614.66+debian9~1.gbpd98023) ...
Processing triggers for libglib2.0-0:amd64 (2.58.3-2+deb10u3) ...
Processing triggers for libc-bin (2.28-10+deb10u1) ...
Processing triggers for libapache2-mod-php7.3 (7.3.33-2+0~20220614.96+debian9~1.gbpe53774) ...
Processing triggers for systemd (241-7~deb10u8) ...
Processing triggers for dbus (1.12.20-0+deb10u1) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for mime support (3.62) ...
Processing triggers for dictionaries-common (1.28.1) ...
Processing triggers for spamassassin (3.4.2-1+deb10u3) ...
OK, restarting spamd due to trigger
Processing triggers for sa-compile (3.4.2-1+deb10u3) ...
Running sa-compile (may take a long time)
'/etc/network/if-down.d/bind9Errors were encountered while processing:
bind9
E: Sub-process /usr/bin/dpkg returned an error code (1)

Plesk could also not be updated via the installer. The installation log showed the same error message. I tried to uninstall and reinstall bind9 with apt remove. That didn't help either. Same error message. Plesk could only be updated after uninstalling bind9.

Hence the question. Is bind9 important or can I leave it uninstalled.

Thank you
Straddi

 

[TobiasP]

Hi,
yes bind9 is needed for the DNS management functionality of plesk - maybe this will help you:

Resolved - DNS does not start via systemd

Hello, i have a problem with starting bind9 as a service. systemctl start bind9.service waits about 15 seconds on the console. OS ‪Debian 9.7‬ Product Plesk Onyx Version 17.8.11 Update #37, systemctl start bind9.service shows: â bind9.service - BIND Domain Name Server Loaded: loaded...

talk.plesk.com

it seems you bind9 is also started with /usr/sbin/named $OPTIONS but it should be /usr/sbin/named -f $OPTIONS

 

[TobiasP]

May I hijack this thread for a question of my own regarding the dist-upgrade?

switching to MSMTP wants me to wants me to uninstall dovecot - is this really necessary? will this remove mailboxes from the server or will they be there after I reinstall dovecot after the upgrade? what happens if I dont switch to msmtp and do the upgrade?

 

[TobiasP]

Hi,
yes bind9 is needed for the DNS management functionality of plesk - maybe this will help you:

Resolved - DNS does not start via systemd

Hello, i have a problem with starting bind9 as a service. systemctl start bind9.service waits about 15 seconds on the console. OS ‪Debian 9.7‬ Product Plesk Onyx Version 17.8.11 Update #37, systemctl start bind9.service shows: â bind9.service - BIND Domain Name Server Loaded: loaded...

talk.plesk.com

it seems you bind9 is also started with /usr/sbin/named $OPTIONS but it should be /usr/sbin/named -f $OPTIONS

But I can report that I have the same issue after following the upgrade steps! after changing it to -f $OPTIONS I get:

Jul 27 01:12:11 lemon named[2607]: open: /etc/named.conf: permission denied
Jul 27 01:12:11 lemon named[2607]: loading configuration: permission denied
Jul 27 01:12:11 lemon named[2607]: exiting (due to fatal error)
Jul 27 01:12:11 lemon systemd[1]: bind9.service: Control process exited, code=exited, status=1/FAILURE
Jul 27 01:12:11 lemon systemd[1]: bind9.service: Failed with result 'exit-code'.
Jul 27 01:12:11 lemon systemd[1]: Failed to start BIND Domain Name Server.

but I don't (think) I have apparmor enabled but I followed https://support.plesk.com/hc/en-us/articles/115003139849 anyway but still cant start bind9 - after running service bind9 start:

Jul 27 01:19:53 lemon systemd[1]: bind9.service: Start operation timed out. Terminating.
Jul 27 01:19:53 lemon named[3258]: shutting down
Jul 27 01:19:53 lemon named[3258]: stopping command channel on 127.0.0.1#953
Jul 27 01:19:53 lemon named[3258]: no longer listening on ::#53
Jul 27 01:19:53 lemon named[3258]: no longer listening on 127.0.0.1#53
Jul 27 01:19:53 lemon named[3258]: no longer listening on 192.168.101.1#53
Jul 27 01:19:53 lemon named[3258]: no longer listening on 172.17.0.1#53
Jul 27 01:19:53 lemon named[3258]: exiting
Jul 27 01:19:53 lemon systemd[1]: bind9.service: Failed with result 'timeout'.
Jul 27 01:19:53 lemon systemd[1]: Failed to start BIND Domain Name Server.

 

[TobiasP]

sorry quick followup:
I only removed the Type=forking from then I followed the link above to fix apparmor then I made sure apparmor is running and then I could start bind again

 

[straddi]

Hi Tobias,
reinstall Postfix and dovecot after the upgrade and everything works again. At least that's how it was for me.
Regarding bind9. I uninstalled it via apt remove and reinstalled it via Plesk installer. After that it starts again.