I've been working on this issue for a few days and I'm getting nowhere with resolving or even understanding the underlying issue.
I have two Proxmox systems; moxprox0, moxprox1. moxprox0 is my primary server host and moxprox1 is a desktop node I want to use for when moxprox0 need to go offline but keep the VMs running. Both nodes are on the same subnet (10.0.30.0/24), they are joined into a cluster...
The only thing I have done to moxprox1 after install is edit the interfaces file to give a VLAN30 flag to eth1 and point vmbr1 at eth1.30. This is the same as moxprox0, only the physical port is eth0.
I have 5 VMs right now; CTs: arcane(100), mumble(103), factorio(104); VMs: ad(101), plex(102)
All storage is on a NFS hosted via FreeNAS on another server.
A CT made on moxprox1 stated with no issues.
Migrating CTs moves the CT but it can not start, giving the following error and logs on moxprox1:
If I transfer the CT back to moxprox0 it starts up no problem. If I try to start the CT wtih IPv6 set to DHCP the CT will actually start on moxprox1 but not when back home on moxprox0.
Migrating VMs does not move the VM and gives the following error and logs on moxprox1:
I am completely lost here. Can anyone give me any insight into what issue I'm having?
I'm sorry for the big wall of logs but I wanted to be thorough.
Thank you for any help provided in advance, it is very appreciated.
I have two Proxmox systems; moxprox0, moxprox1. moxprox0 is my primary server host and moxprox1 is a desktop node I want to use for when moxprox0 need to go offline but keep the VMs running. Both nodes are on the same subnet (10.0.30.0/24), they are joined into a cluster...
Code:
Quorum information
------------------
Date: Sat Feb 3 10:06:12 2018
Quorum provider: corosync_votequorum
Nodes: 2
Node ID: 0x00000001
Ring ID: 1/40
Quorate: Yes
Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 2
Quorum: 2
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.0.30.100 (local)
0x00000002 1 10.0.30.101The only thing I have done to moxprox1 after install is edit the interfaces file to give a VLAN30 flag to eth1 and point vmbr1 at eth1.30. This is the same as moxprox0, only the physical port is eth0.
I have 5 VMs right now; CTs: arcane(100), mumble(103), factorio(104); VMs: ad(101), plex(102)
All storage is on a NFS hosted via FreeNAS on another server.
A CT made on moxprox1 stated with no issues.
Migrating CTs moves the CT but it can not start, giving the following error and logs on moxprox1:
Code:
# CT 100 - Migrate
018-02-03 10:20:40 shutdown CT 100
2018-02-03 10:20:42 starting migration of CT 100 to node 'moxprox1' (10.0.30.101)
2018-02-03 10:20:42 volume 'xochitl-vm:100/vm-100-disk-1.raw' is on shared storage 'xochitl-vm'
2018-02-03 10:20:42 start final cleanup
2018-02-03 10:20:42 start container on target node
2018-02-03 10:20:42 # /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=moxprox1' root@10.0.30.101 pct start 100
2018-02-03 10:21:27 command 'systemctl start pve-container@100' failed: exit code 1
2018-02-03 10:21:27 Job for pve-container@100.service failed because the control process exited with error code.
2018-02-03 10:21:27 See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
2018-02-03 10:21:27 ERROR: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=moxprox1' root@10.0.30.101 pct start 100' failed: exit code 255
2018-02-03 10:21:27 ERROR: migration finished with problems (duration 00:00:47)
TASK ERROR: migration problems
# CT 100 - Start
Job for pve-container@100.service failed because the control process exited with error code.
See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@100' failed: exit code 1
root@moxprox1:~# systemctl status pve-container@100.service
● pve-container@100.service - PVE LXC Container: 100
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-02-03 10:21:27 CST; 2min 37s ago
Docs: man:lxc-start
man:lxc
man:pct
Process: 24459 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 760 Received container state "STOPPING" instead o
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 371 The container failed to start.
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfil
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Killing process 24461 (lxc-start) with signal SIGKILL.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Killing process 24961 (sh) with signal SIGKILL.
Feb 03 10:21:27 moxprox1 systemd[1]: Failed to start PVE LXC Container: 100.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Unit entered failed state.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
root@moxprox1:~# journalctl -xe
Feb 03 10:21:14 moxprox1 pveproxy[2288]: proxy detected vanished client connection
Feb 03 10:21:27 moxprox1 kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Feb 03 10:21:27 moxprox1 systemd-udevd[24880]: Could not generate persistent MAC address for vethKW1L1K: No such file or d
Feb 03 10:21:27 moxprox1 kernel: IPv6: ADDRCONF(NETDEV_UP): veth100i0: link is not ready
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 760 Received containe
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 371 The container failed to start.
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 373 To get more details, run the conta
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 375 Additional information can be obta
Feb 03 10:21:27 moxprox1 pvedaemon[2218]: unable to get PID for CT 100 (not running?)
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
Feb 03 10:21:27 moxprox1 pvestatd[2021]: unable to get PID for CT 100 (not running?)
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Killing process 24461 (lxc-start) with signal SIGKILL.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Killing process 24961 (sh) with signal SIGKILL.
Feb 03 10:21:27 moxprox1 pvestatd[2021]: status update time (35.358 seconds)
Feb 03 10:21:27 moxprox1 pmxcfs[1825]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/moxprox1/xoch
Feb 03 10:21:27 moxprox1 pmxcfs[1825]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/moxprox1/loca
Feb 03 10:21:27 moxprox1 pmxcfs[1825]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/moxprox1/loca
Feb 03 10:21:27 moxprox1 systemd[1]: Failed to start PVE LXC Container: 100.
-- Subject: Unit pve-container@100.service has failed
-- Defined-By: systemd
-- Support:
--
-- Unit pve-container@100.service has failed.
--
-- The result is failed.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Unit entered failed state.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Feb 03 10:21:27 moxprox1 pct[24456]: command 'systemctl start pve-container@100' failed: exit code 1
Feb 03 10:21:27 moxprox1 pct[24451]: <root@pam> end task UPID:moxprox1:00005F88:004C54AE:5A75E15B:vzstart:100:root@pam: co
Feb 03 10:21:27 moxprox1 sshd[24429]: Received disconnect from 10.0.30.100 port 36818:11: disconnected by user
Feb 03 10:21:27 moxprox1 sshd[24429]: Disconnected from 10.0.30.100 port 36818
Feb 03 10:21:27 moxprox1 sshd[24429]: pam_unix(sshd:session): session closed for user root
lines 5874-5909/5977 99%
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Feb 03 10:21:14 moxprox1 pveproxy[2288]: proxy detected vanished client connection
Feb 03 10:21:27 moxprox1 kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Feb 03 10:21:27 moxprox1 systemd-udevd[24880]: Could not generate persistent MAC address for vethKW1L1K: No such file or d
Feb 03 10:21:27 moxprox1 kernel: IPv6: ADDRCONF(NETDEV_UP): veth100i0: link is not ready
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 760 Received containe
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 371 The container failed to start.
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 373 To get more details, run the conta
Feb 03 10:21:27 moxprox1 lxc-start[24459]: lxc-start: 100: tools/lxc_start.c: main: 375 Additional information can be obta
Feb 03 10:21:27 moxprox1 pvedaemon[2218]: unable to get PID for CT 100 (not running?)
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Control process exited, code=exited status=1
Feb 03 10:21:27 moxprox1 pvestatd[2021]: unable to get PID for CT 100 (not running?)
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Killing process 24461 (lxc-start) with signal SIGKILL.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Killing process 24961 (sh) with signal SIGKILL.
Feb 03 10:21:27 moxprox1 pvestatd[2021]: status update time (35.358 seconds)
Feb 03 10:21:27 moxprox1 pmxcfs[1825]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/moxprox1/xoch
Feb 03 10:21:27 moxprox1 pmxcfs[1825]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/moxprox1/loca
Feb 03 10:21:27 moxprox1 pmxcfs[1825]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/moxprox1/loca
Feb 03 10:21:27 moxprox1 systemd[1]: Failed to start PVE LXC Container: 100.
-- Subject: Unit pve-container@100.service has failed
-- Defined-By: systemd
-- Support:
--
-- Unit pve-container@100.service has failed.
--
-- The result is failed.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Unit entered failed state.
Feb 03 10:21:27 moxprox1 systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Feb 03 10:21:27 moxprox1 pct[24456]: command 'systemctl start pve-container@100' failed: exit code 1
Feb 03 10:21:27 moxprox1 pct[24451]: <root@pam> end task UPID:moxprox1:00005F88:004C54AE:5A75E15B:vzstart:100:root@pam: co
Feb 03 10:21:27 moxprox1 sshd[24429]: Received disconnect from 10.0.30.100 port 36818:11: disconnected by user
Feb 03 10:21:27 moxprox1 sshd[24429]: Disconnected from 10.0.30.100 port 36818
Feb 03 10:21:27 moxprox1 sshd[24429]: pam_unix(sshd:session): session closed for user root
Feb 03 10:21:27 moxprox1 systemd-logind[1371]: Removed session 70.
-- Subject: Session 70 has been terminated
-- Defined-By: systemd
-- Support:
-- Documentation:
--
-- A session with the ID 70 has been terminated.
Feb 03 10:21:27 moxprox1 pmxcfs[1825]: [status] notice: received logIf I transfer the CT back to moxprox0 it starts up no problem. If I try to start the CT wtih IPv6 set to DHCP the CT will actually start on moxprox1 but not when back home on moxprox0.
Migrating VMs does not move the VM and gives the following error and logs on moxprox1:
Code:
VM 102 Migrate
2018-02-03 10:33:33 starting migration of VM 102 to node 'moxprox1' (10.0.30.101)
2018-02-03 10:33:33 copying disk images
2018-02-03 10:33:33 starting VM 102 on remote node 'moxprox1'
2018-02-03 10:33:34 start failed: command '/usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/102.pid -daemonize -smbios 'type=1,uuid=2f3d87ea-d1d8-4398-9241-2f03fba76e5a' -name plex -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/102.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 16512 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:dd174a42599' -drive 'file=/mnt/pve/xochitl-vm/template/iso/debian-9.3.0-amd64-netinst.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/mnt/pve/xochitl-vm/images/102/vm-102-disk-1.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=06:89:79:86:37:98,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc-i440fx-2.9' -incoming unix:/run/qemu-server/102.migrate -S' failed: exit code 1
2018-02-03 10:33:34 ERROR: online migrate failure - command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=moxprox1' root@10.0.30.101 qm start 102 --skiplock --migratedfrom moxprox0 --migration_type secure --stateuri unix --machine pc-i440fx-2.9' failed: exit code 255
2018-02-03 10:33:34 aborting phase 2 - cleanup resources
2018-02-03 10:33:34 migrate_cancel
2018-02-03 10:33:34 ERROR: migration finished with problems (duration 00:00:01)
TASK ERROR: migration problems
VM 102 Start
bridge 'vmbr1' does not exist
kvm: -netdev type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on: network script /var/lib/qemu-server/pve-bridge failed with status 512
TASK ERROR: start failed: command '/usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/102.pid -daemonize -smbios 'type=1,uuid=2f3d87ea-d1d8-4398-9241-2f03fba76e5a' -name plex -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/102.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 16512 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:dd174a42599' -drive 'file=/mnt/pve/xochitl-vm/template/iso/debian-9.3.0-amd64-netinst.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/mnt/pve/xochitl-vm/images/102/vm-102-disk-1.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=06:89:79:86:37:98,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc-i440fx-2.9' -incoming unix:/run/qemu-server/102.migrate -S' failed: exit code 1
root@moxprox1:~# journalctl -xe
Feb 03 10:38:10 moxprox1 pmxcfs[1825]: [status] notice: received log
Feb 03 10:38:10 moxprox1 sshd[1916]: Accepted publickey for root from 10.0.30.100 port 36888 ssh2: RSA SHA256:kesYlZmrN+ninF3DZN7Y+9QzSO3dQewrmc/8yguE3Gc
Feb 03 10:38:10 moxprox1 sshd[1916]: pam_unix(sshd:session): session opened for user root by (uid=0)
Feb 03 10:38:10 moxprox1 systemd-logind[1371]: New session 74 of user root.
-- Subject: A new session 74 has been created for user root
-- Defined-By: systemd
-- Support:
-- Documentation:
--
-- A new session with the ID 74 has been created for the user root.
--
-- The leading process of the session is 1916.
Feb 03 10:38:10 moxprox1 systemd[1]: Started Session 74 of user root.
-- Subject: Unit session-74.scope has finished start-up
-- Defined-By: systemd
-- Support:
--
-- Unit session-74.scope has finished starting up.
--
-- The start-up result is done.
Feb 03 10:38:10 moxprox1 sshd[1916]: Received disconnect from 10.0.30.100 port 36888:11: disconnected by user
Feb 03 10:38:10 moxprox1 sshd[1916]: Disconnected from 10.0.30.100 port 36888
Feb 03 10:38:10 moxprox1 sshd[1916]: pam_unix(sshd:session): session closed for user root
Feb 03 10:38:10 moxprox1 systemd-logind[1371]: Removed session 74.
-- Subject: Session 74 has been terminated
-- Defined-By: systemd
-- Support:
-- Documentation:
--
-- A session with the ID 74 has been terminated.
Feb 03 10:38:10 moxprox1 sshd[1936]: Accepted publickey for root from 10.0.30.100 port 36892 ssh2: RSA SHA256:kesYlZmrN+ninF3DZN7Y+9QzSO3dQewrmc/8yguE3Gc
Feb 03 10:38:10 moxprox1 sshd[1936]: pam_unix(sshd:session): session opened for user root by (uid=0)
Feb 03 10:38:10 moxprox1 systemd-logind[1371]: New session 75 of user root.
-- Subject: A new session 75 has been created for user root
-- Defined-By: systemd
-- Support:
-- Documentation:
--
-- A new session with the ID 75 has been created for the user root.
--
-- The leading process of the session is 1936.
Feb 03 10:38:10 moxprox1 systemd[1]: Started Session 75 of user root.
-- Subject: Unit session-75.scope has finished start-up
-- Defined-By: systemd
-- Support:
--
-- Unit session-75.scope has finished starting up.
--
-- The start-up result is done.
Feb 03 10:38:11 moxprox1 qm[1965]: <root@pam> starting task UPID:moxprox1:000007E2:004DEE23:5A75E573:qmstart:102:root@pam:
Feb 03 10:38:11 moxprox1 qm[2018]: start VM 102: UPID:moxprox1:000007E2:004DEE23:5A75E573:qmstart:102:root@pam:
Feb 03 10:38:11 moxprox1 systemd[1]: Started 102.scope.
-- Subject: Unit 102.scope has finished start-up
-- Defined-By: systemd
-- Support:
--
-- Unit 102.scope has finished starting up.
--
-- The start-up result is done.
Feb 03 10:38:11 moxprox1 systemd-udevd[2032]: Could not generate persistent MAC address for tap102i0: No such file or directory
Feb 03 10:38:11 moxprox1 qm[2018]: start failed: command '/usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /va
Feb 03 10:38:11 moxprox1 qm[1965]: <root@pam> end task UPID:moxprox1:000007E2:004DEE23:5A75E573:qmstart:102:root@pam: start failed: command '/usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/
Feb 03 10:38:11 moxprox1 sshd[1936]: Received disconnect from 10.0.30.100 port 36892:11: disconnected by user
Feb 03 10:38:11 moxprox1 sshd[1936]: Disconnected from 10.0.30.100 port 36892
Feb 03 10:38:11 moxprox1 sshd[1936]: pam_unix(sshd:session): session closed for user root
Feb 03 10:38:11 moxprox1 systemd-logind[1371]: Removed session 75.
-- Subject: Session 75 has been terminated
-- Defined-By: systemd
-- Support:
-- Documentation:
--
-- A session with the ID 75 has been terminated.
Feb 03 10:38:11 moxprox1 sshd[2057]: Accepted publickey for root from 10.0.30.100 port 36894 ssh2: RSA SHA256:kesYlZmrN+ninF3DZN7Y+9QzSO3dQewrmc/8yguE3Gc
Feb 03 10:38:11 moxprox1 sshd[2057]: pam_unix(sshd:session): session opened for user root by (uid=0)
Feb 03 10:38:11 moxprox1 systemd-logind[1371]: New session 76 of user root.
-- Subject: A new session 76 has been created for user root
-- Defined-By: systemd
-- Support:
-- Documentation: --
-- A new session with the ID 76 has been created for the user root.
--
-- The leading process of the session is 2057.
Feb 03 10:38:11 moxprox1 systemd[1]: Started Session 76 of user root.
-- Subject: Unit session-76.scope has finished start-up
-- Defined-By: systemd
-- Support:
--
-- Unit session-76.scope has finished starting up.
--
-- The start-up result is done.
Feb 03 10:38:12 moxprox1 qm[2075]: <root@pam> starting task UPID:moxprox1:00000820:004DEE78:5A75E574:qmstop:102:root@pam:
Feb 03 10:38:12 moxprox1 qm[2080]: stop VM 102: UPID:moxprox1:00000820:004DEE78:5A75E574:qmstop:102:root@pam:
Feb 03 10:38:12 moxprox1 qm[2075]: <root@pam> end task UPID:moxprox1:00000820:004DEE78:5A75E574:qmstop:102:root@pam: OK
Feb 03 10:38:12 moxprox1 sshd[2057]: Received disconnect from 10.0.30.100 port 36894:11: disconnected by user
Feb 03 10:38:12 moxprox1 sshd[2057]: Disconnected from 10.0.30.100 port 36894
Feb 03 10:38:12 moxprox1 sshd[2057]: pam_unix(sshd:session): session closed for user root
Feb 03 10:38:12 moxprox1 systemd-logind[1371]: Removed session 76.I am completely lost here. Can anyone give me any insight into what issue I'm having?
I'm sorry for the big wall of logs but I wanted to be thorough.
Thank you for any help provided in advance, it is very appreciated.
