vincss/mcsleepingserverstarter

Blank Console Output when Launching on Pterodactyl

BoredKevin opened this issue · 2 comments

BoredKevin commented

Description:

I am experiencing an issue where the console output appears blank when launching mcsleepingserverstarter on Pterodactyl. This makes it difficult to monitor the server's startup progress and troubleshoot any potential errors.

Steps to Reproduce:

  1. Set up Pterodactyl panel and mcsleepingserverstarter on the server.
  2. Create a new server instance and configure it to use mcsleepingserverstarter as the startup command.
  3. Start the server and observe the console output.

Expected Behavior:

  • The console should display the standard server startup logs and progress updates when using mcsleepingserverstarter.

Actual Behavior:

  • The console output is completely blank, providing no information about the server's startup progress or any potential errors.

Additional Information:

  • I have verified that mcsleepingserverstarter is properly installed and functioning correctly on the server.
  • I have also tested launching the Minecraft server without using mcsleepingserverstarter, and the console output is displayed correctly in that case.
  • This issue occurs inconsistently across different server instances and different versions of Pterodactyl.
  • Seeing from the logs, it seems the server is running normally, just without any console output.

Environment:

  • Pterodactyl Panel version: 1.11.3
  • Pterodactyl Wings version: 1.11.6
  • Operating System: Ubuntu Server 22.04 LTS
  • Minecraft Server Version: 1.20.1

I'm currently actively investigating this issue as it tends to happen only on some pterodactyl instances but not all of them.
chrome_m8C0kR3IuL

chrome_If3pdMyQfk

chrome_GNanxC2Q7d

BoredKevin commented

Hello, it seems like my startup command caused the issue as changing it seems to fix the issue, though it changes the startup behavior.

I am now looking for a possible solution that can keep the previous startup behavior but without the underlying issue.

image
image

BoredKevin commented

I've solved the issue by downloading the proper linux executable according to system architecture but saving it as mcsleepingstarter-linux

The issue was with a faulty startup command, fixed the problem #183 LGTM!