How do I avoid 'confluence1' service name and user name when re-installing from binary?

[Pat Ryan]

• What I want is to be able to do is install confluence on same server, uninstall it, install it again and not have it name the service 'confluence1'.  Reason is I'm automating install/configure using Ansible and need to depend on it always being 'confluence' and never 'confluence1'.
• What file triggers atlassian-confluence-6.2.3-x64.bin to know that Confluence has been installed before and therefore install it as 'confluence1'? 
•  When I install Confluence from '.bin' it creates a user named 'confluence' and service named '/etc/init.d/confluence' and sets ownership of '/opt/atlassian/confluence/logs',  '/opt/atlassian/temp' and '/opt/atlassian/work' to 'confluence' user.
• When I un-install Confluence on my server, then install it again to the same server, from then on it creates a user named 'confluence1' and service '/etc/init.d/confluence1' and the directories are owned by 'confluence1'.  I uninstall by running '/opt/atlassian/confluence/uninstall'.  
• I've tried removing all traces of atlassian/confluence from '/opt', '/var' and '/etc' and removed 'confluence*' user and '/home', but when I install confluence again it always creates 'confluence1'. 

Thanks!

[mehrdaad]

Have you tried to delete confluece user and group?  

Apparently uninstalling Jira deletes it's users and groups but confluence does not.  

Try to run:  

userdel confluence

groupdel confluence