run to almalinux9 qcow2 faild,and proxmox connecnt faild

akaishuichi

New Member
Aug 29, 2022
2
0
1
I need help!
sorry to bother you guys:confused:

I run to qcow2,and restart server,but proxmox connect faild...:eek:
let‘s ...

Bash:
qm importdisk 106 AlmaLinux-9-GenericCloud-latest.x86_64.qcow2 local-lvm --format=qcow2
reboot

#############################################################################################

root@AlmaLinux9-69:~# journalctl -xe
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[7122]: starting 1 worker(s)
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[7122]: worker 9347 started
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[9346]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891.
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[9347]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891.
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[9345]: worker exit
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[7122]: worker 9345 finished
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[7122]: starting 1 worker(s)
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[7122]: worker 9348 started
Aug 29 20:16:58 AlmaLinux9-69 pveproxy[9348]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891.
Aug 29 20:17:00 AlmaLinux9-69 systemd[1]: Starting Proxmox VE replication runner...
░░ Subject: A start job for unit pvesr.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvesr.service has begun execution.
░░
░░ The job identifier is 20616.
Aug 29 20:17:01 AlmaLinux9-69 cron[2057]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Aug 29 20:17:01 AlmaLinux9-69 pvesr[9349]: ipcc_send_rec[1] failed: Connection refused
Aug 29 20:17:01 AlmaLinux9-69 pvesr[9349]: ipcc_send_rec[2] failed: Connection refused
Aug 29 20:17:01 AlmaLinux9-69 pvesr[9349]: ipcc_send_rec[3] failed: Connection refused
Aug 29 20:17:01 AlmaLinux9-69 pvesr[9349]: Unable to load access control list: Connection refused
Aug 29 20:17:01 AlmaLinux9-69 CRON[9350]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Aug 29 20:17:01 AlmaLinux9-69 CRON[9351]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Aug 29 20:17:01 AlmaLinux9-69 CRON[9350]: pam_unix(cron:session): session closed for user root
Aug 29 20:17:01 AlmaLinux9-69 systemd[1]: pvesr.service: Main process exited, code=exited, status=111/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pvesr.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 111.
Aug 29 20:17:01 AlmaLinux9-69 systemd[1]: pvesr.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvesr.service has entered the 'failed' state with result 'exit-code'.
Aug 29 20:17:01 AlmaLinux9-69 systemd[1]: Failed to start Proxmox VE replication runner.
░░ Subject: A start job for unit pvesr.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvesr.service has finished with a failure.
░░
░░ The job identifier is 20616 and the job result is failed.
Aug 29 20:17:03 AlmaLinux9-69 pveproxy[9346]: worker exit
Aug 29 20:17:03 AlmaLinux9-69 pveproxy[9347]: worker exit
Aug 29 20:17:03 AlmaLinux9-69 pveproxy[7122]: worker 9346 finished
Aug 29 20:17:03 AlmaLinux9-69 pveproxy[7122]: starting 1 worker(s)
Aug 29 20:17:03 AlmaLinux9-69 pveproxy[7122]: worker 9354 started

##############################################################################################
root@AlmaLinux9-69:~# cat /etc/hosts
# Your system has configured 'manage_etc_hosts' as True.
# As a result, if you wish for changes to this file to persist
# then you will need to either
# a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl
# b.) change or remove the value of 'manage_etc_hosts' in
#     /etc/cloud/cloud.cfg or cloud-config from user-data
#
# 127.0.1.1 AlmaLinux9-69.14 AlmaLinux9-69
127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
# ::1 ip6-localhost ip6-loopback
# fe00::0 ip6-localnet
# ff00::0 ip6-mcastprefix
# ff02::1 ip6-allnodes
# ff02::2 ip6-allrouters
# ff02::3 ip6-allhosts


How do I recover? Thank you for youro_O
 
supplement... o_O

1661775783034.png



I chose Proxy local network when I created it, I don't know if it's related to that;
But I don't know how to recover the first time using it
 

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!