rodney cheney
- advocaite
- advocaite
- Europe/Stockholm
- Yes
- No
MC-44000
Changed Description:
a new glitch bug extreemly important needs fixing asap
basicly a player come on server and types /me @a @a @a @a @a @a @a @a @a and on till cant no more
then it prints everyones name in chat causeing the client to instantly crash because the string length is too small.
this is a new way players are attacking servers to get op etc etc please fix this URGENThere is a link to the exploit posted on hack forum for all to know
http://www.hackforums.net/showthread.php?tid=3963589
Changed Environment:
linux-ubuntu
linux-ubuntu
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
http://www.hackforums.net/showthread.php?tid=3963589
this is them explaining hwo to do it so this is no joke please fix this
I cant run my snapshot server because of this and will not be able to update to 1.8 as this bug crashes online servers
DOnt know if this helps you guys, but for my vanilla server we sometimes get major lag when lots are on i find clearing the entities well the hostile ones helps this could be due to this zombie issue i never knew about it.
what i do is every 5 mins i send a command to server to set world to peacefull and then set back to hard
this removes all hostile mobs instantly and server runs alot better for it.
I thought it was all due to massive mob grinders but this makes alot more sence
if this helps you let me know
to clear up alot of the lag i send out a change in difficulty every 5 mins to peacfull then back to hard
it kills all hostile mobs and game stops lagging for the most part till. still get random spikes but every 5 mins there is a no lag period that ive noticed
THIS HAPPENS ALL THE TIME WHEN COPY AND PASTING COMMANDS FROM YOUTUBE TO MINECRAFT COMMAND BLOCKS
just make sure to go through command and remove it before you copy and paste
srry caps
im still having this issue in 1.8 getting frustrating as i cant schedule restarts like i like to
im still getting this on 1.8 release just hangs there scheduled restarts are usless atm
For anyone using linux and bash scripts to restart servers
this command below will help stop the server so it can run freely again after stop
feel free to remove ; screen -wipe if you dont use screens
ps -ef | grep java | grep -v grep | awk '
{print $2}' | xargs kill -9 ; screen -wipe
at least then you can have servers restart and not worry about having to be online to do it your self, cause if you use rcon like i do the next java instace will still be running rcon, which means it may be more then just the fact it dosent stop it could be hanging due to something else
here is some log i use a 64 gig dedicated server i get lag alot but i benn getting alot of errors latly here is a error that i noticed during one of the stops
[02:00:31] [Server thread/INFO]: Stopping the server
[02:00:32] [Server thread/INFO]: Stopping server
[02:00:32] [Server thread/INFO]: Saving players
[02:00:32] [Server thread/INFO]: Saving worlds
[02:00:32] [Server thread/INFO]: Saving chunks for level 'world'/Overworld
[02:00:33] [Server thread/INFO]: Saving chunks for level 'world'/Nether
[02:00:33] [Server thread/INFO]: Saving chunks for level 'world'/The End
Sep 08, 2014 2:00:34 AM io.netty.util.concurrent.DefaultPromise notifyListener0
WARNING: An exception was thrown by rk.operationComplete()
io.netty.util.concurrent.BlockingOperationException: DefaultChannelPromise@4bf99325(uncancellable)
at io.netty.util.concurrent.DefaultPromise.checkDeadLock(DefaultPromise.java:397)
at io.netty.channel.DefaultChannelPromise.checkDeadLock(DefaultChannelPromise.java:157)
at io.netty.util.concurrent.DefaultPromise.awaitUninterruptibly(DefaultPromise.java:290)
at io.netty.channel.DefaultChannelPromise.awaitUninterruptibly(DefaultChannelPromise.java:135)
at io.netty.channel.DefaultChannelPromise.awaitUninterruptibly(DefaultChannelPromise.java:28)
at gr.a(SourceFile:199)
at rk.operationComplete(SourceFile:125)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:682)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:607)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:565)
at io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:413)
at io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:82)
at io.netty.channel.ChannelOutboundBuffer.safeSuccess(ChannelOutboundBuffer.java:608)
at io.netty.channel.ChannelOutboundBuffer.remove(ChannelOutboundBuffer.java:344)
at io.netty.channel.socket.nio.NioSocketChannel.doWrite(NioSocketChannel.java:283)
at io.netty.channel.AbstractChannel$AbstractUnsafe.flush0(AbstractChannel.java:694)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.forceFlush(AbstractNioChannel.java:321)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:515)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:464)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:744)
still a big issue really hope someone fixes this
chris is correct there two differant bugs and we should not have to make doggy scripts to kill processes to get servers to full stop
i do not think you understand correctly what is going on here
create portal x=-150110 y=63 z =-81045
enter portal nether cords are x=-18773 y=15 z=-10141
go back in everything is good
head back to nether
cords change to x=-2338 y=51 z=-1279 [WOW that is a big change]
enter portal to go back to over world
your cords are now
x=-18693 y=63 z=-10147
as you can see the issue is not linking my portals no nether portal should work like this 1 block = 8 not 8000
so really its not WAI please look at pictures and see what is happing before you say soem thing is WAI
I have a bunch of these type of crashes and it happens alot now since 1.9 on smp here is my crash reports