Jump to content

Recommended Posts

I have been tasked with intentionally breaking some of our Tomcat instances that run on RedHat.  This is a test for our team to try to fix and start the applications.  I have altered ports, changed permissions, etc but still need to come up with some additional problems.  If anyone has any ideas I would appreciate it. 

Share this post


Link to post
Share on other sites

fill up the hard drive space

use up all the inodes on the hard drive

change permissions on log files so they can't be written to

put random characters in config files

turn off garbage collection

set memory as big or as small as you can

turn on a firewall that blocks all ports

set up cron jobs to perform the stuff above so when they fix it it changes back a minute later

 

Share this post


Link to post
Share on other sites
3 hours ago, blacklab said:

fill up the hard drive space

use up all the inodes on the hard drive

change permissions on log files so they can't be written to

put random characters in config files

turn off garbage collection

set memory as big or as small as you can

turn on a firewall that blocks all ports

set up cron jobs to perform the stuff above so when they fix it it changes back a minute later

 

Thanks for the advice.  There are a couple of things that I can't do but I can use the permissions on the log files.  I already put random characters in config and set the memory to 10GB.

Share this post


Link to post
Share on other sites

create a user and a group called "root_" or "root."

change the group on all the log files to root_

create a cronjob with that user to change permissions on the log files

create a program to run that takes up a shitload or memory and cpu and have it run sporadically.

Share this post


Link to post
Share on other sites
On 6/25/2020 at 11:16 AM, blacklab said:

create a user and a group called "root_" or "root."

change the group on all the log files to root_

create a cronjob with that user to change permissions on the log files

create a program to run that takes up a shitload or memory and cpu and have it run sporadically.

We have an application that takes about 40 minutes to start. At your suggestion I created a cronjob that executes the stop script every 5 minutes.  That was on Thursday morning.  They still haven't figured out whats going on.  I think that's enough.  Thanks for the suggestion.

Share this post


Link to post
Share on other sites
2 hours ago, TexasGary said:

We have an application that takes about 40 minutes to start. At your suggestion I created a cronjob that executes the stop script every 5 minutes.  That was on Thursday morning.  They still haven't figured out whats going on.  I think that's enough.  Thanks for the suggestion.

awesome. glad I could help.

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


mpu


Football ... Basketball ... Baseball ... Other Sports ... Recruiting ... Gambling ... Movies & TV ... Music ... Hobbies ... Lulz ... Food & Travel ... Daily Texan ... Help ... For Sale ... Politics ... Board Discussion
×
×
  • Create New...