1. The forums will be archived and moved to a read only mode in about 2 weeks (mid march).

Solved Server Issues

Discussion in 'Help' started by iTzAnTiFTW, Jul 23, 2017.

  1. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    Server Having Some Issues:

    - After a little while, my server becomes unresponsive, including the console (I can start and send commands) But I am unable to join the server, stuck on syncing pack with server.

    Using Latest Pocketmine MP version &
    PHP7 Binaries.
    Error Codes:
    https://pastebin.com/CLibXd6W
     
  2. EdwardHamHam

    EdwardHamHam Skeleton

    Messages:
    962
    GitHub:
    edwardhamham
    Do you have write access to that directory?
     
  3. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    Yes. Its a VPS
     
  4. EdwardHamHam

    EdwardHamHam Skeleton

    Messages:
    962
    GitHub:
    edwardhamham
    Okay, but what is the chmod value?
     
  5. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    RWX
     
  6. EdwardHamHam

    EdwardHamHam Skeleton

    Messages:
    962
    GitHub:
    edwardhamham
    I think I see the problem. You're trying to run PocketMine under the directory of the root user, according to those error codes. This won't work if you're not running PocketMine on root (which you shouldn't anyways). You should always run programs and executables as a non-root user. If you are, than you should run PocketMine in its home directory or a subdirectory of it. Try running these commands:
    Code:
    cd ~
    mkdir PocketMine
    cd PocketMine
    and install PocketMine there.
     
  7. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    I actually am running under a directory, named 19132.
     
  8. HimbeersaftLP

    HimbeersaftLP Fish

    Messages:
    2,402
    GitHub:
    HimbeersaftLP
    You can just switch to the root user and do
    Code:
    chown -R username dirname/
     
  9. Thunder33345

    Thunder33345 Moderator Staff Member

    Messages:
    2,137
    GitHub:
    Thunder33345
    try doing "pwd" and doing "ls -la" then send screenshot if possible
     
  10. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
     

    Attached Files:

  11. Awzaw

    Awzaw Zombie Pigman Poggit Admin

    Messages:
    726
    GitHub:
    awzaw
    Why does your first error pic say you have installed pocketmine in /root/test, not /root/19132?
     
  12. Thunder33345

    Thunder33345 Moderator Staff Member

    Messages:
    2,137
    GitHub:
    Thunder33345
    firstly it's absolutely the worst idea to run PMMP as ROOT
    and secondly do you use root to run the PMMP? because linux will not like it if anything other than ROOT touch these files
     
    EdwardHamHam likes this.
  13. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    Totally forgot I ran it in the test file directory.
     
  14. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    So I should make a subuser to run pmmp?
     
  15. Thunder33345

    Thunder33345 Moderator Staff Member

    Messages:
    2,137
    GitHub:
    Thunder33345
    yes a user, and also put everything inside /home/username/pmmp/(file here) for example
     
  16. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    Alright, will try that
     
  17. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    Keep getting this when attempting to run ./start.sh

    https://pastebin.com/cwCqm7vB
     
  18. Awzaw

    Awzaw Zombie Pigman Poggit Admin

    Messages:
    726
    GitHub:
    awzaw
    Read this, and this, then try again!
     
  19. iTzAnTiFTW

    iTzAnTiFTW Spider Jockey

    Messages:
    36
    GitHub:
    itzantiftw
    I think this issue is resolved, I will be waiting 24 hours before marking this thread as solved because the issue may reoccur.

    UPDATE: After review, the issue has not reoccurred and I believe it has been resolved.

    Thank you to everyone that helped me with this issue
     
    Last edited: Jul 26, 2017
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.