proxmox not restart

Discussion in 'Proxmox VE: Installation and configuration' started by MKnerd, Aug 4, 2018.

  1. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    Hello,

    i have a problem with my proxmox ve installed on soyoustart dedicated server.

    after reboot this not restart properly, i try to go on rescue modo (of soyoustart) but nothing i am not able to do this.

    could u help me to fix this problem?

    i wait ur help

    thanks
     
  2. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
  3. Christian040

    Christian040 New Member

    Joined:
    Aug 6, 2018
    Messages:
    1
    Likes Received:
    0
  4. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,390
    Likes Received:
    212
    without more info, nobody is able to help you
     
  5. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    what kind of information u need?
     
  6. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,390
    Likes Received:
    212
    any error messages or other information you get
     
  7. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    when i try to connect with ssh i am not bale to connected (network connection failed), but the hosting service told me if u ping the ip (and the port 22) this give u back answer.

    i have reboot, from soyoustart control panel, and after this the web gui don't work anymore (xx.xx.xx.xx:8006) and when i use ssh (xx.xx.xx.xx:22) i am not able to connect to server (only in rescue mode)
     
  8. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,390
    Likes Received:
    212
    without access via an ikvm or something it will be hard to help you
     
  9. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    i ask for an access kvm, and they give it to me, let me know how i have to move now
     
  10. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,390
    Likes Received:
    212
    look what error messages you get on boot and act accordingly
     
  11. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    how i can see the boot error?
     
  12. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    i try in rescue and i have this results
    <code>
    root@rescue:/# pveversion -v
    proxmox-ve: 5.2-2 (running kernel: 4.9.103-mod-std-ipv6-64-rescue)
    pve-manager: not correctly installed (running version: 5.2-6/bcd5f008)
    pve-kernel-4.15.17-2-pve: 4.15.17-10
    corosync: 2.4.2-pve5
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: 1.2-2
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.0-8
    libpve-apiclient-perl: 2.0-5
    libpve-common-perl: 5.0-37
    libpve-guest-common-perl: not correctly installed
    libpve-http-server-perl: 2.0-9
    libpve-storage-perl: 5.0-24
    libqb0: 1.0.1-1
    lvm2: 2.02.168-pve6
    lxc-pve: 3.0.0-3
    lxcfs: 3.0.0-1
    novnc-pve: 1.0.0-2
    openvswitch-switch: 2.7.0-3
    proxmox-widget-toolkit: 1.0-19
    pve-cluster: not correctly installed
    pve-container: not correctly installed
    pve-docs: 5.2-5
    pve-firewall: not correctly installed
    pve-firmware: 2.0-5
    pve-ha-manager: not correctly installed
    pve-i18n: 1.0-6
    pve-libspice-server1: 0.12.8-3
    pve-qemu-kvm: 2.11.2-1
    pve-xtermjs: 1.0-5
    qemu-server: not correctly installed
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    </code>
     
  13. aPollO

    aPollO Member
    Proxmox VE Subscriber

    Joined:
    Mar 6, 2014
    Messages:
    71
    Likes Received:
    3
    Can you boot in normal mode? Not rescue! but with kvm console? it this possible?
     
  14. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    i have a kvm but i have trouble with this
     
  15. aPollO

    aPollO Member
    Proxmox VE Subscriber

    Joined:
    Mar 6, 2014
    Messages:
    71
    Likes Received:
    3
    you have to say what the problem is. "trouble" is not a good problem description.
     
  16. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    i was able to reactivate ssh.... now could one help me to restart proxmox ve
     
  17. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    i try to restart service pveproxy and other service but some of this give me failed start
     
  18. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    if i unistall proxmox-ve and reinstall? this can help? i lost my VPS?

    i have proxmox VE installed on dedicated server SOYOUSTART
     
  19. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,390
    Likes Received:
    212
    As long as you don't:

    clearly write what you did
    clearly write what error messages you get

    nobody can help you
     
  20. MKnerd

    MKnerd New Member

    Joined:
    May 28, 2018
    Messages:
    23
    Likes Received:
    0
    ok,

    for restore i see, in rescue mode, the permission of some file in /etc/ssh/ was incorrect. i modify this with correct permission.
    so i was able to restore SSH connection with my server.

    now when i write, in my internet browser, ip:8006 i have this errore ERR_CONNECTION_REFUSED.
    so i write various service status on terminal and this is results (write only the service with failed status):

    Service PVEDAEMON:
    Code:
     pvedaemon.service - PVE API Daemon
       Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Fri 2018-08-10 08:20:10 UTC; 3h 14min ago
      Process: 2032 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)
          CPU: 554ms
    
    ago 10 08:20:10 ns399714 pvedaemon[2032]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
    ago 10 08:20:10 ns399714 pvedaemon[2032]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
    ago 10 08:20:10 ns399714 pvedaemon[2032]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
    ago 10 08:20:10 ns399714 pvedaemon[2032]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
    ago 10 08:20:10 ns399714 pvedaemon[2032]: Compilation failed in require at /usr/bin/pvedaemon line 11.
    ago 10 08:20:10 ns399714 pvedaemon[2032]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
    ago 10 08:20:10 ns399714 systemd[1]: pvedaemon.service: Control process exited, code=exited status=255
    ago 10 08:20:10 ns399714 systemd[1]: Failed to start PVE API Daemon.
    ago 10 08:20:11 ns399714 systemd[1]: pvedaemon.service: Unit entered failed state.
    ago 10 08:20:11 ns399714 systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
    
    service PVEPROXY status:
    Code:
    pveproxy.service - PVE API Proxy Server
       Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Fri 2018-08-10 08:20:11 UTC; 3h 14min ago
      Process: 2081 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
          CPU: 573ms
    
    ago 10 08:20:11 ns399714 pveproxy[2081]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
    ago 10 08:20:11 ns399714 pveproxy[2081]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
    ago 10 08:20:11 ns399714 pveproxy[2081]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 14.
    ago 10 08:20:11 ns399714 pveproxy[2081]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 14.
    ago 10 08:20:11 ns399714 pveproxy[2081]: Compilation failed in require at /usr/bin/pveproxy line 11.
    ago 10 08:20:11 ns399714 pveproxy[2081]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
    ago 10 08:20:11 ns399714 systemd[1]: pveproxy.service: Control process exited, code=exited status=255
    ago 10 08:20:11 ns399714 systemd[1]: Failed to start PVE API Proxy Server.
    ago 10 08:20:11 ns399714 systemd[1]: pveproxy.service: Unit entered failed state.
    ago 10 08:20:11 ns399714 systemd[1]: pveproxy.service: Failed with result 'exit-code'.
    when i try to restart this two service i have this message:

    Service PVEDAEMON restart:
    Code:
    Job for pvedaemon.service failed because the control process exited with error code.
    See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
    
    Servie PVEPROXY restart:
    Code:
    Job for pveproxy.service failed because the control process exited with error code.
    See "systemctl status pveproxy.service" and "journalctl -xe" for details
    if u need more info tell me what u need (what kind of log, what kind of command i have to write and result of this)

    i wait ur answer and sorry but i am not so skilled on linux.
     
  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