Warning: Creating default object from empty value in [path]/packages/vbcms/controller/list.php on line 425
SWGEmu Forums - Vlada
  • Vlada

    by Published on 08-14-2017 01:18 PM   

    Basilisk extended downtime

    Posted August 9th 2017
    The SWGEmu Staff




    Basilisk extended downtime


    While doing a routine backup before the merge one of the HDD's died, unfortunately that was the second one we lost in a matter of weeks. Right now TheAnswer and the rest of development staff are discussing the options and trying to figure out how best to try to recover all Basilisks data. Of course, with two HDD's gone, there is a strong possibility that what they recover is too corrupt and unusable or they may not even manage to recover all the necessary data to restore Basilisk in its original state before merging it with Publish 9 code and we will be forced to do a full database wipe. Of course its still early to give any predictions but one thing is for sure, we are not at a point where we can definitely say that we will be able to move forward one way or the other.


    We apologize for the extended downtime that is probably going to last for days.


    No matter the the outcome, we thank you for your dedication and your continuous support. Of course we will keep you posted as things progress. As soon as we have any info, you will have it too.

    Update 6:

    Quote Originally Posted by Miztah View Post
    Alright folks, here's our current status. From what we can tell, our database is in good enough shape to proceed with another Publish 9 merge attempt. There's still a lot of potential for corruption or database issues to crop up that we haven't seen, so we're going to be taking some extra precautions in case those issues do pop up. Because of this, when the server is taken down, expect an extended downtime before it comes back up with the new publish.

    Quote Originally Posted by Miztah View Post
    Our current schedule is looking like Basilisk will be taken down approximately 12 hours from now. That timeframe may change between now and then. Once it's taken down, we'll start the process of backing up the database again. With the size of the database, this alone will take a fair amount of time, so we're not going to give an ETA on when it will be back up. Once Basilisk does come up, the server's new navmesh system will begin building meshes for all static and player cities as well as POI's, which will also take some time. Expect the server to remain locked for a while after it comes up.

    TLDR: When we take the server down, expect the update process to take a while to complete, especially with the issues we ran into over the past few days. We'll get the server up and running with Pub9 as quickly as we can.


    Update 5:


    Quote Originally Posted by TheAnswer
    Its a 48 hour test, so its ongoing. But, no bad news so far.
    UPDATE 4:

    Quote Originally Posted by Miztah View Post
    Alright folks, update time. We've managed a recovery of the database and we've got everything copied over to our new SSD's. We're letting Bas run for the weekend as a stress test on the database to ensure there is no corruption that didn't pop up initially. This means that for this weekend, Basilisk is going to remain on Publish 8. We're looking to give the Publish 9 merge another shot on Monday, assuming all goes well over the next 48 hours. We'll update regarding Pub9 closer to Monday when we know for sure.

    In the meantime, continue on Basilisk as you normally would. We'll be keeping an eye out on our side for any potential stability issues.

    Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

    UPDATE 3:

    Quote Originally Posted by TheAnswer
    We finished uploading 1.1TB of data and now we're going though it.
    UPDATE 2:

    Quote Originally Posted by Miztah View Post
    To clarify a bit, Basilisk was up but still in the process of validating the integrity of most of the database objects. The server is currently running through our backup HDD's, which is causing the server's loading to take a lot longer than it normally would on SSD's. We shut down the login server because any actions triggered on Bas will delay the database check, and it's going to take long enough as it is.
    Quote Originally Posted by Miztah View Post
    The good news is, the server didn't explode using the recovered database. There's no current bad news, but as of right now, that's the only good news. We still have to verify that all of the objects in the database are actually valid and load properly, and it will take time. The possibility of a wipe still remains if we find too much corrupted data. Time will tell, but in the meantime you'll see Basilisk go online and offline multiple times, but you won't be able to access it. Those still connected will not be able to reconnect when they disconnect, and in the interest of getting this testing done as quickly as possible, they should disconnect on their own anyway.


    UPDATE:


    Quote Originally Posted by Ivojedi View Post
    About the loading status: We are attempting to load a test db instance to check for data integrity. This should give us an indication of whether we'll need to wipe or not. It's loading on the HDDs so it's slow and will take time. Thanks for the continued patience.


    ~The SWGEMu Staff
    by Published on 08-09-2017 03:27 PM   

    Basilisk extended downtime

    Posted August 9th 2017
    The SWGEmu Staff




    Basilisk extended downtime


    While doing a routine backup before the merge one of the HDD's died, unfortunately that was the second one we lost in a matter of weeks. Right now TheAnswer and the rest of development staff are discussing the options and trying to figure out how best to try to recover all Basilisks data. Of course, with two HDD's gone, there is a strong possibility that what they recover is too corrupt and unusable or they may not even manage to recover all the necessary data to restore Basilisk in its original state before merging it with Publish 9 code and we will be forced to do a full database wipe. Of course its still early to give any predictions but one thing is for sure, we are not at a point where we can definitely say that we will be able to move forward one way or the other.


    We apologize for the extended downtime that is probably going to last for days.


    No matter the the outcome, we thank you for your dedication and your continuous support. Of course we will keep you posted as things progress. As soon as we have any info, you will have it too.


    Update 5:


    Quote Originally Posted by TheAnswer
    Its a 48 hour test, so its ongoing. But, no bad news so far.
    UPDATE 4:

    Quote Originally Posted by Miztah View Post
    Alright folks, update time. We've managed a recovery of the database and we've got everything copied over to our new SSD's. We're letting Bas run for the weekend as a stress test on the database to ensure there is no corruption that didn't pop up initially. This means that for this weekend, Basilisk is going to remain on Publish 8. We're looking to give the Publish 9 merge another shot on Monday, assuming all goes well over the next 48 hours. We'll update regarding Pub9 closer to Monday when we know for sure.

    In the meantime, continue on Basilisk as you normally would. We'll be keeping an eye out on our side for any potential stability issues.

    Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

    UPDATE 3:

    Quote Originally Posted by TheAnswer
    We finished uploading 1.1TB of data and now we're going though it.
    UPDATE 2:

    Quote Originally Posted by Miztah View Post
    To clarify a bit, Basilisk was up but still in the process of validating the integrity of most of the database objects. The server is currently running through our backup HDD's, which is causing the server's loading to take a lot longer than it normally would on SSD's. We shut down the login server because any actions triggered on Bas will delay the database check, and it's going to take long enough as it is.
    Quote Originally Posted by Miztah View Post
    The good news is, the server didn't explode using the recovered database. There's no current bad news, but as of right now, that's the only good news. We still have to verify that all of the objects in the database are actually valid and load properly, and it will take time. The possibility of a wipe still remains if we find too much corrupted data. Time will tell, but in the meantime you'll see Basilisk go online and offline multiple times, but you won't be able to access it. Those still connected will not be able to reconnect when they disconnect, and in the interest of getting this testing done as quickly as possible, they should disconnect on their own anyway.


    UPDATE:


    Quote Originally Posted by Ivojedi View Post
    About the loading status: We are attempting to load a test db instance to check for data integrity. This should give us an indication of whether we'll need to wipe or not. It's loading on the HDDs so it's slow and will take time. Thanks for the continued patience.


    ~The SWGEMu Staff
    by Published on 04-18-2017 07:13 AM   

    SWGEmu Publish 9 - "Secrets of the Force, Redux" loading screen competition

    April 2017
    The SWGEmu Staff




    The SWGEmu Publish 9 - "Secrets of the Force, Redux" loading screen competition


    Hear ye! Hear ye!

    Publish 9 is looming
    Its just around the corner.
    You have waited far too long,
    SWGEmu Staff has worked too damn hard.
    And now... Now we are so close.
    We can almost taste it.
    So we need to spice things up.
    We need to make it even more... grand!
    But we need your help,
    We need your personal touch.

    So come one, come all.
    Release your inner artist.
    And let your Star Wars geekiness shine.
    Make us a damn fine Publish 9 themed loading screen.
    Winner gets a potato!!!
    And bragging rights.
    Gets to be immortalized through their masterpiece.

    Oh and, you might want to throw in a bit of lore
    to accompany your work of art.
    You know, just to explain
    where the inspiration for it came from.












    Rules are:


    1. Loading screen has to be Star Wars (Galaxies) themed
    2. Has to be Publish 9 themed (I'm gonna go with glowbats and space wizards and ****)
    3. No profanity
    4. No anything against SWGEmu rules and policies
    5. If you uses someone else work, give credit where credit is due
    6. Don't be sore losers



    NOTE: As you are well aware we are a fickle bunch, so this announcement is still and always will be subject to change... Or not.




    Winner(s) will be announced same time Publish 9 is announced. Probably.




    ~The SWGEmu Staff
    by Published on 03-07-2017 09:14 PM   

    REMINDER: RL Monetary Trades in-game are a bannable offense

    March 7, 2017
    The SWGEmu Staff




    REMINDER: RL Monetary Trades in-game are a bannable offense


    Lets start off with a quote from our SWGEmu Test Center & Basilisk Rules & Policies

    Quote Originally Posted by Vlada View Post



    1.7. On SWGEmu Servers, all accounts and characters used for financial gain will be deleted/banned. It is forbidden to use your account for:
    • 1.7.1. Soliciting real life monetary trades.
    • 1.7.2. Purchasing of in-game credits or items for real life currency.
    • 1.7.3. Exchange of in-game items/credits for real life items.
    • 1.7.4. Exchange of in-game items/credits for items/currency from other games.
    Basilisk and TC: Nova are temporary test servers, which means everything you have on them, every character, item or credit will be eventually wiped when SWGEmu project is complete. SWGEmu project is free, and everything in game is free and available to anyone willing to put in time and some effort to obtain it by just playing.

    Now that we have that out of the way, lets reiterate. Buying or selling of in-game items and/or credits is against our rules and is a bannable offense. Credits transactions are logged and if caught all those involved will be permanently banned from any and all of our services. SWGEmu does not in any way support nor does it condone any real life monetary trades for in-game items and/or credits.

    Anyone who has purchased credits or in-game items, even if their account has not been banned, should ask for a chargeback immediately and report credit/item seller to paypal or their bank as a scammer.

    Furthermore we will be instituting a "Snitch" program, for those caught or just willing to help us and themselves and get a fresh start on SWGEmu servers. If you bought credits/items and you got caught, you will be offered an option to start fresh with a new account if you cooperate and help us get rid of those breaking our rules and ruining the emulator for everyone.


    ~The SWGEmu Staff
    by Published on 02-21-2017 06:50 PM   

    Vlada's 10th cake day giveaway

    February 21st 2017
    The SWGEmu Staff





    Since its my 10th SWGEmu cake day...




    I decided to organize an event of a sort. Well more of a treasure hunt.


    Somewhere in the galaxy hidden away in plain site is my toon...







    ADK went to Mobyus1...





    Second one went to Kom'rk



    Veplo got the self-pwered harvester



    Good luck and ...





    P.S. Since I am a lazy bastard and cant be bothered to keep looking at my screen while you look, if you find me and I don't reply to your tells, please message me on forums or on IRC.
    by Published on 09-08-2016 07:51 AM   

    Veteran rewards coming back to Basilisk, but with a twist

    September 2016
    The SWGEmu Staff



    Veteran rewards coming back to Basilisk, but with a twist


    On September 17th 2016. we will be re-enabling Veteran rewards on Basilisk. Now for the twist part... Please try to keep an open mind and remember that Basilisk is still our development tool and that we are all helping test. We will be wiping the records of all previously claimed Veteran rewards, so everyone will be able to get the Vet rewards of their choice again even if they previously claimed it.


    PLEASE NOTE: No previously claimed Vet rewards will be deleted, just the records of them being claimed will be removed from the database.


    Thank you for your patience, your understanding and continuous support.



    ~The SWGEmu Staff
    by Published on 05-17-2016 06:13 AM

    SWGEmu Recruitment

    SWGEmu Quality Assurance
    Community Tester Program



    Quality Assurance team - Community Testers Program (non-staff) recruitement

    Community Tester APPLICATION
    • Name of applicant (last name optional):
    • Age of applicant:
    • Email address:
    • Forum, Mantis, and IRC nickname:
    • Time zone:
    • Times you are most often available:


    SWG Knowledge/Experience:

    • When did you start playing SOEs retail SWG? (dates or publish specific):
    • What primary profession(s) did you play Pre-CU?
    • What other profession(s) have you tried Pre-CU?
    • What other experience do you have from Pre-CU?
    • How long have you been following this project?

    QA/Testing Experience:

    • Do you have any previous/current experience in testing/QA? If so, please explain:
    • Situational Assessment: A player comes to you in-game or on IRC/forums with a possible new bug. What is your immediate course of action?
    • Fill out a bug report. You may either link a report you submitted on Mantis previously or make up a new one using the form below.
    Title:
    Category:
    Reproducibility:
    Severity:
    Priority:
    Report Details (feel free to include screenshot(s) if applicable):

    • Please add anything else you would like, to support your application:



    Please send reply to [email protected]


    ~ The SWGEmu QA team
    Page 1 of 6 1 2 3 4 5 ... LastLast