tabbek

I run a small server for myself and a few friends who are all what I would term "factory system tinkerers". As such, we make heavy use of the various machine / electric / piping systems. The biggest issue I have encountered with chunk loader blocks actually has nothing to do with the block itself, but rather the loaded / unloaded boundaries they create. There was a particular instance I remember troubleshooting in which, once joining the server, even from a lan on a gaming rig (server runs on a dual core 1.5ghz system with the worlds stored in a ram-drive) it was like trying to play via slide-show. What I found was that items were flowing properly through pipes in the loaded chunks, but when hitting the unloaded boundary, it acted like an open ended pipe, dropping everything traveling on a single block space. Of note, entirely anecdotal, it seems like 500 items on 1 block space have a higher impact than 250 each on 2 blocks. Could be completely wrong, but I digress. Ended up being able to make my way to the cobble pile of doom, and one click of flint-n-steel, performance was almost instantly restored. Moral of the story : If you use chunkloaders for the purpose of keeping a machine system running (machine used generally, not mod specific), be sure that the entire machine system is included in the chunks kept loaded, and that your system can handle the overhead of doing so.

Re: Server crash on Ubuntu tekkit 2.1 Tried the suggestion from the link Crath suggested. Quick synopsis of the thread : Make all the mods have consistent first letter capitalization. After doing so -- :~/TEST/mods$ ls -ln total 2488 -rw-rw-r-- 1 1000 1000 52489 Mar 3 23:08 Additionalpipes-32.3-bukkit-b1.1R4-r1.zip -rw-rw-r-- 1 1000 1000 29679 Mar 3 17:01 AdvancedMachines_3.6_bukkit.zip -rw-rw-r-- 1 1000 1000 278030 Mar 3 22:12 Buildcraft-2.2.12-b1.1R3.zip drwxrwxr-x 8 1000 1000 4096 Mar 6 19:34 ComputerCraft -rw-rw-r-- 1 1000 1000 15221 Mar 3 23:09 CraftingtableII-1.6.2-bukkit1938.zip -rw-rw-r-- 1 1000 1000 7763 Mar 3 22:12 Door Fix Mod V2.1-R1.zip -rw-rw-r-- 1 1000 1000 419171 Mar 4 00:48 EE2ServerV1.38-bukkit-cb1938.zip -rw-rw-r-- 1 1000 1000 21099 Mar 3 22:13 EnderChest_1.0.1_Bukkit1.1-R4.zip -rw-rw-r-- 1 1000 1000 311483 Mar 3 22:13 Forestry-1.2.6.6-b1.1R4.zip -rw-rw-r-- 1 1000 1000 464632 Mar 3 22:39 Industrialcraft2-1.71-cb1.1R4-r4.zip -rw-rw-r-- 1 1000 1000 34992 Mar 5 00:11 Mod_compactsolars-server-1.2-bukkit-cb1938.zip -rw-rw-r-- 1 1000 1000 28716 Mar 3 22:39 PowerConverters-1.3.1_01-cb1.1R4-r1.zip -rw-rw-r-- 1 1000 1000 414320 Mar 3 23:10 Railcraft-3.4.2-cb1.1rb3-rel1.zip -rw-rw-r-- 1 1000 1000 326727 Mar 3 22:39 Redpower-all-2.0p4d-b1.1R3.zip -rw-rw-r-- 1 1000 1000 93837 Mar 3 22:24 Weaponmod_bukkit.zip drwxrwxr-x 2 1000 1000 4096 Mar 6 19:34 weaponmod -rw-rw-r-- 1 1000 1000 10974 Mar 3 23:09 zChargingBench-1.71-1-IC2-1.71.zip Note, I left zChargingBench as is, since it seems like the intent was to have this load last anyway. When starting up the server now, progress, but a familiar old problem. 2012-03-07 10:56:09 [FINER] THROW java.lang.IllegalArgumentException: Slot 241 is already occupied by codechicken.enderchest.BlockEnderChest@befbf25 when adding ic2.common.BlockRubSapling@28ee1c42 Same thing that happened to me previously: http://forums.technicpack.net/index.php/topic,1937.0.html Found file as downloaded, with ender chests using 178. When deployed, 241. Set the value back to 178. All considering, just noticed 2.1.1 is out, so no point. Jumping on the latest version. Edit: Checked anyway, server runs, client can connect after fixing the ender chest block id that seems to like to switch. Edit #2 : Tekkit 2.1.1 dropped into place nicely and started up without incident.

Launcher/pack Version: Tekkit 2.1 server on Ubuntu 11.10. Operating System: ~/TEST$ uname -a Linux mcbuntu1110 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Version of Java: ~/TEST$ java -version java version "1.7.0_02" Java SE Runtime Environment (build 1.7.0_02-b13) Java HotSpot 64-Bit Server VM (build 22.0-b10, mixed mode) Description of Problem: Attempting to run the server from a clean directory in Ubuntu 11.10 results in a crash. Error Messages: Appears to be an issue with power converters. 2012-03-06 20:34:35 [FINE] Failed to load mod from "mod_PowerConverters.class" 2012-03-06 20:34:35 [FINER] THROW java.lang.NoClassDefFoundError: buildcraft/energy/BlockEngine Link to pastebin of log server.log http://pastebin.com/TSDsPy2c ModLoader.txt http://pastebin.com/LrtMLgRG Any additional details, just ask. Edit : appended (resolved) to subject. Issue resolved in 2.1.1.

found in thread http://forums.technicpack.net/index.php/topic,1937.0.html This is why you dont want to just change the enderchest / rubber sapling IDs arbitrarily. Your clients dont have the same change you made.

