tenpera
tenpera
About
- Username
- tenpera
- Joined
- Visits
- 4,205
- Last Active
- Roles
- Member
- Thanked
- 69
Comments
-
Thanks for offering.
-
(Quote) Absolutely Nothing.
-
Merry Xmas 2023, Let's try Silicon Cloud
-
maybe @VirMach wants you to give up those cheap stuffs.
-
your site is down.
-
I have one vm in NYBC035, it has been working flawlessly.
-
@VirMach, I have one of those Flash Special, not standard vm, can I use Dallas Data Wipe & Redeployment ticket? Or not allowed?
-
@VirMach so, simply put it, DALZ007 won't be operational this year, right?
-
@VirMach DALZ007 situation is unlikely to change in the foreseeable future?
-
edit
-
I wish @VirMach will give a flash deal to those who've been waiting for months for their M/C work, aka DALZ007 customers.
-
thank you for the memory.
-
Happy BF 2023, Let's trail Silicon Cloud
-
Happy BF 2023, Let's try Silicon Cloud
-
Been waiting for OKC promo, no dice?
-
EASYVM BF 2023!
-
ssh -p 1234 user@ipv6 address (port1234)
-
LAX1Z014 -> SEAZ002 is now fully restored in San Jose, working fine. Thanks @VirMach
-
LAX1Z014 The node is currently locked what does that mean?
-
@crunchbits, PA is not ready yet?
-
@mxmla do I use port 22 for ssh?
-
@VirMach, no news about DALZ007?
-
@VirMach, any news regarding DALZ007 ?
-
@VirMach, about LAX1Z014, still fixing? It gives ** failed to raise a network. ** on vnc.
-
LAX1Z014 failed to raise a network. i.p is not pinging, dead. probably takes longer time.
-
@FrankZ, thanks for update, I'm on same boat with 193.93.xx.xxx, but it does not even ping, unmount stuff, reconfiguration, etc, still fails to raise network. weird.
-
so the server is in Italy?
-
@VirMach, so SEAZ002 will go into one of LAX1Z016, LAX1Z015, LAX1Z014, and LAX1Z012?
-
@VirNach, on LAXA-005, is 66.59.xxx.xxx will be permanent or 141.11.xxx.xx?
-
so migration from Seattle to LA is not happening?
-
DALZ007 Operation Timed Out After 90000 Milliseconds With 0 Bytes Received DANZ001 The node is currently locked SEAZ002 The node is currently locked Priority Queue [SEA] Migrate Immediately to [LAX] nothing happening.
-
@VirMach, what's happening with migration from Seattle to LAX (Priority Queue)?
-
DALZ007 Operation Timed Out After 90000 Milliseconds With 0 Bytes Received PHXZ001 The node is currently locked SEAZ002 The node is currently locked DANZ001 The node is currently locked
-
@VirMach, good idea, like OKC. If My Dallas vm can move to OKC, I will wait a month.
-
@VirMach, pls confirm whether DALZ007 moved to N.Y or stays. Also Migrating from Seattle to LAX is on hold or going forward?
-
Dalz007 is up according to Status page, but actually Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
-
@VirMach, my ticket shows "Priority Queue", I think I'm safe.