-Blizzard-

Unzipping the downloaded zip from within the archive(from the command line) (winscp messed it up for me) fixed all of the stalling problems, and the errors are bypassed.

This fixed mine as well. *sigh* It was as simple as typing "unzip Tekkit_server3.1.1.zip"

Wait, I just checked, I'm actually on update 5. root@minecraft:~# java -version java version "1.7.0_05" Java SE Runtime Environment (build 1.7.0_05-b05) Java HotSpot 64-Bit Server VM (build 23.1-b03, mixed mode) root@minecraft:~#

will openjdk be ok? I had some issues with it and netherores, so I had to go through a long process of doing oracle java.

will openjdk be fine? updating oracle java on Debian is a *****

yep, full control. got some secondhand servers from my dads company when they upgraded their data centers.

Shall try typing the command directly.

Sorry for the spam, but I would like this to get noticed. Im running the server on a debian squeeze machine. the terminal freezes up after the 241 id conflict error.

J Running java 7U4 (oracle) on a Debian squeeze machine using the given launch.sh #!/bin/sh java -Xmx3G -Xms2G -jar Tekkit.jar nogui The terminal freezes up and the server does not start after the error.

http://forums.technicpack.net/threads/tekkit-3-1-1-item-conflicts-not-allowing-server-to-start.16645/

Bumping this post, as I am also experiencing this same error, I was forced to backdate to 3.0.4 until a public fix has been released.(On linux machines it prevents the server from starting.)

Bumping this post, as I am also experiencing this same error, I was forced to backdate to 3.0.4 until a public fix has been released.(On linux machines it prevents the server from starting.)

Bumping this post, as I am also experiencing this same error, I was forced to backdate to 3.0.4 until a public fix has been released.(On linux machines it prevents the server from starting.

On linux machines, they cannot be ignored. The error prevents the server from starting. was forced to backdate to 3.0.4 until a public fix is released.

Went back to 3.0.4 and removed wireless redstone, works fine, waiting until a fix is publicly released.