From WWW::Mechanize:

autocheck => [0|1]

Checks each request made to see if it was successful. This saves you the trouble of manually checking yourself. Any errors found are errors, not warnings.

The default value is ON, unless it's being subclassed, in which case it is OFF. This means that standalone WWW::Mechanizeinstances have autocheck turned on, which is protective for the vast majority of Mech users who don't bother checking the return value of get() and post() and can't figure why their code fails. However, if WWW::Mechanize is subclassed, such as for Test::WWW::Mechanize or Test::WWW::Mechanize::Catalyst, this may not be an appropriate default, so it's off.

Here, errors means die(). Since your program used autocheck=>1 by default, it dies when a problem occurs while calling $mech_cgi->follow_link(...). It has no chance to reach your own call to die - which is not what you want - as already observed by roboticus (Updated: paragraph).

Now you have at least two options:

• Wrap the calls that can fail into an eval-block and check for exceptions ($@), or
• create the WWW::Mechanize object using ...new( autocheck=>0 ) and check the results (see HTTP::Response) of $mech_cgi-calls for problems.

Example (2nd alternative):

use strict;
use WWW::Mechanize;
use Storable;

my $mech_cgi = WWW::Mechanize->new( autocheck => 0 );

$mech_cgi->get( 'http://www.molmovdb.org/cgi-bin/browse.cgi' );

my @cgi_links = $mech_cgi->find_all_links( url_regex => qr/motion.cgi/
+ );

for my $link ( @cgi_links ) {  # no C-style loop...
  print "following link: ", $link->url, "\n";

  my $res = $mech_cgi->follow_link( url => $link->url );
  # $res is a HTTP::Response object

  if ( $res->is_success ) {
    print "OK : Processing result ...\n";
  } else {
    print "ERR: Failed to retrieve page: ", $res->status_line, "\n";
  }

  $mech_cgi->back;
 
  sleep 5; # anti-aggressive scraping
}
[download]

Result:

...
following link: http://www.molmovdb.org/cgi-bin/motion.cgi?ID=ntrc
OK : Processing result ...
following link: http://www.molmovdb.org/cgi-bin/motion.cgi?ID=ppar
ERR: Failed to retrieve page: 500 Internal Server Error
following link: http://www.molmovdb.org/cgi-bin/motion.cgi?ID=rhorbp
OK : Processing result ...
...
[download]

Please check also if you have permission to scrape this site.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.