Re^2: Net::Server console or debug output?

I have log level set to 4.

I've even tried using the log file, with log level at 4, and I only get IP connection entries.
Neither print to STDERR nor log->(4,"test message"); show up anywhere.
I understand that if I use the log file that STDERR goes to dev/null.

**UPDATE**
This morning the log output has decided to cooperate, and display on the console. However, I'm still not
getting *my* output to display.
The device on the other end is an
embedded device, so I can not get
the output from the socket.
The two lines I've tried to print with are:

$self->log(4,"client said '$RxString'\r\n");

print STDERR "client said '$RxString'\r\n";
[download]

Thanks,
Aaron

Comment on Re^2: Net::Server console or debug output? Download Code

Replies are listed 'Best First'.
Re^3: Net::Server console or debug output? by alager (Acolyte) on Apr 28, 2009 at 15:46 UTC
UPDATE again...WTF!?!? As I was writing my last update, the messages started appearing! First the CONNECT TCP Peer messages only, then my "client said" messages....this is too weird for me. Aaron	[reply]
Re^4: Net::Server console or debug output? by alager (Acolyte) on Apr 28, 2009 at 23:09 UTC
So I get out of my meetings, and the dang thing isn't printing the log messages again! argh! Has anyone tried this before? Aaron UPDATE: Turns out that there was a firewall issue and it was messing with the DBI call, and it was just hanging there. Therefore no log output. IT fixed firewall settings, I added timeout to DBI connection and all is good again. :)	[reply]