Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Nitrogen Error on Startup #46

Inaimathi opened this Issue · 8 comments

2 participants


I'm getting an error when starting up bin/nitrogen console. It initially happenined on a project I was putting together, but it also happens with the default nitrogen project.

 =ERROR REPORT==== 5-Jun-2012::16:18:28 ===
 ERROR: "Failed to start: ~s~n" - [{case_clause,
 (no error logger present) error: "Error in process <0.102.0> with exit valu\"gen_event.erl\"},{line,219}]},{proc_lib,exit_p,2,[{file,\"proc_lib.erl\"}

Both files only seem to be present in .beam form, so I can't see what the errors in gen_event.erl and proc_lib.erl are.

I've tried doing a fresh clone of the nitrogen source and building it again, but the error persists. Did I accidentally change some piece of state that nitrogen depends on? It doesn't seem to have anything to do with Erlang itself, since systems other than nitrogen start up fine.


Yes. I'm running Debian Wheezy with Erlang R15B01 from the AMD64 apt repo.


Building nitrogen fails with the latest OTP checkout. It throws

 ERROR: Reltool support requires at least reltool-0.5.2; this VM is using reltool
 make[1]: *** [rel_inner] Error 1
 make[1]: Leaving directory `/home/inaimathi/nitrogen'
 make: *** [rel_yaws] Error 2

and exits. The only thing I changed is installing Erlang from here rather than apt. Is reltool something I can install separately?



Just tried a fresh install of Nitrogen on a 32 bit machine, and the error doesn't appear there. This is going to be interesting; I'll keep playing around and post notes.


That might be relevant; I just got the latest checkout from the OTP github (which is up to R15B02, I think).


I've been poking at this on and off for the past few days with no luck.

Just got finished installing nitrogen (from your repo) and Erlang (from the Debian repos) on a clean machine, and I can't repro it. I must have accidentally knocked over something related to the logging processes last time. Closing the issue as far as I'm concerned.

Sorry to worry you (hopefully you didn't waste too much time on this).

@Inaimathi Inaimathi closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.