Meteohub log errors

[Haole]

I'm seeing continuous errors in the Meteohub log file.
It's still reporting fine to the various weather networks.
Could the memory stick be in need of replacement?

loggereval (21.11.2011 00:11:54): illegal data record in line 127 while reading from file /data/weather/201111/raw: 201111010020111101051320 uv0 0
loggereval (21.11.2011 00:11:54): illegal data record in line 259 while reading from file /data/weather/201111/raw: 201111010520111101053806 sol0 0 0
loggereval (21.11.2011 00:11:54): illegal data record in line 521 while reading from file /data/weather/201111/raw: 2020111101072942 sol0 0 0
loggereval (21.11.2011 00:11:54): illegal data record in line 653 while reading from file /data/weather/201111/raw: 220111102051328 wind0 217 72 54 0109
loggereval (21.11.2011 00:11:54): illegal data record in line 1121 while reading from file /data/weather/201111/raw: 20111102053020111103051244 wind0 45 22 31 0030
loggereval (21.11.2011 00:11:54): illegal data record in line 1361 while reading from file /data/weather/201111/raw: 201111030521320111103052750 wind0 49 45 40 0013
loggereval (21.11.2011 00:11:54): illegal data record in line 1481 while reading from file /data/weather/201111/raw: 2011110305320111103063404 wind0 38 18 40 0036
loggereval (21.11.2011 00:11:54): illegal data record in line 1846 while reading from file /data/weather/201111/raw: 2011120111106054500 thb0 214 35 0053 10161 -1 10161
loggereval (21.11.2011 00:11:56): illegal data record in line 14241 while reading from file /data/weather/201111/raw: 201111151520111115172223 wind0 207 67 63 0116
loggereval (21.11.2011 00:11:56): illegal data record in line 14474 while reading from file /data/weather/201111/raw: 20120111116061331 wind0 274 40 31 0020
loggereval (21.11.2011 00:11:56): illegal data record in line 22869 while reading from file /data/weather/201111/raw: 2011111612220111117061502 th0 -25 70 -072
loggereval (21.11.2011 00:11:57): illegal data record in line 27978 while reading from file /data/weather/201111/raw: 2011111710221420111118061424 uv0 0
loggereval (21.11.2011 00:11:57): illegal data record in line 32122 while reading from file /data/weather/201111/raw: 20120111118092208 wind0 191 49 49

-051

MeteohubSysInfo.jpg (129.21 KiB) Viewed 7811 times

[YJB]

Hi,

It seems that all the records reported have timestamps that are messed up. Not sure what can cause it, maybe the dmesg log can give some clarity. If you have access to the shell prompt, I would check the system date and time as well.

[Haole]

I'm not up on Linux at all, but I used my SSH app to get in.

root@meteohub:~$ date
Mon Nov 21 08:44:33 CST 2011

Which is correct

Here's the whole log from dmesg:
DMESG:
<5>Linux version 2.6.21.7 (slug@otto) (gcc version 4.1.2) #1 PREEMPT Mon Dec 24 23:12:24 UTC 2007
<4>CPU: XScale-IXP42x Family [690541f1] revision 1 (ARMv5TE), cr=000039ff
<4>Machine: Linksys NSLU2
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 8192
<7> DMA zone: 64 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 8128 pages, LIFO batch:0
<7> Normal zone: 0 pages used for memmap
<4>CPU0: D VIVT undefined 5 cache
<4>CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>Built 1 zonelists. Total pages: 8128
<5>Kernel command line: rtc-x1205.probe=0,0x6f console=ttyS0,115200n8 root=/dev/mtdblock4 rootfstype=jffs2 rw init=/linuxrc noirqdebug
<6>IRQ lockup detection disabled
<4>PID hash table entries: 128 (order: 7, 512 bytes)
<4>Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
<4>Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>Memory: 32MB = 32MB total
<5>Memory: 30292KB available (1912K code, 153K data, 84K init)
<7>Calibrating delay loop... 132.71 BogoMIPS (lpj=663552)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>NET: Registered protocol family 16
<4>IXP4xx: Using 16MiB expansion bus window size
<4>PCI: IXP4xx is host
<4>PCI: IXP4xx Using direct access for memory space
<6>PCI: bus0: Fast back to back transfers disabled
<6>dmabounce: registered device 0000:00:01.0 on pci bus
<6>dmabounce: registered device 0000:00:01.1 on pci bus
<6>dmabounce: registered device 0000:00:01.2 on pci bus
<5>SCSI subsystem initialized
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Time: OSTS clocksource has been installed.
<6>NET: Registered protocol family 2
<4>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<4>TCP established hash table entries: 1024 (order: 1, 8192 bytes)
<4>TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP: Hash tables configured (established 1024 bind 1024)
<6>TCP reno registered
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<6>JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
<6>serial8250.0: ttyS0 at MMIO 0xc8000000 (irq = 15) is a XScale
<6>serial8250.0: ttyS1 at MMIO 0xc8001000 (irq = 13) is a XScale
<4>RAMDISK driver initialized: 4 RAM disks of 10240K size 1024 blocksize
<6>IXP4XX NPE driver Version 0.3.0 initialized
<6>NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
<6>IXP4XX-Flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
<7>IXP4XX-Flash.0: Found an alias at 0x800000 for the chip at 0x0
<4> Intel/Sharp Extended Query Table at 0x0031
<6>Using buffer write method
<5>cfi_cmdset_0001: Erase suspend on write enabled
<7>erase region 0: offset=0x0,size=0x20000,blocks=64
<5>Searching for RedBoot partition table in IXP4XX-Flash.0 at offset 0x7e0000
<5>6 RedBoot partitions found on MTD device IXP4XX-Flash.0
<5>Creating 6 MTD partitions on "IXP4XX-Flash.0":
<5>0x00000000-0x00040000 : "RedBoot"
<6>nslu2 mac: 00:18:39:aa:27:d9
<5>0x00040000-0x00060000 : "SysConf"
<5>0x00060000-0x00080000 : "Loader"
<5>0x00080000-0x00180000 : "Kernel"
<5>0x00180000-0x007e0000 : "Flashdisk"
<5>0x007e0000-0x00800000 : "FIS directory"
<4>npe: searching for firmware...
<6>npe: found at 0x1c010, IXP425/NPE-B func: 00, rev: 2.1, size: 11964, id: 01000201
<6>Image loaded to NPE-B Func:0, Rel: 2:1, Status: 82c00000
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<6>input: ixp4xx beeper as /class/input/input0
<6>i2c /dev entries driver
<6>x1205 0-006f: chip found, driver version 1.0.7
<6>x1205 0-006f: rtc core: registered x1205 as rtc0
<6>Registered led device: ready
<6>Registered led device: status
<6>Registered led device: disk-1
<6>Registered led device: disk-2
<6>TCP cubic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>XScale DSP coprocessor detected.
<6>x1205 0-006f: setting the system clock to 2011-11-18 12:27:45 (1321619265)
<4>VFS: Mounted root (jffs2 filesystem).
<6>Freeing init memory: 84K
<4>PCI: enabling device 0000:00:01.2 (0140 -> 0142)
<6>ehci_hcd 0000:00:01.2: EHCI Host Controller
<6>ehci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
<6>ehci_hcd 0000:00:01.2: irq 26, io mem 0x48002000
<6>ehci_hcd 0000:00:01.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 5 ports detected
<7>ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
<4>PCI: enabling device 0000:00:01.0 (0140 -> 0142)
<6>ohci_hcd 0000:00:01.0: OHCI Host Controller
<6>ohci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
<6>ohci_hcd 0000:00:01.0: irq 28, io mem 0x48000000
<6>usb usb2: configuration #1 chosen from 1 choice
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 3 ports detected
<6>usb 1-2: new high speed USB device using ehci_hcd and address 2
<4>PCI: enabling device 0000:00:01.1 (0140 -> 0142)
<6>ohci_hcd 0000:00:01.1: OHCI Host Controller
<6>ohci_hcd 0000:00:01.1: new USB bus registered, assigned bus number 3
<6>ohci_hcd 0000:00:01.1: irq 27, io mem 0x48001000
<6>usb usb3: configuration #1 chosen from 1 choice
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 2 ports detected
<6>usb 1-2: configuration #1 chosen from 1 choice
<6>scsi0 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 2
<7>usb-storage: waiting for device to settle before scanning
<5>scsi 0:0:0:0: Direct-Access ZyRUS mini Swing Plus 1100 PQ: 0 ANSI: 0 CCS
<5>SCSI device sda: 3915776 512-byte hdwr sectors (2005 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 43 00 00 00
<3>sda: assuming drive cache: write through
<5>SCSI device sda: 3915776 512-byte hdwr sectors (2005 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 43 00 00 00
<3>sda: assuming drive cache: write through
<6> sda: sda1 sda2 sda3
<5>sd 0:0:0:0: Attached scsi removable disk sda
<7>usb-storage: device scan complete
<6>kjournald starting. Commit interval 5 seconds
<4>EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
<6>EXT3 FS on sda1, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>IXP4XX Q Manager 0.2.1 initialized.
<6>ixp4xx_mac driver 0.3.1: eth0 on NPE-B with PHY[1] initialized
<6>kjournald starting. Commit interval 5 seconds
<4>EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
<6>EXT3 FS on sda3, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>Adding 131064k swap on /dev/sda2. Priority:-1 extents:1 across:131064k
<6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
<7>Link of eth0 is full-duplex
<4>IXP4xx Watchdog Timer: heartbeat 60 sec
<6>usbcore: registered new interface driver usbserial
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
<6>usbcore: registered new interface driver usbserial_generic
<6>drivers/usb/serial/usb-serial.c: USB Serial Driver core
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
<6>usbcore: registered new interface driver pl2303
<6>drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for cp2101
<6>usbcore: registered new interface driver cp2101
<6>drivers/usb/serial/cp2101.c: Silicon Labs CP2101/CP2102 RS232 serial adaptor driver v0.07
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
<6>usbcore: registered new interface driver ftdi_sio
<6>drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 196987, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 196987, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 196987, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 196987, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 196987, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 196987, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 196987, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 196987, count = 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 295141, count = 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 295165, count = 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 295213, count = 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 295382, count = 1
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 300253
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 302741
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 304494
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 306404
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 306768
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 307028
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 307154
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 309426
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 309713
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 310133
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 310293
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 312428
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 313028
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 313203
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 303146
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 303110
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 309161
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 310748
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 314461
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 300730
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 300906
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 302278
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 302453
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 302576
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 305157
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 305341
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 305345
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 305357
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 305737
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 305835
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 306147
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 307373
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 307509
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 307736
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 308086
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 311573
<2>EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 312049
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<6>usb 2-1: new full speed USB device using ohci_hcd and address 2
<6>usb 2-1: configuration #1 chosen from 1 choice
<6>cp2101 2-1:1.0: cp2101 converter detected
<6>usb 2-1: reset full speed USB device using ohci_hcd and address 2
<6>usb 2-1: cp2101 converter now attached to ttyUSB0
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 196987, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1
<2>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - blocks from 164328, length 1
<2>EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system zones - Block = 164328, count = 1

USB:
Bus 3 Device 1: ID 0000:0000
Bus 2 Device 2: ID 10c4:ea60
Bus 2 Device 1: ID 0000:0000
Bus 1 Device 2: ID 090c:1000
Bus 1 Device 1: ID 0000:0000

PCI:
00:01.0 0c03: 1033:0035 (rev 43)
00:01.1 0c03: 1033:0035 (rev 43)
00:01.2 0c03: 1033:00e0 (rev 04)

iPartitions:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda1 412524 225149 166077 58% /
/dev/mtdblock4 6528 5580 948 85% /initrd
/dev/sda1 412524 225149 166077 58% /dev/.static/dev
tmpfs 2048 36 2012 2% /dev
/dev/sda3 1354092 876092 409216 68% /data
tmpfs 15188 1120 14068 7% /var/volatile
tmpfs 15188 0 15188 0% /dev/shm

Process:
PID Uid VmSize Stat Command
1 root 572 S init [3]
2 root RWN [ksoftirqd/0]
3 root SW< [events/0]
4 root SW< [khelper]
5 root SW< [kthread]
38 root RW< [kblockd/0]
41 root SW< [khubd]
56 root SW [pdflush]
58 root SW< [kswapd0]
59 root SW< [aio/0]
81 root SW [mtdblockd]
82 root SW [nftld]
167 root SW< [scsi_eh_0]
168 root SW< [usb-storage]
192 root SW< [kjournald]
238 root 604 S < udevd --daemon
599 root SW< [kjournald]
910 daemon 424 S /sbin/portmap
964 root 448 S /home/meteohub/watchdog
973 root 936 S /home/meteohub/meteoschedule /dev/meteohub
1033 root 932 S /usr/sbin/sshd
1097 root 2068 S N /usr/sbin/smbd
1100 root 1148 S /usr/sbin/nmbd
1110 root 1036 S /usr/sbin/thttpd -C /etc/thttpd.conf
1116 root 812 S /usr/sbin/thttpdbackup -C /etc/thttpd-backup.conf
1123 root 1284 R /home/meteohub/meteonet -r
1129 root 1028 S /usr/bin/ntpd -p /var/run/ntpd.pid -g
1138 root 1588 S N /usr/sbin/smbd
1142 root 556 S /usr/bin/rsync /var/run/rsyncd.pid --daemon
1143 root 692 S /usr/sbin/cron
1174 root 544 S /sbin/getty 115200 ttyS0
1403 root 2980 S N /usr/sbin/smbd
6026 root SW [pdflush]
11117 root 2044 S sshd: root@pts/0
11161 root 936 S -sh
13298 root 452 S /USR/SBIN/CRON
13299 root 596 S /bin/sh -c sleep 32; [ -z "`ls /var/run/meteohub/uploads/`" ] || [ -n "`/bin/pidof /usr/bin/ncftpput`" ] |
13309 root 540 S sleep 32
13357 root 1476 S < meteohub.cgi
13359 root 552 R /usr/sbin/thttpd -C /etc/thttpd.conf
13384 root 796 R < ps w
17827 root 2768 S N /usr/sbin/smbd
31705 root 604 S /usr/sbin/thttpd -C /etc/thttpd.conf
31743 root 372 S < /home/meteohub/loggerd /var/run/loggerd.pid
31744 root 1820 S < /home/meteohub/loggerd /var/run/loggerd.pid

[YJB]

Hi,

Not sure what happened to your system, but the filesystem is definitely corrupted:

Code: Select all

>EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone -

Since this is a NSLU2 system, I would expect that your memory stick is dying

[Haole]

That was my suspicion as well, but didn't know for sure.
Good thing I made a clone when it was new.

[Haole]

No luck with a new memory stick.
I'm still getting the same errors with the odd dates.

Any ideas?

[admin]

when the corrupted data gets copied to a new stick the data is still corrupted.
Try using the "cleanup" feature on "inspect data" page (selecting month "2011-11").

[Haole]

I did the clean up and it drastically reduced the errors logged.
I did it about 8 hours ago and since then this is all that has logged.

loggereval (23.11.2011 12:13:04): illegal data record in line 20388 while reading from file /data/weather/201110/raw: 20111013220111013205258 wind0 296 13 22 0149
loggereval (23.11.2011 12:13:05): illegal data record in line 23208 while reading from file /data/weather/201110/raw: 2020111015062740 wind0 268 36 45 0079
loggereval (23.11.2011 12:14:10): illegal data record in line 20388 while reading from file /data/weather/201110/raw: 20111013220111013205258 wind0 296 13 22 0149
loggereval (23.11.2011 12:14:11): illegal data record in line 23208 while reading from file /data/weather/201110/raw: 2020111015062740 wind0 268 36 45 0079
loggereval (23.11.2011 18:13:03): illegal data record in line 20388 while reading from file /data/weather/201110/raw: 20111013220111013205258 wind0 296 13 22 0149
loggereval (23.11.2011 18:13:05): illegal data record in line 23208 while reading from file /data/weather/201110/raw: 2020111015062740 wind0 268 36 45 0079
loggereval (23.11.2011 18:14:16): illegal data record in line 20388 while reading from file /data/weather/201110/raw: 20111013220111013205258 wind0 296 13 22 0149
loggereval (23.11.2011 18:14:17): illegal data record in line 23208 while reading from file /data/weather/201110/raw: 2020111015062740 wind0 268 36 45 0079

[admin]

when you look at the log in detail you can see that this time there are errors in monthly raw data of 2011-10.
Please selct this month on "inspect data" page and do a cleanup again. Cleanup is limitied to the selected month.

[Haole]

Now that I know what to look for in the date, I saw that I needed to go back thru June and clean it up.
So far so good.

Thanks