Login or Register to Ask a Question and Join Our Community


Solaris

Message in /var/adm

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Message in /var/adm
# 1  
Old 02-20-2013
Question Message in /var/adm
Good Morning..

Hello Everyone, I've been receiving this message in /Var/adm 2 days ago, I'm a new administrator for Solaris 10 and don't know what it means..

Thanks for your help

Here is the full message:

Code:
Feb 18 03:30:45 sun3000 ebus: [ID 521012 kern.info] se0 at ebus0: offset 1,400000
Feb 18 03:30:45 sun3000 genunix: [ID 936769 kern.info] se0 is /pci@9,700000/ebus@1/serial@1,400000
Feb 18 03:30:46 sun3000 ebus: [ID 521012 kern.info] gpio_873170 at ebus0: offset 1,300600
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] gpio_873170 is /pci@9,700000/ebus@1/gpio@1,300600
Feb 18 03:30:46 sun3000 ebus: [ID 521012 kern.info] su0 at ebus0: offset 1,3062f8
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] su0 is /pci@9,700000/ebus@1/rsc-control@1,3062f8
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: trapstat0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] trapstat0 is /pseudo/trapstat@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: mem_cache0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] mem_cache0 is /pseudo/mem_cache@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Feb 18 03:30:46 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: tod0
Feb 18 03:30:46 sun3000 genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Feb 18 03:30:47 sun3000 ebus: [ID 521012 kern.info] su1 at ebus0: offset 1,3083f8
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] su1 is /pci@9,700000/ebus@1/rsc-console@1,3083f8
Feb 18 03:30:47 sun3000 scsi: [ID 193665 kern.info] st20 at qus2: target 5 lun 0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] st20 is /pci@9,700000/pci@3/scsi@4/st@5,0
Feb 18 03:30:47 sun3000 scsi: [ID 365881 kern.info] /pci@9,700000/pci@3/scsi@4/st@5,0 (st20):
Feb 18 03:30:47 sun3000     <HP DDS-4 DAT (Sun)>
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Feb 18 03:30:47 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Feb 18 03:30:47 sun3000 scsi: [ID 799468 kern.info] ses0 at fp5: name w50800200001e1ba1,0, bus address dc
Feb 18 03:30:47 sun3000 genunix: [ID 936769 kern.info] ses0 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ses@w50800200001e1ba1,0
Feb 18 03:30:56 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(9): port attach failed
Feb 18 03:30:56 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(9): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:31:06 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(1): port attach failed
Feb 18 03:31:06 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(1): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:31:16 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(3): port attach failed
Feb 18 03:31:16 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(3): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:31:26 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(4): port attach failed
Feb 18 03:31:26 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(4): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:31:36 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(7): port attach failed
Feb 18 03:31:36 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(7): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:31:46 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(10): port attach failed
Feb 18 03:31:46 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(10): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:31:56 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(2): port attach failed
Feb 18 03:31:56 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(2): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:32:06 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(5): port attach failed
Feb 18 03:32:06 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(5): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:32:16 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(8): port attach failed
Feb 18 03:32:16 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(8): attach failed for SunFC FCIP v20100509-1.50
Feb 18 03:32:26 sun3000 fcip: [ID 842839 kern.warning] WARNING: fcip(0): port attach failed
Feb 18 03:32:26 sun3000 fctl: [ID 626979 kern.warning] WARNING: fctl(0): attach failed for SunFC FCIP v20100509-1.50
Feb 19 12:22:18 sun3000 ge: [ID 580805 kern.info] SUNW,pci-gem0: SUNW,pci-gem (Rev Id = 1) Found
Feb 19 12:22:18 sun3000 ge: [ID 580805 kern.info] SUNW,pci-gem0: Local Ethernet address = 0:3:ba:7b:20:77
Feb 19 12:22:18 sun3000 pcisch: [ID 370704 kern.info] PCI-device: network@1, ge0
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] ge0 is /pci@8,600000/network@1
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: llc10
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd0
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd0 is /pseudo/wrsmd@0
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd1
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd1 is /pseudo/wrsmd@1
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd2
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd2 is /pseudo/wrsmd@2
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd3
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd3 is /pseudo/wrsmd@3
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd4
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd4 is /pseudo/wrsmd@4
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd5
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd5 is /pseudo/wrsmd@5
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd6
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd6 is /pseudo/wrsmd@6
Feb 19 12:22:18 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd7
Feb 19 12:22:18 sun3000 genunix: [ID 936769 kern.info] wrsmd7 is /pseudo/wrsmd@7
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd8
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd8 is /pseudo/wrsmd@8
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd9
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd9 is /pseudo/wrsmd@9
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd10
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd10 is /pseudo/wrsmd@10
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd11
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd11 is /pseudo/wrsmd@11
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd12
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd12 is /pseudo/wrsmd@12
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd13
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd13 is /pseudo/wrsmd@13
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd14
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd14 is /pseudo/wrsmd@14
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd15
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] wrsmd15 is /pseudo/wrsmd@15
Feb 19 12:22:19 sun3000 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Feb 19 12:22:19 sun3000 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0

Last edited by Scrutinizer; 02-20-2013 at 10:52 AM.. Reason: code tags
# 2  
Old 02-22-2013
Which one in particular?
# 3  
Old 02-23-2013
Those are invents happening in your box. The kernel is just notifying you of them. If you have messages like kern.emerg or kern.critic you should definitely check those. If I where you, i will set up syslog not to send me info messages. Your file system will get full fast with all these info messages
# 4  
Old 02-26-2013
Thanks for your answers but, how can I do that configuration?
# 5  
Old 02-26-2013
There's an info line/area in syslog.conf, see Man Page for syslog.conf (opensolaris Section 4) - The UNIX and Linux Forums
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

/var/adm/messages (insterface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages Apr 22 16:43:05 Prod-App1 in.routed: interface net0 to 172.16.101.1 turned off Apr 22 16:43:33 Prod-App1 mac: NOTICE: nxge0 link up, 1000 Mbps, full duplex Apr 22 16:43:34 Prod-App1 mac: NOTICE: nxge0 link... (2 Replies)
Discussion started by: javeedkaleem
2 Replies

2. Solaris

/var/adm/messages (interface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# cat /var/adm//messages Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved Apr 20 08:24:18 Prod-App1... (0 Replies)
Discussion started by: javeedkaleem
0 Replies

3. Solaris

Mail loops back to me error in /var/adm/message after patching

Hi, I am getting the below messsage in /var/adm/message after patching but sendmail is working after restoring the backup file. sendmail: q4G7U1Cj014774: SYSERR(root): 127.0.0.1 config error: mail loops back to me (MX problem?) sendmail: q4G801cw025824: SYSERR(root): 127.0.0.1 config... (3 Replies)
Discussion started by: fayaz
3 Replies

4. Solaris

Getting continually error message in /var/adm/messages.

Hi Friends, Please help me to resove this issue ASAP. Nov 17 16:25:52 server1 sendmail: pAH8Pnh22099: SYSERR: putoutmsg (NO-HOST): error on output channel sending "553 5.1.3 @123.com.... User address required": File too large Nov 17 16:25:53 server1 sendmail: pAH8Pnh22099:... (1 Reply)
Discussion started by: holds_me
1 Replies

5. Solaris

diff b/w /var/log/syslog and /var/adm/messages

hi sirs can u tell the difference between /var/log/syslogs and /var/adm/messages in my working place i am having two servers. in one servers messages file is empty and syslog file is going on increasing.. and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies

6. UNIX for Advanced & Expert Users

separate "named daemon" message from /var/adm/messages

Hello group, How can I separate "named daemon" messages to the other file instead of /var/adm/messages. I still want all other daemons log the messages to /var/adm/messages. i.e. named => /var/adm/named.message other daemons => /var/adm/messages. I searched unix.com, and google but I still... (5 Replies)
Discussion started by: dannytrinh
5 Replies

7. Solaris

NRPE message in /var/adm/messages

Hi Guru's On one of our servers we have every few seconds following error: Apr 28 10:15:27 svr10010 nrpe: connect from reno.customs.govt.nz Apr 28 10:15:29 svr10010 nrpe: connect from reno.customs.govt.nz Here are the details from this box: SunOS svr10010 5.10 Generic_125100-10 sun4v... (3 Replies)
Discussion started by: gnom
3 Replies

8. UNIX for Advanced & Expert Users

an idea? /var/adm/message

hiho, my sun ultra1 print me in my /var/adm/message file: Aug 3 03:16:29 dazinger1 raid: AEN event = Host=3Ddazinger1 Ctrl=3D1T04359235 Dev=3Dc1t1d0 Aug 3 03:16:29 dazinger1 raid: ASC=3DA0 = ASCQ=3D00 FRU=3D00 LUN=3D00 LUN Stat=3D00 Aug 3 03:16:29 dazinger1 raid: =... (3 Replies)
Discussion started by: pressy
3 Replies

9. UNIX for Dummies Questions & Answers

HELP! The '/var/adm/message' file increase every few seconds???

Hi, guys, I have a big problem. I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It becomes a large file in a short time. I wander if there are some mistakes configuring the workstation. the /var/adm/message is as follow: ... (3 Replies)
Discussion started by: cloudsmell
3 Replies

10. Filesystems, Disks and Memory

HELP! The '/var/adm/message' file increase every few seconds???

Hi, guys, I have a big problem. I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It soon becomes a large file. I wander if there are some mistakes configuring the workstation. the /var/adm/message is as follow: ... (1 Reply)
Discussion started by: cloudsmell
1 Replies
Login or Register to Ask a Question