Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep getting libdaemonjvm.server.LockError$ZombieFound in Earthly satellite #397

Open
nafg opened this issue Jul 28, 2024 · 1 comment
Open

Comments

@nafg
Copy link
Contributor

nafg commented Jul 28, 2024

               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Caught libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36, trying again in 3 seconds
               +dist | Exception in thread "main" java.lang.Exception: libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36
               +dist | 	at bloop.Bloop$.loop$1(Bloop.scala:102)
               +dist | 	at bloop.Bloop$.main(Bloop.scala:114)
               +dist | 	at bloop.Bloop.main(Bloop.scala)
               +dist | Caused by: libdaemonjvm.server.LockError$ZombieFound: Cannot connect to process 36
               +dist | 	at libdaemonjvm.server.Lock$.ifProcessRunning$1(Lock.scala:59)
               +dist | 	at libdaemonjvm.server.Lock$.$anonfun$tryAcquire$6(Lock.scala:76)
               +dist | 	at libdaemonjvm.server.Lock$.$anonfun$tryAcquire$6$adapted(Lock.scala:75)
               +dist | 	at scala.Option.flatMap(Option.scala:[283](https://gitlab.com/bookphone/igud-bnei-torah/-/jobs/7445435560#L283))
               +dist | 	at libdaemonjvm.server.Lock$.ifFiles$1(Lock.scala:75)
               +dist | 	at libdaemonjvm.server.Lock$.tryAcquire(Lock.scala:94)
               +dist | 	at bloop.Bloop$.loop$1(Bloop.scala:93)
               +dist | 	... 2 more
               +dist | Caused by: java.net.ConnectException: Connection refused
               +dist | 	at java.base/sun.nio.ch.UnixDomainSockets.connect0(Native Method)
               +dist | 	at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:154)
               +dist | 	at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:150)
               +dist | 	at java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:878)
               +dist | 	at libdaemonjvm.internal.Java16SocketHandler$.client(Java16SocketHandler.scala:22)
               +dist | 	at libdaemonjvm.internal.SocketHandler$.client(SocketHandler.scala:18)
               +dist | 	at libdaemonjvm.internal.SocketFile$.connect(SocketFile.scala:23)
               +dist | 	at libdaemonjvm.internal.SocketFile$.canConnect(SocketFile.scala:14)
               +dist | 	at libdaemonjvm.server.Lock$.ifProcessRunning$1(Lock.scala:57)
               +dist | 	... 8 more
@oyvindberg
Copy link
Owner

Interesting. What happens before this? And what is the platform?

It does look a problem outside of bleep, somewhere in bloop-rifle, bloop or libdaemonjvm. It may absolutely be bleep's fault, but I don't have any insight into this part of the start to be honest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants