Wed Jul 6 02:09:59 CEST 2011
Application tree was working...has been for weeks.
Ran rebar and it crashed, shit all over my nodes (again.) No problem,
been there done that, fix it up...
Now when I run it (after rebar's generate) it gives me the "undef
Spend hours trying to figure out everything from how my lib_dirs got
changed, env, everything, full cleans, everything.
Pull a backup ... it works.
Hand merge all new changes... works, runs fine.
Nuke the directory and copy the backup into the directory....undef start/2.
Copy the entire tree to another directory ... runs fine.
What/where/WTF has been corrupted that running it from a specific
directory would cause issues?
/opt/name/proj <-- undef start/2, used to work
/opt/name/wtf/proj <-- works
My lib_dirs have not changed, binary cp -r between the two directories
so they're identical.
Rebar may have caused it, but now that it's in this completely f'd up
state I need to figure out how to get it OUT of this state, since
rebar's just a packaging system in front of erlexec.
So ... two identical directory structures, one works and one does not.
Again, it's been working for weeks .. this is not a fundamental issue
but more "state."
I have -not- rebooted. I want to understand this fully before I push
in into production.
Anyone know of a good place to start digging?
More information about the erlang-questions