I have a very old Sun Solaris Server running on on SPARC platform
# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 09 June 2006
Running an old java application server on it
$ asadmin version
Unable to communicate with admin server, getting version locally.
Version = Sun Java System Application Server Platform Edition 8.2
Command version executed successfully.
We had a planned power shut at our office so we needed to shut the servers down for few hours, after the shut down window, I started the servers - servers boot successfully but while starting the application server i was getting output "null" the server even was not writing any logs to the server.log file
asadmin> start-domain
Starting Domain domain1, please wait.
Log redirected to /xyz/SUNWappserver/domains/domain1/logs/server.log.
null
$
It was a nightmare that I could not even get clue of the problem so that i can google and resolve, additionally not being an application and linux guy it only worsen the situation and it took me days to reach the at the unexpected root cause of the problem that was crashing the application and not allowing even to write logs.
The issue with application server was that it had exhausted inode limits of the file system. And I confirmed it with this command.
$ df -oi /
Filesystem iused ifree %iused Mounted on
/dev/md/dsk/d0 2486848 0 100% /
To resolve the issue off course I needed to find the unwanted files and delete them to free up inode capacity for the file system. And for that my main target was all log folders in the servers. Exploring the log folders I found millions of small log files which were created since the server was installed and running for years.
After finding and deleting millions of log files in different log folders in the server (mainly in /xyz/SUNWappserver/domains/domain1/logs and /var/logs) I reduced the inode usage below 30% and after that the applications was started like a charm.
During this troubleshooting I learnt importance of the backup and how to backup domain :-)
# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 09 June 2006
Running an old java application server on it
$ asadmin version
Unable to communicate with admin server, getting version locally.
Version = Sun Java System Application Server Platform Edition 8.2
Command version executed successfully.
asadmin> start-domain
Starting Domain domain1, please wait.
Log redirected to /xyz/SUNWappserver/domains/domain1/logs/server.log.
null
$
It was a nightmare that I could not even get clue of the problem so that i can google and resolve, additionally not being an application and linux guy it only worsen the situation and it took me days to reach the at the unexpected root cause of the problem that was crashing the application and not allowing even to write logs.
The issue with application server was that it had exhausted inode limits of the file system. And I confirmed it with this command.
$ df -oi /
Filesystem iused ifree %iused Mounted on
/dev/md/dsk/d0 2486848 0 100% /
To resolve the issue off course I needed to find the unwanted files and delete them to free up inode capacity for the file system. And for that my main target was all log folders in the servers. Exploring the log folders I found millions of small log files which were created since the server was installed and running for years.
After finding and deleting millions of log files in different log folders in the server (mainly in /xyz/SUNWappserver/domains/domain1/logs and /var/logs) I reduced the inode usage below 30% and after that the applications was started like a charm.
During this troubleshooting I learnt importance of the backup and how to backup domain :-)
Comments
Post a Comment