[Orca-users] Procallator.pl Reports 503 Errors

[David DeVault]

What is the output of the following command:

cat /proc/partitions

or 

cat /proc/diskstats


Depending on which file exists.

-----Original Message-----
From: Christopher Barros [mailto:cbarros at hbs.edu] 
Sent: Tuesday, October 16, 2007 12:43 PM
To: David DeVault; orca-users at orcaware.com
Subject: Re: [Orca-users] Procallator.pl Reports 503 Errors

Hi-

The problem doesn't appear to be with Orca as all the UNIX servers
appear to be updating currently to Orca or orcollator. The problem
appears to be only with the two Linux servers running procollator. I
moved proccol-* to a new directory on both orca and the linux server and
re-ran the procollator.pl script but I still receive the same 503 error.

We're running Redhat 4. Now that you mention it, I believe that in Feb
of last year one of the two servers were patched however, I can't be
sure that is what caused the problem.


On 10/16/07 2:54 PM, "David DeVault" <ddevault at icontrol.com> wrote:

> The code around line 503 does not get nfs stats so I doubt that's the 
> problem.  There must have been some kind of hardware related issue 
> around Feb 26.  Maybe a partition filled up or the system ran out of 
> memory.
> 
> What flavor of Linux are you running?  Were there any kernel updates 
> applied around the end of Feb?
> 
> Since you do not have any data from Feb 26th I would rename the last 
> data file and re-run orca.  Name the file something other than 
> proccol-*.  You can also move it to a different directory.  If that 
> does not work try a fresh orca install.
> 
> It would be interesting to see the latest datafile.  Can you send it?
> 
> Thanks.
> David
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Christopher Barros [mailto:cbarros at hbs.edu]
> Sent: Tuesday, October 16, 2007 11:28 AM
> To: David DeVault; orca-users at orcaware.com
> Subject: Re: [Orca-users] Procallator.pl Reports 503 Errors
> 
> Hi-
> 
> The Linux servers local disk layouts haven't changed. However, this 
> server is NFS attached to a Solaris server and shares out project 
> directories.
> Project directories on this server tends to change. Thus, /etc/fstab 
> is constantly being updated.
> 
> The server is being mirrored however, I don't know if it's a raid 1 or

> raid 5. I inherited this box and I'm trying to work out the kinks. I 
> would think it's a raid 1. No hardware has been replaced that I'm 
> aware of since Feb.
> 
> 
> On 10/16/07 1:51 PM, "David DeVault" <ddevault at icontrol.com> wrote:
> 
>> Hi Chris.
>> 
>> I could be wrong here, however, I have seen situations like this when

>> the disk partitions change for some reason.  Are you running any kind
> of
>> mirroring?  Have you replaced any hardware recently?  Did you create
> any
>> new partitions? 
>> 
>> David
>> 
>> -----Original Message-----
>> From: orca-users-bounces+ddevault=icontrol.com at orcaware.com
>> [mailto:orca-users-bounces+ddevault=icontrol.com at orcaware.com] On
> Behalf
>> Of Christopher Barros
>> Sent: Tuesday, October 16, 2007 8:55 AM
>> To: orca-users at orcaware.com
>> Subject: [Orca-users] Procallator.pl Reports 503 Errors
>> 
>> Hi-
>> 
>> We're currently running orca on a Solaris server and we have two 
>> Linux servers using Procollator.pl to update to orca. However, both 
>> servers stopped updating on Feb 26th (strange...). I've tried to 
>> restart procollator but I receive the following error messages:
>> 
>> Oct 15 16:40:00 natick procallator.pl: Argument "" isn't numeric in 
>> multiplication (*) at /usr/local/bin/procallator.pl line 503.
>> 
>> Oct 15 16:40:00 natick procallator.pl: Use of uninitialized value in 
>> multiplication (*) at /usr/local/bin/procallator.pl line 503.
>> 
>> Does anyone know how to resolve the 503 error messages. Thanks for
> your
>> help
>> in advance. 
>> 
>> 
>> _______________________________________________
>> Orca-users mailing list
>> Orca-users at orcaware.com
>> http://www.orcaware.com/mailman/listinfo/orca-users
> 
>