Announcement

Collapse
No announcement yet.

no headers with w3c log file

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • no headers with w3c log file

    I tried to include the shoutcast w3c log in our sawmill installation, but it can't recognize the format. After contacting Sawmill I found out the problem lies in shoutcast, as it does not include header information in the w3c log. The headers are part of the W3C specification as can be found here: http://www.w3.org/TR/WD-logfile.html

    Can I include an extra option in the conf to get the headers or is it a bug from shoutcast?

    Regards,
    Coennie

  • #2
    to my knowledge the w3c log which is created hasn't had it's format changed in years (if at all) and not knowing what version of the DNAS you're using makes that trickier to give an answer. however, from a quick search, sawmill claims to support the SHOUTcast w3c log so something doesn't seem right either way (be it their claims or from the version of the DNAS you're using).

    -daz
    WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

    Comment


    • #3
      Hi Dro,

      Sorry should had to include my version.
      I'm using the latest version: shoutcast 2.0.29
      In the server conf i've included:
      W3CEnable=Yes
      w3clog=D:\Logs\Shoutcast\sc_w3c.log

      This generates a w3c log file with no headers, just entries. I've send these log files to sawmill and got this response:

      We have support for a SHOUTcast log that has W3C headers (in fact the headers are part of the W3C specification) and we detect SHOUTcast by this regex string: "^#Software: SHOUTcast".

      Beyond that I can't add much. If you know the fields in your logs, you can add your own fields line, this is the specification:



      We also support version 1.9 of the standard logging, if that is any help?
      But that leave me with the question is it a Sawmill error of a Shoutcast one.

      Regards,

      Coennie

      Comment


      • #4
        Originally Posted by coennie View Post
        But that leave me with the question is it a Sawmill error of a Shoutcast one.
        until i can compare a v1 and v2 w3c log file i'm not sure, though i've a feeling it's probably something in the v2 DNAS not being the same as the v1 DNAS did things which i can only assume is what Sawmill are working against.

        will advise once i've had a chance to check things out between the old DNAS and the current one.

        -daz
        WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

        Comment


        • #5
          Great

          will advise once i've had a chance to check things out between the old DNAS and the current one.
          I can supply you with a version 2 w3c log file, but would like to send it by email instead of a forum.

          Regards,

          Coennie

          Comment


          • #6
            i've already got a v2 file, it's a v1 file that i need to make be able to compare things which i've now got and yes there's a massive difference between the v2 and v1 files. will look to get that resolved for the next public release though will likely contact you with a test version to try out to confirm it works ok.

            since the v1 DNAS outputs the following before then listing the actually logging parts:
            #Software: SHOUTcast
            #Version: 1.9.8
            #Fields: c-ip c-dns date time cs-uri-stem c-status cs(User-Agent) sc-bytes x-duration avgbandwidth
            -daz
            WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

            Comment


            • #7
              i've already got a v2 file, it's a v1 file that i need to make be able to compare things which i've now got and yes there's a massive difference between the v2 and v1 files. will look to get that resolved for the next public release though will likely contact you with a test version to try out to confirm it works ok.

              since the v1 DNAS outputs the following before then listing the actually logging parts:
              thank you for your quick response!

              Regards,
              Coennie

              Comment


              • #8
                can you confirm what OS you're using to run the DNAS on as i've implemented the changes now (and fixed some extra line break issues with the Windows version). will then pm you a link to a test build to try out.

                -daz
                WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                Comment


                • #9
                  Hi DrO,

                  I'm using a Windows Server 2008 (6.0.6001).

                  Regards,
                  Coennie

                  Comment


                  • #10
                    pm sent with a link to a test build to try out with Sawmill.

                    -daz
                    WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                    Comment


                    • #11
                      was there any further follow-up on this working or not from the Sawmill tests?

                      -daz
                      WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                      Comment


                      • #12
                        Hi DrO,

                        Sawmill made a change in there software, I've tested with a pre-release and all is working well now. So in the next version of Sawmill it is solved.
                        Thank you for your cooperation!

                        Regards Coennie

                        Comment


                        • #13
                          that's good to know. will suggest to keep an eye out on things here so you can install a non-internal build of the DNAS hopefully in a few weeks.

                          -daz
                          WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                          Comment

                          Working...
                          X