Skip to main content
T
T-Hawk__DELT_
Participating Frequently
January 11, 2010
Question

Issues with Logging config being ignored in FMS 3.5

  • January 11, 2010
  • 2 replies
  • 2411 views

I recently upgraded our FMS server from 3.0 to 3.5.  I was using a custom logging format so that we could process the streaming logs using awstats.  I backed up, uninstalled, and installed 3.5.  I ported over the configs for the server by manually going through the old files and new files and updating where necessary.

Here is an excerpt from my Logger.xml:

<FileName>access.[NN].log</FileName>
.....
<Schedule type="daily">02:00</Schedule>

      <!-- Max number of log files to keep, files will be named access.01.log,  -->
      <!-- access.02.log, access.03.log etc.                                    -->
      <History>30</History>
.....
<Events>play;stop</Events>
.....
<Fields>c-ip;date;time;x-sname;x-status;c-proto;sc-bytes</Fields>

However, when I look at the log file, first it is named:

 8 -rw-rw----   1 nobody nobody     6318 Dec 31 15:19 access.2009123000.log
 4 -rw-rw----   1 nobody nobody     1694 Jan  1 23:53 access.2009123100.log
 4 -rw-rw----   1 nobody nobody      988 Jan  2 00:08 access.2010010100.log

which isn't the format I specified...and it isn't rotating when I specified, and:

session connect-pending 2010-01-01      23:53:56        100     xxx.xxx.xxx.xxx   3073    3073    normal  -       -       -       -       -       -

it isn't logging what I told it to.

I'm fairly new to FMS administration, so not sure what is up.

Everything is streaming correctly (we only use it to stream videos at this time), and I've restarted it twice since the installation.  Once after I modified the config, and then late last week when I got the proper key installed.  So it should be using the correct configuration.

I went through the recent release notes for the .1, .2, and .3 releases, but saw no mention of the Logging issue I've mentioned here.  I will consider upgrading again though if that will solve the problem.

Any insights anyone has would be useful.

Thanks

    This topic has been closed for replies.

    2 replies

    A
    Anonymous
    January 12, 2010

    I concur with Asa, there is something else causing the logs not to be written correctly. Here are the highlights of a typical Logger.xml that I deploy:

      <Access>
         <Directory>${LOGDIR}</Directory>
        <FileName>access.[YYYY]-[MM]-[DD]-[NN].log</FileName>
        <Time></Time>
        <Rotation>
          <MaxSize>1048576</MaxSize> 
           <Schedule type="daily">00:00</Schedule>
          <History>99</History>
          <Rename>true</Rename>
        </Rotation>
        <Events>connect;disconnect</Events>
         <Fields> # snipped for privacy purposes # </Fields>
      </Access>

    I can confirm that custom logging in 3.5.* works just fine, as I'm using it myself.

    Hope this helps!

    RMT.
    --
    Rick Tait
    e: rickt@stickam.com

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    January 11, 2010

    Hmm, that's unexpected.  It sounds like none of the changes that you've made have taken hold in the logs.  We should confirm that FMS is actually reading the logs from that location and not another one.  Have you checked in your system logs to make sure that FMS was able to open the Logger.xml file and isn't accidentally having permissions or mangled XML issues?  If you can, try a small local install and see if it's still not taking for you - I have a feeling that this has to do with FMS getting ahold of that log file and the warning not making itself seen.

    Asa

    T
    T-Hawk__DELT_Author
    Participating Frequently
    January 13, 2010

    I checked the system error log (messages) and didn't see anything about Logger.xml.  Just two messages about when I restarted the server and successfully loading Server.xml.  So nothing positive or negative about Logger.xml.

    I did notice that one of the logs had ballooned to 8.6 GB, and when trying to figure out why, it was errors FMS was throwing to the file (which stopped when I rebooted the server on the 5th, and started on the 3rd.  I did the upgrade on the 29th)

    I'm going to be upgrading to 3.5.3 tomorrow morning, and I'll take a closer look at the log problem at that time.

    When I run the update installers, do I have to follow the same procedure I did when I ran the upgrade? (backup -> uninstall -> reinstall -> port over content/settings)

    Thanks,

    T
    T-Hawk__DELT_Author
    Participating Frequently
    January 14, 2010

    I just completed the upgrade to 3.5.3.  Still not reading the logs config correctly.  Here is some output from /var/log/messages and from the console when starting the server.

    Jan 14 07:57:09 gill Service[26165]: Server stopped .
    Jan 14 07:57:14 gill Service[26713]: Server starting...
    Jan 14 07:57:14 gill Service[26713]: Server started (/opt/adobe/fms/conf/Server.xml).
    Jan 14 07:57:14 gill Adaptor[26733]: Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4
    Jan 14 07:57:15 gill Adaptor[26733]: Listener started ( _defaultRoot__edge1 ) : 1935/v4

    and:

    # ./fmsmgr server fms restart
    Server:fms command:restart
    NPTL 2.3.4
    Stopping Adobe Flash Media Server (please check /var/log/messages)
    Server has shutdown...

    Starting Adobe Flash Media Server (please check /var/log/messages)

    Nothing there that would seem to indicate anything regarding Logger.xml.

    Is there somewhere/something else I can check?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices