Plesk unter Proxmox LCX Container installieren

q-member

Member
Sep 3, 2021
35
0
11
37
Hallo zusammen!

Ich versuche gerade auf einem Linux Container Plesk zu installieren. Egal welches Betriebssystem ich installiere bekomme ich meistens folgende Fehler:

Code:
mknod: /var/www/vhosts/chroot/dev/null: Operation not permitted
chown: cannot access '/var/www/vhosts/chroot/dev/null': No such file or directory
mknod: /var/www/vhosts/chroot/dev/random: Operation not permitted
mknod: /var/www/vhosts/chroot/dev/urandom: Operation not permitted
chown: cannot access '/var/www/vhosts/chroot/dev/random': No such file or directory
chown: cannot access '/var/www/vhosts/chroot/dev/urandom': No such file or directory

Code:
Executing: /lib/systemd/systemd-sysv-install enable networking
insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
xinetd.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable xinetd

Kann mir jemand helfen ?
 
Also ich habe folgendes getan:

1659534006960.png

1659534037353.png

1659534066486.png

1659534123603.png

1659534261673.png

1659534343682.png

Bei diesen Einstellungen und der Installation bekomme ich immer den bereits genannten Fehler im log:

mknod: /var/www/vhosts/chroot/dev/null: Operation not permitted
chown: cannot access '/var/www/vhosts/chroot/dev/null': No such file or directory
mknod: /var/www/vhosts/chroot/dev/random: Operation not permitted
mknod: /var/www/vhosts/chroot/dev/urandom: Operation not permitted
chown: cannot access '/var/www/vhosts/chroot/dev/random': No such file or directory
chown: cannot access '/var/www/vhosts/chroot/dev/urandom': No such file or directory

insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
xinetd.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable xinetd

Am Ende sagt er sogar das er quasi fertig ist ... im Plesk gibt es dann aber auch diverse Fehler:

1659538608445.png

Hier beispielsweise in der Prozessliste
 

Attachments

  • 1659534204312.png
    1659534204312.png
    87.8 KB · Views: 2
probier mal die mknod option fuer deinen container einzusetzen: pct set 200 -features nesting=1,mknod=1 (oder im GUI unter "Options -> Features -> Create Device Nodes")
 
Habe mit der Option andere Fehler nach der Installation:

Dieser Fehler kommt wenn ich das System überprüfen lasse:

Code:
The operation failed with the following error: {"id":1,"cmd":"plesk repair fs -n","type":"progress","message":"Checking Linux system files","level":0} {"id":2,"cmd":"plesk repair fs -n","type":"error","message":"There are incorrect permissions on some items: \/dev\/null","level":1} {"id":3,"cmd":"plesk repair fs -n","type":"error","message":"There are incorrect permissions on some items: \/dev\/random","level":1} {"id":4,"cmd":"plesk repair fs -n","type":"error","message":"There are incorrect permissions on some items: \/dev\/urandom","level":1} {"id":5,"cmd":"plesk repair fs -n","type":"progress","message":"Checking virtual hosts' file system","level":0} {"id":5,"cmd":"plesk repair fs -n","type":"success","message":"Checking virtual hosts' file system","level":0}

1659605605154.png

Wenn ich Repair sage:

Code:
The operation failed with the following error: {"id":1,"cmd":"plesk repair fs -y","type":"progress","message":"Checking Linux system files","level":0} {"id":2,"cmd":"plesk repair fs -y","type":"error","message":"There are incorrect permissions on some items: \/dev\/null","level":1} {"id":3,"cmd":"plesk repair fs -y","type":"progress","message":"Repairing incorrect permissions","level":2} {"id":3,"cmd":"plesk repair fs -y","type":"failed","message":"Repairing incorrect permissions","level":2} {"id":3,"cmd":"plesk repair fs -y","type":"failed","message":"Repairing incorrect permissions","level":2,"details":"fsmng failed: ERROR:[Errno 1] Operation not permitted:\n'\/dev\/null'\n"} {"id":4,"cmd":"plesk repair fs -y","type":"error","message":"There are incorrect permissions on some items: \/dev\/random","level":1} {"id":5,"cmd":"plesk repair fs -y","type":"progress","message":"Repairing incorrect permissions","level":2} {"id":5,"cmd":"plesk repair fs -y","type":"failed","message":"Repairing incorrect permissions","level":2} {"id":5,"cmd":"plesk repair fs -y","type":"failed","message":"Repairing incorrect permissions","level":2,"details":"fsmng failed: ERROR:[Errno 1] Operation not permitted:\n'\/dev\/random'\n"} {"id":6,"cmd":"plesk repair fs -y","type":"error","message":"There are incorrect permissions on some items: \/dev\/urandom","level":1} {"id":7,"cmd":"plesk repair fs -y","type":"progress","message":"Repairing incorrect permissions","level":2} {"id":7,"cmd":"plesk repair fs -y","type":"failed","message":"Repairing incorrect permissions","level":2} {"id":7,"cmd":"plesk repair fs -y","type":"failed","message":"Repairing incorrect permissions","level":2,"details":"fsmng failed: ERROR:[Errno 1] Operation not permitted:\n'\/dev\/urandom'\n"} {"id":8,"cmd":"plesk repair fs -y","type":"progress","message":"Checking virtual hosts' file system","level":0} {"id":8,"cmd":"plesk repair fs -y","type":"success","message":"Checking virtual hosts' file system","level":0}


Im Bereich der Prozessliste:

Code:
An error has occurred while receiving disk operations usage. Stdout: Stderr: Traceback (most recent call last): File "/usr/sbin/iotop", line 17, in main() File "/usr/lib/python3/dist-packages/iotop/ui.py", line 737, in main main_loop() File "/usr/lib/python3/dist-packages/iotop/ui.py", line 727, in main_loop = lambda: run_iotop(options) File "/usr/lib/python3/dist-packages/iotop/ui.py", line 618, in run_iotop return run_iotop_window(None, options) File "/usr/lib/python3/dist-packages/iotop/ui.py", line 609, in run_iotop_window taskstats_connection = TaskStatsNetlink(options) File "/usr/lib/python3/dist-packages/iotop/data.py", line 151, in __init__ self.family_id = controller.get_family_id('TASKSTATS') File "/usr/lib/python3/dist-packages/iotop/genetlink.py", line 76, in get_family_id m = GeNlMessage.recv(self.conn) File "/usr/lib/python3/dist-packages/iotop/genetlink.py", line 56, in recv msg = conn.recv() File "/usr/lib/python3/dist-packages/iotop/netlink.py", line 255, in recv raise err OSError: Netlink error: No such file or directory (2) Exit code: 1

Bei der Installation sind mir folgende Fehler aufgefallen:

Code:
dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x

Job for dovecot.service failed because the control process exited with error code.
See "systemctl status dovecot.service" and "journalctl -xe" for details.
 Trying to switch Horde Ingo backend to 'sieve'... Ingo doesn't seem to be installed. Skip.
 Trying to start service dovecot... inactive
 
 ***** installing problem report *****
Warning: start service dovecot failed
***** installing problem report *****
Warning: start service dovecot failed
STOP plesk-dovecot-2.3.18 installing AT Thu Aug  4 09:07:41 UTC 2022: PROBLEMS FOUND

ERROR: Upgrade step 2019-02-19-12-00-23_EnableSpfDkimDmarc.php failed with code 1 and output:
INFO: Executing upgrade task: 2019-02-19-12-00-23 (clean)
[2022-08-04 09:08:16.404] 26972:62eb8c8062a1b ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/mailmng-service' '--restart-service' '--mail-component=all'] with exit code [1]
[2022-08-04 09:08:16.487] 26972:62eb8c8062a1b ERR [panel] mailmng-service failed: :
0: /opt/psa/admin/plib/Upgrade/upgrade.php:46
ERROR: Plesk\Upgrade\Exception: mailmng-service failed:  (upgrade.php:46)
0: /opt/psa/admin/plib/Upgrade/upgrade.php:46

insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
***** installing problem report *****
Warning: execute post install/upgrade actions
***** installing problem report *****
Warning: execute post install/upgrade actions
STOP plesk-core-18.0 installing AT Thu Aug  4 09:08:37 UTC 2022: PROBLEMS FOUND
xinetd.service is not a native service, redirecting to systemd-sysv-install.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!