Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Offers
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

1…126127129131132…339

Comments

  • bedr8mbedr8m Member

    im done

  • ravenchadravenchad Member

    @xmd5 said:
    Ryzen Special 2560 None of them are active?

    maybe. since mine is still not active :). still waiting PATIENTLY. 🙏

  • plumbergplumberg Veteran, Megathread Squad

    @bedr8m said:
    im done

    Try again, this time read last to first page. Come back after 4 days to show you have really understood how to get this plan

  • qwerttaaqwerttaa Member

    oh shit...039, auto shutdown again

    utc+8

    Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:17:01 AAA CRON[4103]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session closed for user root
Apr 12 00:47:01 AAA CRON[4112]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:47:01 AAA CRON[4113]: (root) CMD ("/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null)
Apr 12 00:47:02 AAA CRON[4112]: pam_unix(cron:session): session closed for user root
Apr 12 00:49:33 AAA sshd[3504]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 63 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-63.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 63.
Apr 12 00:49:33 AAA sshd[3527]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 65 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Consumed 2.155s CPU time.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 65.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Manager for UID 0...
Apr 12 00:49:43 AAA systemd[3507]: Activating special unit Exit the Session...
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Main User Target.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Basic System.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Paths.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Sockets.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Timers.
Apr 12 00:49:43 AAA systemd[3507]: Closed D-Bus User Message Bus Socket.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG network certificate management daemon.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 00:49:43 AAA systemd[3507]: Removed slice User Application Slice.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Shutdown.
Apr 12 00:49:43 AAA systemd[3507]: Finished Exit the Session.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Exit the Session.
Apr 12 00:49:43 AAA systemd[3508]: pam_unix(systemd-user:session): session closed for user root
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Manager for UID 0.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Runtime Directory /run/user/0...
Apr 12 00:49:43 AAA systemd[1]: run-user-0.mount: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Runtime Directory /run/user/0.
Apr 12 00:49:43 AAA systemd[1]: Removed slice User Slice of UID 0.
Apr 12 00:49:43 AAA systemd[1]: user-0.slice: Consumed 2.253s CPU time.
-- Boot dc40196210b744cf892XXXXXXXXXXXXX --
Apr 12 01:10:31 AAA kernel: Linux version 5.16.0-0.bpo.4-cloud-amd64 ([email protected]) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld>
lines 78-121

    manually boot at 01:10:31

    anything unusual?

  • FrankZFrankZ Barred
    edited April 2022

    Node 39 has been looking good from my point of view since ~6:30 AM PDT. (~5 hours) Network has been real world stable with less then 1% cpu steal rate. No noticeable disk I/O issues. I am not doing any yabs or checking maximum network transfer rates. No shutdowns. I was able to install CentOS 7 from template in the billing panel and from CentOS7server ISO in SolusVM without any problems. Thank you VirMach.

    Thanked by 2ZA_capetown FAT32
  • VirMachVirMach Member, Patron Provider

    @FrankZ said:

    Node 39 has been looking good from my point of view since ~6:30 AM PDT. (~5 hours) Network has been real world stable with less then 1% cpu steal rate. No noticeable disk I/O issues. I am not doing any yabs or checking maximum network transfer rates. Thank you VirMach.

    CPU steal only 1%? Network is stable? Let me fix all that with more activations. Actually this node is the lowest CPU usage right now and highest RAM usage. That usually happens when everyone gets settled down into ... the idle zone.

    Thanked by 4FrankZ skorous ZA_capetown Xrmaddness
  • qwerttaaqwerttaa Member

    @qwerttaa said:
    oh shit...039, auto shutdown again

    utc+8

    Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:17:01 AAA CRON[4103]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session closed for user root
Apr 12 00:47:01 AAA CRON[4112]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:47:01 AAA CRON[4113]: (root) CMD ("/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null)
Apr 12 00:47:02 AAA CRON[4112]: pam_unix(cron:session): session closed for user root
Apr 12 00:49:33 AAA sshd[3504]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 63 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-63.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 63.
Apr 12 00:49:33 AAA sshd[3527]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 65 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Consumed 2.155s CPU time.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 65.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Manager for UID 0...
Apr 12 00:49:43 AAA systemd[3507]: Activating special unit Exit the Session...
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Main User Target.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Basic System.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Paths.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Sockets.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Timers.
Apr 12 00:49:43 AAA systemd[3507]: Closed D-Bus User Message Bus Socket.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG network certificate management daemon.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 00:49:43 AAA systemd[3507]: Removed slice User Application Slice.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Shutdown.
Apr 12 00:49:43 AAA systemd[3507]: Finished Exit the Session.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Exit the Session.
Apr 12 00:49:43 AAA systemd[3508]: pam_unix(systemd-user:session): session closed for user root
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Manager for UID 0.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Runtime Directory /run/user/0...
Apr 12 00:49:43 AAA systemd[1]: run-user-0.mount: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Runtime Directory /run/user/0.
Apr 12 00:49:43 AAA systemd[1]: Removed slice User Slice of UID 0.
Apr 12 00:49:43 AAA systemd[1]: user-0.slice: Consumed 2.253s CPU time.
-- Boot dc40196210b744cf892XXXXXXXXXXXXX --
Apr 12 01:10:31 AAA kernel: Linux version 5.16.0-0.bpo.4-cloud-amd64 ([email protected]) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld>
lines 78-121

    manually boot at 01:10:31

    anything unusual?

    from nginx
    so, maybe the time between 01:03:06 ~ 01:12:05???

    80.251.213.115 - - [12/Apr/2022:01:00:47 +0800] "GET / HTTP/1.1" 101 291827 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:03:06 +0800] "GET / HTTP/1.1" 101 5662 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:12:05 +0800] "GET / HTTP/1.1" 101 6463 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:13:47 +0800] "GET / HTTP/1.1" 101 15526 "-" "Go-http-client/1.1" "-"
  • VirMachVirMach Member, Patron Provider

    @qwerttaa said:

    @qwerttaa said:
    oh shit...039, auto shutdown again

    utc+8

    Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:17:01 AAA CRON[4103]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session closed for user root
