Results 1 to 4 of 4

Thread: Connect failed: connect: Connection refused; Connection refused (500)

  1. #1
    Join Date
    Mar 2010
    Posts
    432

    Default Connect failed: connect: Connection refused; Connection refused (500) *SOLVED*

    this issue was solved by running
    Code:
    pvecm updatecerts
    see 2-nd post.
    ---
    Hello
    I have a server which had been running Proxmox 2.0 since December. according to aptitude logs it originally had proxmox-ve-2.6.32 2.0-53 . the node name is fbc241 .

    Today I backed up and removed the vm's and added fbc241 to the cluster. here is pvecm status and nodes:

    Code:
    fbc241 s012 /var/log # pvecm nodes
    Node  Sts   Inc   Joined               Name
       1   M    196   2012-04-16 06:38:08  s009
       2   M    196   2012-04-16 06:38:08  fbc246
       3   M    196   2012-04-16 06:38:08  s002
       4   M    188   2012-04-16 06:37:42  fbc241
    
    fbc241 s012 /var/log # pvecm status
    Version: 6.2.0
    Config Version: 19
    Cluster Name: fbcluster
    Cluster Id: 52020
    Cluster Member: Yes
    Cluster Generation: 196
    Membership state: Cluster-Member
    Nodes: 4
    Expected votes: 4
    Total votes: 4
    Node votes: 1
    Quorum: 3  
    Active subsystems: 5
    Flags: 
    Ports Bound: 0  
    Node name: fbc241
    Node ID: 4
    Multicast addresses: 239.192.203.0 
    Node addresses: 10.100.100.241
    The problem is on the pve screen, when I try to click on fbc241 this error displays:
    "Connect failed: connect: Connection refused; Connection refused (500) "

    Other issues:
    from other nodes ' ssh fbc241 ' requires a password, even when trying 'ssh-copy-id ' .

    /root/.ssh/ :has
    authorized_keys -> /etc/pve/priv/authorized_keys

    but if I copy the original authorized_keys back ssh login does not need a password.

    In the past when I ran into this problem a reinstall is the only solution I could find.

    But it would be good to try to fix this issue incase anyone else runs in to the problem.


    Any suggestions?


    ps: thank you for the great Proxmox PVE system.
    Last edited by bread-baker; 04-16-2012 at 03:08 PM.

  2. #2
    Join Date
    Mar 2010
    Posts
    432

    Default Re: Connect failed: connect: Connection refused; Connection refused (500)

    after checking other threads :

    Code:
    ls -l /etc/pve/local/pve-ssl.pem
    ls: cannot access /etc/pve/local/pve-ssl.pem: No such file or directory
    
    pvecm updatecerts
    fbc241 s012 ~ # ls -l /etc/pve/local/pve-ssl.pem                                                                                      
    -rw-r----- 1 root www-data 1363 Apr 16 08:36 /etc/pve/local/pve-ssl.pem
    still get the error. try rebooting node fbc241

    that fixed pve access. the connection error is gone.

    but ssh logins are not ok:
    Code:
    root@fbc1 /home/rob/Downloads # ssh-copy-id fbc241
    root@fbc241's password: 
    Now try logging into the machine, with "ssh 'fbc241'", and check in:
    
      .ssh/authorized_keys
    
    to make sure we haven't added extra keys that you weren't expecting.
    # 
    # then try to log in, but password is still needed:
    ssh fbc241
    root@fbc241's password:

  3. #3
    Join Date
    Mar 2010
    Posts
    432

    Default Re: Connect failed: connect: Connection refused; Connection refused (500)

    the ssh issue fixed it self. I do not know how, my guess is a cluster cronscript did something.

  4. #4
    Join Date
    Mar 2010
    Posts
    432

    Default Re: Connect failed: connect: Connection refused; Connection refused (500)

    the ssh issue had something to do with the old server running one of our cronscripts which was ok for non cluster setup.
    Last edited by bread-baker; 04-16-2012 at 05:15 PM. Reason: solved, issue was nothing to do with PVE

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •