v4.2 no graphic/details/stats and date 01.01.1970

Discussion in 'Proxmox VE: Installation and configuration' started by informant, May 9, 2016.

  1. informant

    informant Member

    Joined:
    Jan 31, 2012
    Messages:
    667
    Likes Received:
    4
    Hi, we have installed a new server with v4.2 after installation we have in statistic screens cpu usage ... all 01.01.1970. date and time are ok, we have install ntp, buit issue are the same. why do we dont´s view details and wrong dates?
    no-usages-listen.png

    regards
     
  2. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,340
    Likes Received:
    286
    Installed using the proxmox installation CD? If not, please post the output of

    # pveversion -v
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. informant

    informant Member

    Joined:
    Jan 31, 2012
    Messages:
    667
    Likes Received:
    4
    hi dietmar, yes with install cd. here the pveversion -v:

    Code:
    pveversion -v
    proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
    pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
    pve-kernel-4.4.6-1-pve: 4.4.6-48
    lvm2: 2.02.116-pve2
    corosync-pve: 2.3.5-2
    libqb0: 1.0-1
    pve-cluster: 4.0-39
    qemu-server: 4.0-72
    pve-firmware: 1.1-8
    libpve-common-perl: 4.0-59
    libpve-access-control: 4.0-16
    libpve-storage-perl: 4.0-50
    pve-libspice-server1: 0.12.5-2
    vncterm: 1.2-1
    pve-qemu-kvm: 2.5-14
    pve-container: 1.0-62
    pve-firewall: 2.0-25
    pve-ha-manager: 1.0-28
    ksm-control-daemon: 1.2-1
    glusterfs-client: 3.5.2-2+deb8u1
    lxc-pve: 1.1.5-7
    lxcfs: 2.0.0-pve2
    cgmanager: 0.39-pve1
    criu: 1.6.0-1
    zfsutils: 0.6.5-pve9~jessie
     
  4. informant

    informant Member

    Joined:
    Jan 31, 2012
    Messages:
    667
    Likes Received:
    4
    In syslog i have found this:
    Code:
    May 09 20:17:12 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462817806 when last update time is 1462818588 (minimum one second step))
    May 09 20:17:43 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462817836 when last update time is 1462818588 (minimum one second step))
    May 09 20:18:13 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462817866 when last update time is 1462818588 (minimum one second step))
    May 09 20:18:43 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462817896 when last update time is 1462818588 (minimum one second step))
    May 09 20:19:14 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462817926 when last update time is 1462818588 (minimum one second step))
    May 09 20:19:45 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462817956 when last update time is 1462818588 (minimum one second step))
    May 09 20:20:15 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462817986 when last update time is 1462818588 (minimum one second step))
    May 09 20:20:45 proxmox rrdcached[3556]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-node/proxmox) failed with status -1. (/var/lib/rrdcached/db/pve2-node/proxmox: illegal attempt to update using time 1462818016 when last update time is 1462818588 (minimum one second step)
     
  5. informant

    informant Member

    Joined:
    Jan 31, 2012
    Messages:
    667
    Likes Received:
    4
    Solution is, i have remove proxmox rdd file in
    /var/lib/rrdcached/db/pve2-node
    and after remove it works fine.
    regards
     
  6. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,340
    Likes Received:
    286
    Is the time configured in the BIOS correct?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. informant

    informant Member

    Joined:
    Jan 31, 2012
    Messages:
    667
    Likes Received:
    4
    yes, it is.
     
  8. Neppumuck

    Neppumuck New Member

    Joined:
    Feb 13, 2019
    Messages:
    1
    Likes Received:
    0
    Hi, thanks for this Solution!
    In my Case, the BIOS Time was not set right. Proxmox got the right Time from Server. But in BIOS, there was an hour difference.
    After duing it on Post #5, my Graph works fine. :)
     
  9. shantanu

    shantanu Member

    Joined:
    Mar 30, 2012
    Messages:
    97
    Likes Received:
    6
    ntpd doesn't force jump time, it slowly drifts to the correct time, in small jump.

    To force set the time use the cmd 'ntpdate'

    Example:
    # ntpdate -u pool.ntp.org
     
  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