NEWS:

jail: fetch: transfer timed out / protocol not supported

March 31st, 2012

After recent efforts to get old jails running on a new server, I tried to upgrade some ports today. I failed.

portupgrade was erroring out and reporting: protocol not supported

A simple fetch http://www.google.com/ was giving me fetch: transfer timed out

I tried portaudit -Fa. Nothing. fetch: transfer timed out

I checked ifconfig on the jail host. There is was. I’ll show only a small part of the ifconfig output:

$ ifconfig
	inet 10.45.0.100 netmask 0x20 broadcast 255.255.255.255
	inet 10.45.0.101 netmask 0x20 broadcast 255.255.255.255
	inet 10.45.0.102 netmask 0xffffffff broadcast 10.45.0.102
	inet 10.45.0.104 netmask 0xffffffff broadcast 10.45.0.104

See that 0×20. That’s wrong. It should be 0xffffffff like the others. I recall making this error at the time.

I had copied pasted the entries from /etc/rc.conf to the command line. In my haste, I tried:

sudo ifconfig em0 alias 10.45.0.101/32

Which failed. So then I tried:

sudo ifconfig em0 alias 10.45.0.101 netmask 32

Which succeeded, but was not what I wanted.

Solution, stop the jail in question, then:

sudo ifconfig em0 delete 10.45.0.100
sudo ifconfig em0 alias 10.45.0.100 netmask 255.255.255.255

After, restart the jail. All was well.

jail: execv: /bin/sh: No such file or directory

March 31st, 2012

Recently, I was moving some jails from one server to another.

First, I created the jail using the -x switch, which indicates the jail already exists, don’t create it, just add entries for it:

# ezjail-admin create -f bacula -x mysql41.example.org 10.35.0.100
Warning: Some services already seem to be listening on IP 10.35.0.100
  This may cause some confusion, here they are:
root     ntpd       63822 25 udp4   10.35.0.100:123       *:*
Warning: Some services already seem to be listening on all IP, (including 10.35.0.100)
  This may cause some confusion, here they are:
root     ntpd       63822 20 udp4   *:123                 *:*
#

Then, I tried starting that jail:

# /usr/local/etc/rc.d/ezjail.sh start
 ezjailConfiguring jails:.
Starting jails: cannot start jail "mysql41_unixathome_org":
jail: execvp: /bin/sh: No such file or directory
.
[root@kraken /usr/local/etc/ezjail]#

DOH! Why?

Eventually, I read through my old notes and realized: I have never run on jails on this new server.

I had not created the basejail…

ezjail-admin update -ip

This step takes quite some time. Be prepared.

But that was not quite enough. ezjail uses symlinks. Extensively. They are missing. Compare this newly created jail with my old jail:

[root@kraken /storage/compressed/jails]# ls -l pg74.unixathome.org XXXXXXXXXXX.unixathome.org
XXXXXXXXXXX.unixathome.org:
total 41
-rw-r--r--   2 root  wheel   794 Mar 30 18:25 .cshrc
-rw-r--r--   2 root  wheel   261 Mar 30 18:25 .profile
-r--r--r--   1 root  wheel  6196 Mar 30 18:25 COPYRIGHT
drwxr-xr-x   2 root  wheel     2 Mar 30 18:25 basejail
lrwxr-xr-x   1 root  wheel    13 Mar 30 18:25 bin -> /basejail/bin
lrwxr-xr-x   1 root  wheel    14 Mar 30 18:25 boot -> /basejail/boot
dr-xr-xr-x   2 root  wheel     2 Mar 30 18:25 dev
drwxr-xr-x  20 root  wheel   101 Mar 30 18:25 etc
lrwxr-xr-x   1 root  wheel    13 Mar 30 18:25 lib -> /basejail/lib
lrwxr-xr-x   1 root  wheel    17 Mar 30 18:25 libexec -> /basejail/libexec
drwxr-xr-x   2 root  wheel     2 Mar 30 18:25 media
drwxr-xr-x   2 root  wheel     2 Mar 30 18:25 mnt
dr-xr-xr-x   2 root  wheel     2 Mar 30 18:25 proc
lrwxr-xr-x   1 root  wheel    16 Mar 30 18:25 rescue -> /basejail/rescue
drwxr-xr-x   2 root  wheel     6 Mar 30 18:25 root
lrwxr-xr-x   1 root  wheel    14 Mar 30 18:25 sbin -> /basejail/sbin
lrwxr-xr-x   1 root  wheel    11 Mar 30 18:25 sys -> usr/src/sys
drwxrwxrwt   6 root  wheel     6 Mar 30 18:28 tmp
drwxr-xr-x   5 root  wheel    16 Mar 30 18:25 usr
drwxr-xr-x  24 root  wheel    24 Mar 30 18:28 var

pg74.unixathome.org:
total 47
-rw-r--r--   1 root  wheel   794 Jan 22  2010 .cshrc
-rw-r--r--   1 root  wheel   261 Jan 22  2010 .profile
-r--r--r--   1 root  wheel  6202 Jan 22  2010 COPYRIGHT
drwxr-xr-x   2 root  wheel     2 Jan 22  2010 basejail
dr-xr-xr-x   2 root  wheel     2 Jan 22  2010 dev
drwxr-xr-x  21 root  wheel   106 Aug 21  2010 etc
drwxr-xr-x   3 root  wheel     3 Jan 22  2010 home
drwxr-xr-x   2 root  wheel     2 Jan 22  2010 media
drwxr-xr-x   2 root  wheel     2 Jan 22  2010 mnt
dr-xr-xr-x   2 root  wheel     2 Jan 22  2010 proc
drwxr-xr-x   2 root  wheel     9 Jan 23  2010 root
drwxrwxrwt   6 root  wheel   183 Jul 28  2011 tmp
drwxr-xr-x   5 root  wheel     5 Jan 22  2010 usr
drwxr-xr-x  24 root  wheel    24 Jul 27  2011 var
[root@kraken /storage/compressed/jails]#

After creating those symlinks by hand, the jail still would not start:

# /usr/local/etc/rc.d/ezjail.sh start
 ezjailConfiguring jails:.
Starting jails: mysql41.unixathome.org.
# jls
   JID  IP Address      Hostname                      Path

Hmm, starting the jail manually yields a clue:

# jail /storage/compressed/jails/mysql41.unixathome.org mysql41.unixathome.org 10.55.0.100 /bin/sh
Cannot read termcap database;
using dumb terminal settings.
#

The solution: create symlinks by hand:

cd /storage/compressed/jails/mysql41.unixathome.org
ln -s /basejail/bin
ln -s /basejail/boot
ln -s /basejail/lib
ln -s /basejail/libexec
ln -s /basejail/rescue
ln -s /basejail/sbin
ln -s usr/src/sys

cd /storage/compressed/jails/mysql41.unixathome.org/usr
ln -s /basejail/usr/bin
ln -s /basejail/usr/games
ln -s /basejail/usr/include
ln -s /basejail/usr/lib
ln -s /basejail/usr/lib32
ln -s /basejail/usr/libdata
ln -s /basejail/usr/libexec
ln -s /basejail/usr/ports
ln -s /basejail/usr/sbin
ln -s /basejail/usr/share
ln -s /basejail/usr/src

Now the jail starts.

Upgrading to Bacula database version 14

March 26th, 2012

After running the script which upgrades your Bacula database to version 14, there are a couple of fix-ups you may wish to run:

alter table restoreobject owner to bacula;
grant all on restoreobject_restoreobjectid_seq to bacula;
grant all on restoreobject to bacula;

You may or may not have to do this, depending on how you ran the upgrade script.

Examine the following command output for your database:

bacula=# \dt restoreobject
            List of relations
 Schema |     Name      | Type  | Owner
--------+---------------+-------+--------
 public | restoreobject | table | bacula
(1 row)

bacula=#

If the table owner is not bacula, you have to run the script.

Pentabarf authentication issues

February 29th, 2012

I encountered this situation recently. I had consolidated two logins. One was for 2012, the other for 2011. It’s better to reuse your login from previous years instead of creating a new one each year. Why? It lets the program committee see what you’ve submitted in previous years. They can see your previous acceptances/rejections. That is very useful, both in a negative and a positive fashion.

The error upon login was:

You are lacking permissions to login to the submission system. The most likely cause for this is your account has not yet been activated.

The solution: add an entry to the auth.account_role table.

I discovered this by poking around via psql. I found this interesting difference.

FYI, the person_id values represent:

  1. 1 - me
  2. 160 - the person who could not login
  3. 187 - a person who could login
pentabarf_bsdcan=# select * from auth.account_role where account_id in ( select account_id from auth.account where person_id in (1, 160));
 account_id |   role
------------+-----------
         49 | admin
         49 | developer
(2 rows)

In the above case, the other person has no entries.

pentabarf_bsdcan=# select * from auth.account_role where account_id in ( select account_id from auth.account where person_id in (1, 187));
account_id | role
————+———–
49 | admin
49 | developer
177 | submitter
(3 rows)

But as you can see here, the person who can log in has a ’submitter’ row.

The solution is to add in the missing row:

pentabarf_bsdcan=# begin;
BEGIN
pentabarf_bsdcan=# insert into auth.account_role values (186, ’submitter’);
INSERT 0 1
pentabarf_bsdcan=# commit;
COMMIT
pentabarf_bsdcan=#

PGCon 2012 schedule released

February 28th, 2012

The list of talks and speakers for PGCon 2012 has been released. For 2012, we once again have a strong collection of talks that will appeal to a wide range of attendees. Registration will open soon and we will send out an announcement when it does. Be sure to start making your travel plans now.

Please consider becoming a sponsor.

Follow us:

Pentabarf travel

January 21st, 2012

Here is the start of a query for pulling out travel requirements for conference attendees.

SELECT P.last_name, P.first_name,
       CPT.arrival_from,
       CPT.arrival_to,
       CPT.need_accommodation
  FROM conference_person_travel CPT, conference_person CP, conference C, person P
 WHERE CPT.need_accommodation
   AND CPT.conference_person_id = CP.conference_person_id
   AND P.person_id              = CP.person_id
   AND CP.conference_id         = C.conference_id
   AND C.acronym                = 'BSDCan2012'

memtestosx

January 8th, 2012

I just bought and downloaded memtestosx.

Last login: Sun Jan  8 16:14:10 on ttys001
[dan@dent:~] $ /Volumes/memtest_422/memtest/memtest ; exit;

Memtest version 4.22 (64-bit)
Copyright (C) 2004 Charles Cazabon
Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port)
Licensed under the GNU General Public License version 2 only

NOTE: No command-line arguments have been specified
Using defaults: Test all available memory, one test pass, no logfile

Mac OS X 10.7.2 (11C74) running in multiuser mode
Memory Page Size: 4096
System has 8 Intel core(s) with SSE
Requested memory: 2099MB (2201194496 bytes)
Available memory: 2099MB (2201194496 bytes)
Allocated memory: 2099MB (2201194496 bytes) at local address 0x0000000101000000
Attempting memory lock... locked successfully
Partitioning memory into 2 comparison buffers...
Buffer A: 1049MB (1100597248 bytes) starts at local address 0x0000000101000000
Buffer B: 1049MB (1100597248 bytes) starts at local address 0x000000014299c800

Running 1 test sequence... (CTRL-C to quit)

Test sequence 1 of 1:

Running tests on full 2099MB region...
  Stuck Address       : ok
  Linear PRN          : ok
Running comparison tests using 1049MB buffers...
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok                

All tests passed!  Execution time: 606 seconds.

logout

[Process completed]

Pentabarf fix

December 30th, 2011

After a very long effort, this is the solution:

CREATE OR REPLACE FUNCTION conflict.conflict_statistics(conference_id integer, OUT conflict_level text, OUT conflicts integer)
 RETURNS SETOF record
 LANGUAGE plpgsql
