7
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"><LINK
9
TITLE="FreeTDS User Guide"
10
HREF="index.htm"><LINK
12
TITLE="Troubleshooting"
13
HREF="troubleshooting.htm"><LINK
15
TITLE="Is the server there?"
16
HREF="serverthere.htm"><LINK
18
TITLE='"Page contains no data"'
19
HREF="pagenodata.htm"></HEAD
41
> User Guide: A Guide to Installing, Configuring, and Running <SPAN
52
HREF="serverthere.htm"
59
>Chapter 7. Troubleshooting</TD
85
> has quite extensive logging capabilities. These are often invaluable in setting up new configurations, when it's hard to be sure precisely what configuration information is being used, and what communication is (not) working. Often such questions can be quickly resolved by turning on logging and examining the logs.
93
>Environment Variables that Control Logging</A
107
>Log files can be turned on using the <TT
110
> environment variable. For instance, setting the location of a dumpfile
119
>export TDSDUMP=/tmp/freetds.log</B
123
Will generate a log file named <TT
143
write information to on how the configuration information is being
144
obtained, e.g. from environment variables, a <TT
150
> file. Sometimes it's unclear what source of information <SPAN
153
> is using to connect to a given dataserver. This variable can make that bright and clear. </P
155
>If set to the null string, the log file name will default to <TT
157
>/tmp/tdsconfig.log.<TT
168
> is the pid of the process generating the log. </P
186
SRC="../images/tip.gif"
193
>What if you were running <SPAN
203
> variable to a null string will cause <SPAN
206
> to open a log under every PID.
215
>export TDSDUMP=""</B
219
The log files will be named <TT
221
>/tmp/freetds.log.<TT
232
> is the pid number of the process generating the log.
239
>A couple of important notes about using the logs with <SPAN
243
the logs tend to grow large, so trim or archive them often. Secondly,
247
> will record certain network packets to the log, this
250
>includes login packets which can contain clear text or clear text
251
equivalent passwords.</I
252
> So, if this is a concern (most likely
253
is) make sure that the files are not world readable, and avoid posting
254
them to mailing lists.
257
>Once in a while, someone writes to the mailing list, asking why <SPAN
263
>. It sometimes turns out that logging was left turned on. Don't you be the next victim! <SPAN
266
> logs are meant for development and debugging, not as a system monitoring tool.
285
HREF="serverthere.htm"
301
HREF="pagenodata.htm"
310
>Is the server there?</TD
316
HREF="troubleshooting.htm"
323
>"Page contains no data"</TD
b'\\ No newline at end of file'