pveproxy: problem with client xxx.xxx.x.xxx; ssl3_read_bytes: ssl handshake failure

Discussion in 'Proxmox VE: Installation and configuration' started by bonibom, Mar 29, 2019.

  1. bonibom

    bonibom New Member

    Joined:
    Jun 5, 2017
    Messages:
    3
    Likes Received:
    0
    Hi guys,

    Please help me with the problem:

    When a client attempts to connect to noVNC console the following error appears in the syslog:

    Code:
    pveproxy: problem with client xxx.xxx.x.xxx; ssl3_read_bytes: ssl handshake failure
    I did

    Code:
    pvecm updatecerts -f
    systemctl restart pveproxy
    with no success. This happens with all clients. noVNC session is working 15-20 seconds then reconnects.

    My configuration is:
    1. PVE server is located in a local network
    2. PVE version is 4.4 and I am not able to update to PVE 5.x

    Code:
    pve-manager/4.4-24/08ba4d2d (running kernel: 4.4.134-1-pve)
    root@pve-server:~# pveversion -v
    proxmox-ve: 4.4-112 (running kernel: 4.4.134-1-pve)
    pve-manager: 4.4-24 (running version: 4.4-24/08ba4d2d)
    pve-kernel-4.4.134-1-pve: 4.4.134-112
    lvm2: 2.02.116-pve3
    corosync-pve: 2.4.2-2~pve4+2
    libqb0: 1.0.1-1
    pve-cluster: 4.0-55
    qemu-server: 4.0-115
    pve-firmware: 1.1-12
    libpve-common-perl: 4.0-96
    libpve-access-control: 4.0-23
    libpve-storage-perl: 4.0-76
    pve-libspice-server1: 0.12.8-2
    vncterm: 1.3-2
    pve-docs: 4.4-4
    pve-qemu-kvm: 2.9.1-9~pve4
    pve-container: 1.0-106
    pve-firewall: 2.0-33
    pve-ha-manager: 1.0-41
    ksm-control-daemon: 1.2-1
    glusterfs-client: 3.5.2-2+deb8u3
    lxc-pve: 2.0.7-4
    lxcfs: 2.0.8-2~pve4
    criu: 1.6.0-1
    novnc-pve: 0.5-9
    smartmontools: 6.5+svn4324-1~pve80
    zfsutils: 0.6.5.9-pve15~bpo80
    Thanks in advance. I will appreciate any help.

    P.S. Sorry for my English also :)
     
  2. oguz

    oguz Proxmox Staff Member
    Staff Member

    Joined:
    Nov 19, 2018
    Messages:
    315
    Likes Received:
    26
    Try clearing your browser cache.

    If that doesn't work, please post the entire log:
    Code:
    cat /var/log/syslog | grep pveproxy
    
    You should also really consider upgrading to the latest version, to get the latest bugfixes and features.
    https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. bonibom

    bonibom New Member

    Joined:
    Jun 5, 2017
    Messages:
    3
    Likes Received:
    0
    Hi ogus,

    Thank you a lot for your response. Here is syslog for pveproxy:

    Code:
    root@pve-server:~# cat /var/log/syslog | grep pveproxy
    Mar 29 10:35:52 pve-server pveproxy[1709]: worker exit
    Mar 29 10:35:52 pve-server pveproxy[1706]: worker 1709 finished
    Mar 29 10:35:52 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 10:35:52 pve-server pveproxy[1706]: worker 8873 started
    Mar 29 10:42:46 pve-server pveproxy[1708]: worker exit
    Mar 29 10:42:46 pve-server pveproxy[1706]: worker 1708 finished
    Mar 29 10:42:46 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 10:42:46 pve-server pveproxy[1706]: worker 9898 started
    Mar 29 11:04:34 pve-server pveproxy[1706]: worker 1707 finished
    Mar 29 11:04:34 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 11:04:34 pve-server pveproxy[1706]: worker 13228 started
    Mar 29 11:04:36 pve-server pveproxy[13227]: got inotify poll request in wrong process - disabling inotify
    Mar 29 11:04:37 pve-server pveproxy[13227]: worker exit
    Mar 29 11:04:54 pve-server pveproxy[1706]: worker 8873 finished
    Mar 29 11:04:54 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 11:04:54 pve-server pveproxy[1706]: worker 13305 started
    Mar 29 11:04:57 pve-server pveproxy[13304]: got inotify poll request in wrong process - disabling inotify
    Mar 29 11:08:57 pve-server pveproxy[13304]: worker exit
    Mar 29 11:20:15 pve-server pveproxy[1706]: worker 9898 finished
    Mar 29 11:20:15 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 11:20:15 pve-server pveproxy[1706]: worker 15722 started
    Mar 29 11:20:16 pve-server pveproxy[15721]: got inotify poll request in wrong process - disabling inotify
    Mar 29 11:20:16 pve-server pveproxy[15721]: worker exit
    Mar 29 11:26:26 pve-server pveproxy[1706]: worker 13305 finished
    Mar 29 11:26:26 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 11:26:26 pve-server pveproxy[1706]: worker 16649 started
    Mar 29 11:26:29 pve-server pveproxy[16648]: got inotify poll request in wrong process - disabling inotify
    Mar 29 11:43:01 pve-server pveproxy[13228]: worker exit
    Mar 29 11:43:01 pve-server pveproxy[1706]: worker 13228 finished
    Mar 29 11:43:01 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 11:43:01 pve-server pveproxy[1706]: worker 19178 started
    Mar 29 11:46:16 pve-server pveproxy[15722]: worker exit
    Mar 29 11:46:16 pve-server pveproxy[1706]: worker 15722 finished
    Mar 29 11:46:16 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 11:46:16 pve-server pveproxy[1706]: worker 19690 started
    Mar 29 11:47:57 pve-server pveproxy[1706]: worker 16649 finished
    Mar 29 11:47:57 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 11:47:57 pve-server pveproxy[1706]: worker 19944 started
    Mar 29 11:47:59 pve-server pveproxy[19942]: worker exit
    Mar 29 11:58:58 pve-server pveproxy[19944]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 11:59:40 pve-server pveproxy[16648]: worker exit
    Mar 29 12:00:24 pve-server pveproxy[19944]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:00:24 pve-server pveproxy[19178]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:00:47 pve-server pveproxy[19690]: worker exit
    Mar 29 12:00:47 pve-server pveproxy[1706]: worker 19690 finished
    Mar 29 12:00:47 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:00:47 pve-server pveproxy[1706]: worker 22049 started
    Mar 29 12:01:34 pve-server pveproxy[22049]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:01:40 pve-server pveproxy[22049]: problem with client 192.168.1.150; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:04:28 pve-server pveproxy[22049]: problem with client 192.168.1.150; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:04:43 pve-server pveproxy[1706]: worker 19944 finished
    Mar 29 12:04:43 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:04:43 pve-server pveproxy[1706]: worker 22859 started
    Mar 29 12:04:47 pve-server pveproxy[22858]: got inotify poll request in wrong process - disabling inotify
    Mar 29 12:05:39 pve-server pveproxy[22859]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:05:42 pve-server pveproxy[22859]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:06:25 pve-server pveproxy[22858]: worker exit
    Mar 29 12:08:22 pve-server pveproxy[19178]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:08:22 pve-server pveproxy[19178]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:09:51 pve-server pveproxy[19178]: worker exit
    Mar 29 12:09:51 pve-server pveproxy[1706]: worker 19178 finished
    Mar 29 12:09:51 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:09:51 pve-server pveproxy[1706]: worker 23642 started
    Mar 29 12:10:51 pve-server pveproxy[1706]: worker 22049 finished
    Mar 29 12:10:51 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:10:51 pve-server pveproxy[1706]: worker 23784 started
    Mar 29 12:10:52 pve-server pveproxy[23783]: got inotify poll request in wrong process - disabling inotify
    Mar 29 12:13:13 pve-server pveproxy[1706]: worker 22859 finished
    Mar 29 12:13:13 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:13:13 pve-server pveproxy[1706]: worker 24163 started
    Mar 29 12:13:13 pve-server pveproxy[24162]: got inotify poll request in wrong process - disabling inotify
    Mar 29 12:13:14 pve-server pveproxy[24162]: worker exit
    Mar 29 12:14:46 pve-server pveproxy[24163]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:16:54 pve-server pveproxy[23784]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:18:10 pve-server pveproxy[23784]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:19:38 pve-server pveproxy[24163]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:19:50 pve-server pveproxy[23784]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:20:14 pve-server pveproxy[23642]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:21:08 pve-server pveproxy[23784]: worker exit
    Mar 29 12:21:08 pve-server pveproxy[1706]: worker 23784 finished
    Mar 29 12:21:08 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:21:08 pve-server pveproxy[1706]: worker 25428 started
    Mar 29 12:21:10 pve-server pveproxy[1706]: worker 23642 finished
    Mar 29 12:21:10 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:21:10 pve-server pveproxy[1706]: worker 25447 started
    Mar 29 12:21:11 pve-server pveproxy[25446]: got inotify poll request in wrong process - disabling inotify
    Mar 29 12:21:13 pve-server pveproxy[25446]: worker exit
    Mar 29 12:21:54 pve-server pveproxy[25447]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:24:24 pve-server pveproxy[24163]: worker exit
    Mar 29 12:24:24 pve-server pveproxy[1706]: worker 24163 finished
    Mar 29 12:24:24 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:24:24 pve-server pveproxy[1706]: worker 25957 started
    Mar 29 12:24:30 pve-server pveproxy[25447]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:24:38 pve-server pveproxy[25428]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:28:10 pve-server pveproxy[25428]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:28:14 pve-server pveproxy[25447]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:28:48 pve-server pveproxy[23783]: worker exit
    Mar 29 12:28:54 pve-server pveproxy[25447]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:30:35 pve-server pveproxy[25428]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:30:43 pve-server pveproxy[25447]: worker exit
    Mar 29 12:30:43 pve-server pveproxy[1706]: worker 25447 finished
    Mar 29 12:30:43 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:30:43 pve-server pveproxy[1706]: worker 26957 started
    Mar 29 12:31:05 pve-server pveproxy[25428]: worker exit
    Mar 29 12:31:05 pve-server pveproxy[1706]: worker 25428 finished
    Mar 29 12:31:05 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:31:05 pve-server pveproxy[1706]: worker 27015 started
    Mar 29 12:33:06 pve-server pveproxy[25957]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:33:06 pve-server pveproxy[25957]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:33:12 pve-server pveproxy[26957]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:34:04 pve-server pveproxy[25957]: worker exit
    Mar 29 12:34:04 pve-server pveproxy[1706]: worker 25957 finished
    Mar 29 12:34:04 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:34:04 pve-server pveproxy[1706]: worker 27488 started
    Mar 29 12:37:13 pve-server pveproxy[27488]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:38:23 pve-server pveproxy[27015]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:38:53 pve-server pveproxy[27488]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:40:45 pve-server pveproxy[26957]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:41:39 pve-server pveproxy[26957]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:43:42 pve-server pveproxy[27015]: worker exit
    Mar 29 12:43:42 pve-server pveproxy[1706]: worker 27015 finished
    Mar 29 12:43:42 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:43:42 pve-server pveproxy[1706]: worker 28959 started
    Mar 29 12:44:43 pve-server pveproxy[26957]: worker exit
    Mar 29 12:44:43 pve-server pveproxy[1706]: worker 26957 finished
    Mar 29 12:44:43 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:44:43 pve-server pveproxy[1706]: worker 29099 started
    Mar 29 12:46:12 pve-server pveproxy[27488]: worker exit
    Mar 29 12:46:12 pve-server pveproxy[1706]: worker 27488 finished
    Mar 29 12:46:12 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:46:12 pve-server pveproxy[1706]: worker 29334 started
    Mar 29 12:48:05 pve-server pveproxy[28959]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:51:12 pve-server pveproxy[29334]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:51:59 pve-server pveproxy[29334]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:53:22 pve-server pveproxy[29334]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:53:53 pve-server pveproxy[29099]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:55:14 pve-server pveproxy[29099]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:55:14 pve-server pveproxy[28959]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:55:17 pve-server pveproxy[1706]: worker 28959 finished
    Mar 29 12:55:17 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:55:17 pve-server pveproxy[1706]: worker 30784 started
    Mar 29 12:55:17 pve-server pveproxy[29334]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:55:20 pve-server pveproxy[30783]: worker exit
    Mar 29 12:55:50 pve-server pveproxy[1706]: worker 29334 finished
    Mar 29 12:55:50 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:55:50 pve-server pveproxy[1706]: worker 30867 started
    Mar 29 12:55:50 pve-server pveproxy[30784]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:55:50 pve-server pveproxy[30784]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:55:52 pve-server pveproxy[30866]: worker exit
    Mar 29 12:57:14 pve-server pveproxy[30867]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:57:26 pve-server pveproxy[30784]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:57:26 pve-server pveproxy[30784]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:57:38 pve-server pveproxy[31159]: got inotify poll request in wrong process - disabling inotify
    Mar 29 12:57:38 pve-server pveproxy[1706]: worker 29099 finished
    Mar 29 12:57:38 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 12:57:38 pve-server pveproxy[1706]: worker 31160 started
    Mar 29 12:57:39 pve-server pveproxy[31159]: worker exit
    Mar 29 12:58:18 pve-server pveproxy[30867]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:58:22 pve-server pveproxy[31160]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 12:59:05 pve-server pveproxy[31160]: problem with client 192.168.1.186; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:01:35 pve-server pveproxy[31160]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:01:38 pve-server pveproxy[31160]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:02:19 pve-server pveproxy[30784]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:02:20 pve-server pveproxy[30867]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:05:21 pve-server pveproxy[30784]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:05:21 pve-server pveproxy[30784]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:06:34 pve-server pveproxy[1706]: worker 31160 finished
    Mar 29 13:06:34 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:06:34 pve-server pveproxy[1706]: worker 32556 started
    Mar 29 13:06:37 pve-server pveproxy[32555]: worker exit
    Mar 29 13:06:45 pve-server pveproxy[30867]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:06:46 pve-server pveproxy[30867]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:06:46 pve-server pveproxy[32556]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:07:39 pve-server pveproxy[30867]: worker exit
    Mar 29 13:07:39 pve-server pveproxy[1706]: worker 30867 finished
    Mar 29 13:07:39 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:07:39 pve-server pveproxy[1706]: worker 32714 started
    Mar 29 13:07:49 pve-server pveproxy[1706]: worker 30784 finished
    Mar 29 13:07:49 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:07:49 pve-server pveproxy[1706]: worker 32753 started
    Mar 29 13:07:50 pve-server pveproxy[32752]: worker exit
    Mar 29 13:09:56 pve-server pveproxy[32556]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:10:38 pve-server pveproxy[32714]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:11:14 pve-server pveproxy[32714]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:11:14 pve-server pveproxy[32753]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:11:46 pve-server pveproxy[32753]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:13:03 pve-server pveproxy[32556]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:13:47 pve-server pveproxy[32556]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:17:04 pve-server pveproxy[1706]: worker 32753 finished
    Mar 29 13:17:04 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:17:04 pve-server pveproxy[1706]: worker 1906 started
    Mar 29 13:17:04 pve-server pveproxy[1905]: got inotify poll request in wrong process - disabling inotify
    Mar 29 13:17:07 pve-server pveproxy[1905]: worker exit
    Mar 29 13:17:19 pve-server pveproxy[1706]: worker 32556 finished
    Mar 29 13:17:19 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:17:19 pve-server pveproxy[1706]: worker 1959 started
    Mar 29 13:17:19 pve-server pveproxy[1958]: got inotify poll request in wrong process - disabling inotify
    Mar 29 13:17:20 pve-server pveproxy[1958]: worker exit
    Mar 29 13:18:18 pve-server pveproxy[1906]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:18:30 pve-server pveproxy[1959]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:19:09 pve-server pveproxy[1959]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:19:39 pve-server pveproxy[1959]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:20:19 pve-server pveproxy[1959]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:21:30 pve-server pveproxy[32714]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:21:58 pve-server pveproxy[1959]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:23:19 pve-server pveproxy[32714]: worker exit
    Mar 29 13:23:19 pve-server pveproxy[1706]: worker 32714 finished
    Mar 29 13:23:19 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:23:19 pve-server pveproxy[1706]: worker 3010 started
    Mar 29 13:25:59 pve-server pveproxy[3010]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:27:33 pve-server pveproxy[1906]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:27:35 pve-server pveproxy[1959]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:27:35 pve-server pveproxy[3010]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:27:43 pve-server pveproxy[1959]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:27:43 pve-server pveproxy[3010]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:27:55 pve-server pveproxy[1959]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:28:03 pve-server pveproxy[1959]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:28:34 pve-server pveproxy[1959]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:28:58 pve-server pveproxy[1959]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:29:04 pve-server pveproxy[1906]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:29:14 pve-server pveproxy[1906]: worker exit
    Mar 29 13:29:14 pve-server pveproxy[1706]: worker 1906 finished
    Mar 29 13:29:14 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:29:14 pve-server pveproxy[1706]: worker 3953 started
    Mar 29 13:29:22 pve-server pveproxy[1959]: worker exit
    Mar 29 13:29:22 pve-server pveproxy[1706]: worker 1959 finished
    Mar 29 13:29:22 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:29:22 pve-server pveproxy[1706]: worker 3975 started
    Mar 29 13:29:25 pve-server pveproxy[3953]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:30:29 pve-server pveproxy[3975]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:30:29 pve-server pveproxy[3953]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:30:33 pve-server pveproxy[3953]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:31:05 pve-server pveproxy[3010]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:31:52 pve-server pveproxy[1706]: worker 3010 finished
    Mar 29 13:31:52 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:31:52 pve-server pveproxy[1706]: worker 4333 started
    Mar 29 13:31:53 pve-server pveproxy[4332]: worker exit
    Mar 29 13:31:56 pve-server pveproxy[4333]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:31:59 pve-server pveproxy[4333]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:32:05 pve-server pveproxy[4333]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:32:05 pve-server pveproxy[3975]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:33:01 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:33:05 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:34:13 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:34:29 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:34:44 pve-server pveproxy[3953]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:34:44 pve-server pveproxy[3975]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:35:19 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:35:24 pve-server pveproxy[3953]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:35:28 pve-server pveproxy[3975]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:37:20 pve-server pveproxy[3975]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:37:47 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:38:36 pve-server pveproxy[4333]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:39:11 pve-server pveproxy[3975]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:40:13 pve-server pveproxy[1706]: worker 3975 finished
    Mar 29 13:40:13 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:40:13 pve-server pveproxy[1706]: worker 5668 started
    Mar 29 13:40:16 pve-server pveproxy[5667]: worker exit
    Mar 29 13:40:35 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:41:31 pve-server pveproxy[5668]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:41:51 pve-server pveproxy[4333]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:42:37 pve-server pveproxy[1706]: worker 4333 finished
    Mar 29 13:42:37 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:42:37 pve-server pveproxy[1706]: worker 6041 started
    Mar 29 13:42:39 pve-server pveproxy[6040]: worker exit
    Mar 29 13:42:51 pve-server pveproxy[6041]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:43:08 pve-server pveproxy[5668]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:43:35 pve-server pveproxy[3953]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:43:35 pve-server pveproxy[5668]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:43:43 pve-server pveproxy[6041]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:44:11 pve-server pveproxy[6041]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:44:11 pve-server pveproxy[5668]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:44:32 pve-server pveproxy[6041]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:44:42 pve-server pveproxy[5668]: problem with client 192.168.1.144; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:45:10 pve-server pveproxy[3953]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:45:21 pve-server pveproxy[3953]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:46:27 pve-server pveproxy[6041]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:46:51 pve-server pveproxy[6041]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:48:58 pve-server pveproxy[3953]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:49:10 pve-server pveproxy[3953]: problem with client 192.168.1.173; ssl3_read_bytes: ssl handshake failure
    Mar 29 13:50:24 pve-server pveproxy[3953]: worker exit
    Mar 29 13:50:25 pve-server pveproxy[1706]: worker 3953 finished
    Mar 29 13:50:25 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 13:50:25 pve-server pveproxy[1706]: worker 7319 started
    Mar 29 14:01:10 pve-server pveproxy[5668]: worker exit
    Mar 29 14:01:10 pve-server pveproxy[1706]: worker 5668 finished
    Mar 29 14:01:10 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 14:01:10 pve-server pveproxy[1706]: worker 9028 started
    Mar 29 14:08:42 pve-server pveproxy[6041]: worker exit
    Mar 29 14:08:42 pve-server pveproxy[1706]: worker 6041 finished
    Mar 29 14:08:42 pve-server pveproxy[1706]: starting 1 worker(s)
    Mar 29 14:08:42 pve-server pveproxy[1706]: worker 10192 started
    Mar 29 14:12:13 pve-server pveproxy[10192]: problem with client 192.168.1.186; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:17:22 pve-server pveproxy[7319]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:17:25 pve-server pveproxy[10192]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:17:31 pve-server pveproxy[10192]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:18:13 pve-server pveproxy[10192]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:42 pve-server pveproxy[10192]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:45 pve-server pveproxy[9028]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:45 pve-server pveproxy[7319]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:48 pve-server pveproxy[9028]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:49 pve-server pveproxy[7319]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:53 pve-server pveproxy[7319]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:55 pve-server pveproxy[9028]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:56 pve-server pveproxy[7319]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    Mar 29 14:19:57 pve-server pveproxy[9028]: problem with client 192.168.1.187; ssl3_read_bytes: ssl handshake failure
    
     
  4. tomte76

    tomte76 New Member

    Joined:
    Mar 6, 2015
    Messages:
    20
    Likes Received:
    0
    I have the same problem. I suddenly appeared out of nowhere. No reboot or anything. We have a eight node cluster and this only happens if I connect to the first node in the cluster which we are using as the "Web-UI-Host". If I connect to the second one everything works fine. I also restarted pveproxy without success. Upgrading the whole cluster to Proxmox 5 unfortunately is not a short term option. Any hints to track this down and fix it?

    Code:
    Apr 15 08:47:41 pxm01 pveproxy[35792]: starting 1 worker(s)
    Apr 15 08:47:41 pxm01 pveproxy[35792]: worker 120476 started
    Apr 15 08:48:15 pxm01 pveproxy[120476]: Clearing outdated entries from certificate cache
    Apr 15 08:51:31 pxm01 pveproxy[120476]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 08:52:16 pxm01 pveproxy[120476]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 08:52:57 pxm01 pveproxy[120476]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 08:52:57 pxm01 pveproxy[120476]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 08:55:55 pxm01 pveproxy[104960]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 08:57:08 pxm01 pveproxy[120476]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 08:59:27 pxm01 pveproxy[81791]: Clearing outdated entries from certificate cache
    Apr 15 09:01:58 pxm01 pveproxy[81791]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:02:24 pxm01 pveproxy[81791]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:06:45 pxm01 pveproxy[104960]: worker exit
    Apr 15 09:06:45 pxm01 pveproxy[35792]: worker 104960 finished
    Apr 15 09:06:45 pxm01 pveproxy[35792]: starting 1 worker(s)
    Apr 15 09:06:45 pxm01 pveproxy[35792]: worker 159425 started
    Apr 15 09:07:17 pxm01 pveproxy[120476]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:07:20 pxm01 pveproxy[159425]: Clearing outdated entries from certificate cache
    Apr 15 09:07:20 pxm01 pveproxy[159425]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:08:42 pxm01 pveproxy[120476]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:09:03 pxm01 pveproxy[159425]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:10:38 pxm01 pveproxy[159425]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:13:36 pxm01 pveproxy[159425]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:16:44 pxm01 pveproxy[159425]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:17:09 pxm01 pveproxy[35792]: worker 81791 finished
    Apr 15 09:17:09 pxm01 pveproxy[35792]: starting 1 worker(s)
    Apr 15 09:17:09 pxm01 pveproxy[35792]: worker 179248 started
    Apr 15 09:17:10 pxm01 pveproxy[179247]: worker exit
    Apr 15 09:17:11 pxm01 pveproxy[179248]: Clearing outdated entries from certificate cache
    Apr 15 09:18:59 pxm01 pveproxy[179248]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:20:21 pxm01 pveproxy[179248]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:20:27 pxm01 pveproxy[179248]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:22:17 pxm01 pveproxy[159425]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    Apr 15 09:22:55 pxm01 pveproxy[179248]: problem with client 212.9.180.53; ssl3_read_bytes: ssl handshake failure
    
    Code:
    root@pxm01:/var/log# pveversion -v
    proxmox-ve: 4.4-103 (running kernel: 4.4.98-3-pve)
    pve-manager: 4.4-21 (running version: 4.4-21/e0dadcf8)
    pve-kernel-4.4.98-3-pve: 4.4.98-103
    pve-kernel-4.4.8-1-pve: 4.4.8-52
    pve-kernel-4.4.13-2-pve: 4.4.13-58
    pve-kernel-4.4.21-1-pve: 4.4.21-71
    pve-kernel-4.4.10-1-pve: 4.4.10-54
    lvm2: 2.02.116-pve3
    corosync-pve: 2.4.2-2~pve4+1
    libqb0: 1.0.1-1
    pve-cluster: 4.0-54
    qemu-server: 4.0-114
    pve-firmware: 1.1-11
    libpve-common-perl: 4.0-96
    libpve-access-control: 4.0-23
    libpve-storage-perl: 4.0-76
    pve-libspice-server1: 0.12.8-2
    vncterm: 1.3-2
    pve-docs: 4.4-4
    pve-qemu-kvm: 2.9.1-5~pve4
    pve-container: 1.0-104
    pve-firewall: 2.0-33
    pve-ha-manager: 1.0-41
    ksm-control-daemon: 1.2-1
    glusterfs-client: 3.5.2-2+deb8u5
    lxc-pve: 2.0.7-4
    lxcfs: 2.0.6-pve1
    criu: 1.6.0-1
    novnc-pve: 0.5-9
    smartmontools: 6.5+svn4324-1~pve80
    zfsutils: 0.6.5.9-pve15~bpo80
    
     
  5. oguz

    oguz Proxmox Staff Member
    Staff Member

    Joined:
    Nov 19, 2018
    Messages:
    315
    Likes Received:
    26
    You can try restarting pvedaemon just to check. Other than that, clearing browser caches might work. I can't think of anything else but to suggest you to upgrade to 5.4, PVE 4.4 has been out of support for a while now.

    Take a look here:
    https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0

    EDIT: Another reason for upgrading to latest PVE is, we're only seeing this bug on the older versions like 4.x, so it's highly possible that it was fixed between releases.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice