I'm trying to search for the FOP2 log file and searched for "where is the fop log file". All the words were rejected as too common and the search failed. Any suggestions?
Ok, that didn't get me any further than my forum searching and I can't find the answer in the on-line documentation so I'll just ask the question - where in a config file can I find where FOP2 logs errors?
Ok, after further research I found what I was looking for. I found two types of logging with examples of how to control them with the command line.
-- audit /path/to/log.file (I used /var/log/fop2/audit.log)
I added this option to /etc/default/fop2 (which is pulled in by /etc/init.d/fop2 on my system). After creating the directory and restarting fop2 audit.log was automatically created and began logging logins and logouts.
I then set the log directory with "-l /var/log/fop2/"
Again, I added this to /etc/default/fop2. Entries started accumulating in error.log and output.log. I found the logging level in these responded to changes to the debug level. The default level on my system appears to be 0, but I added the following option as a placeholder to make it easier for future debugging:
--debuglevel 0
Increasing to examples found in the forums for command line option -X n creates increasingly detailed entries as n increases. On a general unused test system I accumulated over 4MB in output.log over a couple of hours.
Thanks! I was about to post just that question. I haven't found this elsewhere in the documentation or forum, just references to a few of the levels by number with no explanation of what is being logged. It might be helpful to have it on the http://www.fop2.com/documentation-insta ... ommandLine page.
BTW, in the --debuglevel description on that page, it mentions the command line option overrides the value in fop2.cfg. I didn't see any comments for debuglevel in my fop2.cfg, and putting in debuglevel = n also didn't seem to work. I'm running version 2.22.
Comments
site:www.fop2.com where is the fop log file
View Post 905
Best regards,
-- audit /path/to/log.file (I used /var/log/fop2/audit.log)
I added this option to /etc/default/fop2 (which is pulled in by /etc/init.d/fop2 on my system). After creating the directory and restarting fop2 audit.log was automatically created and began logging logins and logouts.
I then set the log directory with "-l /var/log/fop2/"
Again, I added this to /etc/default/fop2. Entries started accumulating in error.log and output.log. I found the logging level in these responded to changes to the debug level. The default level on my system appears to be 0, but I added the following option as a placeholder to make it easier for future debugging:
--debuglevel 0
Increasing to examples found in the forums for command line option -X n creates increasingly detailed entries as n increases. On a general unused test system I accumulated over 4MB in output.log over a couple of hours.
Hope this helps someone!
It is used for bitwise operations, where
1 = manager sent
2 - manager received
4 - fop2 sent
8 - fop2 received
16 - verbose level 1
32 - verbose level 2
64 - verbose level 3
128 - verbose level 4
256 - verbose level 5
So, for full debug use -X 511
for just AMI debug use -X 3
for AMI and FOP2 protocol debug use -X 15
BTW, in the --debuglevel description on that page, it mentions the command line option overrides the value in fop2.cfg. I didn't see any comments for debuglevel in my fop2.cfg, and putting in debuglevel = n also didn't seem to work. I'm running version 2.22.