reby.log is your friend. Look in there for anything that looks like an error (e.g. stack traces). Did you follow the installation instructions exactly?

Make sure you're not editing your files with a crude Windows editor. In particular, you do NOT want to edit your conf file with NotePad, WordPad or MS Word. Such editors will put Windows-style line endings (CR-LF) or worse garbage into your conf file, rendering it unusable by the Reby script which wants it to be in UNIX format. Use a real text editor.

Telnet to your bot (or DCC to the party line) as the same eggdrop user that is being used by Reby. Then issue a ".tcl binds" command. If you get "What? You need '.help'" back from the bot, that means Tcl is not working yet on your bot. If you haven't already, comment out these two lines in your conf:

 unbind dcc n tcl *dcc:tcl
 unbind dcc n set *dcc:set

If that doesn't help either, then also change this line to a setting of 0:

 set must-be-owner 1

If you're patient, you can do it the clean way with the resetreby script. But this will take a while until a signal-handling bug is fixed in reby.rb.

If you're not patient, you can run killreby to rudely kill the process, then rerun reby.rb.

Reby cannot survive across a bot rehash or restart. Whenever you startup, restart or rehash your bot, you must restart Reby. Note that Reby automatically rehashes the bot whenever it starts up.