Problem Filler causing server lock-up?

[Ariaera]

A player on my server has built and deployed a Filler machine and it's apparently causing the server to lock-up and stop responding as soon as he logs in on the chunk where the machine is at.

When I restart the server, the console is not showing that the world is being saved...just shows it starting up again.

The chunk(s) affected are far away from anyone's used area and in an ocean biome. Is there a way to force a chunk or set of chunks to regen? Is there a way to delete a certain machine or the items on the ground in a certain chunk or anything of the sort?

What I need to know is what are my possible fixes in this case?

 

[glasspelican]

I am not aware of a way to force a chunk reset, but you can open the world with mcedit and remove machines.
please note this could and probably will brake all the moditems in the chunk so backup first

 

[Ariaera]

I don't think MCEdit loads properly on my computer, but I have attempted a chunkreset with it. Any idea what would have cause this with that particular machine? I have searched the forums here and have not seen any complaints about it?

 

[glasspelican]

On slowpokes stream last week some time one of the mod devs mentioned the "buildcraft filler bug" in passing, I was under the impression that is was that it hammered on the server cpu not that it outright crashed

if all you want is the user to be able to login, remove his/her player.dat from the server, the users inventory will be empty and thy will login at spawn

 

[mrzpicklez]

or you can get NBT edit/explorer it will allow you to change a persons location if you know the coords you want to put them at and they can keep their inventory... the reason that you cant get in there is because of the entitys that have been dropped by the filler. someone will need to go there and suck up all the items it will remove the person crashing there.

 

[Ariaera]

It's not just him crashing though. It doesn't actually crash the server, but it renders it as good as crashed. As soon as the chunk becomes active, the server stops responding. Meaning no one can go there and suck anything up.

I "fixed" the issue by taking the world into MCEdit and regenerating the affected chunks, thereby removing the machine causing the issue.