Jump to content

Moleculor

Members
  • Posts

    21
  • Joined

  • Last visited

About Moleculor

  • Birthday 11/20/1982

Moleculor's Achievements

Grass

Grass (2/9)

1

Reputation

  1. Did you update MCPC as per '?do=embed' frameborder='0' data-embedContent>> ?
  2. You're going to need to paste the crash log.
  3. First guess, it's an out of memory problem. You'll probably need to allocate more memory. PermGen might be the thing. Try googling 'minecraft permgen' for some options. Allocating more memory through the launcher might do it too. However, realize that Tekkit's current recommended releases are UNSTABLE and do have a memory leak related to Project Red. For some reason they didn't include the fixes in version e, even after being told about the issue beforehand. Don't know why they're dragging their feet on this issue.
  4. I pretty much haven't been able to play Tekkit in a week because we're still using the bad version of Project Red. Or at least we're pretty sure it's that issue, even though we've removed all the pipes we could find. Could you *please* consider updating to a much more stable version? We'd like to eliminate this as a potential source of the server issues we're having. Or at the very least release a beta version with the stable version of Project Red?
  5. That's not 1.2.8d. That's even beyond >1.2.8e. You've somehow downloaded files that are even later than the latest Tekkit files. Try reverting to your backup and make sure you're running only 1.2.8d.
  6. What we had to do was restart the server and log in quickly, break all the pipes. The server for us would be up for about five minutes before crashing and if we broke the pipes fast enough it stayed up.
  7. Yeah, unfortunately even 1.2.8d is too unstable for public use. There were several days where we couldn't keep the server up for longer than five minutes. Eventually we had to revert back to our 1.2.8b backups. The CPU/Memory issue with Project Red *really* bad. It can be caused by a mere twenty or thirty pipe sections.
  8. Check to see who's using pipes. Kill all the pipes. See if you still have the problem. 1.2.8d has a very bad memory leak problem with Project Red and pipes. (Ducts are fine.)
  9. Could you also include a fix for the out-of-control CPU and memory usage in Project Red? Version 4.3.5 build #30 should do that. It's crashing our server after about three minutes of uptime. (I say crash, I really mean error-less hang. Took us a few days to figure out that it was the problem. Buildcraft pipes basically bork the servers.)
  10. I'm having a similar or same problem on the server I play on. The admin and I are trying to figure out what's going on. It's a bit difficult since there's no error messages in the logs. Basically the server is only up for about five minutes before it hangs, stops communicating with anyone, and stops responding to pings and commands. Highly frustrating.
  11. Ok, never mind for now. I got into a chat with the server owner, and it seems like the server is actually just somehow blocking further connections once someone connects to the server. It doesn't seem to leave a log of any kind. I'm going to work on it a bit with him, see if we can't get some more information.
  12. Default Tekkit, so far as I know. I didn't provide the server log because it seems to be completely uninformative? It's possible the admin hasn't provided me with the right log. We've actually been having a problem with the server for a couple days now, so it's not the MCPC+ thing.
  13. Since we don't seem to have that installed... no. Any other ideas?
  14. I have a log. This is not my server. This is the output of the Technic Launcher shortly after the player is connecting. I haven't been able to connect, myself, since the server crashes when people connect, and so far it's the (presumably very busy) server operator who's been connecting and crashing it.
  15. Our server apparently had a similar issue. Kind've annoying that we've had to delete all the pocket dimensions.
×
×
  • Create New...