This all depends on how the script is coded. With no information, I am guessing the script is hanging for some reason.
kill off the all of the processes running the script
Edit your script: either use some kind of lockfile or search ps output for more than 1 occurrence of your script
Make sure the cron envrionment - especially the PATH - is exactly the same as yours is when you test the script and it works. This includes the current working directory.
Don't use relative paths to files.
Change the cron entry to have the script create a log file .. myscript > /path/to/logfile
What is that script trying to do..? Are you calling any other scripts/applications inside your script? If that is the case, what you are referrung may be the child processes.
Make entries in the script before the startup to see any existing processes and kill it(its not a fair idea to kill the process if you have a neat option to stop the application process/script)..
Something like below can be used to kill the process.
The script which is in question is used for deleting the files based on the timestamp which have been calculated using some logic.
The script is not calling any other script.
Now, please suggest:
Can I kill all the PIDs related to the script so that it can be started again succesfully. The script is already in the production environment, therefore can't make any other changes. Before moving it to the production, it has been tested successfully and worked in the production environment as well.
I see 4 PIDs in total for one scrip of which 2 shows running state and other 2 sleep state.