On 10/24/2012 03:45 PM, G V wrote:
Software Raid. Both drives have the same 1 error.
On Wed, Oct 24, 2012 at 2:57 PM, Eric Shubert mailto:e...@shubes.net>> wrote:
HW or SW raid?
On 10/24/2012 02:33 PM, G V wrote:
Yes using RAID1. And it looks like you are correct. Hard drive
Actually I was mistaken. This system does not use SW raid but rather LVM to
join two drives together.
Yes I will need to look into this problem.
Thanks for all your help.
On Wed, Oct 24, 2012 at 4:23 PM, Eric Shubert wrote:
> Hmmm. Sounds peculiar.
> I'll let you take it from here.
> Please let
Hmmm. Sounds peculiar.
I'll let you take it from here.
Please let us know how you make out.
--
-Eric 'shubes'
On 10/24/2012 03:45 PM, G V wrote:
Software Raid. Both drives have the same 1 error.
On Wed, Oct 24, 2012 at 2:57 PM, Eric Shubert mailto:e...@shubes.net>> wrote:
HW or SW raid?
Software Raid. Both drives have the same 1 error.
On Wed, Oct 24, 2012 at 2:57 PM, Eric Shubert wrote:
> HW or SW raid?
>
>
> On 10/24/2012 02:33 PM, G V wrote:
>
>> Yes using RAID1. And it looks like you are correct. Hard drive error.
>>
>> Error 1 occurred at disk power-on lifetime: 27 hours
HW or SW raid?
On 10/24/2012 02:33 PM, G V wrote:
Yes using RAID1. And it looks like you are correct. Hard drive error.
Error 1 occurred at disk power-on lifetime: 27 hours (1 days + 3 hours)
When the command that caused the error occurred, the device was
active or idle.
After command co
Yes using RAID1. And it looks like you are correct. Hard drive error.
Error 1 occurred at disk power-on lifetime: 27 hours (1 days + 3 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH
These are essentially the same versions I have on my host.
This error is intermittent too. For some packages, the problem never
occurs. The first error you posted is from the sandbox. This last run,
everything installed ok in the sandbox, and the error didn't occur until
the upgrade to the liv
Here you go.
rpm -qa | grep rpm | sort
redhat-rpm-config-8.0.45-32.el5.centos
rpm-4.4.2.3-28.el5_8
rpm-build-4.4.2.3-28.el5_8
rpm-devel-4.4.2.3-28.el5_8
rpmforge-release-0.5.2-2.el5.rf
rpm-libs-4.4.2.3-28.el5_8
rpm-python-4.4.2.3-28.el5_8
Eric, thanks for your patience and continued help. This has
Dang. They're identical, which they should be. That's good.
So how does rpm manage to install the packages in the sandbox, but
chokes on them (sometimes) when installing them in the base system?
I don't think I've run this stuff on COS 5.8 yet. Has anyone updated
these packages with qtp-newmo
On 10/23/2012 9:47 PM, Eric Shubert wrote:
> Ok, George. Let's keep digging. There's something weird going on here.
>
> # cd /usr/src/qtp-upgrade/RPMS
> # ls -l *.i686.rpm
-rw-r--r-- 1 root root 307536 Oct 23 22:17
courier-authlib-toaster-0.59.2-1.3.10.i686.rpm
-rw-r--r-- 1 root root 853017 Oct
Ok, George. Let's keep digging. There's something weird going on here.
# cd /usr/src/qtp-upgrade/RPMS
# ls -l *.i686.rpm
# md5sum *.i686.rpm
Then, with sandbox still mounted:
# cd /mnt/qtp-sandbox/usr/src/redhat/RPMS/i686
# ls -l *.i686.rpm
# md5sum *.i686.rpm
The file sizes and md5sums should
Eric,
Thanks for all your help.
Cleaned out those directories and tried again. Same issue.
Starting the install/upgrade ...
qtp-remove-pkgs v0.3.1
Here goes 'rpm -Uvh' for the packages we're processing ...
/usr/src/qtp-upgrade/RPMS/courier-authlib-toaster-0.59.2-1.3.10.i686.rpm: not
an rpm package
Here you go.
qtp-whatami
qtp-whatami v0.3.8 Tue Oct 23 11:03:44 PDT 2012
REAL_DIST=CentOS
DISTRO=CentOS
OSVER=5.8
QTARCH=i686
QTKERN=2.6.18-308.16.1.el5PAE
BUILD_DIST=cnt50
BUILD_DIR=/usr/src/redhat
This machine's OS is supported and has been tested
Thanks
On Tue, Oct 23, 2012 at 10:37 AM, Eric
I've looked at the code a bit (it's been a while since I wrote this).
It appears that there should be a /usr/src/qtp-upgrade/RPMS/ directory
which is used for updating the actual RPMS. Do you have this directory?
If so, please wipe it out, remove rpms from the build tree, and try
again with a f
For some reason, it appears that the part which copies the binary rpms
out of the sandbox into the main filesystem is hosing the rpms somehow.
Probably something to do with the unionfs.
I seem to remember seeing your kernel version, but can't find it now.
Please post:
# qtp-whatami
Thanks.
On Tue, Oct 23, 2012 at 10:11 AM, Eric Shubert wrote:
> This is very peculiar.
>
> What do you have for:
>
> # rpm -qa | grep fuse | sort
>
rpm -qa | grep fuse | sort
dkms-fuse-2.7.4-1.nodist.rf
fuse-2.8.0-1.qtp
fuse-unionfs-0.23-2.qtp
>
> What is the size and md5sum of your
> /usr/src/qtp-upg
This is very peculiar.
What do you have for:
# rpm -qa | grep fuse | sort
What is the size and md5sum of your
/usr/src/qtp-upgrade/RPMS/courier-authlib-toaster-0.59.2-1.3.10.i686.rpm
?
--
-Eric 'shubes'
On 10/23/2012 09:52 AM, G V wrote:
It ran perfectly this time and restarted qmail. In the
It ran perfectly this time and restarted qmail. In the end it failed to
unmount the sandbox. It still seems to not have updated. I have found one
line in output and have it bold below.
qtp-ami-up2date
New Qmail-Toaster Packages Available:
available: vpopmail-toaster-5.4.33-1.4.0
(installed: vpop
Yes i did just y. This has happened before too. Then I have rerun it
and it may do the same thing or it may work. I have tried mutliple
times. I will try again.
Thanks,
George
On Tue, Oct 23, 2012 at 8:45 AM, Eric Shubert wrote:
> Did you enter y or something? It needs to match y or Y specificall
Did you enter y or something? It needs to match y or Y
specifically (or nothing, as this is the default action). If you simply
rerun qtp-newmodel, it should get you to that point again fairly
quickly, recognizing that everything is already built and ready to go.
On 10/22/2012 08:06 PM, G V wro
I tried updating vpopmail-toaster and yes noticed those dependencies. It
looked like all went well but in the end the updates were not installed.
No errors in the build log either.
qtp-build-rpms v0.3.7
qtp-remove-pkgs v0.3.1
Building vpopmail-toaster-5.4.33-1.4.0 ...
Installing vpopmail-toaster-5
That's interesting (to me at least), George.
You should be aware that when upgrading vpopmail-toaster, there are
dependencies which need to be rebuilt, and qtp-newmodel will select
these packages automatically.
Keep us posted.
Thanks.
--
-Eric 'shubes'
On 10/21/2012 09:05 PM, G V wrote:
Er
Eric,
I installed control-panel-toaster without issue. I then went ahead and
installed qmailmrtg-toaster followed by autorespond-toaster as per your
previous instructions.
Then also installed spamassassin-toaster, clamav-toaster and
simscan-toaster together again as you instructed.
At first i seem
So let's try installing control-panel-toaster using qtp-newmodel.
I haven't a clue as to why control-panel-toaster is not installed, but
it doesn't really matter.
If that's successful, then try upgrading qmailmrtg-toaster.
--
-Eric 'shubes'
On 10/21/2012 04:45 PM, G V wrote:
Here you go.
rp
Here you go.
rpm -qa | grep toaster | sort
autorespond-toaster-2.0.4-1.3.6
clamav-toaster-0.97.3-1.3.44
courier-authlib-toaster-0.59.2-1.3.10
courier-imap-toaster-4.1.2-1.3.10
daemontools-toaster-0.76-1.3.6
ezmlm-cgi-toaster-0.53.324-1.3.6
ezmlm-toaster-0.53.324-1.3.6
isoqlog-toaster-2.1-1.3.7
lib
On 10/20/2012 10:26 PM, G V wrote:
Thanks Eric.
Had problem with first step.
On 10/20/2012 8:29 PM, Eric Shubert wrote:
>There must be something a bit peculiar about this host then, or
>perhaps the combination of packages being updated.
>
>Let's try upgrading something simple first, by itself.
Thanks Eric.
Had problem with first step.
On 10/20/2012 8:29 PM, Eric Shubert wrote:
> There must be something a bit peculiar about this host then, or
> perhaps the combination of packages being updated.
>
> Let's try upgrading something simple first, by itself. Please try
> upgrading only qmailmr
There must be something a bit peculiar about this host then, or perhaps
the combination of packages being updated.
Let's try upgrading something simple first, by itself. Please try
upgrading only qmailmrtg-toaster, by itself.
If that's successful, try autorespond-toaster by itself.
If that's
On 10/20/2012 8:39 AM, Eric Shubert wrote:
> On 10/19/2012 09:29 PM, G V wrote:
>> Just tried again. Removed rpms from both those directories and also
>> /usr/src/redhat/SRPMS/
>> Confirmed sandbox was not mounted before starting then mounted it while
>> running qtp-newmodel.
>
> You should let qt
On 10/19/2012 09:29 PM, G V wrote:
Just tried again. Removed rpms from both those directories and also
/usr/src/redhat/SRPMS/
Confirmed sandbox was not mounted before starting then mounted it while
running qtp-newmodel.
You should let qtp-newmodel create a *new* sandbox, not simply mount one
t
Just tried again. Removed rpms from both those directories and also
/usr/src/redhat/SRPMS/
Confirmed sandbox was not mounted before starting then mounted it while
running qtp-newmodel.
I did notice that apart from updating packages it was also installing
control-panel-toaster which I did not have i
Are you sure you deleted the rpm from /usr/src/redhat/RPMS/i686/? This
is separate from the ones in /usr/src/qtp-upgrade/old-rpms/.
Does qtp-newmodel rebuild the binary rpm in the sandbox, or say that it
already exists?
On 10/19/2012 02:08 PM, G V wrote:
Yes I have tried unmounting sandbox a
Yes I have tried unmounting sandbox and recreating. I have also tried
deleting rpms and also srpms.
Still no go.
On Fri, Oct 19, 2012 at 12:19 PM, Eric Shubert wrote:
> Did you have qtp-newmodel create a new sandbox after doing so? I think
> you'll need to do so.
>
>
> On 10/19/2012 10:29 AM, G V
Did you have qtp-newmodel create a new sandbox after doing so? I think
you'll need to do so.
On 10/19/2012 10:29 AM, G V wrote:
Thanks for the response. I have already tried that.
On Fri, Oct 19, 2012 at 7:44 AM, Aleksander Podsiadły wrote:
Dnia 2012-10-19, pią o godzinie 06:02 -0700, George
34 matches
Mail list logo