[baltimorepm] Baltimore-pm Digest, Vol 41, Issue 3

Tue Oct 7 14:08:33 PDT 2014

Thanks everyone for your help with my Net::HL7::Connection issue. I tried
netstat and adjusting firewall settings, telnetting to the server with the
port and all came up empty. Then a colleague suggested checking the
database server to see if it had an HL7 service running, and yep, hl7d was
running. I restarted that. and. it. worked! Ahhem. Thanks everyone! :)

On Mon, Oct 6, 2014 at 3:00 PM, <baltimore-pm-request at pm.org> wrote:

> Send Baltimore-pm mailing list submissions to
>         baltimore-pm at pm.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mail.pm.org/mailman/listinfo/baltimore-pm
> or, via email, send a message with subject or body 'help' to
>         baltimore-pm-request at pm.org
>
> You can reach the person managing the list at
>         baltimore-pm-owner at pm.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Baltimore-pm digest..."
>
>
> Today's Topics:
>
>    1. Re: help with Net::HL7::Connection (Stephen Belcher)
>    2. Re: help with Net::HL7::Connection (Zachary Zebrowski)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 6 Oct 2014 10:36:09 -0400
> From: Stephen Belcher <sbelcher at gmail.com>
> To: Baltimore Perl Mongers <baltimore-pm at pm.org>
> Subject: Re: [baltimorepm] help with Net::HL7::Connection
> Message-ID:
>         <
> CAA1vO_7b4txrNu5jFAPhzyRBE4oUWkSv8_m7gvw-kdAKPMwpbQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> FWIW, on CentOS, it seems that the `netstat -en` command doesn't list
> listening sockets, for that you'll need to add the `-l` flag (which then
> seems to list *only* listening sockets, not sure how to get both).
> Additionally, you can `grep` that output for the port you're trying to
> connect on to see if it's open, instead of parsing the whole output,
> *e.g.*,
> `netstat -len | grep :12345` (not 12345, natch, just whatever the port is).
> I was hoping there was a way to instruct `netstat` to only care about
> particular ports, but I can't seem to find that.
>
> --Stephen
>
> On Mon, Oct 6, 2014 at 10:13 AM, Bernie Simon <bsimon at stsci.edu> wrote:
>
> >  The standard command to check for open ports is
> >
> >  netstat -en
> >
> >  More information can be found on the web. Don?t know how this stuff in
> > configured under Windows.
> >
> >   From: Dawn Wallis <wallisds at gmail.com>
> > Reply-To: Baltimore Perl Mongers <baltimore-pm at pm.org>
> > Date: Monday, October 6, 2014 at 9:48 AM
> > To: "baltimore-pm at pm.org" <baltimore-pm at pm.org>
> > Subject: [baltimorepm] help with Net::HL7::Connection
> >
> >   At work we had a Windows XP computer setup to collect lab results from
> > Quest. That data was parsed and transferred to our mysql database (on a
> > CentOS server) using Net::HL7::Connection. Recently we had to upgrade to
> > Windows 7 for the capturing computer. So I'm using Windows 7 to collect
> > blood work data from Quest.
> >
> >  The scripts that were on the XP machine seem to work pretty well on the
> > 7 box too, so I am able to get the data parsed and ready for transport to
> > my mysql database server, but it doesn't send.
> >
> >  I am getting a "Could not connect. No connection could be made because
> > the target machine actively refused it" error.
> >
> >  Net::HL7::Connection takes a host and port but no password or anything.
> > I figure I'm supposed to open a port on the db server to allow this
> > incoming connection, but I'm having trouble figuring that part out. I
> don't
> > know where to look on the centos server to see if a port is open for the
> > other xp computer, what file to edit... etc.
> >
> > Any suggestions?
> >
> >
> >
> > Thanks,
> > Dawn
> >
> > _______________________________________________
> > Baltimore-pm mailing list
> > Baltimore-pm at pm.org
> > http://mail.pm.org/mailman/listinfo/baltimore-pm
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.pm.org/pipermail/baltimore-pm/attachments/20141006/2696ad5f/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Mon, 6 Oct 2014 10:50:01 -0400
> From: Zachary Zebrowski <zak.zebrowski at gmail.com>
> To: Baltimore Perl Mongers <baltimore-pm at pm.org>
> Subject: Re: [baltimorepm] help with Net::HL7::Connection
> Message-ID:
>         <CAO3DSneu2ga=eSXfN=w8NnF-QvSd=
> 5q3wObYiQJ463sSq05b7Q at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Also, it could be a firewall issue.  Some OS's block all ports by default
> for inbound connections.  I don't know the correct invocation on centos to
> see what the firewall settings are, but if centos uses ufw.  See if you can
> do a:
>
> sudo ufw status
>
> if you see it enabled, do a sudo ufw disable and then see if you can
> connect in...  Obviously, the correct solution then is to figure out what
> ports the application is using and then enable those in the firewall, and
> re-enable the firewall if this is the case...
>
> Good luck
>
> Zak
>
>
> On Mon, Oct 6, 2014 at 10:36 AM, Stephen Belcher <sbelcher at gmail.com>
> wrote:
>
> > FWIW, on CentOS, it seems that the `netstat -en` command doesn't list
> > listening sockets, for that you'll need to add the `-l` flag (which then
> > seems to list *only* listening sockets, not sure how to get both).
> > Additionally, you can `grep` that output for the port you're trying to
> > connect on to see if it's open, instead of parsing the whole output,
> > *e.g.*, `netstat -len | grep :12345` (not 12345, natch, just whatever the
> > port is). I was hoping there was a way to instruct `netstat` to only care
> > about particular ports, but I can't seem to find that.
> >
> > --Stephen
> >
> > On Mon, Oct 6, 2014 at 10:13 AM, Bernie Simon <bsimon at stsci.edu> wrote:
> >
> >>  The standard command to check for open ports is
> >>
> >>  netstat -en
> >>
> >>  More information can be found on the web. Don?t know how this stuff in
> >> configured under Windows.
> >>
> >>   From: Dawn Wallis <wallisds at gmail.com>
> >> Reply-To: Baltimore Perl Mongers <baltimore-pm at pm.org>
> >> Date: Monday, October 6, 2014 at 9:48 AM
> >> To: "baltimore-pm at pm.org" <baltimore-pm at pm.org>
> >> Subject: [baltimorepm] help with Net::HL7::Connection
> >>
> >>   At work we had a Windows XP computer setup to collect lab results from
> >> Quest. That data was parsed and transferred to our mysql database (on a
> >> CentOS server) using Net::HL7::Connection. Recently we had to upgrade to
> >> Windows 7 for the capturing computer. So I'm using Windows 7 to collect
> >> blood work data from Quest.
> >>
> >>  The scripts that were on the XP machine seem to work pretty well on the
> >> 7 box too, so I am able to get the data parsed and ready for transport
> to
> >> my mysql database server, but it doesn't send.
> >>
> >>  I am getting a "Could not connect. No connection could be made because
> >> the target machine actively refused it" error.
> >>
> >>  Net::HL7::Connection takes a host and port but no password or anything.
> >> I figure I'm supposed to open a port on the db server to allow this
> >> incoming connection, but I'm having trouble figuring that part out. I
> don't
> >> know where to look on the centos server to see if a port is open for the
> >> other xp computer, what file to edit... etc.
> >>
> >> Any suggestions?
> >>
> >>
> >>
> >> Thanks,
> >> Dawn
> >>
> >> _______________________________________________
> >> Baltimore-pm mailing list
> >> Baltimore-pm at pm.org
> >> http://mail.pm.org/mailman/listinfo/baltimore-pm
> >>
> >
> >
> > _______________________________________________
> > Baltimore-pm mailing list
> > Baltimore-pm at pm.org
> > http://mail.pm.org/mailman/listinfo/baltimore-pm
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.pm.org/pipermail/baltimore-pm/attachments/20141006/3cd119b3/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Baltimore-pm mailing list
> Baltimore-pm at pm.org
> http://mail.pm.org/mailman/listinfo/baltimore-pm
>
> ------------------------------
>
> End of Baltimore-pm Digest, Vol 41, Issue 3
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/baltimore-pm/attachments/20141007/f611e70c/attachment.html>