• Spawn claim issues

    Support
    2
    0 Votes
    2 Posts
    461 Views
    GreenMage2G

    I got unstuck.
    However I lost a second horse due to it being stuck on claims.

  • Technical issues have been resolved

    Network news
    1
    0 Votes
    1 Posts
    632 Views
    BentB

    alt text

    All issues which began on the 12th of November 2017 have been resolved.

    The affected services are back online. The reason for this outage was a physical defect of an HDD as well as a simultaneous failure of an SSD in our server HV01.

    For the technical folks this is what the servers sata controller threw into the kernel log:

    Nov 11 21:43:35 hv01-de-fs kernel: [7126302.696057] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 11 21:43:35 hv01-de-fs kernel: [7126302.745078] ata4.00: failed command: SMART Nov 11 21:43:35 hv01-de-fs kernel: [7126302.769558] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 2 pio 512 in Nov 11 21:43:35 hv01-de-fs kernel: [7126302.769558] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Nov 11 21:43:35 hv01-de-fs kernel: [7126302.866348] ata4.00: status: { DRDY } Nov 11 21:43:35 hv01-de-fs kernel: [7126302.890274] ata4: hard resetting link Nov 11 21:43:37 hv01-de-fs kernel: [7126304.764062] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 11 21:43:37 hv01-de-fs kernel: [7126304.765199] ata4.00: configured for UDMA/133 Nov 11 21:43:37 hv01-de-fs kernel: [7126304.765218] ata4: EH complete Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060380] sd 3:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060382] sd 3:0:0:0: [sdb] tag#24 Sense Key : Illegal Request [current] Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060384] sd 3:0:0:0: [sdb] tag#24 Add. Sense: Unaligned write command Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060386] sd 3:0:0:0: [sdb] tag#24 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060389] blk_update_request: I/O error, dev sdb, sector 0

    this error has been thrown over and over again fatally crashing the controller in the end. We have resolved the issue with the help of Hetzner’s technicians which did replace the affected disks within a few hours. Great support as always!

    Icon: “Cloud Synced by ✦ Shmidt Sergey ✦ from the Noun Project”

    @Administrators @Global-Moderators @Greenhorn @Novus

  • Technical Issues

    Network news
    1
    0 Votes
    1 Posts
    609 Views
    S

    We are currently experiencing some issues with one of our root servers disks. Some services may not be working as expected. We are working on resolving the issue. We apologize for the inconvenience. If you have any question feel free to contact us at: emergency@unitedworldminers.com

    Affected Services :

    Some Modpack Downloads Teamspeak (Failback TS Online) Vanilla Prime Steves Adventure Craft
  • 0 Votes
    12 Posts
    3k Views
    B

    Spoke to him just earlier, We added a quick system to see if it can be fixed and just going to wait and see now if any more problems arise I will request the old system to be put in place

  • Issues joining server [Solved]

    Support
    20
    0 Votes
    20 Posts
    4k Views
    NickN

    THANK YOU
    sir

  • Recent server downtime

    Locked Steve's Adventure Craft
    1
    0 Votes
    1 Posts
    970 Views
    BentB

    Dear Steve’s Adventure Pack community,

    my name is Bent, I am the CTO of Unitedworldminers.

    Yesterday we noticed abnormal high disk I/O load on the Linux server on which the Steve’s Adventure Pack server is running. As we always work hard to provide our users with the best possible performance, we tracked down the issue and found out that the Towny plugin on this server led to this issue.

    Towny was configured to use the disks of our server for it’s database. This is no issue for small servers, but the community here is really large and the admins might not have configured this while setting up towny.
    To remove the high I/O load, we set Towny up to use our database server which worked without any issues (in our testing).

    About 16 hours later we got a message that a Town on the server is completely griefed and thought that the issue was our (the Unitedworldminers team’s) fault.

    So we started restoring some backups and found that the city has been destroyed for about 10 days already. While we were working on the server we had to restart it multiple times, which led to some inconvenience which we sincerely apologize for.

    We reverted the server back to it’s original state before starting our work.

    In conclusion we can say that the issue was neither produced by us nor will we put our hands on this again as the server admin @soringaming has to look into the issues you send him here

    Best regards

    the Unitedworldminers team