Where is the location of snort.conf

The Snort application has a pretty robust logging subsystem. By enabling the unified log format you should, and are, seeing two types of logs:

1. alert file - contains high level information regarding the event
2. log file - contains much more detailed information including a packet dump

Both files are written to disk in binary format. While this makes it harder for the analyst to review, it is significantly faster for the application. For a little more, albeit not much, information the Snort Docs for the unified output plugin would be a worthwhile read.

If you want a raw text version of the triggered alerts, I would recommend the syslog output type. This is one of the more flexible, since it allows you to manage your logging on the host instead of the application. In addition, since you have the -d command line switch flipped, a capture of each packet that triggers an alert will be saved in pcap format. This still gives you good information to use in false positive analysis.

As long as the Snort daemon is running the problem that generally causes this behavior is usually one of three things:

1. Missing rule set, does not appear to apply here.
2. Interface not configured correctly (listening on inside interface, not external monitor port)
3. External interface not connected via a tap (if you are monitoring other hosts).

My best guess at this point is that probably need to specify the interface to the daemon differently. Unless you are actually using a bonded interface (not mentioned in your question) that would be the first place I would look.