A dmesg error!!!

[Cem Tugrul]

Hello Forum,
my rp-5430 server gives an error when i run dmesg...
so what does it mean or what kind of an error
that i face to face????
Please help!!!
Best Regards,

[Robert-Jan Goossens_1]

Would be helpfull if you add the error message to this forum.

[Cem Tugrul]

opppss,
here it is...

btlan: Initializing 10/100BASE-TX card at 0/0/0/0....

System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 4194304
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x22000; start = 310112, size = 2097152
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: 8388608 Kbytes, lockable: 7738696 Kbytes, available: 7400672 Kbytes

[Pete Randall]

And which of those lines do you consider to be an error?


Pete

[Robert-Jan Goossens_1]

Hi,

The only think which looks a bit strange is

Wed Nov 8 19:24:56 PST 2000

The rest are normal boot messages.

Regards,
Robert-Jan

[john korterman]

Hi,
do you have many messages from registrar/TCP in your syslog, like e.g.:
inetd[]: registrar/tcp: Connection from () ?

regards,
John K.

[Cem Tugrul]

Hi,

also from syslog.log;

Nov 8 16:43:24 newhr vmunix: 97 processor
Nov 8 16:43:24 newhr vmunix: 192 memory
Nov 8 16:43:24 newhr vmunix: btlan: Initializing 10/100BASE-TX card at 0/0/0/0....
Nov 8 16:43:24 newhr vmunix:
Nov 8 16:43:24 newhr vmunix: System Console is on the Built-In Serial Interface
Nov 8 16:43:24 newhr vmunix: Entering cifs_init...
Nov 8 16:43:24 newhr vmunix: Initialization finished successfully... slot is 9
Nov 8 16:43:24 newhr vmunix: Logical volume 64, 0x3 configured as ROOT
Nov 8 16:43:24 newhr vmunix: Logical volume 64, 0x2 configured as SWAP
Nov 8 16:43:24 newhr vmunix: Logical volume 64, 0x2 configured as DUMP
Nov 8 16:43:24 newhr vmunix: Swap device table: (start & size given in 512-byte blocks)
Nov 8 16:43:24 newhr vmunix: entry 0 - major is 64, minor is 0x2; start = 0, size = 4194304
Nov 8 16:43:24 newhr vmunix: Dump device table: (start & size given in 1-Kbyte blocks)
Nov 8 16:43:24 newhr vmunix: entry 0000000000000000 - major is 31, minor is 0x22000; start = 310112, size = 2097152
Nov 8 16:43:24 newhr vmunix: Starting the STREAMS daemons-phase 1
Nov 8 16:43:24 newhr vmunix: Create STCP device files
Nov 8 16:43:24 newhr vmunix: Starting the STREAMS daemons-phase 2
Nov 8 16:43:24 newhr vmunix: $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 $
Nov 8 16:43:24 newhr vmunix: Memory Information:
Nov 8 16:43:24 newhr vmunix: physical page size = 4096 bytes, logical page size = 4096 bytes
Nov 8 16:43:24 newhr vmunix: Physical: 8388608 Kbytes, lockable: 7738696 Kbytes, available: 7400672 Kbytes
Nov 8 16:43:24 newhr vmunix:
Nov 8 16:43:25 newhr nettl[523]: nettl starting up.
Nov 8 16:43:33 newhr rpcbind: check_netconfig: Found CLTS loopback transport
Nov 8 16:43:33 newhr rpcbind: check_netconfig: Found COTS loopback transport
Nov 8 16:43:33 newhr rpcbind: check_netconfig: Found COTS ORD loopback transport
Nov 8 16:43:33 newhr rpcbind: init_transport: check binding for udp
Nov 8 16:43:33 newhr rpcbind: init_transport: check binding for tcp
Nov 8 16:43:33 newhr rpcbind: init_transport: check binding for ticlts
Nov 8 16:43:33 newhr rpcbind: init_transport: check binding for ticotsord
Nov 8 16:43:33 newhr rpcbind: init_transport: check binding for ticots
Nov 8 16:43:33 newhr inetd[636]: Reading configuration
Nov 8 16:43:33 newhr inetd[636]: protocol = tcp
Nov 8 16:43:33 newhr inetd[636]: ftp/tcp: Added service, server /usr/lbin/ftpd
Nov 8 16:43:33 newhr inetd[636]: telnet/tcp: Added service, server /usr/lbin/telnetd
Nov 8 16:43:33 newhr inetd[636]: protocol = udp
Nov 8 16:43:33 newhr inetd[636]: tftp/udp: Added service, server /usr/lbin/tftpd
Nov 8 16:43:33 newhr inetd[636]: protocol = tcp

[Michael Schulte zur Sur]

Hi,

and where is the error?

greetings,

Michael

[john korterman]

Hi again,
one of the machines that I look after has similar lines in the syslog:

vmunix: Create STCP device files
$Revision: vmunix: vw: -proj
selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_b
l2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $

and I think that they have to do with inetd checking dead monitors to connect to registrar/tcp. It is the only thing that I find unusual, but it is probably not an error.

regards,
John K.

[Cem Tugrul]

Hi,

i had maintenance 2 days ago on Wednesday and
i only have done increase /opt file system.
and rebot at 16:45 pm and checked my oracle
was OK and also still everything is OK but
on the date;
Wed Nov 8 19:24:56 PST 2000
what had happened????
Do you all of you think that no need to be panic!!! if so wait your points :-)

Best Regards,

[Robert-Jan Goossens_1]

Hi Cem,

Just check if your server is running current date.

# date

if your server is not running the current date, you can use

# set_parms date_time

to correct this problem.

[Cem Tugrul]

hi,
newhr:/#date
Fri Nov 12 15:46:58 GMT 2004

baan01:/#date
Fri Nov 12 15:50:48 EET 2004

baan02:/#date
Fri Nov 12 15:44:17 EET 2004

baan03:/#date
Fri Nov 12 15:52:24 EET 2004

rp-5430 is newhr:/

[john korterman]

Hi cem and Robert-Jan,
The lines that I pasted in my previous post are authentic from one of the machines that I attend; you see the same date as from cem's machine. Apparently it is hard-coded information from a program and has no relation to the system's cutrent time setting.

Has noone else seen this?

regards,
John K.

[Pete Randall]

Nope!


Pete

[Robert-Jan Goossens_1]

Hi John and Cem,

Nope :-) just checked my rp54xx, seems to be bound a specific cpu or firmware revision.

Regards,
Robert-Jan

Ps. Cem check if you have an internal ntp device and sync your servers to one clock.

[Cem Tugrul]

hi,

i do not have any ntp...

[Robert-Jan Goossens_1]

check this thread for more info.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=245734

Best regards,
Robert-Jan

[Cem Tugrul]

Hi again,

Well..it is a good link... so do you think setting a ntp service solve my "undefine" dmesg message on my rp-5430...

Best Regards,

[Robert-Jan Goossens_1]

No :-)

just the time differences between your servers.

Best regards and a good weekend,

Robert-Jan

[Gerhard Roets]

build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $


You are talking about when this was built right ?

Regards
Gerhard

[Andrew Merritt_2]

The problem you appear to be asking about is a fixed date in a message put out by the kernel starting up. The whole line is:

Nov 8 16:43:24 newhr vmunix: $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 $

I don't think there is any error involved here. The date would appear to be the date that some section of the kernel was built.

Andrew

[Bill Hassell · Accepted solution]

Absolutely normal. If you change your HP terminal (or Reflection for HP) to 132 character width, then list syslog or dmesg, you'll see that the 'orphaned' date is on the same line Or if you only have dumb terminals, vi the file and you will see that it is part of the same line. Most terminals fold each line at column 80 which makes long lines confusing to read.

[Cem Tugrul]

Hi Again,

you all persuaded me this is not an error...
so i can close the thread...

thank's to All...

[Cem Tugrul]

decided it is not an error....