I'm a bit confused by your reply... sorry for my misunderstanding here.
The issue is duplicate share submissions. There are a few ways that have been posted on how to mitigate this behavior (for example, force the nonce to lower case):
name : message.params,
jobId : message.params,
extraNonce2 : message.params,
nTime : message.params.toLowerCase(),
nonce : message.params.toLowerCase()
Are there any other known fixes to address duplicate shares in NOMP?
Once the appropriate code changes have been made, is there anything other than restarting the stratum server that needs to be done? If so, what other steps need to be taken (not sure what crontab scripts you're referring to, please explain)?
Erroneous shares... if indeed it is the case that duplicate shares have been submitted, then writing SQL to clean them out of the shares tables isn't too hard to do. In fact, if it were indeed discovered that a user had been successfully submitting duplicate shares, I'd simply wipe all of that user's shares from the database and ban the user from the pool.
Thanks again for the replies.