emacsclient unable to connect to daemon under snap installation of Emacs

I am facing with a well know problem, when I try to start emacs --daemon on a remote machine, I am getting following error emacsclient: connect: Connection refused:

$ ps aux | grep -E "[e]macs"  # returns empty
$ emacsclient -t -q doo.py
emacsclient: connect: Connection refused

Warning: due to a long standing Gtk+ bug
https://gitlab.gnome.org/GNOME/gtk/issues/221
Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.
Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.
## ...
Starting Emacs daemon.
Unable to start the daemon.
Another instance of Emacs is running the server, either as daemon or interactively.
You can use emacsclient to connect to that Emacs process.
Error: server did not start correctly
Error: Could not start the Emacs daemon

---

The way I connect into the remote machine ssh -Y4t user@IP zsh --login -i

• I have done this set-up X11 Forwarding over ssh an it works, where xclock displays gui.
• echo $DISPLAY => workstation:10.0

I don’t know what can I debug more to handle this or what is the issue. I also have same configuration on a different remote machine where it works without a problem.

---

Update based on @phils guide(please see in comments) debug in depth.

$ kill -9 $(ps aux | grep -E "[e]macs" | awk '{print $2}')
$ ps aux | grep -E "[e]macs"  # returns empty
$ emacsclient -t -q doo.py
emacsclient: can't find socket; have you started the server?
emacsclient: To start the server in Emacs, type "M-x server-start".

Warning: due to a long standing Gtk+ bug
https://gitlab.gnome.org/GNOME/gtk/issues/221
Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.
Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.

$ ps aux | grep -E "[e]macs"  # returns empty
netlab    9885 14.1  0.4 464628 67812 ?        Ssl  01:40   0:04 /snap/emacs/296/usr/bin/emacs --daemon
$ kill -9 $(ps aux | grep -E "[e]macs" | awk '{print $2}')
$ ps aux | grep -E "[e]macs"  # returns empty

$ unset ALTERNATE_EDITOR
$ echo $ALTERNATE_EDITOR

$ ls -l /tmp/emacs1002/server
srwx------ 1 netlab netlab 0 Jul 16 01:40 /tmp/emacs1002/server
$ rm -rf /tmp/emacs1002/server
$ ls -l /tmp/emacs1002/server
ls: cannot access '/tmp/emacs1002/server': No such file or directory
$ emacsclient -t
emacsclient: can't find socket; have you started the server?
emacsclient: To start the server in Emacs, type "M-x server-start".
emacsclient: No socket or alternate editor.  Please use:

    --socket-name
    --server-file      (or environment variable EMACS_SERVER_FILE)
    --alternate-editor (or environment variable ALTERNATE_EDITOR)
$ emacs -Q --daemon

Warning: due to a long standing Gtk+ bug
https://gitlab.gnome.org/GNOME/gtk/issues/221
Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.
Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.
Starting Emacs daemon.
$ ls -l /tmp/emacs1002/server
srwx------ 1 netlab netlab 0 Jul 16 01:42 /tmp/emacs1002/server
$  emacsclient -t
emacsclient: can't find socket; have you started the server?
emacsclient: To start the server in Emacs, type "M-x server-start".
emacsclient: No socket or alternate editor.  Please use:

    --socket-name
    --server-file      (or environment variable EMACS_SERVER_FILE)
    --alternate-editor (or environment variable ALTERNATE_EDITOR)