Solved Server freezing when using 'show' command

Hi there, I just wanted to report something that I have noticed.

Since this recent update I have had my server go down about 5 times, on this last crash I had realised what I did just before the crash.
I had used the oxide.show command, The problem is that I did not define it properly.
Instead of oxide.show group modperm, I typed: oxide.show modperm
As there doesn't seem to be a error check it tries to launch the code causing the server to drop out and hang as everyone almost instantly looses connection and RCon becomes unresponsive.

Please have a look.
Thanks
#################################
Edit: It has not also happened when done correctly.

> version
Protocol: 1327.105.1
Build Version: 679.78
Build Date: 10/21/2015 6:45:59 PM
Unity Version: 5.2.1p3
> oxide.version
Oxide version: 2.0.1531, Rust Protocol: 1327

 

that would be my understanding, But it seems to just hang only seconds after I type the message, at first it didn't happen, but not it has been, could this possible be that my permission file is corrupted then?
I ask as everything seems to work fine on my pc, no high memory or CPU usage either, but once I type or misty that everyone one server looses connection, rcon drops and I have to log into acp.vilayer.com and stop/restart.

 

hhhmm.
OK well tonight when home I will backup my content and reinstall server to guarantee that's not the issue.
If it still happens after a fresh wipe what would you recommend.
and thank you for your help thus far.
[DOUBLEPOST=1446038883,1445976907][/DOUBLEPOST]## Update ##

It seems that with a group with either too many parents or permissions seems to cause the hang, as everything was great but once I added another parent to add 3 extra perms it started happening, so now every time I type oxide.show group owner.
I am happy to let you on my server as moderator ID so you can test it.

 

Short answer Yes I used parenting, and yes its likely while typing I F**Ked up and created loops, it is hard to remember as this happened 3 times (as in reinstalled server 3 times) These did happen while I was bloody tired and 3 in the morning. I have really long permission lists and used parenting to make it easier, for now I have just done it the hard way and given each group ALL the perms they have.

So yeah it probably was that But I would have no idea as I cant remember that well.
Anyway Here is my original reply, its messy as I am tired from a long day at work so sorry if its hard to understand.
Again thanks for your help and responses I think this mod and the oxide community has been great.

 

I only ever used console for parenting.I only manually edited json to easily as permissions and to visually check everything off.
But I'm using a fresh install of my server so I have only used console for that.

 

I have a few times when deleting the file while server is offline and then restarting to get new file, This has worked but then after adding either around 7 parents or some other things it will happen, for now I have manually typed permissions for each group, this is a pain, if there is a way to stop accidental loops or to possibly make parenting easier/safer I would be very happy.

What I will do now is manually type all perms per group, back that up and then try parenting to keep it clean.

 

Thanks, as said ill back up my safe version before using parenting again, and if this happens ill upload the file for you to inspect.
another situation when this problem seems to happen is when I have completed the perm parenting and then try and parent the tag group to its relative eg ownertag patent ownerperm, it will say that ownertag could not be changed and after that point will have issues aswell.
I wish I could give more detail BUT I can not see exactly when the error starts untill I try oxide.show.

For now though since I haven't used parent its fine.

 

I have also experienced this, it is definitely related to parenting. It has completely stopped after removing all parents.

 

Yeah as said I have this problem as well, But regards to it not being fixed after removing parenting did you do as I said, stop the server, delete the group config file then start the server.
Reason being is that after creating a loop it seems to bug that file and no matter what it will freeze every time until you delete it and generate a new one.

 

Hey @Wulf
Would like to say thanks to you and your team for fixing the show bug, I will be redoing my permision tree this weekend .
I will let you know if any errors, other wise I am super happy with this bug being fixed.

Regards
Alpha