Just an idea, to maybe come closer to the problem, try to
use Data::Dumper;
somewhere early in your script and add some debugging aids into the problematic sub, like
sub get_remote_file { print "Retrieving data file..."; my @site_data; print Dumper( $conx ); chomp( @site_data = `$conx` ); print Dumper( @site_data ); if ( $? >> 8 ) { print "Failed!\n"; } else{ print "Success!\n"; } for $line( @site_data ) { ( $name, $filepath, $mod, $md5 ) = split( "\,", $line ); $site_data{$name} = ["$filepath", "$mod", "$md5"]; } @site_data = (); }
Maybe that reveals something that would explain the different behavior of the first run compared with the subsequent ones.

In reply to Re: Processing data from SSH stream by Krambambuli
in thread Processing data from SSH stream by Spasticus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.