Closed Thread
Results 1 to 15 of 828

Thread: Basilisk extended downtime 08/09/2017

Hybrid View

  1. #1
    Junior Member
    Join Date
    May 2015
    Posts
    82
    Play Stats
    Inactive
    more from discord:


    RisenAngel - Today at 4:25 PM
    To clarify a bit, Basilisk is 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.

    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.
    drop off vendor Tatooine /waypoint 1882 -5008

  2. #2
    Addicted
    Join Date
    Mar 2007
    Location
    Perception Purgatory
    Posts
    4,506
    Play Stats
    Inactive
    Quote Originally Posted by Lostphoenix View Post
    more from discord:
    Here's the actual quote...

    Quote Originally Posted by Miztah View Post
    To clarify a bit, Basilisk is 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.

    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.
    ...from this other thread in Basilisk section.

    ------

    Login server should be UP now btw, for anyone wanting to test anything on TCNova during the interim.

  3. #3
    "Retired" SWGEmu Staff risenangel's Avatar
    Join Date
    Aug 2011
    Location
    0,0 Dathomir
    Posts
    672
    Play Stats
    Inactive
    Quote Originally Posted by Lostphoenix View Post
    more from discord:


    RisenAngel - Today at 4:25 PM
    To clarify a bit, Basilisk is 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.

    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.
    that was from Miztah...

    edit: oh hi nee. see you said that already.
    Kyada <BoS>
    Everything I ever did was about pushing the project forward.

Closed Thread

Thread Information

Users Browsing this Thread

There are currently 13 users browsing this thread. (0 members and 13 guests)

     

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts