dmesg problem

[Rene Mendez_4]

Hi I have two server in server1 the output the command dmesg is:
cobis-hp>#dmesg

Oct 9 14:39
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
1 cell
1/0 sba
1/0/0 lba
1/0/0/0/0 func0
1/0/0/0/1 asio0
c8xx BUS: 0 SCSI C1010 Ultra160 Wide LVD A6793-60001 assigned CPU: 1
1/0/0/3/0 c8xx
1/0/0/3/0.6 tgt
1/0/0/3/0.6.0 sdisk
1/0/0/3/0.7 tgt
1/0/0/3/0.7.0 sctl
c8xx BUS: 1 SCSI C1010 Ultra Wide Single-Ended A6793-60001 assigned CPU: 2
1/0/0/3/1 c8xx
1/0/0/3/1.2 tgt
1/0/0/3/1.2.0 sdisk
1/0/0/3/1.7 tgt
1/0/0/3/1.7.0 sctl
1/0/1 lba
1/0/1/0/0 PCItoPCI
c8xx BUS: 2 SCSI C1010 Ultra160 Wide LVD assigned CPU: 3
1/0/1/0/0/1/0 c8xx
1/0/1/0/0/1/0.0 tgt
1/0/1/0/0/1/0.0.0 sdisk
1/0/1/0/0/1/0.1 tgt
1/0/1/0/0/1/0.1.0 sdisk
1/0/1/0/0/1/0.2 tgt
1/0/1/0/0/1/0.2.0 sdisk
1/0/1/0/0/1/0.3 tgt
1/0/1/0/0/1/0.3.0 sdisk
1/0/1/0/0/1/0.4 tgt
1/0/1/0/0/1/0.4.0 sdisk
1/0/1/0/0/1/0.5 tgt
1/0/1/0/0/1/0.5.0 sdisk
1/0/1/0/0/1/0.7 tgt
1/0/1/0/0/1/0.7.0 sctl
1/0/1/0/0/1/0.8 tgt
1/0/1/0/0/1/0.8.0 sdisk
c8xx BUS: 3 SCSI C1010 Ultra160 Wide LVD assigned CPU: 0
1/0/1/0/0/1/1 c8xx
1/0/1/0/0/1/1.6 tgt
1/0/1/0/0/1/1.6.0 sdisk
1/0/1/0/0/1/1.7 tgt
1/0/1/0/0/1/1.7.0 sctl
1/0/1/0/0/4/0 igelan
1/0/2 lba
1/0/4 lba
1/0/4/0/0 td
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 1/0/4/0/0
1/0/6 lba
1/0/6/0/0 PCItoPCI
c8xx BUS: 8 SCSI C1010 Ultra160 Wide LVD assigned CPU: 2
1/0/6/0/0/1/0 c8xx
1/0/6/0/0/1/0.7 tgt
1/0/6/0/0/1/0.7.0 sctl
c8xx BUS: 9 SCSI C1010 Ultra160 Wide LVD assigned CPU: 3
1/0/6/0/0/1/1 c8xx
1/0/6/0/0/1/1.7 tgt
1/0/6/0/0/1/1.7.0 sctl
1/0/6/0/0/4/0 igelan
1/0/8 lba
1/0/10 lba
1/0/12 lba
1/0/14 lba
1/5 memory
1/10 processor
1/11 processor
1/12 processor
1/13 processor

System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/1/0/0/4/0
igelan2: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/6/0/0/4/0
Entering cifs_init...
Initialization finished successfully... slot is 9
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 2, minor is 0x1; start = 0, size = 16777216
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x36000; start = 310368, size = 8388608
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 8380416 Kbytes, lockable: 6369392 Kbytes, available: 7320168 Kbytes



In server 2 dmesg output
hp-pro>#dmesg