AS $function$
#variable_conflict use_variable
  DECLARE
    conflict TEXT;
    conflict_rows INTEGER;
  BEGIN
    FOR conflict_level IN
      SELECT conflict_level.conflict_level FROM conflict.conflict_level WHERE conflict_level.conflict_level <> ’silent’ ORDER BY rank
    LOOP
      conflicts = 0;
        FOR conflict IN
          SELECT conference_phase_conflict.conflict
          FROM
            conflict.conference_phase_conflict
            INNER JOIN conference ON (
              conference.conference_id = conference_id AND
              conference.conference_phase = conference_phase_conflict.conference_phase )
          WHERE conference_phase_conflict.conflict_level = conflict_level
        LOOP
          EXECUTE ‘SELECT count(1) FROM conflict.conflict_’ || conflict || ‘(’ || conference_id || ‘);’ INTO STRICT conflict_rows;
          conflicts := conflicts + conflict_rows;
        END LOOP;
      RETURN NEXT;
    END LOOP;
  END;
$function$

Such devious spam

October 6th, 2011

Today I received this rather devious spam. Invoke education, children, libraries, and hope that someone will link to their site. I’m not sure *why* they want this particular site promoted. There’s not much useful information there. No attempt to sell anything. I’m confused.

Perhaps this was legit. But then, if you search for certain phrases contained in this email, you’ll see other such posts. I’m certain it’s spam.

By, the way, I’ve amended their URLs by appending .invalid to them. No sense giving them a link.

Received: from mx.districtlibrary.org ([173.234.9.58]) by na3sys009amx170.postini.com ([74.125.148.10]) with SMTP;
	Thu, 06 Oct 2011 08:00:34 PDT
To: help@racingsystem.com
From: agriffin@districtlibrary.org.invalid
Subject: Fan Mail/Question on the Racing System Links pg.
Date: Thu, 6 Oct 2011 10:57:39 -0400
X-pstn-neptune: 0/0/0.00/0
X-pstn-levels:     (S: 9.25315/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
Message-ID: <2615178027880354086370761583678@psmtp.com>
X-pstn-settings: 2 (0.5000:0.5000) s cv gt3 gt2 gt1
X-pstn-addresses: from  [1862/74] 

Hi,

I just wanted to send out a quick thank you letter in regards to your racing system links page -
(http://www.racingsystem.com/links.html).  I’m a librarian and used some of your resources for the
sports of our new site.   Great leads there, I appreciate it :) 

I planned on having the students that participated with the site, mail out a handwritten thank you note,
but we’ve been so busy I haven’t had a chance. So I’m writing on their behalf today as well.  As a small
token of our appreciation, I wanted to share another resource that might be perfect for your page.  This
page has been popular among the staff here that are avid cyclists:

“A Guide to Bike Racing for Beginners and Competitors” - (http://www.cyclesport.com.invalid/guide-to-bike-
racing-for-beginners-and-competitors/).

I hope you like the link and thanks again for the help.

Sincerely,
Anne Griffin

P.S. I think the students would get a kick out of hearing from a friend in cyberspace. If you include the
link and don’t mind giving me a shout back, I’ll show them that you used our suggestion :)

When is a cleaning tape needed?

June 20th, 2011

As part of my magical Bacula website, I wanted to know when my tape drive required a cleaning tape. It appears that smartctl will reveal this information:

[dan@kraken:/usr/home/dan] $ sudo /usr/local/sbin/in/smartctl -d scsi -x /dev/nsa0
Password:
smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 8.2-STABLE amd64] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Device: DEC      TZ89     (C) DEC Version: 2561
Serial number: CXA02S1766
Device type: tape
Local Time is: Tue Jun 21 00:22:26 2011 UTC
Temperature Warning Disabled or Not Supported
TapeAlert Supported
TapeAlert Errors (C=Critical, W=Warning, I=Informational):
[0x14] C: The tape drive needs cleaning:
  1. If the operation has stopped, eject the tape and clean the drive.
  2. If the operation has not stopped, wait for it to finish and then
  clean the drive.
  Check the tape drive users manual for device specific cleaning instructions.

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0        0         0         0          0          0.023           0
write:         0        0        15        15          0          3.611           0

