- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Syslog Error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 04:46 PM
тАО12-10-2003 04:46 PM
Nov 19 16:03:39 HP2000 ftpd[2681]: exiting on signal 14
Nov 19 17:07:49 HP2000 ftpd[4886]: FTP LOGIN FROM 128.128.100.49 [128.128.100.49], oracle
Nov 19 17:09:16 HP2000 ftpd[4886]: FTP session closed
Nov 20 14:42:00 HP2000 su: + tb root-oracle
Nov 24 13:43:42 HP2000 su: + tc root-jdeb7333
Nov 24 13:44:13 HP2000 ftpd[1799]: FTP LOGIN FROM 128.128.100.179 [128.128.100.179], root
Nov 24 14:08:38 HP2000 ftpd[1799]: FTP session closed
Dec 5 09:45:41 HP2000 ftpd[3548]: FTP LOGIN FROM 128.128.1.200 [128.128.1.200], root
Dec 5 09:45:53 HP2000 ftpd[3548]: FTP session closed
Dec 9 12:46:59 HP2000 EMS [1988]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/system/events/core_hw/core_hw" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 130285570 -r /system/events/core_hw/core_hw -n 130285569 -a
What's wrong? who can help me?
10 points will be yours for good answers.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 04:51 PM
тАО12-10-2003 04:51 PM
Re: Syslog Error
Also did you run this as specified
#/opt/resmon/bin/resdata -R 130285570 -r /system/events/core_hw/core_hw -n 130285569 -a
Revert back
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 04:56 PM
тАО12-10-2003 04:56 PM
Re: Syslog Error
It looks like you have H/W problem so need to verify which problem was occured.
Have a look at the " evenlog " from EMS in /var/opt/resmon/logs/
It will be more detailed information and what action you need on the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 04:56 PM
тАО12-10-2003 04:56 PM
Re: Syslog Error
/opt/resmon/bin/resdata -R 130285570 -r /system/events/core_hw/core_hw -n 130285569 -a
but nothing happened.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 05:00 PM
тАО12-10-2003 05:00 PM
Re: Syslog Error
/var/opt/resmon/log
# ll
total 8216
lrwxr-xr-x 1 bin bin 27 Nov 1 2001 api.log -> /etc/opt/resmon/log/api.log
lrwxr-xr-x 1 bin bin 30 Nov 1 2001 client.log -> /etc/opt/resmon/log/client.log
-rw-r--r-- 1 root root 136103 Dec 9 12:46 event.log
-r--r----- 1 root root 501860 Sep 1 2002 event.log1
-r--r----- 1 root root 500063 Feb 21 2003 event.log2
-r--r----- 1 root root 500564 Mar 3 2003 event.log3
-r--r----- 1 root root 501182 Mar 4 2003 event.log4
-r--r----- 1 root root 505905 Mar 12 2003 event.log5
-r--r----- 1 root root 500835 Mar 24 2003 event.log6
-r--r----- 1 root root 500534 Apr 2 2003 event.log7
-r--r----- 1 root root 505209 Apr 3 2003 event.log8
lrwxr-xr-x 1 bin bin 33 Nov 1 2001 registrar.log -> /etc/opt/resmon/log/registrar.log
#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 05:08 PM
тАО12-10-2003 05:08 PM
Re: Syslog Error
Open the eventlog and check it what happened.
-rw-r--r-- 1 root root 136103 Dec 9 12:46 event.log
# vi eventlog
any problem??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 05:21 PM
тАО12-10-2003 05:21 PM
Re: Syslog Error
Notification Time: Tue Dec 9 12:46:59 2003
HP2000 sent Event Monitor notification information:
/system/events/core_hw/core_hw is >= 1.
Its current value is SERIOUS(4).
Event data from monitor:
Event Time..........: Tue Dec 9 12:46:59 2003
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: HP2000
Summary:
Service processor not responding
Description of Error:
The operating system is unable to communicate with the service processor.
Probable Cause / Recommended Action:
The support bus which connects the system processors, the service
processor and the Power Monitor or Platform Monitor may have become hung.
(The support bus can be tested by issuing the service processor command
"XD", and selecting the I2C access test).
To reset the bus, issue the service processor command "XD" and then
select "R", use the HP-UX command `stty +resetGSP press the service processor reset button. If this solves the problem
(if the I2C access test now works) and the system is an N-Class,
rp7400, L-Class, rp5400, rp5430, rp5450 or rp5470, check the service
processor firmware revision using the service processor command "HE".
If the service processor firmware version is less than A.01.09,
schedule an update of the service processor firmware to version
A.01.09 or a more recent version to prevent a reoccurrence of this
problem.
There could be a problem with the service processor.
Verify that the service processor appears to be operating normally.
This can be done by typing a
that the service processor responds to commands. If the service
processor has failed, contact your HP support representative to check
the core I/O board.
There could be a problem with the system board.
Contact your HP support representative to check the system board if
necessary.
Additional Event Data:
System IP Address...: 128.128.105.105
Event Id............: 0x3fd553c300000000
Monitor Version.....: B.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_core_hw.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x3fd553c300000000
Additional System Data:
System Model Number.............: 9000/800/L2000-44
EMS Version.....................: A.03.20
STM Version.....................: A.28.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_core_hw.htm#32
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
FRU Physical Location: 0xffffffffffffff00
FRU Source = 0 (unknown, no source stated)
Source Detail = 0 (unknown, no source stated)
Cannot decode any remaining physical location data.
>---------- End Event Monitoring Service Event Notification ----------<
#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 05:26 PM
тАО12-10-2003 05:26 PM
Re: Syslog Error
The core_hw EMS error looks like a temperature alarm to me.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 05:27 PM
тАО12-10-2003 05:27 PM
Re: Syslog Error
The service processor errors can be ignored. WE have not been able to fix this error even after we did everything the hp guys told us to do. Now we simply ignore the service processor not responding errors.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2003 05:32 PM
тАО12-10-2003 05:32 PM
Re: Syslog Error
>> To reset the bus, issue the service processor command "XD" and then
select "R", use the HP-UX command `stty +resetGSP press the service processor reset button. <<
After then Update the firmware of GSP (guardian service processor) that download it trough http://us-support3.external.hp.com/wpsl/bin/doc.pl/sid=207c10ef0a844b545c/screen=wpslSelectPlatform
>> If this solves the problem
(if the I2C access test now works) and the system is an N-Class,
rp7400, L-Class, rp5400, rp5430, rp5450 or rp5470, check the service
processor firmware revision using the service processor command "HE".
If the service processor firmware version is less than A.01.09,
schedule an update of the service processor firmware to version
A.01.09 or a more recent version to prevent a reoccurrence of this
problem. <<
I guess that the version of GSP(Guardian Service Processor) is too lower more than newest that's main reason.
good luck!