Apr 12 00:47:01 AAA CRON[4112]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:47:01 AAA CRON[4113]: (root) CMD ("/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null)
Apr 12 00:47:02 AAA CRON[4112]: pam_unix(cron:session): session closed for user root
Apr 12 00:49:33 AAA sshd[3504]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 63 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-63.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 63.
Apr 12 00:49:33 AAA sshd[3527]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 65 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Consumed 2.155s CPU time.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 65.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Manager for UID 0...
Apr 12 00:49:43 AAA systemd[3507]: Activating special unit Exit the Session...
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Main User Target.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Basic System.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Paths.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Sockets.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Timers.
Apr 12 00:49:43 AAA systemd[3507]: Closed D-Bus User Message Bus Socket.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG network certificate management daemon.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 00:49:43 AAA systemd[3507]: Removed slice User Application Slice.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Shutdown.
Apr 12 00:49:43 AAA systemd[3507]: Finished Exit the Session.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Exit the Session.
Apr 12 00:49:43 AAA systemd[3508]: pam_unix(systemd-user:session): session closed for user root
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Manager for UID 0.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Runtime Directory /run/user/0...
Apr 12 00:49:43 AAA systemd[1]: run-user-0.mount: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Runtime Directory /run/user/0.
Apr 12 00:49:43 AAA systemd[1]: Removed slice User Slice of UID 0.
Apr 12 00:49:43 AAA systemd[1]: user-0.slice: Consumed 2.253s CPU time.
-- Boot dc40196210b744cf892XXXXXXXXXXXXX --
Apr 12 01:10:31 AAA kernel: Linux version 5.16.0-0.bpo.4-cloud-amd64 ([email protected]) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld>
lines 78-121

    manually boot at 01:10:31

    anything unusual?

    from nginx
    so, maybe the time between 01:03:06 ~ 01:12:05???

    80.251.213.115 - - [12/Apr/2022:01:00:47 +0800] "GET / HTTP/1.1" 101 291827 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:03:06 +0800] "GET / HTTP/1.1" 101 5662 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:12:05 +0800] "GET / HTTP/1.1" 101 6463 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:13:47 +0800] "GET / HTTP/1.1" 101 15526 "-" "Go-http-client/1.1" "-"

    What's your info on that? DM me your IP. I'll check logs on my end.

  • qwerttaaqwerttaa Member

    @VirMach said:

    @qwerttaa said:

    @qwerttaa said:
    oh shit...039, auto shutdown again

    utc+8

    Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:17:01 AAA CRON[4103]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 12 00:17:01 AAA CRON[4102]: pam_unix(cron:session): session closed for user root
