Home/ Questions/Q 5944811
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T16:35:33+00:00

Normally, when my Erlang application starts via run_erl -daemon , I see in the

  • 0

Normally, when my Erlang application starts via run_erl -daemon, I see in the logs:

=====
===== LOGGING STARTED Mon May 16 14:39:11 UTC 2011
=====
Exec: /mware/erts-5.8.3/bin/erlexec -boot /mware/releases/1/gmcontroller -embedded -config /mware/etc/app.config -args_file /mware/etc/vm.args -- console
Root: /mware
heart_beat_kill_pid = 2302

Eshell V5.8.3  (abort with ^G)

(gmcontroller@127.0.0.1)1> 
===== ALIVE Mon May 16 14:54:34 UTC 2011

===== ALIVE Mon May 16 15:09:35 UTC 2011

===== ALIVE Mon May 16 15:24:36 UTC 2011

...

However, one time I’ve got 

=====
===== LOGGING STARTED Mon May 16 19:48:14 UTC 2011
=====
Exec: /mware/erts-5.8.3/bin/erlexec -boot /mware/releases/1/gmcontroller -embedded -config /mware/etc/app.config -args_file /mware/etc/vm.args -- console
Root: /mware
heart_beat_kill_pid = 2217

with no prompt and no ===== ALIVE ... messages until rebooting the computer. Are there any known causes for such behavior? My own suspicion is a problem with the file system.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Do/did you have old and invalid named pipes hanging around under /tmp/? It could be that restarting cleared your /tmp/ directory and that’s why it works now.

    • 0