When starting the atom, its status goes to "stopped" or "Offline" within seconds. The logs do not show any message.
A privileged user started the atom previously then the atom terminated unexpectedly, leaving behind a non-writable file.
Look for a file which name starts with "i4jdaemon__" followed by the location of the atom file with underscore as separator in the "/tmp" folder (at the root of the filesystem):
ls -l /tmp/i4jdaemon_*
The presence of this file while the atom is not running is preventing the atom from starting.
Delete the file using any required privileges.
Always start the atom using the designated user account.