Apr 12 00:47:01 AAA CRON[4112]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 12 00:47:01 AAA CRON[4113]: (root) CMD ("/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null)
Apr 12 00:47:02 AAA CRON[4112]: pam_unix(cron:session): session closed for user root
Apr 12 00:49:33 AAA sshd[3504]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 63 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-63.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 63.
Apr 12 00:49:33 AAA sshd[3527]: pam_unix(sshd:session): session closed for user root
Apr 12 00:49:33 AAA systemd-logind[284]: Session 65 logged out. Waiting for processes to exit.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Deactivated successfully.
Apr 12 00:49:33 AAA systemd[1]: session-65.scope: Consumed 2.155s CPU time.
Apr 12 00:49:33 AAA systemd-logind[284]: Removed session 65.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Manager for UID 0...
Apr 12 00:49:43 AAA systemd[3507]: Activating special unit Exit the Session...
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Main User Target.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Basic System.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Paths.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Sockets.
Apr 12 00:49:43 AAA systemd[3507]: Stopped target Timers.
Apr 12 00:49:43 AAA systemd[3507]: Closed D-Bus User Message Bus Socket.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG network certificate management daemon.
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 00:49:43 AAA systemd[3507]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 00:49:43 AAA systemd[3507]: Removed slice User Application Slice.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Shutdown.
Apr 12 00:49:43 AAA systemd[3507]: Finished Exit the Session.
Apr 12 00:49:43 AAA systemd[3507]: Reached target Exit the Session.
Apr 12 00:49:43 AAA systemd[3508]: pam_unix(systemd-user:session): session closed for user root
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Manager for UID 0.
Apr 12 00:49:43 AAA systemd[1]: Stopping User Runtime Directory /run/user/0...
Apr 12 00:49:43 AAA systemd[1]: run-user-0.mount: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: [email protected]: Deactivated successfully.
Apr 12 00:49:43 AAA systemd[1]: Stopped User Runtime Directory /run/user/0.
Apr 12 00:49:43 AAA systemd[1]: Removed slice User Slice of UID 0.
Apr 12 00:49:43 AAA systemd[1]: user-0.slice: Consumed 2.253s CPU time.
-- Boot dc40196210b744cf892XXXXXXXXXXXXX --
Apr 12 01:10:31 AAA kernel: Linux version 5.16.0-0.bpo.4-cloud-amd64 ([email protected]) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld>
lines 78-121

    manually boot at 01:10:31

    anything unusual?

    from nginx
    so, maybe the time between 01:03:06 ~ 01:12:05???

    80.251.213.115 - - [12/Apr/2022:01:00:47 +0800] "GET / HTTP/1.1" 101 291827 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:03:06 +0800] "GET / HTTP/1.1" 101 5662 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:12:05 +0800] "GET / HTTP/1.1" 101 6463 "-" "Go-http-client/1.1" "-"
80.251.213.115 - - [12/Apr/2022:01:13:47 +0800] "GET / HTTP/1.1" 101 15526 "-" "Go-http-client/1.1" "-"

    What's your info on that? DM me your IP. I'll check logs on my end.

    thx
    check your Inbox

  • FrankZFrankZ Barred

    @VirMach said: CPU steal only 1%? Network is stable? Let me fix all that with more activations. Actually this node is the lowest CPU usage right now and highest RAM usage. That usually happens when everyone gets settled down into ... the idle zone.

    Only running a DNS server, a from Tokyo monitoring script, and a small website on the 1.5GB VPS. I was waiting to step on the accelerator harder until things settled down. I will still probably wait a few days to start doing large file transfers on the larger one, which is also on Node 39, so save a little cpu and I/O for me. :)

    Thanked by 1bdl
  • qwerttaaqwerttaa Member

    @FrankZ said:

    @VirMach said: CPU steal only 1%? Network is stable? Let me fix all that with more activations. Actually this node is the lowest CPU usage right now and highest RAM usage. That usually happens when everyone gets settled down into ... the idle zone.

    Only running a DNS server, a from Tokyo monitoring script, and a small website on the 1.5GB VPS. I was waiting to step on the accelerator harder until things settled down. I will still probably wait a few days to start doing large file transfers on the larger one, which is also on Node 39, so save a little cpu and I/O for me. :)

    emmmmm....

    top - 03:09:25 up 1:58, 1 user, load average: 0.00, 0.00, 0.00
    Tasks: 71 total, 2 running, 69 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 95.2 id, 0.0 wa, 0.0 hi, 1.9 si, 2.9 st
    MiB Mem : 348.5 total, 192.7 free, 59.0 used, 96.8 buff/cache
    MiB Swap: 256.0 total, 256.0 free, 0.0 used. 279.0 avail Mem

    only used to fxxk the wall from my country....

    Thanked by 1FrankZ
  • FrankZFrankZ Barred 
    top - 14:15:15 up 22:11,  2 users,  load average: 0.04, 0.03, 0.05
Tasks:  97 total,   2 running,  95 sleeping,   0 stopped,   0 zombie
%Cpu(s):  6.3 us,  7.3 sy,  0.0 ni, 85.0 id,  0.0 wa,  0.0 hi,  0.7 si,  0.7 st
KiB Mem :  1530728 total,   499304 free,   482868 used,   548556 buff/cache
KiB Swap:   524284 total,   524284 free,        0 used.   880360 avail Mem

    The new nodes with Ryzen and NVMe disks make a huge difference in load average compared to the old Xeon nodes. It almost look like I am idling.

    Thanked by 1ZA_capetown
  • qwerttaaqwerttaa Member

    ??????

    again...when i "apt-get autoclean"

    then...shutdown again...

    im off to bed

    good luck

  • qwerttaaqwerttaa Member

    @FrankZ said:
    top - 14:15:15 up 22:11, 2 users, load average: 0.04, 0.03, 0.05
    Tasks: 97 total, 2 running, 95 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 6.3 us, 7.3 sy, 0.0 ni, 85.0 id, 0.0 wa, 0.0 hi, 0.7 si, 0.7 st
    KiB Mem : 1530728 total, 499304 free, 482868 used, 548556 buff/cache
    KiB Swap: 524284 total, 524284 free, 0 used. 880360 avail Mem

    The new nodes with Ryzen and NVMe disks make a huge difference in load average compared to the old Xeon nodes. It almost look like I am idling.

    Good Neighborhood :wink:

    Thanked by 1FrankZ
  • foitinfoitin Member
    edited April 2022

    That's why you don't want early deployment.
    Things are bound to break.
    Unknown issues are basically inevitable. :)

  • AlwaysSkintAlwaysSkint Member

    @foitin said:
    That's why you don't want early deployment.
    Things are bound to break.
    Unknown issues are basically inevitable. :)

    Seemingly your short paragraph doesn't properly translate, for some communities. :|

    Thanked by 1bdl
  • foitinfoitin Member

    @AlwaysSkint said:

    @foitin said:
    That's why you don't want early deployment.
    Things are bound to break.
    Unknown issues are basically inevitable. :)

    Seemingly your short paragraph doesn't properly translate, for some communities. :|

    Then I guess they'll learn haste makes waste the hard way.
    It's just NVMe plans now. On storage VPS, even a small issue can potentially result in huge amount of data losses :)

  • VirMachVirMach Member, Patron Provider

    @qwerttaa said:
    ??????

    again...when i "apt-get autoclean"

    then...shutdown again...

    im off to bed

    good luck

    It's the same issue I see with everyone else on Debian 10 + 384MB. It's crashing due to OOM.

  • miaumiau Member

    @VirMach said:

    @qwerttaa said:
    ??????

    again...when i "apt-get autoclean"

    then...shutdown again...

    im off to bed

    good luck

    It's the same issue I see with everyone else on Debian 10 + 384MB. It's crashing due to OOM.

    Debian template doesn't create swap at all or what?

  • duckeeyuckduckeeyuck Member

    @miau said: Debian template doesn't create swap at all or what?

    You can't create it at all of what?

  • skorousskorous Member

    @VirMach said: It's the same issue I see with everyone else on Debian 10 + 384MB. It's crashing due to OOM.

    So it crashes due to OOM and then the automation shuts it down the way it would one of the invalid OS machine?

  • miaumiau Member
    edited April 2022

    @duckeeyuck said:

    @miau said: Debian template doesn't create swap at all or what?

    You can't create it at all of what?

    I don't use Debian template, so I don't know how it is going over there.
    But there are too many people encountering oom as if the swap were never created by default.
    Sure you can create it, but you can't count on everyone on LET to know to do anything beyond normal shell usage.

    In Alma template 2gb swapfile is created on deployment.

    People that getting their entire box nuked from oom maybe earlyoom could help?
    https://github.com/rfjakob/earlyoom

  • totototototo Member
    edited April 2022

    This is just a report, but the upload speed now looks a bit slow.

    root@TYOC039:~# speedtest -L
Closest servers:

    ID  Name                           Location             Country
