Re: is RELENG_5 Borked?

From: Andreas Klemm <andreas_at_freebsd.org>
Date: Mon, 15 Nov 2004 10:15:00 +0100
On Mon, Nov 15, 2004 at 12:15:53AM -0800, Julian Elischer wrote:
> I have no clue as to the problem.. the system freezes absolutly
> from yesterday's RELENG_5 or doesn't fail. No debugger, no dump etc..

Same for me. Left the system in X11 (fvwm2) yesterday evening
and 2-3 hours later it kind of freezed.

Its the 2nd or 3rd time in the last week.

This morning I only saw a black screen not more.

Powercycled and only found this in messages:

Nov 15 02:06:47 titan postgres[8020]: [12-1] ERROR:  duplicate key violates uniq
ue constraint "dspam_token_data_token_key"
Nov 15 02:07:37 titan postgres[8020]: [13-1] ERROR:  duplicate key violates uniq
ue constraint "dspam_token_data_token_key"
Nov 15 02:35:21 titan postgres[9339]: [2-1] ERROR:  duplicate key violates uniqu
e constraint "dspam_token_data_token_key"
Nov 15 02:35:21 titan postgres[9339]: [3-1] ERROR:  duplicate key violates uniqu
e constraint "dspam_token_data_token_key"
Nov 15 08:54:18 titan syslogd: kernel boot file is /boot/kernel/kernel
Nov 15 08:54:18 titan kernel: Copyright (c) 1992-2004 The FreeBSD Project.
Nov 15 08:54:18 titan kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 
1991, 1992, 1993, 1994
Nov 15 08:54:18 titan kernel: The Regents of the University of California. All r

	Andreas ///

am I maybe using bad kernel options ? ADAPTIVE_GIANT ?

See kernel options and /var/log/messages of today.
The fsck was needed since I had to hit reset.

FreeBSD titan.klemm.apsfilter.org 5.3-STABLE FreeBSD 5.3-STABLE #0: Wed Nov 10 10:37:30 CET 2004     root_at_titan.klemm.apsfilter.org:/usr/src/sys/i386/compile/TITAN  i386


options 	KTRACE			#ktrace(1) support
options		PANIC_REBOOT_WAIT_TIME=-1

machine		i386
cpu		I686_CPU
ident		TITAN

options 	INCLUDE_CONFIG_FILE     # Include this file in kernel
options 	SCHED_4BSD		#4BSD scheduler
options         ADAPTIVE_GIANT          # Giant mutex is adaptive.

options		VFS_AIO			# vmware

options 	INET			#InterNETworking
options 	FFS			#Berkeley Fast Filesystem
options 	SOFTUPDATES		#Enable FFS soft updates support
options 	UFS_EXTATTR
options 	UFS_ACL			#Support for access control lists
options 	UFS_DIRHASH		#Improve performance on big directories
options 	MD_ROOT			#MD is a potential root device
options 	CD9660			#ISO 9660 Filesystem
options 	PSEUDOFS		#Pseudo-filesystem framework
options 	PROCFS			#Process filesystem (requires PSEUDOFS)
options 	FDESCFS			#File descriptor filesystem
options 	MSDOSFS			#MS DOS File System (FAT, FAT32)
options		GEOM_GPT		#Disk Encryption
options		GEOM_BDE		#Disk Encryption

options 	COMPAT_43		#Compatible with BSD 4.3 [KEEP THIS!]
options 	COMPAT_FREEBSD4		#Compatible with FreeBSD4
options 	_KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev

options 	IPFIREWALL		#firewall
options 	IPFIREWALL_VERBOSE	#enable logging to syslogd(8)
options 	IPDIVERT		#divert sockets
options 	IPSTEALTH		#support for stealth forwarding
options 	DUMMYNET
options 	ZERO_COPY_SOCKETS
options		IPSEC			#IP security
options		IPSEC_ESP		#IP security (crypto; define w/ IPSEC)

options         ALTQ
options         ALTQ_CBQ        # Class Bases Queueing
options         ALTQ_RED        # Random Early Drop
options         ALTQ_RIO        # RED In/Out
options         ALTQ_HFSC       # Hierarchical Packet Scheduler
options         ALTQ_CDNR       # Traffic conditioner
options         ALTQ_PRIQ       # Priority Queueing

# Postgresql database
options         SYSVSHM
options         SYSVSEM
options         SYSVMSG
options         SHMMAXPGS=65536
options         SEMMNI=40
options         SEMMNS=240
options         SEMUME=40
options         SEMMNU=120

device		isa
device		pci

# Floppy drives
device		fdc

# ATA and ATAPI devices
device		ata
device		atadisk			# ATA disk drives
device		atapicd			# ATAPI CDROM drives
device		atapifd			# ATAPI floppy drives
options 	ATA_STATIC_ID		#Static device numbering

# SCSI bus
device		scbus		# base SCSI code
device		da		# SCSI direct access devices (aka disks)
device		cd		#
device		pass		# CAM passthrough driver
device		atapicam	# emulate ATAPI devices as SCSI ditto via CAM

# atkbdc0 controls both the keyboard and the PS/2 mouse
device		atkbdc		# AT keyboard controller
device		atkbd		# AT keyboard
device		psm		# PS/2 mouse

device		vga		# VGA video card driver

device		splash		# Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device		sc
options 	SC_HISTORY_SIZE=512	# number of history buffer lines
options		SC_PIXEL_MODE		# add support for the raster text mode

device		agp		# support several AGP chipsets

# Floating point support - do not disable.
device		npx

# Serial (COM) ports
device		sio		# 8250, 16[45]50 based serial ports

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device		miibus		# MII bus support
device		fxp		# Intel EtherExpress PRO/100B (82557, 82558)

# Pseudo devices - the number indicates how many units to allocate.
device		random		# Entropy device
device		loop		# Network loopback
device		ether		# Ethernet support
device		pty		# Pseudo-ttys (telnet etc)
device		md		# Memory "disks"

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
device		bpf		# Berkeley packet filter

