Shell Programming and Scripting

I assume that you have a Platform.pm available somewhere on your system. There are a few ways to include it, but the easiest in my view is to add the following at the top of your script...

Code:

#!/usr/bin/perl -w

BEGIN {
push @INC, "<directory containing Platform.pm>";
}
.
.

This dynamically adds the directory to the @INC variable before any of the main code runs and makes it clear what you're doing. You can do the same thing by adding a -I option on the command line but then you have to invoke Perl explicitly rather than just executing your .pl script

they are there, though I'm not sure what "missing in @INC" means because they are in the same directory as the aws-daemon

would it say its missing if the process wasn't running?

the only thing that happened at the same time this occured was the data center where this is hosted experienced an outage

Having them listed in your perl script is not the same as having the modules installed on your system somewhere.

The @INC is a list of directories where perl will look to find these modules.

Code:

(@INC contains:
/etc/perl
/usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.8
/usr/share/perl/5.8
/usr/local/lib/site_perl
.)

It wouldn't hurt to run a simple command to see if the file exists and is simply not in the path:

Code:

find / -name Platform.pm -print

Yes, Platform.pm is on the system

I don't really want to add the @INC variable at this time because I'm completely sure what even caused the perl process to stop, if it was due to the network outage then thats fine I just want to know that I'm not trying to initiate something that had been terminated because of another problem in the system.

I thought I had a disaster recovery plan so that I could reboot the system entirely myself in a matter of a few short steps but I think we blew that off or forgot about it. My sysadmin is off onto another adventure and unreachable so I'm trying my best to not do more harm than good.

---------- Post updated at 04:39 PM ---------- Previous update was at 04:25 PM ----------

i ran that and its in the same directory

/same/path/to/aws-daemon

How does @INC provide the path, in other words it looks like it provides the path to

/etc/perl
/usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.8
/usr/share/perl/5.8
/usr/local/lib/site_perl

So shouldn't the /same/path/to/Platform.pm be in that list

---------- Post updated at 04:56 PM ---------- Previous update was at 04:39 PM ----------

Ok, so I ran:

Code:

perl -e "print join(\"\n\", @INC);"

and the /path/to/Platform.pm is not in the results this is all thats there:

/etc/perl
/usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.8
/usr/share/perl/5.8
/usr/local/lib/site_perl

Is it possible that when the reboot occured it upgraded to 5.8.8 and wiped the @INC array clean?

If thats the case, then this /path/to/Platform.pm may just be one of many that are now missing in the @INC array, so if I just manually add it back in via command line as:

Code:

perl -I /path/to/Platform.pm

Now I also see a Platform.pm.old in the same directory but not sure if that is of any help.

---------- Post updated at 08:03 PM ---------- Previous update was at 04:56 PM ----------

I tried doing the perl -I command and it didn't seem to add it to the @INC list

---------- Post updated at 09:57 PM ---------- Previous update was at 08:03 PM ----------

Ok another discovery

when I login to root with su the /Platform.pm and the /aws.conf are not there

is that what the problem is? when I'm logged in as a regular user they are there.

---------- Post updated 09-02-09 at 03:39 PM ---------- Previous update was 09-01-09 at 09:57 PM ----------

Added the following to the top of the script, which worked.

Code:

use lib '/path/to/modules';