Loading ...
Sorry, an error occurred while loading the content.

upgrade to 0.55 == messed up logging

Expand Messages
  • pcg4242
    I upgraded our servers to 0.55 from 0.5[01] late last week. After I ... use SOAP::Lite +trace = result = sub { print STDERR join( | ,$$,(scalar
    Message 1 of 3 , Apr 22, 2002
    • 0 Attachment
      I upgraded our servers to 0.55 from 0.5[01] late last week. After I
      did so, some server-side logging seemingly broke. The CGI code:

      --- code ---
      use SOAP::Lite +trace =>
      result =>
      sub {
      print STDERR join('|',$$,(scalar localtime),$ENV
      {'REMOTE_ADDR'},'result',@_), "\n";
      #for (sort keys %ENV) { print STDERR "\t$_: $ENV{$_}\n" }
      },
      parameters =>
      sub {
      my ($act) = ($ENV{'HTTP_SOAPACTION'} =~ m!#([^\"]+)!);
      print STDERR join('|',$$,(scalar localtime),$ENV
      {'REMOTE_ADDR'},'parameters',$act,@_), "\n";
      },
      ;
      ------

      Before the upgrade (with 0.50), I saw the following in the Apache
      error log (which is where STDERR goes):

      --- before ---
      26706|Wed Apr 10 18:48:47 2002|192.168.202.25|parameters|alive

      26706|Wed Apr 10 18:48:48 2002|192.168.202.25|result|online

      26713|Wed Apr 10 18:48:49 2002|192.168.202.25|parameters|get_name|-
      key|00139970|-output|WW1|-return|FirstAsArray

      26713|Wed Apr 10 18:48:50
      2002|192.168.202.25|result|NAME||139970||abc123|Mr. Foo Bar|Bar|Mr.
      Bar|90210|pcg-test1@...|0|||Mr.
      Foo Bar|123 Main Street|Anywhere, CA 90210|||
      ------

      (I've added an extra "\n" after each individual line for
      readability.) That told me exactly what I wanted: what was called,
      and what the result was, in a very nice (for my programmers) format.

      NOW, with 0.55, I get wacky stuff:

      --- after ---
      4206|Mon Apr 22 18:00:05
      2002|192.168.202.25|result|alive|SOAP::Lite|parameters

      4206|Mon Apr 22 18:00:05 2002|192.168.202.25|parameters|alive|1

      SOAP::Server::handle: online

      4265|Mon Apr 22 18:00:08
      2002|192.168.202.25|result|get_name|SOAP::Lite|parameters

      4265|Mon Apr 22 18:00:08 2002|192.168.202.25|parameters|get_name|1

      SOAP::Server::handle: NAME 139970 abc123 Mr. Foo Bar Bar Mr. Bar
      90210 pcg-test1@... 0 Mr. Foo Bar 123 Main Street Anywh
      ere, CA 90210
      ------

      What in the world is this?! It looks like @_ only EVER contains
      [ 'SOAP::Lite' ] (verified with Data::Dumper). Why is
      SOAP::Server::handle logging, and not through my defined function?
      Why is 'parameters' (defined after 'result') getting stuck on to the
      end of my 'result' debugging msgs, i.e.:

      ...|result|get_name|SOAP::Lite|parameters

      and '1' getting stuck on to the end of my 'parameters' debugging
      msgs, i.e.:

      ...|parameters|get_name|1

      ?! I'm sure I'm doing something wrong in the first place, but this
      *was* working with 0.50, and I just want to get it working again with
      0.55.

      Thanks for the help,

      Peter
    • pcg4242
      Can no one help with my message, re-posted below? Does no one care about logging anything on their systems? Could someone maybe post their code to do logging
      Message 2 of 3 , Apr 30, 2002
      • 0 Attachment
        Can no one help with my message, re-posted below? Does no one care
        about logging anything on their systems? Could someone maybe post
        their code to do logging that is *working* with 0.55?

        TIA,

        Peter

        --- I wrote:
        > I upgraded our servers to 0.55 from 0.5[01] late last week. After I
        > did so, some server-side logging seemingly broke. The CGI code:
        >
        > --- code ---
        > use SOAP::Lite +trace =>
        > result =>
        > sub {
        > print STDERR join('|',$$,(scalar localtime),$ENV
        > {'REMOTE_ADDR'},'result',@_), "\n";
        > #for (sort keys %ENV) { print STDERR "\t$_: $ENV{$_}\n" }
        > },
        > parameters =>
        > sub {
        > my ($act) = ($ENV{'HTTP_SOAPACTION'} =~ m!#([^\"]+)!);
        > print STDERR join('|',$$,(scalar localtime),$ENV
        > {'REMOTE_ADDR'},'parameters',$act,@_), "\n";
        > },
        > ;
        > ------
        >
        > Before the upgrade (with 0.50), I saw the following in the Apache
        > error log (which is where STDERR goes):
        >
        > --- before ---
        > 26706|Wed Apr 10 18:48:47 2002|192.168.202.25|parameters|alive
        >
        > 26706|Wed Apr 10 18:48:48 2002|192.168.202.25|result|online
        >
        > 26713|Wed Apr 10 18:48:49 2002|192.168.202.25|parameters|get_name|-
        > key|00139970|-output|WW1|-return|FirstAsArray
        >
        > 26713|Wed Apr 10 18:48:50
        > 2002|192.168.202.25|result|NAME||139970||abc123|Mr. Foo Bar|Bar|Mr.
        > Bar|90210|pcg-test1@a...|0|||Mr.
        > Foo Bar|123 Main Street|Anywhere, CA 90210|||
        > ------
        >
        > (I've added an extra "\n" after each individual line for
        > readability.) That told me exactly what I wanted: what was called,
        > and what the result was, in a very nice (for my programmers) format.
        >
        > NOW, with 0.55, I get wacky stuff:
        >
        > --- after ---
        > 4206|Mon Apr 22 18:00:05
        > 2002|192.168.202.25|result|alive|SOAP::Lite|parameters
        >
        > 4206|Mon Apr 22 18:00:05 2002|192.168.202.25|parameters|alive|1
        >
        > SOAP::Server::handle: online
        >
        > 4265|Mon Apr 22 18:00:08
        > 2002|192.168.202.25|result|get_name|SOAP::Lite|parameters
        >
        > 4265|Mon Apr 22 18:00:08 2002|192.168.202.25|parameters|get_name|1
        >
        > SOAP::Server::handle: NAME 139970 abc123 Mr. Foo Bar Bar Mr. Bar
        > 90210 pcg-test1@a... 0 Mr. Foo Bar 123 Main Street Anywh
        > ere, CA 90210
        > ------
        >
        > What in the world is this?! It looks like @_ only EVER contains
        > [ 'SOAP::Lite' ] (verified with Data::Dumper). Why is
        > SOAP::Server::handle logging, and not through my defined function?
        > Why is 'parameters' (defined after 'result') getting stuck on to
        the
        > end of my 'result' debugging msgs, i.e.:
        >
        > ...|result|get_name|SOAP::Lite|parameters
        >
        > and '1' getting stuck on to the end of my 'parameters' debugging
        > msgs, i.e.:
        >
        > ...|parameters|get_name|1
        >
        > ?! I'm sure I'm doing something wrong in the first place, but this
        > *was* working with 0.50, and I just want to get it working again
        with
        > 0.55.
        >
        > Thanks for the help,
        >
        > Peter
      • Paul Kulchenko
        Hi, Peter! I ll take a look and get back to you later today. I don t think there were any changes in logging algorithm between 0.52 and 0.55, so something
        Message 3 of 3 , Apr 30, 2002
        • 0 Attachment
          Hi, Peter!

          I'll take a look and get back to you later today. I don't think there
          were any changes in logging algorithm between 0.52 and 0.55, so
          something probably happened before 0.52.

          Best wishes, Paul.

          --- pcg4242 <pcg-yahoo@...> wrote:
          > Can no one help with my message, re-posted below? Does no one care
          > about logging anything on their systems? Could someone maybe post
          > their code to do logging that is *working* with 0.55?
          >
          > TIA,
          >
          > Peter
          >
          > --- I wrote:
          > > I upgraded our servers to 0.55 from 0.5[01] late last week. After
          > I
          > > did so, some server-side logging seemingly broke. The CGI code:
          > >
          > > --- code ---
          > > use SOAP::Lite +trace =>
          > > result =>
          > > sub {
          > > print STDERR join('|',$$,(scalar localtime),$ENV
          > > {'REMOTE_ADDR'},'result',@_), "
          ";
          > > #for (sort keys %ENV) { print STDERR " $_: $ENV{$_}
          " }
          > > },
          > > parameters =>
          > > sub {
          > > my ($act) = ($ENV{'HTTP_SOAPACTION'} =~ m!#([^"]+)!);
          > > print STDERR join('|',$$,(scalar localtime),$ENV
          > > {'REMOTE_ADDR'},'parameters',$act,@_), "
          ";
          > > },
          > > ;
          > > ------
          > >
          > > Before the upgrade (with 0.50), I saw the following in the Apache
          >
          > > error log (which is where STDERR goes):
          > >
          > > --- before ---
          > > 26706|Wed Apr 10 18:48:47 2002|192.168.202.25|parameters|alive
          > >
          > > 26706|Wed Apr 10 18:48:48 2002|192.168.202.25|result|online
          > >
          > > 26713|Wed Apr 10 18:48:49
          > 2002|192.168.202.25|parameters|get_name|-
          > > key|00139970|-output|WW1|-return|FirstAsArray
          > >
          > > 26713|Wed Apr 10 18:48:50
          > > 2002|192.168.202.25|result|NAME||139970||abc123|Mr. Foo
          > Bar|Bar|Mr.
          > > Bar|90210|pcg-test1@a...|0|||Mr.
          > > Foo Bar|123 Main Street|Anywhere, CA 90210|||
          > > ------
          > >
          > > (I've added an extra "
          " after each individual line for
          > > readability.) That told me exactly what I wanted: what was
          > called,
          > > and what the result was, in a very nice (for my programmers)
          > format.
          > >
          > > NOW, with 0.55, I get wacky stuff:
          > >
          > > --- after ---
          > > 4206|Mon Apr 22 18:00:05
          > > 2002|192.168.202.25|result|alive|SOAP::Lite|parameters
          > >
          > > 4206|Mon Apr 22 18:00:05 2002|192.168.202.25|parameters|alive|1
          > >
          > > SOAP::Server::handle: online
          > >
          > > 4265|Mon Apr 22 18:00:08
          > > 2002|192.168.202.25|result|get_name|SOAP::Lite|parameters
          > >
          > > 4265|Mon Apr 22 18:00:08
          > 2002|192.168.202.25|parameters|get_name|1
          > >
          > > SOAP::Server::handle: NAME 139970 abc123 Mr. Foo Bar Bar Mr.
          > Bar
          > > 90210 pcg-test1@a... 0 Mr. Foo Bar 123 Main Street Anywh
          > > ere, CA 90210
          > > ------
          > >
          > > What in the world is this?! It looks like @_ only EVER contains
          > > [ 'SOAP::Lite' ] (verified with Data::Dumper). Why is
          > > SOAP::Server::handle logging, and not through my defined
          > function?
          > > Why is 'parameters' (defined after 'result') getting stuck on to
          > the
          > > end of my 'result' debugging msgs, i.e.:
          > >
          > > ...|result|get_name|SOAP::Lite|parameters
          > >
          > > and '1' getting stuck on to the end of my 'parameters' debugging
          > > msgs, i.e.:
          > >
          > > ...|parameters|get_name|1
          > >
          > > ?! I'm sure I'm doing something wrong in the first place, but
          > this
          > > *was* working with 0.50, and I just want to get it working again
          > with
          > > 0.55.
          > >
          > > Thanks for the help,
          > >
          > > Peter
          >
          >
          > ------------------------ Yahoo! Groups Sponsor
          >
          > To unsubscribe from this group, send an email to:
          > soaplite-unsubscribe@yahoogroups.com
          >
          >
          >
          > Your use of Yahoo! Groups is subject to
          > http://docs.yahoo.com/info/terms/
          >
          >


          __________________________________________________
          Do You Yahoo!?
          Yahoo! Health - your guide to health and wellness
          http://health.yahoo.com
        Your message has been successfully submitted and would be delivered to recipients shortly.