you may want to focus your search on why enderchest.cfg is getting reset instead of choosing an arbitrary ID to change (which clients would not have the same change by default). If you chop down a rubber tree, do ender chests fall from the leaves? :P

Are you running tekkit from a clean directory, or one you ran a server from previously? I see "[1]buildcraft-2.2.11-b1.0.1R1-r2.zip" in yours, but in checking my server, I have "buildcraft-2.2.12-b1.1R3.zip". It would appear that you have an old buildcraft.

Could you provide more detail on when specifically it changes back to 241 for you? Change, save, close, reopen and it reverts? Change, save, close, start server, reopen and it's reverted? I'm trying to figure out if / when the file "changes back". Possibilities: Change to file isn't actually saved - block id appears to revert if you reopen the file right after write/closing, before starting the server Change to file reverted at server start - block ID is saved correctly, and remains correct when file is write/closed and reopened, but changes after the server is started. Change to file reverted at server stop - I doubt this is it, as the error condition would need to be present when the server starts or is starting. --> pieiscool32 : What environment are you running tekkit server in (os and version) and permissions do you see on the file itself, and container directory? :~/config$ ls -lan total 84 drwxrwxr-x 4 1000 1000 4096 Feb 24 11:21 . drwxr-xr-x 18 1000 1000 4096 Feb 24 13:50 .. -rw-rw-r-- 1 1000 1000 194 Feb 24 12:41 EnderChest.cfg -rw-rw-r-- 1 1000 1000 7894 Feb 24 12:41 IC2.cfg -rw-rw-r-- 1 1000 1000 11579 Jan 31 12:29 IC2.lang -rw-rw-r-- 1 1000 1000 236 Feb 21 23:24 IC2ChargingBench.cfg -rw-rw-r-- 1 1000 1000 762 Feb 24 12:41 ModLoader.cfg -rw-rw-r-- 1 1000 1000 702 Jan 31 12:29 NEI.cfg -rw-rw-r-- 1 1000 1000 503 Feb 22 00:37 NEIServer.cfg -rw-rw-r-- 1 1000 1000 1063 Feb 24 12:41 NetherOres.cfg -rw-rw-r-- 1 1000 1000 3036 Feb 24 12:41 PowerConverters.cfg drwxrwxr-x 2 1000 1000 4096 Feb 23 18:22 forestry drwxrwxr-x 3 1000 1000 4096 Feb 23 18:22 itemdescriptions -rw-rw-r-- 1 1000 1000 533 Feb 2 23:10 mod_ComputerCraft.cfg -rw-rw-r-- 1 1000 1000 13912 Feb 24 12:41 railcraft.cfg

Re: Block id error when launching server in linux (Slot 241 is already occupied) Was able to redownload to check the files. Not sure why, but when deploying on linux, EnderChest.cfg gets changed. as downloaded: #EnderChest Configuration File #Deleting any element will restore it to it's default value #Block ID's will be automatically generated the first time it's run block.id=178 gui.id=165 Deployed and run: $ cat EnderChest.cfg #EnderChest Configuration File #Deleting any element will restore it to it's default value #Block ID's will be automatically generated the first time it's run block.id=241 gui.id=165 Just finished a quick test. Not sure what about the first time run caused the block ID to be modified, but once I manually edited the EnderChest.cfg on the server from 241 back to 178, the server was able to start without issue, including the wireless redstone error noted in my initial log. No access to client to actually try and log in, but the server started without error after the change. *Current Workaround* After deploying to the linux host, start the server, let it error and die. Edit the EnderChest.cfg and modify "241" to "178". Save. Restart the server. Win. *Current Problem Statement* When running the server after a fresh download, the preconfigured value for enderchests is changed from 178 to 241. Unknown what or why the block id changed.

Re: Block id error when launching server in linux Seems there are a few other threads open now regarding the Slot 241 issue. Hope this gets a bit more attention. Really confused regarding why it has no block conflicts when run in a Windows environment, but the exact same files copied to a fresh linux environment, server will not run without the slot 241 error. Edit for more info. From the linux server: ~/config$ for i in `ls` ; do echo $i ; cat $i | grep 241 ; done EnderChest.cfg block.id=241 IC2.cfg blockRubSapling=241 IC2.lang <trimmed rest of output> Waiting on ~/config/* from a friend hosing on windows for comparison as I do not have access to anything other than *nix atm.

Re: Block id error when launching server in linux Ah, didn't notice the error waylon531 noted. Possibly a 2nd issue?

When launching the server on my ubuntu box (11.10 x86_64) I get a block ID error of the following: java.lang.IllegalArgumentException: Slot 241 is already occupied by ic2.common.BlockRubSapling@15b08736 when adding codechicken.enderchest.BlockEnderChest@787cf559 server.log @ http://pastebin.com/9mNZdG6G ModLoader.log @ http://pastebin.com/bpanCPBZ ~$ which java /usr/bin/java ~$ java -version java version "1.7.0_02" Java SE Runtime Environment (build 1.7.0_02-b13) Java HotSpot 64-Bit Server VM (build 22.0-b10, mixed mode) NOTE : "1-industrialcraft2-1.70-cb1.1R4-r2.zip" I added the "1-" in an attempt to see if it was an issue with load order. With the zip name unmodified, the same error occurs, but ic2.common.BlockRubSapling and codechicken.enderchest.BlockEnderChest are reversed. I can take the same set of files, copy them to my windows 7 box, and run the server without issue. Server was previously hosting a 1.1.4 tekkit server and was cleared out and repurposed for 2.0. If I'm missing something glaring, please send me off with a slap to the head :-\ edit: appended "Slot 241 is already occupied" to subject.