Oct 27 14:26
...
0/8/0/0.1.0.0.0.0.3 sdisk
1/0/8/0/0.1.1.0.0.0.1 sdisk
1/0/8/0/0.1.1.0.0.0.2 sdisk
1/0/8/0/0.1.1.0.0.0.3 sdisk
0/0/8/0/0.1.2.0.0.0.1 hsx
0/0/8/0/0.1.2.0.0.0.2 hsx
0/0/8/0/0.1.2.0.0.0.3 hsx
0/0/8/0/0.1.3.0.0.0.1 hsx
0/0/8/0/0.1.3.0.0.0.2 hsx
0/0/8/0/0.1.3.0.0.0.3 hsx
1/0/8/0/0.1.0.0.0.0.1 hsx
1/0/8/0/0.1.0.0.0.0.2 hsx
1/0/8/0/0.1.0.0.0.0.3 hsx
1/0/8/0/0.1.1.0.0.0.1 hsx
1/0/8/0/0.1.1.0.0.0.2 hsx
1/0/8/0/0.1.1.0.0.0.3 hsx
255/255/0.0.0 sdisk
255/255/0.0.1 sdisk
255/255/0.0.2 sdisk
0/0/8/0/0.1.2.0.0.0.1 sdisk
0/0/8/0/0.1.2.0.0.0.2 sdisk
0/0/8/0/0.1.2.0.0.0.3 sdisk
1/0/8/0/0.1.0.0.0.0.1 sdisk
1/0/8/0/0.1.0.0.0.0.2 sdisk
1/0/8/0/0.1.0.0.0.0.3 sdisk
0/0/8/0/0.1.3.0.0.0.1 sdisk
0/0/8/0/0.1.3.0.0.0.2 sdisk
0/0/8/0/0.1.3.0.0.0.3 sdisk
1/0/8/0/0.1.1.0.0.0.1 sdisk
1/0/8/0/0.1.1.0.0.0.2 sdisk
1/0/8/0/0.1.1.0.0.0.3 sdisk
0/0/8/0/0.1.2.0.0.0.1 hsx
0/0/8/0/0.1.2.0.0.0.2 hsx
0/0/8/0/0.1.2.0.0.0.3 hsx
0/0/8/0/0.1.3.0.0.0.1 hsx
0/0/8/0/0.1.3.0.0.0.2 hsx
0/0/8/0/0.1.3.0.0.0.3 hsx
1/0/8/0/0.1.0.0.0.0.1 hsx
1/0/8/0/0.1.0.0.0.0.2 hsx
1/0/8/0/0.1.0.0.0.0.3 hsx
1/0/8/0/0.1.1.0.0.0.1 hsx
1/0/8/0/0.1.1.0.0.0.2 hsx
1/0/8/0/0.1.1.0.0.0.3 hsx
255/255/0.0.0 sdisk
255/255/0.0.1 sdisk
255/255/0.0.2 sdisk
0/0/8/0/0.1.2.0.0.0.1 sdisk
0/0/8/0/0.1.2.0.0.0.2 sdisk
0/0/8/0/0.1.2.0.0.0.3 sdisk
1/0/8/0/0.1.0.0.0.0.1 sdisk
1/0/8/0/0.1.0.0.0.0.2 sdisk
1/0/8/0/0.1.0.0.0.0.3 sdisk
0/0/8/0/0.1.3.0.0.0.1 sdisk
0/0/8/0/0.1.3.0.0.0.2 sdisk
0/0/8/0/0.1.3.0.0.0.3 sdisk
1/0/8/0/0.1.1.0.0.0.1 sdisk
1/0/8/0/0.1.1.0.0.0.2 sdisk
1/0/8/0/0.1.1.0.0.0.3 sdisk

Because en server 2 no show the memory information.

Regards,
RenÃ

[Jeff Schussele]

Hi Rene,

The dmesg utility just uses a small circular buffer to store the info. I suspect that something has "pushed" the bootup info out of that buffer. You can find all this info at the top of /var/adm/syslog/syslog.log....UNLESS you have a utility that rolls the syslog.log regularly. Then you'll have to go back to the day/week/whatever that this system actually booted.

Rgds,
Jeff

[Kevin Wright]

It was overwritten. To keep your dmesg logs, run dmesg >> /var/adm/syslog/syslog.log from cron every half hour or so.

system errors are written to dmesg, and it is a fixed size, circular buffer.

[Con O'Kelly]

Hi

Just to add to Kevin's point, I'd use the syntax in cron as follows:
0,15,30,45 * * * * /usr/sbin/dmesg - >> /var/adm/messages

This will write dmesg output to /var/adm/messages file every 15mins. Note the "-" which will ensure only new messages (ie since dmesg was last run) will be written to the messages file.

Cheers
Con

[Rene Mendez_4]

ok with dmesg i rewiew :

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 8380416 Kbytes, lockable: 6369392 Kbytes, available: 7320168 Kbyt

How to check this ?

[Con O'Kelly]

Hi

Well that's telling you that you have about 8184 MBytes of RAM (ie 8380416 / 1024).
You can also check memory with:
# echo "phys_mem_pages/D" | adb /stand/vmunix /dev/kmem

Look at "phys_mem_pages" value & multiply by 4 to get amount of memory in kbytes.
Hope that's what you're after?

Cheers
Con

[Patrick Wallek]

Instead of 'dmesg' use /var/adm/syslog/syslog.log. Unless you somehow rotate you syslog.log files, all of the information should be there as well.