/ Register

Discover Centmin Mod today
Register Now

Vultr SSH time outs with Vultr

Discussion in 'Virtual Private Server (VPS) hosting' started by Josephm, Sep 13, 2014.

Tags:
Previous Thread Next Thread
Loading...
Page 2 of 2
  1. Sep 20, 2014 #21
    Josephm

    Josephm Active Member

    132
    44
    28
    Aug 26, 2014
    Ratings:
    +48
    Local Time:
    11:35 PM
    1.9.5
    10.0.21
    Another confirmation that no more time-out issue :D
    Code:
    [root@vu7 ~]# uptime
 01:28:00 up 1 day,  8:04,  1 user,  load average: 0.00, 0.01, 0.05

     
  2. Oct 22, 2014 #22
    Josephm

    Josephm Active Member

    132
    44
    28
    Aug 26, 2014
    Ratings:
    +48
    Local Time:
    11:35 PM
    1.9.5
    10.0.21
    I had another timeout problem at Vultr. I suspect that the second NIC which uses private network (internal IP) might make my connection timeout. I used your latest beta script with fresh Centos 7:
    And this is my var/log/messages
    [​IMG]
    [​IMG]
    Will try single NIC to see if problem still occurs.
     
    Last edited: Oct 22, 2014
  3. Oct 22, 2014 #23
    eva2000

    eva2000 Administrator Staff Member

    55,236
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,832
    Local Time:
    2:35 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    is this the same vps that you got timeout in 1st post of this thread ?
     
  4. Oct 22, 2014 #24
    eva2000

    eva2000 Administrator Staff Member

    55,236
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,832
    Local Time:
    2:35 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    just confirmed with Vultr support that multicast dns isn't used by them but CentOS 7 default enables avahi-daemon which uses multicast dns i believe, so you can disable it on CentOS 7 (do not remove avahi-daemon just disable and stop it service - removing it will remove network service and all ip functionality).

    Code:
    systemctl stop avahi-daemon.socket avahi-daemon.service
systemctl disable avahi-daemon.socket avahi-daemon.service
    see if that works.. if it does will add to check for CentOS 7 only step to run
     
  5. Oct 22, 2014 #25
    Josephm

    Josephm Active Member

    132
    44
    28
    Aug 26, 2014
    Ratings:
    +48
    Local Time:
    11:35 PM
    1.9.5
    10.0.21
    It's not the same my 1st post vps, I'll try to stop and disable avahi-daemon to know where it solves this problem.

    Edited: Just stopped and disabled daemon and it's not solved. The strange thing is that vps in Chicago has this issue, I tested in Atlanta and Seattle location and did not see this problem.
     
    Last edited: Oct 22, 2014
  6. Oct 23, 2014 #26
    Josephm

    Josephm Active Member

    132
    44
    28
    Aug 26, 2014
    Ratings:
    +48
    Local Time:
    11:35 PM
    1.9.5
    10.0.21
    I switched both eth0 and eth1 to static ip addresses instead of DHCP and it's fine now.
     
  7. Oct 23, 2014 #27
    eva2000

    eva2000 Administrator Staff Member

    55,236
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,832
    Local Time:
    2:35 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    interesting solution but thanks for sharing :)
     
  8. Nov 23, 2021 #28
    rdan

    rdan Well-Known Member

    5,449
    1,410
    113
    May 25, 2014
    Ratings:
    +2,204
    Local Time:
    12:35 AM
    Mainline
    10.2
    So port 67/68 isn't really needed to open/whitelist on most or all CentOS7 CMM install?
     
  9. Nov 23, 2021 #29
    eva2000

    eva2000 Administrator Staff Member

    55,236
    12,253
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,832
    Local Time:
    2:35 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
Previous Thread Next Thread
Loading...
Page 2 of 2

.