Last n error events log page
  Error event 0:
    Packet # 211 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22282/353/0A4E0714/1/80/02/00

  Error event 1:

  Error event 2:
    Packet # 212 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22307/353/0A4E7DB4/1/80/02/00

  Error event 3:

  Error event 4:
    Packet # 213 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22309/353/0A4EB06D/1/80/02/00

  Error event 5:

  Error event 6:
    Packet # 214 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22313/353/0A4E7DB4/1/80/02/00

  Error event 7:

  Error event 8:
    Packet # 215 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22318/353/0A4E7DB4/1/80/02/00

  Error event 9:

  Error event 10:
    Packet # 216 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22337/353/7098FB99/1/80/02/00

  Error event 11:

  Error event 12:
    Packet # 217 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22361/353/7098FB99/1/80/02/00

  Error event 13:

  Error event 14:
    Packet # 218 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22385/353/7098FB99/1/80/02/00

  Error event 15:

  Error event 16:
    Packet # 219 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22409/353/7098FB99/1/80/02/00

  Error event 17:

  Error event 18:
    Packet # 220 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22433/353/0A4EA033/1/80/02/00

  Error event 19:

  Error event 20:
    Packet # 221 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22457/353/0A4EA033/1/80/02/00

  Error event 21:

  Error event 22:
    Packet # 222 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22458/353/0A4EB06D/1/80/02/00

  Error event 23:

  Error event 24:
    Packet # 223 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22481/353/0A4EA033/1/80/02/00

  Error event 25:

  Error event 26:
    Packet # 224 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22505/353/0A4EA033/1/80/02/00

  Error event 27:

  Error event 28:
    Packet # 225 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22506/353/0A4EB06D/1/80/02/00

  Error event 29:

  Error event 30:
    Packet # 226 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22560/353/16A280CB/1/80/02/00

  Error event 31:

  Error event 32:
    Packet # 227 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22602/353/48C6831E/1/80/02/00

  Error event 33:

  Error event 34:
    Packet # 228 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22625/353/0A4E7213/1/80/02/00

  Error event 35:

  Error event 36:
    Packet # 229 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22626/353/48C6831E/1/80/02/00

  Error event 37:

  Error event 38:
    Packet # 230 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22649/353/0A4E7213/1/80/02/00

  Error event 39:

  Error event 40:
    Packet # 231 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22650/353/48C6831E/1/80/02/00

  Error event 41:

  Error event 42:
    Packet # 232 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22673/353/0A4E7213/1/80/02/00

  Error event 43:

  Error event 44:
    Packet # 233 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22674/353/48C6831E/1/80/02/00

  Error event 45:

  Error event 46:
    Packet # 234 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22697/353/0A4E7213/1/80/02/00

  Error event 47:

  Error event 48:
    Packet # 235 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22721/353/0A4E7213/1/80/02/00

  Error event 49:

  Error event 50:
    Packet # 236 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22793/353/4F5B1D10/1/80/02/00

  Error event 51:

  Error event 52:
    Packet # 237 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22817/353/4F5B1D10/1/80/02/00

  Error event 53:

  Error event 54:
    Packet # 238 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22833/353/4F5B1D10/1/80/02/00

  Error event 55:

  Error event 56:
    Packet # 239 - Event: A401  [V97-0  29-DEC-1999]  616:41:33.323  POH/PC= 22841/353
       11004F5B 1D100101 00400000 10100027 65B20000 0A0B0000 00000000 00000000
       00060001 A1920000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 57:
    0000 00000000 00000000 00000000

  Error event 58:
    Packet # 240 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22841/353/4F5B1D10/3/0C/00/00

  Error event 59:

  Error event 60:
    Packet # 241 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22841/353/4F5B1D10/3/0C/00/00

  Error event 61:

  Error event 62:
    Packet # 242 - Event: A401  [V97-0  29-DEC-1999]  616:42:05.351  POH/PC= 22841/353
       11004F5B 1D100101 00400000 13000027 65D60000 0A0C0000 00000000 00000000
       00060001 A19F0000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 63:
    0000 00000000 00000000 00000000

  Error event 64:
    Packet # 243 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22841/353/4F5B1D10/3/80/01/00

  Error event 65:

  Error event 66:
    Packet # 244 - Event: A401  [V97-0  29-DEC-1999]  616:42:34.111  POH/PC= 22841/353
       11004F5B 1D100101 00400000 13000027 65D60000 0A0C0000 00000000 00000000
       00060001 A3860000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 67:
    0000 00000000 00000000 00000000

  Error event 68:
    Packet # 245 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22841/353/4F5B1D10/3/0C/00/00

  Error event 69:

  Error event 70:
    Packet # 246 - Event: A401  [V97-0  29-DEC-1999]  617:19:25.841  POH/PC= 22842/353
       11004F5B 912A0101 00400000 10100003 65A80000 0A1C0000 00000000 00000000
       00020002 86640000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 71:
    0000 00000000 00000000 00000000

  Error event 72:
    Packet # 247 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22842/353/4F5B912A/3/0C/00/00

  Error event 73:

  Error event 74:
    Packet # 248 - Event: A401  [V97-0  29-DEC-1999]  617:19:58.191  POH/PC= 22842/353
       11004F5B 912A0101 00400000 13000003 65CC0000 0A1D0000 00000000 00000000
       00020002 866C0000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 75:
    0000 00000000 00000000 00000000

  Error event 76:
    Packet # 249 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22842/353/4F5B912A/3/80/01/00

  Error event 77:

  Error event 78:
    Packet # 250 - Event: A401  [V97-0  29-DEC-1999]  617:20:27.305  POH/PC= 22842/353
       11004F5B 912A0101 00400000 13000003 65CC0000 0A1D0000 00000000 00000000
       00020002 88520000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 79:
    0000 00000000 00000000 00000000

  Error event 80:
    Packet # 251 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22842/353/4F5B912A/3/0C/00/00

  Error event 81:

  Error event 82:
    Packet # 252 - Event: A401  [V97-0  29-DEC-1999]  617:28:03.290  POH/PC= 22842/353
       11000A4E 21940101 00400000 10100001 65D90000 0A200000 00000000 00000000
       00020001 45A60000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 83:
    0000 00000000 00000000 00000000

  Error event 84:
    Packet # 253 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22842/353/0A4E2194/3/0C/00/00

  Error event 85:

  Error event 86:
    Packet # 254 - Event: A401  [V97-0  29-DEC-1999]  617:28:37.765  POH/PC= 22842/353
       11000A4E 21940101 00400000 13000001 65FE0000 0A210000 00000000 00000000
       00020001 45AC0000 00000000 00000000 00000000 00000000 00000000 00000000
       0000
  Error event 87:
    0000 00000000 00000000 00000000

  Error event 88:
    Packet # 255 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22842/353/0A4E2194/3/80/01/00

  Error event 89:

  Error event 90:
    Packet # 0 - Event: A401  [V97-0  29-DEC-1999]  617:29:08.860  POH/PC= 22842/353
       11000A4E 21940101 00400000 13000001 65FE0000 0A210000 00000000 00000000
       00020001 45AD0000 00000000 00000000 00000000 00000000 00000000 00000000
       000000
  Error event 91:
    00 00000000 00000000 00000000

  Error event 92:
    Packet # 1 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22842/353/0A4E2194/3/0C/00/00

  Error event 93:

  Error event 94:
    Packet # 2 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=22889/353/4F5B6963/1/80/02/00

  Error event 95:

Device does not support Self Test logging
Device does not support Background scan results logging
scsiPrintSasPhy Log Sense Failed [unsupported field in scsi command]
[dan@kraken:/usr/home/dan] $

This information is available only upon the first query. The query clears the flag. I’ll need to write a script to detect, then store this flag.