# new 5.3
device          mem             # Memory and kernel memory devices
device          io              # I/O device

# USB support
#options 	USB_DEBUG
device		uhci		# UHCI PCI->USB interface
device		ohci		# OHCI PCI->USB interface
device		ehci		# OHCI PCI->USB interface
device		usb		# USB Bus (required)
#device		udbp		# USB Double Bulk Pipe devices
device		ugen		# Generic
device		uhid		# "Human Interface Devices"
device		ulpt		# Printer
device		umass		# Disks/Mass storage - Requires scbus and da
device		urio		# Diamond Rio 500 MP3 player
device		uscanner	# Scanners
device		ucom		# USB serial support


Nov 15 00:19:52 titan kernel: Copyright (c) 1992-2004 The FreeBSD Project.
Nov 15 00:19:52 titan kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 15 00:19:52 titan kernel: The Regents of the University of California. All rights reserved.
Nov 15 00:19:52 titan kernel: FreeBSD 5.3-STABLE #0: Wed Nov 10 10:37:30 CET 2004
Nov 15 00:19:52 titan kernel: root_at_titan.klemm.apsfilter.org:/usr/src/sys/i386/compile/TITAN
Nov 15 00:19:52 titan kernel: WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
Nov 15 00:19:52 titan kernel: WARNING: MPSAFE network stack disabled, expect reduced performance.
Nov 15 00:19:52 titan kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Nov 15 00:19:52 titan kernel: CPU: Intel Pentium III (997.46-MHz 686-class CPU)
Nov 15 00:19:52 titan kernel: Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
Nov 15 00:19:52 titan kernel: Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
Nov 15 00:19:52 titan kernel: real memory  = 536854528 (511 MB)
Nov 15 00:19:52 titan kernel: avail memory = 519884800 (495 MB)
Nov 15 00:19:52 titan kernel: npx0: [FAST]
Nov 15 00:19:52 titan kernel: npx0: <math processor> on motherboard
Nov 15 00:19:52 titan kernel: npx0: INT 16 interface
Nov 15 00:19:52 titan kernel: acpi0: <ASUS MED_2001> on motherboard
Nov 15 00:19:52 titan kernel: acpi0: Power Button (fixed)
Nov 15 00:19:52 titan kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Nov 15 00:19:52 titan kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
Nov 15 00:19:52 titan kernel: cpu0: <ACPI CPU (3 Cx states)> on acpi0
Nov 15 00:19:52 titan kernel: acpi_button0: <Power Button> on acpi0
Nov 15 00:19:52 titan kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Nov 15 00:19:52 titan kernel: pci0: <ACPI PCI bus> on pcib0
Nov 15 00:19:52 titan kernel: agp0: <VIA 82C691 (Apollo Pro) host to PCI bridge> mem 0xf0000000-0xf7ffffff at device 0.0 on pci0
Nov 15 00:19:52 titan kernel: pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
Nov 15 00:19:52 titan kernel: pcib1: could not get PCI interrupt routing table for \_SB_.PCI0.AGP_ - AE_NOT_FOUND
Nov 15 00:19:52 titan kernel: pci1: <ACPI PCI bus> on pcib1
Nov 15 00:19:52 titan kernel: pcib0: no PRT entry for 0.1.INTA
Nov 15 00:19:52 titan kernel: pci1: <display, VGA> at device 0.0 (no driver attached)
Nov 15 00:19:52 titan kernel: pci1: <display> at device 0.1 (no driver attached)
Nov 15 00:19:52 titan kernel: isab0: <PCI-ISA bridge> at device 4.0 on pci0
Nov 15 00:19:52 titan kernel: isa0: <ISA bus> on isab0
Nov 15 00:19:52 titan kernel: atapci0: <VIA 82C686A UDMA66 controller> port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0
Nov 15 00:19:52 titan kernel: ata0: channel #0 on atapci0
Nov 15 00:19:52 titan kernel: ata1: channel #1 on atapci0
Nov 15 00:19:52 titan kernel: uhci0: <VIA 83C572 USB controller> port 0xb400-0xb41f irq 11 at device 4.2 on pci0
Nov 15 00:19:52 titan kernel: uhci0: [GIANT-LOCKED]
Nov 15 00:19:52 titan kernel: usb0: <VIA 83C572 USB controller> on uhci0
Nov 15 00:19:52 titan kernel: usb0: USB revision 1.0
Nov 15 00:19:52 titan kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
Nov 15 00:19:52 titan kernel: uhub0: 2 ports with 2 removable, self powered
Nov 15 00:19:52 titan kernel: ulpt0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2, iclass 255/204
Nov 15 00:19:52 titan kernel: ulpt0: using bi-directional mode
Nov 15 00:19:52 titan kernel: umass0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2
Nov 15 00:19:52 titan kernel: ugen0: Syncrosoft Protected Executer, rev 1.10/1.01, addr 3
Nov 15 00:19:52 titan kernel: uhci1: <VIA 83C572 USB controller> port 0xb000-0xb01f irq 11 at device 4.3 on pci0
Nov 15 00:19:52 titan kernel: uhci1: [GIANT-LOCKED]
Nov 15 00:19:52 titan kernel: usb1: <VIA 83C572 USB controller> on uhci1
Nov 15 00:19:52 titan kernel: usb1: USB revision 1.0
Nov 15 00:19:52 titan kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
Nov 15 00:19:52 titan kernel: uhub1: 2 ports with 2 removable, self powered
Nov 15 00:19:52 titan kernel: fxp0: <Intel 82559 Pro/100 Ethernet> port 0xa800-0xa83f mem 0xd5800000-0xd58fffff,0xd6000000-0xd6000fff irq 10 at device 9.0 on pci0
Nov 15 00:19:52 titan kernel: miibus0: <MII bus> on fxp0
Nov 15 00:19:52 titan kernel: inphy0: <i82555 10/100 media interface> on miibus0
Nov 15 00:19:52 titan kernel: inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Nov 15 00:19:52 titan kernel: fxp0: Ethernet address: 00:d0:b7:ba:c1:c2
Nov 15 00:19:52 titan kernel: fxp0: [GIANT-LOCKED]
Nov 15 00:19:52 titan kernel: pci0: <multimedia, audio> at device 10.0 (no driver attached)
Nov 15 00:19:52 titan kernel: fdc0: <floppy drive controller> port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
Nov 15 00:19:52 titan kernel: fdc0: [FAST]
Nov 15 00:19:52 titan kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
Nov 15 00:19:52 titan kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Nov 15 00:19:52 titan kernel: sio0: type 16550A
Nov 15 00:19:52 titan kernel: atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
Nov 15 00:19:52 titan kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Nov 15 00:19:52 titan kernel: kbd0 at atkbd0
Nov 15 00:19:52 titan kernel: atkbd0: [GIANT-LOCKED]
Nov 15 00:19:52 titan kernel: psm0: <PS/2 Mouse> irq 12 on atkbdc0
Nov 15 00:19:52 titan kernel: psm0: [GIANT-LOCKED]
Nov 15 00:19:52 titan kernel: psm0: model IntelliMouse Explorer, device ID 4
Nov 15 00:19:52 titan kernel: orm0: <ISA Option ROMs> at iomem 0xd0000-0xd17ff,0xc0000-0xccfff on isa0
Nov 15 00:19:52 titan kernel: sc0: <System console> at flags 0x100 on isa0
Nov 15 00:19:52 titan kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Nov 15 00:19:52 titan kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 15 00:19:52 titan kernel: sio1: configured irq 3 not in bitmap of probed irqs 0
Nov 15 00:19:52 titan kernel: sio1: port may not be enabled
Nov 15 00:19:52 titan kernel: Timecounter "TSC" frequency 997461263 Hz quality 800
Nov 15 00:19:52 titan kernel: Timecounters tick every 10.000 msec
Nov 15 00:19:52 titan kernel: IPsec: Initialized Security Association Processing.
Nov 15 00:19:52 titan kernel: ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging unlimited
Nov 15 00:19:52 titan kernel: acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0%
Nov 15 00:19:52 titan kernel: ad0: 176700MB <IC35L180AVV207-1/V26OA63A> [359010/16/63] at ata0-master UDMA66
Nov 15 00:19:52 titan kernel: acd0: DVDROM <LITEON DVD-ROM LTD122/IHNC> at ata0-slave UDMA33
Nov 15 00:19:52 titan kernel: ad2: 176700MB <IC35L180AVV207-1/V26OA63A> [359010/16/63] at ata1-master UDMA66
Nov 15 00:19:52 titan kernel: acd1: DVDR <HL-DT-ST DVDRAM GSA-4082B/A201> at ata1-slave UDMA33
Nov 15 00:19:52 titan kernel: cd0 at ata0 bus 0 target 1 lun 0
Nov 15 00:19:52 titan kernel: cd0: <LITEON DVD-ROM LTD122 IHNC> Removable CD-ROM SCSI-0 device 
Nov 15 00:19:52 titan kernel: cd0: 33.000MB/s transfers
Nov 15 00:19:52 titan kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present
Nov 15 00:19:52 titan kernel: cd1 at ata1 bus 0 target 1 lun 0
Nov 15 00:19:52 titan kernel: cd1: <HL-DT-ST DVDRAM GSA-4082B A201> Removable CD-ROM SCSI-0 device 
Nov 15 00:19:52 titan kernel: cd1: 33.000MB/s transfers
Nov 15 00:19:52 titan kernel: cd1: Attempt to query device size failed: NOT READY, Medium not present
Nov 15 00:19:52 titan kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Nov 15 00:19:52 titan kernel: da0: <HP psc 2210 1.00> Removable Direct Access SCSI-2 device 
Nov 15 00:19:52 titan kernel: da0: 1.000MB/s transfers
Nov 15 00:19:52 titan kernel: da0: Attempt to query device size failed: NOT READY, Medium not present
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Medium not present
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error
Nov 15 00:19:52 titan kernel: Opened disk da0 -> 6
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Medium not present
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error
Nov 15 00:19:52 titan kernel: Opened disk da0 -> 6
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Medium not present
Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error
Nov 15 00:19:52 titan kernel: Opened disk da0 -> 6
Nov 15 00:19:52 titan kernel: Mounting root from ufs:/dev/ad2s1a
Nov 15 00:19:52 titan savecore: no dumps found
Nov 15 00:19:53 titan named[330]: starting BIND 9.3.0 -u bind -t /var/named
Nov 15 00:19:53 titan named[330]: command channel listening on 127.0.0.1#953
Nov 15 00:20:02 titan rpcbind: cannot create socket for udp6
Nov 15 00:20:03 titan lpd[491]: lpd startup: logging=0
Nov 15 00:20:03 titan ntpd[503]: ntpd 4.2.0-a Wed Nov 10 11:31:07 CET 2004 (1)
Nov 15 00:20:03 titan ntpd[503]: no IPv6 interfaces found
Nov 15 00:20:10 titan kernel: WARNING: driver "vmmon" used unreserved major device number 200
Nov 15 00:20:10 titan kernel: vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 (3.2.x mvm) $
Nov 15 00:20:10 titan kernel: vmmon: Module vmmon: initialized
Nov 15 00:22:20 titan su: andreas to root on /dev/ttyp0
Nov 15 00:23:16 titan ntpd[503]: kernel time sync disabled 2041
Nov 15 00:24:19 titan ntpd[503]: kernel time sync enabled 2001
Nov 15 00:40:13 titan sm-mta[3643]: iAENUQAK003576: Truncated MIME Content-Type header due to field size (length = 129) (possible attack)
Nov 15 00:47:05 titan postgres[5415]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:47:05 titan postgres[5415]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:47:05 titan postgres[5415]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:47:05 titan postgres[5415]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:47:05 titan postgres[5415]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:47:05 titan postgres[5415]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:47:05 titan postgres[5415]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:25 titan postgres[5625]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:25 titan postgres[5625]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:25 titan postgres[5625]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:25 titan postgres[5625]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:25 titan postgres[5625]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:25 titan postgres[5625]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:25 titan postgres[5618]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:26 titan postgres[5625]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:26 titan postgres[5618]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:26 titan postgres[5618]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:26 titan postgres[5618]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:26 titan postgres[5625]: [9-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:26 titan postgres[5625]: [10-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:26 titan postgres[5618]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5625]: [11-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [9-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5625]: [12-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [10-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [11-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [12-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [13-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5618]: [14-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:27 titan postgres[5625]: [13-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5618]: [15-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5625]: [14-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5625]: [15-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5625]: [16-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5618]: [16-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5625]: [17-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5625]: [18-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5618]: [17-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5618]: [18-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5618]: [19-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:28 titan postgres[5625]: [19-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5618]: [20-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5618]: [21-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [20-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [21-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [22-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5618]: [22-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [23-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [24-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [25-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [26-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5618]: [23-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [27-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:29 titan postgres[5625]: [28-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [29-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5618]: [24-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [30-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5618]: [25-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [31-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [32-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5618]: [26-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5618]: [27-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5618]: [28-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [33-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5618]: [29-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [34-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [35-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5618]: [30-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:30 titan postgres[5625]: [36-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5618]: [31-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5618]: [32-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5625]: [37-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5625]: [38-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5625]: [39-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5618]: [33-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5618]: [34-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5625]: [40-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5625]: [41-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 00:50:31 titan postgres[5618]: [35-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:12:00 titan postgres[6697]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:15:09 titan postgres[6633]: [2-1] ERROR:  deadlock detected
Nov 15 01:15:09 titan postgres[6633]: [2-2] DETAIL:  Process 6633 waits for ShareLock on transaction 1158996; blocked by process 5748.
Nov 15 01:15:09 titan postgres[6633]: [2-3] 	Process 5748 waits for ShareLock on transaction 1163189; blocked by process 6633.
Nov 15 01:48:32 titan postgres[7490]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:48:45 titan postgres[7490]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:48:53 titan postgres[7490]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:49:15 titan postgres[7490]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:49:15 titan postgres[7490]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:49:53 titan postgres[7490]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:50:15 titan postgres[7490]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 01:50:36 titan postgres[7490]: [9-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:05:10 titan postgres[8020]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:05:15 titan postgres[8020]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:05:26 titan postgres[8020]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:05:35 titan postgres[8020]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:05:47 titan postgres[8020]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:05:56 titan postgres[8020]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:06:05 titan postgres[8020]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:06:07 titan postgres[8020]: [9-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:06:40 titan postgres[8020]: [10-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:06:47 titan postgres[8020]: [11-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:06:47 titan postgres[8020]: [12-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:07:37 titan postgres[8020]: [13-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:35:21 titan postgres[9339]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 02:35:21 titan postgres[9339]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 08:54:18 titan syslogd: kernel boot file is /boot/kernel/kernel
Nov 15 08:54:18 titan kernel: Copyright (c) 1992-2004 The FreeBSD Project.
Nov 15 08:54:18 titan kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 15 08:54:18 titan kernel: The Regents of the University of California. All rights reserved.
Nov 15 08:54:18 titan kernel: FreeBSD 5.3-STABLE #0: Wed Nov 10 10:37:30 CET 2004
Nov 15 08:54:18 titan kernel: root_at_titan.klemm.apsfilter.org:/usr/src/sys/i386/compile/TITAN
Nov 15 08:54:18 titan kernel: WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
Nov 15 08:54:18 titan kernel: WARNING: MPSAFE network stack disabled, expect reduced performance.
Nov 15 08:54:18 titan kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Nov 15 08:54:18 titan kernel: CPU: Intel Pentium III (997.46-MHz 686-class CPU)
Nov 15 08:54:18 titan kernel: Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
Nov 15 08:54:18 titan kernel: Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
Nov 15 08:54:18 titan kernel: real memory  = 536854528 (511 MB)
Nov 15 08:54:18 titan kernel: avail memory = 519884800 (495 MB)
Nov 15 08:54:18 titan kernel: npx0: [FAST]
Nov 15 08:54:18 titan kernel: npx0: <math processor> on motherboard
Nov 15 08:54:18 titan kernel: npx0: INT 16 interface
Nov 15 08:54:18 titan kernel: acpi0: <ASUS MED_2001> on motherboard
Nov 15 08:54:18 titan kernel: acpi0: Power Button (fixed)
Nov 15 08:54:18 titan kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Nov 15 08:54:18 titan kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
Nov 15 08:54:18 titan kernel: cpu0: <ACPI CPU (3 Cx states)> on acpi0
Nov 15 08:54:18 titan kernel: acpi_button0: <Power Button> on acpi0
Nov 15 08:54:18 titan kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Nov 15 08:54:18 titan kernel: pci0: <ACPI PCI bus> on pcib0
Nov 15 08:54:18 titan kernel: agp0: <VIA 82C691 (Apollo Pro) host to PCI bridge> mem 0xf0000000-0xf7ffffff at device 0.0 on pci0
Nov 15 08:54:18 titan kernel: pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
Nov 15 08:54:18 titan kernel: pcib1: could not get PCI interrupt routing table for \_SB_.PCI0.AGP_ - AE_NOT_FOUND
Nov 15 08:54:18 titan kernel: pci1: <ACPI PCI bus> on pcib1
Nov 15 08:54:18 titan kernel: pcib0: no PRT entry for 0.1.INTA
Nov 15 08:54:18 titan kernel: pci1: <display, VGA> at device 0.0 (no driver attached)
Nov 15 08:54:18 titan kernel: pci1: <display> at device 0.1 (no driver attached)
Nov 15 08:54:18 titan kernel: isab0: <PCI-ISA bridge> at device 4.0 on pci0
Nov 15 08:54:18 titan kernel: isa0: <ISA bus> on isab0
Nov 15 08:54:18 titan kernel: atapci0: <VIA 82C686A UDMA66 controller> port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0
Nov 15 08:54:18 titan kernel: ata0: channel #0 on atapci0
Nov 15 08:54:18 titan kernel: ata1: channel #1 on atapci0
Nov 15 08:54:18 titan kernel: uhci0: <VIA 83C572 USB controller> port 0xb400-0xb41f irq 11 at device 4.2 on pci0
Nov 15 08:54:18 titan kernel: uhci0: [GIANT-LOCKED]
Nov 15 08:54:18 titan kernel: usb0: <VIA 83C572 USB controller> on uhci0
Nov 15 08:54:18 titan kernel: usb0: USB revision 1.0
Nov 15 08:54:18 titan kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
Nov 15 08:54:18 titan kernel: uhub0: 2 ports with 2 removable, self powered
Nov 15 08:54:18 titan kernel: ulpt0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2, iclass 255/204
Nov 15 08:54:18 titan kernel: ulpt0: using bi-directional mode
Nov 15 08:54:18 titan kernel: umass0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2
Nov 15 08:54:18 titan kernel: ugen0: Syncrosoft Protected Executer, rev 1.10/1.01, addr 3
Nov 15 08:54:18 titan kernel: uhci1: <VIA 83C572 USB controller> port 0xb000-0xb01f irq 11 at device 4.3 on pci0
Nov 15 08:54:18 titan kernel: uhci1: [GIANT-LOCKED]
Nov 15 08:54:18 titan kernel: usb1: <VIA 83C572 USB controller> on uhci1
Nov 15 08:54:18 titan kernel: usb1: USB revision 1.0
Nov 15 08:54:18 titan kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
Nov 15 08:54:18 titan kernel: uhub1: 2 ports with 2 removable, self powered
Nov 15 08:54:18 titan kernel: fxp0: <Intel 82559 Pro/100 Ethernet> port 0xa800-0xa83f mem 0xd5800000-0xd58fffff,0xd6000000-0xd6000fff irq 10 at device 9.0 on pci0
Nov 15 08:54:18 titan kernel: miibus0: <MII bus> on fxp0
Nov 15 08:54:18 titan kernel: inphy0: <i82555 10/100 media interface> on miibus0
Nov 15 08:54:18 titan kernel: inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Nov 15 08:54:18 titan kernel: fxp0: Ethernet address: 00:d0:b7:ba:c1:c2
Nov 15 08:54:18 titan kernel: fxp0: [GIANT-LOCKED]
Nov 15 08:54:18 titan kernel: pci0: <multimedia, audio> at device 10.0 (no driver attached)
Nov 15 08:54:18 titan kernel: fdc0: <floppy drive controller> port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
Nov 15 08:54:18 titan kernel: fdc0: [FAST]
Nov 15 08:54:18 titan kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
Nov 15 08:54:18 titan kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Nov 15 08:54:18 titan kernel: sio0: type 16550A
Nov 15 08:54:18 titan kernel: atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
Nov 15 08:54:18 titan kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Nov 15 08:54:18 titan kernel: kbd0 at atkbd0
Nov 15 08:54:18 titan kernel: atkbd0: [GIANT-LOCKED]
Nov 15 08:54:18 titan kernel: psm0: <PS/2 Mouse> irq 12 on atkbdc0
Nov 15 08:54:18 titan kernel: psm0: [GIANT-LOCKED]
Nov 15 08:54:18 titan kernel: psm0: model IntelliMouse Explorer, device ID 4
Nov 15 08:54:18 titan kernel: orm0: <ISA Option ROMs> at iomem 0xd0000-0xd17ff,0xc0000-0xccfff on isa0
Nov 15 08:54:18 titan kernel: sc0: <System console> at flags 0x100 on isa0
Nov 15 08:54:18 titan kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Nov 15 08:54:18 titan kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 15 08:54:18 titan kernel: sio1: configured irq 3 not in bitmap of probed irqs 0
Nov 15 08:54:18 titan kernel: sio1: port may not be enabled
Nov 15 08:54:18 titan kernel: Timecounter "TSC" frequency 997461023 Hz quality 800
Nov 15 08:54:18 titan kernel: Timecounters tick every 10.000 msec
Nov 15 08:54:18 titan kernel: IPsec: Initialized Security Association Processing.
Nov 15 08:54:18 titan kernel: ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging unlimited
Nov 15 08:54:18 titan kernel: acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0%
Nov 15 08:54:18 titan kernel: ad0: 176700MB <IC35L180AVV207-1/V26OA63A> [359010/16/63] at ata0-master UDMA66
Nov 15 08:54:18 titan kernel: acd0: DVDROM <LITEON DVD-ROM LTD122/IHNC> at ata0-slave UDMA33
Nov 15 08:54:18 titan kernel: ad2: 176700MB <IC35L180AVV207-1/V26OA63A> [359010/16/63] at ata1-master UDMA66
Nov 15 08:54:18 titan kernel: acd1: DVDR <HL-DT-ST DVDRAM GSA-4082B/A201> at ata1-slave UDMA33
Nov 15 08:54:18 titan kernel: cd0 at ata0 bus 0 target 1 lun 0
Nov 15 08:54:18 titan kernel: cd0: <LITEON DVD-ROM LTD122 IHNC> Removable CD-ROM SCSI-0 device 
Nov 15 08:54:18 titan kernel: cd0: 33.000MB/s transfers
Nov 15 08:54:18 titan kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present
Nov 15 08:54:18 titan kernel: cd1 at ata1 bus 0 target 1 lun 0
Nov 15 08:54:18 titan kernel: cd1: <HL-DT-ST DVDRAM GSA-4082B A201> Removable CD-ROM SCSI-0 device 
Nov 15 08:54:18 titan kernel: cd1: 33.000MB/s transfers
Nov 15 08:54:18 titan kernel: cd1: Attempt to query device size failed: NOT READY, Medium not present
Nov 15 08:54:18 titan kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Nov 15 08:54:18 titan kernel: da0: <HP psc 2210 1.00> Removable Direct Access SCSI-2 device 
Nov 15 08:54:18 titan kernel: da0: 1.000MB/s transfers
Nov 15 08:54:18 titan kernel: da0: Attempt to query device size failed: NOT READY, Medium not present
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Medium not present
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error
Nov 15 08:54:18 titan kernel: Opened disk da0 -> 6
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Medium not present
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error
Nov 15 08:54:18 titan kernel: Opened disk da0 -> 6
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Medium not present
Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error
Nov 15 08:54:18 titan kernel: Opened disk da0 -> 6
Nov 15 08:54:18 titan kernel: Mounting root from ufs:/dev/ad2s1a
Nov 15 08:54:18 titan kernel: WARNING: / was not properly dismounted
Nov 15 08:54:18 titan kernel: WARNING: /home was not properly dismounted
Nov 15 08:54:18 titan kernel: /home: mount pending error: blocks 8 files 1
Nov 15 08:54:18 titan kernel: /home: superblock summary recomputed
Nov 15 08:54:18 titan kernel: WARNING: /usr was not properly dismounted
Nov 15 08:54:18 titan kernel: /usr: mount pending error: blocks 100 files 48
Nov 15 08:54:18 titan kernel: /usr: superblock summary recomputed
Nov 15 08:54:18 titan kernel: WARNING: /var was not properly dismounted
Nov 15 08:54:18 titan kernel: /var: superblock summary recomputed
Nov 15 08:54:18 titan savecore: no dumps found
Nov 15 08:54:19 titan named[336]: starting BIND 9.3.0 -u bind -t /var/named
Nov 15 08:54:19 titan named[336]: command channel listening on 127.0.0.1#953
Nov 15 08:54:28 titan rpcbind: cannot create socket for udp6
Nov 15 08:54:29 titan lpd[497]: lpd startup: logging=0
Nov 15 08:54:29 titan ntpd[509]: ntpd 4.2.0-a Wed Nov 10 11:31:07 CET 2004 (1)
Nov 15 08:54:29 titan ntpd[509]: no IPv6 interfaces found
Nov 15 08:54:45 titan kernel: WARNING: driver "vmmon" used unreserved major device number 200
Nov 15 08:54:45 titan kernel: vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 (3.2.x mvm) $
Nov 15 08:54:45 titan kernel: vmmon: Module vmmon: initialized
Nov 15 08:54:46 titan postgres[1567]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:46 titan postgres[1581]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:46 titan postgres[1595]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:47 titan postgres[1613]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:47 titan postgres[1618]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:47 titan postgres[1623]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:47 titan postgres[1636]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:47 titan postgres[1650]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:47 titan postgres[1664]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:47 titan postgres[1680]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:48 titan postgres[1694]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:48 titan postgres[1699]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:48 titan postgres[1715]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:48 titan postgres[1716]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:48 titan postgres[1733]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:48 titan postgres[1749]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1763]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1768]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1773]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1789]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1792]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1807]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1821]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:49 titan postgres[1836]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:50 titan postgres[1851]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:50 titan postgres[1865]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:50 titan postgres[1874]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:50 titan postgres[1883]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:50 titan postgres[1898]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:50 titan postgres[1913]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:51 titan postgres[1927]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:51 titan postgres[1941]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:51 titan postgres[1957]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:51 titan postgres[1959]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:51 titan postgres[1975]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:51 titan postgres[1989]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:51 titan postgres[2003]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:52 titan postgres[2018]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:52 titan postgres[2033]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:52 titan postgres[2047]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:52 titan postgres[2056]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:52 titan postgres[2065]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:52 titan postgres[2081]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:53 titan postgres[2095]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:53 titan postgres[2109]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:53 titan postgres[2119]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:53 titan postgres[2125]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:53 titan postgres[2137]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2149]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2163]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2175]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2187]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2200]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2204]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2217]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:54 titan postgres[2229]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:55 titan postgres[2241]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:55 titan postgres[2253]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:55 titan postgres[2267]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:55 titan postgres[2279]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:55 titan postgres[2290]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:55 titan postgres[2295]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:55 titan postgres[2308]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:56 titan postgres[2321]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:56 titan postgres[2333]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:56 titan postgres[2345]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:56 titan postgres[2359]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:56 titan postgres[2370]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:56 titan postgres[2375]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:57 titan postgres[2388]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:57 titan postgres[2403]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:57 titan postgres[2417]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:57 titan postgres[2431]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:57 titan postgres[2443]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:57 titan postgres[2450]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:58 titan postgres[2465]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:58 titan postgres[2479]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:58 titan postgres[2493]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:58 titan postgres[2507]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:58 titan postgres[2523]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:58 titan postgres[2528]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:59 titan postgres[2541]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:59 titan postgres[2555]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:59 titan postgres[2569]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:59 titan postgres[2584]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:59 titan postgres[2599]: [2-1] FATAL:  the database system is starting up
Nov 15 08:54:59 titan postgres[2613]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:00 titan postgres[2627]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:00 titan postgres[2631]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:00 titan postgres[2669]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:00 titan postgres[2670]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:00 titan postgres[2705]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:00 titan postgres[2732]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:00 titan postgres[2736]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:01 titan postgres[2762]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:01 titan postgres[2767]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:01 titan postgres[2787]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:01 titan postgres[2792]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:01 titan postgres[2816]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:01 titan postgres[2817]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:01 titan postgres[2833]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:02 titan postgres[2849]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:02 titan postgres[2864]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:02 titan postgres[2878]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:02 titan postgres[2890]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:02 titan postgres[2899]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:02 titan postgres[2914]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:02 titan postgres[2928]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:03 titan postgres[2945]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:03 titan postgres[2960]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:03 titan postgres[2974]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:03 titan postgres[2986]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:03 titan postgres[2995]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:03 titan postgres[3010]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:04 titan postgres[3024]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:04 titan postgres[3038]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:04 titan postgres[3054]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:04 titan postgres[3071]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:04 titan postgres[3072]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:04 titan postgres[3088]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:05 titan postgres[3102]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:05 titan postgres[3118]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:05 titan postgres[3134]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:05 titan postgres[3148]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:05 titan postgres[3162]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:05 titan postgres[3176]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:05 titan postgres[3180]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:06 titan postgres[3196]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:06 titan postgres[3212]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:06 titan postgres[3226]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:06 titan postgres[3240]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:06 titan postgres[3255]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:06 titan postgres[3262]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:07 titan postgres[3276]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:07 titan postgres[3290]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:07 titan postgres[3305]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:07 titan postgres[3315]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:08 titan postgres[3326]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:08 titan postgres[3340]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:08 titan postgres[3358]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:08 titan postgres[3372]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:08 titan postgres[3386]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:09 titan postgres[3393]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:09 titan postgres[3408]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:09 titan postgres[3422]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:09 titan postgres[3436]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:09 titan postgres[3452]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:09 titan postgres[3475]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3493]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3507]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3508]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3524]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3529]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3556]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3561]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:10 titan postgres[3579]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:11 titan postgres[3591]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:11 titan postgres[3613]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:11 titan postgres[3621]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:11 titan postgres[3635]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:11 titan postgres[3649]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:11 titan postgres[3653]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:12 titan postgres[3679]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:12 titan postgres[3683]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:12 titan postgres[3707]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:12 titan postgres[3717]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:12 titan postgres[3727]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:12 titan postgres[3732]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:12 titan postgres[3751]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:13 titan postgres[3763]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:13 titan postgres[3780]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:13 titan postgres[3791]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:13 titan postgres[3815]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:13 titan postgres[3819]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:13 titan postgres[3834]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:13 titan postgres[3837]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:14 titan postgres[3861]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:14 titan postgres[3863]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:14 titan postgres[3886]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:14 titan postgres[3900]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:14 titan postgres[3905]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:14 titan postgres[3918]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:14 titan postgres[3932]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:15 titan postgres[3946]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:15 titan postgres[3960]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:15 titan postgres[3974]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:15 titan postgres[3979]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:15 titan postgres[3992]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:15 titan postgres[4006]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:16 titan postgres[4020]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:16 titan postgres[4034]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:16 titan postgres[4048]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:16 titan postgres[4062]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:16 titan postgres[4077]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:16 titan postgres[4080]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:16 titan postgres[4094]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:17 titan postgres[4108]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:17 titan postgres[4122]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:17 titan postgres[4137]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:17 titan postgres[4151]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:17 titan postgres[4165]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:17 titan postgres[4176]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:17 titan postgres[4183]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:18 titan postgres[4197]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:18 titan postgres[4211]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:18 titan postgres[4225]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:18 titan postgres[4240]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:18 titan postgres[4255]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:18 titan postgres[4258]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:19 titan postgres[4272]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:19 titan postgres[4286]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:19 titan postgres[4300]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:19 titan postgres[4314]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:19 titan postgres[4328]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:19 titan postgres[4342]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:19 titan postgres[4345]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:20 titan postgres[4360]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:20 titan postgres[4374]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:20 titan postgres[4388]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:20 titan postgres[4402]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:20 titan postgres[4416]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:21 titan postgres[4427]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:21 titan postgres[4434]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:21 titan postgres[4448]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:21 titan postgres[4462]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:21 titan postgres[4476]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:21 titan postgres[4490]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:22 titan postgres[4504]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:22 titan postgres[4507]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:22 titan postgres[4522]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:22 titan postgres[4535]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:22 titan postgres[4553]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:22 titan postgres[4557]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:22 titan postgres[4581]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:23 titan postgres[4585]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:23 titan postgres[4602]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:23 titan postgres[4605]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:23 titan postgres[4626]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:23 titan postgres[4629]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:23 titan postgres[4645]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:23 titan postgres[4658]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:24 titan postgres[4680]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:24 titan postgres[4694]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:24 titan postgres[4709]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:24 titan postgres[4710]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:24 titan postgres[4726]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:25 titan postgres[4740]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:25 titan postgres[4754]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:25 titan postgres[4768]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:25 titan postgres[4780]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:25 titan postgres[4786]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:25 titan postgres[4800]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:26 titan postgres[4814]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:26 titan postgres[4828]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:26 titan postgres[4842]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:26 titan postgres[4856]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:26 titan postgres[4867]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:26 titan postgres[4874]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:26 titan postgres[4888]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:27 titan postgres[4902]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:27 titan postgres[4916]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:27 titan postgres[4931]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:27 titan postgres[4934]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:27 titan postgres[4948]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:27 titan postgres[4962]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:28 titan postgres[4976]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:28 titan postgres[4990]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:28 titan postgres[5004]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:28 titan postgres[5018]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:28 titan postgres[5026]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:28 titan postgres[5036]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:29 titan postgres[5050]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:29 titan postgres[5064]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:29 titan postgres[5078]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:29 titan postgres[5093]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:29 titan postgres[5094]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5110]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5124]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5138]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5147]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5163]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5178]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5184]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:30 titan postgres[5196]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:31 titan postgres[5197]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:31 titan postgres[5217]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:31 titan postgres[5227]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:31 titan postgres[5247]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:31 titan postgres[5253]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:31 titan postgres[5274]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5279]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5290]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5306]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5307]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5321]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5339]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5351]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:32 titan postgres[5365]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:33 titan postgres[5373]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:33 titan postgres[5391]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:33 titan postgres[5401]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:33 titan postgres[5405]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:33 titan postgres[5428]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:33 titan postgres[5433]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5457]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5458]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5475]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5478]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5492]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5506]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5520]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:34 titan postgres[5534]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:35 titan postgres[5548]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:35 titan postgres[5553]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:35 titan postgres[5566]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:36 titan postgres[5580]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:36 titan postgres[5594]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:36 titan postgres[5609]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:36 titan postgres[5610]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:36 titan postgres[5626]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:36 titan postgres[5640]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:36 titan postgres[5654]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5668]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5682]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5696]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5707]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5714]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5728]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5742]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:37 titan postgres[5756]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:38 titan postgres[5770]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:39 titan postgres[5774]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:39 titan postgres[5779]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:39 titan postgres[5792]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:39 titan postgres[5806]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:39 titan postgres[5820]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:40 titan postgres[5834]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:40 titan postgres[5848]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:41 titan postgres[5861]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:41 titan postgres[5867]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:42 titan postgres[5872]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:42 titan postgres[5893]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:43 titan postgres[5899]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:43 titan postgres[5902]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:44 titan postgres[5906]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[5943]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[5944]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[5967]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[5969]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[5968]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[5989]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[6011]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[6017]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:45 titan postgres[6023]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6052]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6055]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6069]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6092]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6105]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6106]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6109]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6133]: [2-1] FATAL:  the database system is starting up
Nov 15 08:55:46 titan postgres[6144]: [2-1] FATAL:  the database system is starting up
Nov 15 08:57:43 titan ntpd[509]: kernel time sync disabled 2041
Nov 15 08:58:49 titan ntpd[509]: kernel time sync enabled 2001
Nov 15 09:10:14 titan fsck: /dev/ad2s1f: INCORRECT BLOCK COUNT I=2001921 (20832 should be 20864) (CORRECTED)
Nov 15 09:10:14 titan fsck: /dev/ad2s1f: UNREF FILE I=2001921  OWNER=root MODE=100440
Nov 15 09:10:14 titan fsck: /dev/ad2s1f: SIZE=17179869944 MTIME=Nov 15 04:57 2004  (CLEARED)
Nov 15 09:10:14 titan fsck: /dev/ad2s1f: Reclaimed: 0 directories, 1 files, 0 fragments
Nov 15 09:10:14 titan fsck: /dev/ad2s1f: 108049 files, 5416049 used, 2706118 free (31662 frags, 334307 blocks, 0.4% fragmentation)
Nov 15 09:11:49 titan postgres[7761]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [9-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [10-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [11-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:50 titan postgres[7761]: [12-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [13-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [14-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [15-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [16-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [17-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [18-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [19-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [20-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [21-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:11:51 titan postgres[7761]: [22-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:12:47 titan postgres[7826]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:12:47 titan postgres[7826]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:12:47 titan postgres[7826]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:12:47 titan postgres[7826]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:12:47 titan postgres[7826]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:07 titan postgres[8060]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:07 titan postgres[8060]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:07 titan postgres[8060]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [9-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [10-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [11-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [12-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [13-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [14-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [15-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:08 titan postgres[8060]: [16-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [17-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [18-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [19-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [20-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [21-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [22-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [23-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [24-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [25-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [26-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [27-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [28-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [29-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [30-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [31-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:09 titan postgres[8060]: [32-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:10 titan postgres[8060]: [33-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:16:10 titan postgres[8060]: [34-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [2-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [3-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [4-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [5-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [6-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [7-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [8-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [9-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [10-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:24 titan postgres[8187]: [11-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [12-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [13-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [14-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [15-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [16-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [17-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [18-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:25 titan postgres[8187]: [19-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:26 titan postgres[8187]: [20-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:26 titan postgres[8187]: [21-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:26 titan postgres[8187]: [22-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:26 titan postgres[8187]: [23-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:26 titan postgres[8187]: [24-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:18:26 titan postgres[8187]: [25-1] ERROR:  duplicate key violates unique constraint "dspam_token_data_token_key"
Nov 15 09:20:03 titan sendmail[8287]: iAF8F9Uu007983: Truncated MIME Content-Type header due to field size (length = 144) (possible attack)
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26387  OWNER=root MODE=100644
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=168 MTIME=Nov 12 04:42 2004  (CLEARED)
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26392  OWNER=root MODE=100644
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=169 MTIME=Nov 12 04:42 2004  (CLEARED)
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26393  OWNER=root MODE=100644
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=168 MTIME=Nov 12 04:42 2004  (CLEARED)
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26396  OWNER=root MODE=100644
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=177 MTIME=Nov 12 04:42 2004  (CLEARED)
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=989284  OWNER=root MODE=100644
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=170 MTIME=Nov 12 04:42 2004  (CLEARED)
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=989285  OWNER=root MODE=100644
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=172 MTIME=Nov 12 04:42 2004  (CLEARED)
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: Reclaimed: 11 directories, 22 files, 16 fragments
Nov 15 09:34:02 titan fsck: /dev/ad2s1e: 338362 files, 1393331 used, 2667716 free (69044 frags, 324834 blocks, 1.7% fragmentation)
Nov 15 09:35:58 titan fsck: /dev/ad2s1d: UNREF FILE I=188572  OWNER=root MODE=140666
Nov 15 09:35:58 titan fsck: /dev/ad2s1d: SIZE=0 MTIME=Nov 15 00:19 2004  (CLEARED)
Nov 15 09:35:58 titan fsck: /dev/ad2s1d: Reclaimed: 0 directories, 2 files, 11 fragments
Nov 15 09:35:58 titan fsck: /dev/ad2s1d: 50753 files, 1189501 used, 839519 free (32543 frags, 100872 blocks, 1.6% fragmentation)
Nov 15 10:03:53 titan su: andreas to root on /dev/ttyp0

-- 
Andreas Klemm - Powered by FreeBSD 5.1-CURRENT
Need a magic printfilter today ? -> http://www.apsfilter.org/
Received on Mon Nov 15 2004 - 08:20:32 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:22 UTC