However, having worked on these before, I also remember having a central workstation where I could push to every machine I was connected to. If I had to send a file, an update, a command, I could do a broadcast and boom, every machine was done at once. Duplicating the code across two, twenty, or two hundred for that matter, shouldn't be that hard(unless there are errors and THEN you have to do them all individually, god help that poor soul).
If servers really need to rebooted, things will take time. Primarily because things need to be started up in the proper sequence; like you can't start the login server ere you have an up and running database server, SAMBA servers, all sorts of connectivity hubs, etc. THAT is what takes time, not pushing a patch per se.
If servers really need to rebooted, things will take time. Primarily because things need to be started up in the proper sequence; like you can't start the login server ere you have an up and running database server, SAMBA servers, all sorts of connectivity hubs, etc. THAT is what takes time, not pushing a patch per se.
Update 5 (10:19 AM PST) Running a few final checks and it shouldn't be much longer until the servers are unlocked. We'll keep you posted.
Why do I always fall for that?! They will keep extending it, and then I need to go to bed, and the day is shot. Seriously, 7 hours is almost a full working day.
When it comes to maintenance and downtime, Dwight on the NeverWinter forums takes the gold star for 'Community Management', Smirk & Trendy should take heed as by comparison they look pretty lackluster!
I hate to say this as I actually like Smirk & Trendy but this is certainly one area where you guys need to improve your performance!
Um, samba not for sure, you don't use SMB protocol for security reasons in a production environment, sFTP is more likely because it's harder for some random ransomware to encrypt everything (duh!) at the shared path. But whatever, all the system built-in services on linux server like samba, ssh, ftpd and similar start in several seconds so i don't think reboot is an issue if they are indeed using *nix servers. But fsck running on a multiple drive RAID... oooh, yeah... that would take exactly two hours if they rebooted the server(s) and one/some of them decided it's perfect time to check the filesystem. You don't mess with fsck once it starts!
We can really only guess what went wrong with the upgrade but it's besides the point - we can't either help or influence it, all we can do is play the sys admin cluedo. It was the curly tech support guy with a magnet v.s. third member of raid array. He dood it!
LOL. I take your word for it. Point just was that things need to be booted in sequence, and that THAT is what takes time.
Star Trek Online @trekonlinegame · 2m 2 minutes ago
Thank you for your patience everyone, Holodeck is back online! Chat service will remain offline until further notice
Comments
If servers really need to rebooted, things will take time. Primarily because things need to be started up in the proper sequence; like you can't start the login server ere you have an up and running database server, SAMBA servers, all sorts of connectivity hubs, etc. THAT is what takes time, not pushing a patch per se.
samba server!? rofl hahaha m)
I am guessing this "Samba" is Simba's Mirror Self and that Samba is actually more like Scar right?
Why do I always fall for that?! They will keep extending it, and then I need to go to bed, and the day is shot. Seriously, 7 hours is almost a full working day.
Yea and tomorrow and next week we can see what a long hard day of work it was.
Looking for a fun PvE fleet? Join us at Omega Combat Division today.
I hate to say this as I actually like Smirk & Trendy but this is certainly one area where you guys need to improve your performance!
LOL. I take your word for it.