I run a couple of minecraft worlds for my daughter and a few friends (yeah, ok, and for me :D ). Up to now we were running velocity and paper servers. I kept hearing that fabric servers were supposed to be more vanilla, and there were a couple of mods not ported to paper, so I wanted to try to replicate my servers with fabric.

The server runs fine, but the output of the terminal is extremely verbose compared to paper, and I don’t know if this is expected or if I’ve got something misconfigured.

Most of the output is about “netty”

"Netty Epoll Server IO #3" at io.netty.channel.epoll.Native.epollWait(Native.java:213)
os_prio=0 cpu=6.33ms elapsed=1517.77s tid=0x00007068e00160d0 nid=1862005 runnable at io.netty.channel.epoll.Native.epollWait(Native Method)`___`

for example.

Does someone have any ideas? I wouldn’t mind posting a large chunk of the output if someone thinks there might be an issue. Thanks!

  • Blisterexe@lemmy.zip
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 days ago

    okay, in the logs you sent nothing really looks like an error, in that case try removing all those flags, one of them is probably causing the verbose output

    • Reven@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 days ago

      Ok, so I have removed all the flags and all the mods. I also shut down the upstream velocity proxy, in case it was an issue with polling the server or something. Even running by itself the consoled gets completely spammed by messages. I know that these are not errors in themselves, but spamming the console just makes catching any real errors or relevant warnings that much more difficult. As a side issue, I’m using puffer panel to manage all the worlds and installs and the spam to the console makes the admin panel unresponsive. I have no idea where to trouble shoot next.

      • Blisterexe@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        5 days ago

        hm, try making another server with the same mod set but a different world, and see if it still happens.

        edit: actually, try replacing the main minecraft jar