About the author
Christian Stottmeister is a technical projectmanager responsible for large website setups with a personal interest in security, web technology and projectmanagement issues. Contact information and more details about Stotti can be found here.
@cstottmeister on Twitter
- What you just saw whas the first tweet of my son. ;) At the same time it was my last tweet for the next two weeks. We're on vacation. Twitter 2010/07/24
- vce3434q2w33s37zthblxc te tr5 gtr5f Twitter 2010/07/24
- RT @xperseguers: Relatively unknown feature of #TYPO3: the trash in fileadmin: http://bit.ly/dvCK3k Your editors won't lose files anymore! Twitter 2010/07/21
- Had a nice evening at @GameDuell_DE's listening to @andremichelle. Thanks for the event! #gdtechtalk Twitter 2010/07/21
- Heading for #gdtechtalk at @@GameDuell_DE. Unfortunately we'll be a bit late. Twitter 2010/07/20
-
RSS Links
Most popular posts of last month
License
This work by Christian Stottmeister is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Germany.
sun fire v20z: service processor troubleshooting
i usually check the service processors (sp) of my machines quite frequently. recently i had several occurances regarding sp system events on different sun fire v20z servers. so let’s troubleshoot some of them.
[code]xxxxx-sp $ sp get events
ID Last Update Component Severity Message
2 11/27/2005 22:55 SP informational Error deserializing events
3 12/13/2005 12:11 SP informational Error deserializing events
[...]
9 08/07/2006 18:29 SP warning System event capacity exceeded. 0 events purged [0 critical, 0 warning, 0 informational], 194 historical records purged[/code]
what does this mean?
Error deserializing events
according to appendix b of the “Sun Fire V20z and Sun Fire V40z Servers Troubleshooting Techniques and Diagnostics Guide ” (sun no. 817-7184-12) this occurs while the system is not shutting down properly (see table b-31):
but i guess this cannot be the only reason for this (informational) error, because the system has an uptime of several hundred days – so it hasn’t been shut down. i don’t know where this comes from. perhaps some of my fellow readers know the exact cause and may leave a comment clarifiying the issue.
System event capacity exceeded
this is nothing to worry about. the internal memory that holds the event list is full and needs to flush so that it may contain more up-to-date entries. this warning occurs frequently, depending on the amount of other events.
..more to come..