Date:  Thu, 21 Sep 2006 02:57:47 -0400
From:  "MJR" <mjr (at mark) misswebhost.com>
Subject:  [coba-e:07148] Re: Existing lock /var/run/yum.pid: another copy is running. Aborting.
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <03a001c6dd4b$3f1f9d40$0701a8c0@desktop>
In-Reply-To:  AAAAAI9FR8AAx3JDrLpx6B1SkOTE3jEC
X-Mail-Count: 07148

Hi,

I'm getting the same thing on a test server 
In the tmp files I found 
   13 -rw-r-----   1 root root 1642 Sep 19 15:03 yum.update
   19 -rw-r-----   1 root root    0 Sep 19 15:03 yum.updating

The contents of yum.update is:
Updating:
 base-bluequartz-capstone  noarch     5100R-1.20060918BQ74.centos4
BlueQuartz         10 k
 base-bluequartz-glue    noarch     5100R-1.20060918BQ74.centos4  BlueQuartz
43 k

Transaction Summary
============================================================================
=
Install      0 Package(s)
Update       2 Package(s)
Remove       0 Package(s)
Total download size: 53 k
Downloading Packages:
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
^M  Updating  : base-bluequartz-glue         ######################### [1/4]

Then it goes blank.... 

Regards,
Mitch


-----Original Message-----
From: Yada Ho [mailto:yada (at mark) ds3.net] 
Sent: Wednesday, September 20, 2006 10:31 PM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:07145] Existing lock /var/run/yum.pid: another copy is
running. Aborting.

Hi Blues

I am getting this email daily
Cron <root@ns1> /usr/sausalito/handlers/nuonce-solarspeed/yum/yum_update
Existing lock /var/run/yum.pid: another copy is running. Aborting.
Existing lock /var/run/yum.pid: another copy is running. Aborting.

using nuonce v4.5
last update - Sep 16 04:00:09 Updated: hwdata.noarch 0.146.23.EL-1

rebooted

tried telnet
[root@ns1 /]# yum update
Existing lock /var/run/yum.pid: another copy is running. Aborting.

now can not add vsites or users to existing vsites

Yada