[csw-users] Blastwave.org unavailable?
EBradley at williams-int.com
EBradley at williams-int.com
Fri Jun 1 17:21:33 CEST 2007
Ugh...and on a Friday, no less. Well, here's hoping that it doesn't
spill over into your weekend! :-\
Evan Bradley
-----Original Message-----
From: users-bounces+ebradley=3Dwilliams-int.com at lists.blastwave.org
[mailto:users-bounces+ebradley=3Dwilliams-int.com at lists.blastwave.org] On
Behalf Of Dennis Clarke
Sent: Friday, June 01, 2007 11:15 AM
To: questions and discussions
Subject: Re: [csw-users] Blastwave.org unavailable?
> It appears that www.blastwave.org has been unavailable for some time
> (as of Friday 9am ET), is there an estimated time when it will be up?
In 2 hours or less. That is a safe estimate.
I have dragged in new networking equipment among other things.
Also, we all need to see the value of a build system and code repository
for this project and thus I needed to take svn.blastwave.org down also.
Why ?
here is why :
# ls -lap /var/crash/`uname -n`/*4
-rw-r--r-- 1 root root 1217657 Jun 1 10:49
/var/crash/svn/unix.4
-rw-r--r-- 1 root root 167092224 Jun 1 10:50
/var/crash/svn/vmcore.4
# mdb -k /var/crash/svn/unix.4 /var/crash/svn/vmcore.4 Loading modules:
[ unix krtld genunix specfs ufs sd md ip sctp usba fctl nca nfs random
sppp crypto ]
> $c
vpanic(0, 3, 2a100457738, 2a100457980, 81010100, 2a100457738)
cpu_aflt_log+0x520(170, 2a10045778b, 2a1004579b0, 10, 2a1004578c7,
11ed180) cpu_async_error+0xc08(11ed000, 0, 180000000, 183b454,
2a100457aa4, 0)
utl0+0x4c(14011d0, 1084, 257d4, 0, ff348000, 14011d0)
> $<msgbuf
MESSAGE
SunOS Release 5.10 Version Generic_118833-03 64-bit Copyright 1983-2005
Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
<snip>
IP Filter: v4.0.2, running.
WARNING: [AFT1] Uncorrectable Memory Error on CPU0 Data access at TL=3D0,
errID 0x 0001e5e0.d66f1850
AFSR 0x00000001<ME>.00300000<UE,CE> AFAR 0x00000000.17c01298
AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0xff2e7500
UDBH 0x028b<UE> UDBH.ESYND 0x8b UDBL 0x0000 UDBL.ESYND 0x00
UDBH Syndrome 0x8b Memory Module Upper [AFT2] errID
0x0001e5e0.d66f1850 E$tag !=3D PA from AFAR; E$line was victimized
dumping memory from PA 0x00000000.17c01280 instead [AFT2] E$Data
(0x00): 0x00000000.00000000 [AFT2] E$Data (0x08): 0x00000000.00000000
[AFT2] E$Data (0x10): 0x00000000.00000000 [AFT2] E$Data (0x18):
0x00000000.00005245 [AFT2] E$Data (0x20): 0x00000000.00000000 [AFT2]
E$Data (0x28): 0x00000000.00003135 [AFT2] E$Data (0x30):
0x00000000.00000000 [AFT2] E$Data (0x38): 0x00000000.00002c52
panic[cpu0]/thread=3D30001f53660:
[AFT1] errID 0x0001e5e0.d66f1850 UE Error(s)
See previous message(s) for details
000002a100457680 SUNW,UltraSPARC-IIi:cpu_aflt_log+520 (170, 2a10045778b,
2a10045
79b0, 10, 2a1004578c7, 11ed180)
%l0-3: 00000000000f0000 000002a100457738 000002a1004578c8
0000000000000000
%l4-7: 00000300000cc1c0 0000000000000003 0000000000001000
00000000011ed800 000002a1004578d0
SUNW,UltraSPARC-IIi:cpu_async_error+c08 (11ed000, 0, 180000000,
183b454, 2a100457aa4, 0)
%l0-3: 0000000000000000 00000000011ed000 0000000000000001
000000000180c000
%l4-7: 0000000000000000 0000000000000000 000000007e600000
000000007fe00000
syncing file systems...
1
done
dumping to /dev/dsk/c0t0d0s3, offset 65536, content: kernel
>
#
So I am fixing that and then once it is up and running I will migrate it
to a Niagara based machine.
So .. this was not exactly well planned but necessary.
The internet connection went offline at midnight last night and I had it
back up by 2AM and then off and on since then.
In fact .. you may ( or may not ) be able to ping www.blastwave.org and
login.blastwave.org also.
I'll keep you briefed.
Dennis
_______________________________________________
users mailing list
users at lists.blastwave.org
https://lists.blastwave.org/mailman/listinfo/users
This email message and any attachment(s) are for the sole use of the intende=
d recipient(s) and may contain proprietary and/or confidential information w=
hich may be privileged or otherwise protected from disclosure.=0A=
=0A=
Any unauthorized review, use, disclosure or distribution is prohibited. If y=
ou are not the intended recipient(s), please contact the sender by reply ema=
il and destroy the original message and any copies of the message as well as=
any attachment(s) to the original message.
More information about the users
mailing list