[Dshield] Dshield timestamp function

Peter Stendahl-Juvonen peter.stendahl-juvonen at welho.com
Sat Apr 22 21:11:58 GMT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The normal figures may have been intermittent.

The figures are again as as follows:

System Status

Current Time: Sat, 22 Apr 2006 21:04:27 +0000

Reports Parsing and Import
Size of unparsed reports queue: 504KBytes (should be less then 100 MByte)
Oldest Unparsed Reports: 1145739867 seconds (should be less then 600 sec)
Size of parsed reports queue waiting for import: 9.5K Bytes

Please note "Oldest Unparsed Reports: 1145739867 seconds"

And circa five minutes later:

System Status

Current Time: Sat, 22 Apr 2006 21:09:54 +0000
Reports Parsing and Import
Size of unparsed reports queue: 504KBytes (should be less then 100 MByte)
Oldest Unparsed Reports: 1145740194 seconds (should be less then 600 sec)
Size of parsed reports queue waiting for import: 15K Bytes

Please again note "Oldest Unparsed Reports: 1145740194 seconds"


22.4.2006 22:54 (UTC+3), Dave kirjoitti:
> The DShield 'timestamp' function seems to be broken...  Is anyone else
> experiencing this issue?
>
> I have a daily cron that sends a timestamp request web page, I get the
> response on port 100xx from 24.128.226.56, but the 'timestamp status'
> never seems to get updated...  It's showing a last updated date in
> February: Last check: Feb 14th 2006. Offset: 0 seconds.  ( Well, at
> least the offset is correct. :-)
>
> For the last 3 days: ( Date/Time is correct, NTP derived. )
> 2006-04-20 11:11:06 -04:00      5206xxxx        1       65.173.218.97
> 60763   24.128.x.x   10094   ???
> 2006-04-21 11:11:03 -04:00      5206xxxx        1       65.173.218.97
> 34776   24.128.x.x   10027   ???
> 2006-04-22 11:11:03 -04:00      5206xxxx        1       65.173.218.97
> 50271   24.128.x.x   10088   ???

1) Have noticed the same thing.

The timestamp feature apparently broke when the site was modified in
order to accept login (and maintain the login status) without the use of
cookies. Would think making the feature work again is so to say in process.


2) Noticed today this oddity at https://secure.dshield.org/status.php

System Status

Current Time: Sat, 22 Apr 2006 20:50:23 +0000

Reports Parsing and Import
Size of unparsed reports queue: 504KBytes (should be less then 100 MByte)
Oldest Unparsed Reports: 1145739023 seconds (should be less then 600 sec)
Size of parsed reports queue waiting for import: 13K Bytes


Please note the "Oldest Unparsed Reports: 1145739023 seconds" which
converts to some 36+ in years. ;-)

Can't figure out how that is possible if the log excerpts should be no
longer than two days old. (If memory serves.)

The figures were odd for quite a while, but look normal again:

System Status

Current Time: Sat, 22 Apr 2006 21:02:35 +0000

Reports Parsing and Import
Size of unparsed reports queue: 512KBytes (should be less then 100 MByte)
Oldest Unparsed Reports: 118 seconds (should be less then 600 sec)
Size of parsed reports queue waiting for import: 6.3K Bytes



- -Pete

            "It's kind of fun to do the impossible."
  Walt Disney (1901-1966); US cartoonist and movie producer.





- --

Parhain terveisin

Peter Stendahl-Juvonen
toimitusjohtaja
Inertia Oy
p. (09)  884 29 39
GSM   044  38 28 991


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFESpweQ21KCihDnSQRAnhKAJ4nVUSGtaE6W87EnEALZNdetlU3WACeIkLR
/JJLYsio5Ca114H5ginmgR8=
=cWfP
-----END PGP SIGNATURE-----


More information about the list mailing list