==============================================================================
 20976  GLBB Japan                     Tokyo                Japan
 21569  i3D.net                        Tokyo                Japan
 38241  BudgetVM                       Tokyo                Japan
 28910  fdcservers.net                 Tokyo                Japan
 24333  Rakuten Mobile, Inc            Tokyo                Japan
 44988  Misaka Network, Inc.           Tokyo                Japan
 48463  IPA CyberLab 400G              Tokyo                Japan
 14623  IPA CyberLab                   Bunkyo               Japan
  8407  Allied Telesis Capital Corporation Sagamihara           Japan
  6087  Allied Telesis Capital Corporation Fussa-shi            Japan

root@TYOC039:~# speedtest -s 38241

   Speedtest by Ookla

     Server: BudgetVM - Tokyo (id = 38241)
        ISP: Owl Limited
    Latency:     2.94 ms   (9.44 ms jitter)
   Download:   291.67 Mbps (data used: 346.0 MB )
     Upload:    17.36 Mbps (data used: 33.6 MB )
Packet Loss:     0.0%
 Result URL: https://www.speedtest.net/result/c/4050527f-d83f-4c26-982f-dd1f6427d848


root@TYOC039:~# speedtest -s 21569

   Speedtest by Ookla

     Server: i3D.net - Tokyo (id = 21569)
        ISP: Owl Limited
    Latency:     2.52 ms   (0.52 ms jitter)
   Download:   244.75 Mbps (data used: 445.8 MB )
     Upload:    26.42 Mbps (data used: 29.6 MB )
Packet Loss:     1.0%
 Result URL: https://www.speedtest.net/result/c/dbe02969-5c69-4fb6-a36a-870f20d8faef

root@TYOC039:~# speedtest -s 48463

   Speedtest by Ookla

     Server: IPA CyberLab 400G - Tokyo (id = 48463)
        ISP: Owl Limited
    Latency:     3.10 ms   (1.60 ms jitter)
   Download:   223.70 Mbps (data used: 334.8 MB )
     Upload:    21.10 Mbps (data used: 38.4 MB )
Packet Loss:     1.8%
 Result URL: https://www.speedtest.net/result/c/accfedba-de0b-4efc-9088-9a910cd785fd
  • umzakumzak Member

    @VirMach said:
    Everyone who is potentially causing issues will be suspended and re-created on another node using a stable OS.

    this is the result of bench.monster on node 40, after a few vps were suspended, the IO score was better, but the network speed didn't seem to have increased much, maybe there are still many who do speedtest

  • miaumiau Member

    Node 39 suddenly under high steal again

  • MartachjbvguknvMartachjbvguknv Member
    edited April 2022

    @VirMach said:

    @vhhjkgl said:

    @Martachjbvguknv said:
    The network of TYOC040 is broken again.
    I ping gateway from my server, and it return
    about 300±200ms.

    virmach checked the Node40 and still did not find the cause of the problem。

    The cause is already found.

    Now we're still working on the permanent fix. I'm trying to avoid doing what you or someone else previously suggested which is just abandoning the node. It's not that the node has any problems, but it's possible that the fix may take longer than just moving everyone to another node. I'm still evaluating.

    Now it down to 100±100ms, nice.

  • AlwaysSkintAlwaysSkint Member
    edited April 2022

    Is it me? If you purchase a 384MB RAM VPS, don't know how to configure swap and don't realise that you're gonna be restricted in what software can be used, then you really shouldn't have bought it.

    (Oh, and a 2GB swap is plain silly, in my book - but hey, it's fast NVMe, so why not? /s )

    Thanked by 1FrankZ
  • sour_lemonsour_lemon Member

    37 node network problems

    root@45:~# traceroute 45.149.159.1

    traceroute to 45.149.159.1 (45.149.159.1), 30 hops max, 46 byte packets
    1 45.66.128.1.static.xtom.com (45.66.128.1) 127.956 ms 172.714 ms 111.461 ms
    2 45.149.159.1 (45.149.159.1) 739.663 ms * *

  • passwapasswa Member

    Sudden high latency on nodes 33 and 37

  • 360717125360717125 Member

    @VirMach said:

    @qwerttaa said:
    ??????

    again...when i "apt-get autoclean"

    then...shutdown again...

    im off to bed

    good luck

    It's the same issue I see with everyone else on Debian 10 + 384MB. It's crashing due to OOM.

    Excuse me, how long does it take for the waiting 768 I purchased to agree to apply for a refund and return the balance for more than a day. The service order is #414812

This discussion has been closed.