Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. Forum search problem

Forum search problem

Scheduled Pinned Locked Moved Support
7 Posts 2 Posters 116 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    S
    sbrehm_yahoo.com
    wrote on last edited by
    #1

    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?

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      You can use google, search for:

      site:www.fop2.com where is the fop log file

      1 Reply Last reply
      0
      • S
        S
        sbrehm_yahoo.com
        wrote on last edited by
        #3

        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?

        1 Reply Last reply
        0
        • N
          N
          nicolas
          wrote on last edited by
          #4

          You can search for the word "debug", one of the results is this post in the forum that will help you:

          View Post 905

          Best regards,

          1 Reply Last reply
          0
          • S
            S
            sbrehm_yahoo.com
            wrote on last edited by
            #5

            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.

            Hope this helps someone!

            1 Reply Last reply
            0
            • N
              N
              nicolas
              wrote on last edited by
              #6

              Thanks for taking the time to write the post, let me further explain the debug levels ( -X option )

              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

              1 Reply Last reply
              0
              • S
                S
                sbrehm_yahoo.com
                wrote on last edited by
                #7

                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.

                1 Reply Last reply
                0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                Powered by NodeBB Contributors
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups