You've installed Sametime 8.5, it isn't working, what now?
Category Sametime Logs
You were really excited, you downloaded Sametime 8.5, purchased additional hardware and installed it. But there are problems, it doesn't seem to work, how do you get a clue as to what's going on?
Each of the Sametime 8.5 server components do create log files, sadly there isn't like a single location for them they are spread all over the place. The Sametime 8.5 Infocenter will tell you the location of the log files, but erhm, that document is incorrect, if you were running Sametime 8.5 beta 3 it would be correct but for shipping sametime it's incorrect.
Here is close to where you can actually find them (~~~~~ is short server name for the machine they are installed on):
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaDMProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaDMProfile1\logs\dmgr\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\ffdc\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\nodeagent\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\STMediaServer\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingDMProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingDMProfile1\logs\dmgr\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\STMeetingServer\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\STMeetingHttpProxy\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\nodeagent\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~ProxyDMProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~ProxyDMProfile1\logs\dmgr\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~ProxyPNProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\STConsoleServer\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\nodeagent\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\ffdc\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\logs\ffdc\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\logs\dmgr\*.*
Now in each of these locations, you aren't going to find a single log file, you will find lots of them, typically the ones to look in are the SystemOut.Log and SystemErr.Log, rad through the log files for the component you are having issues with to try and find the cause.
You were really excited, you downloaded Sametime 8.5, purchased additional hardware and installed it. But there are problems, it doesn't seem to work, how do you get a clue as to what's going on?
Each of the Sametime 8.5 server components do create log files, sadly there isn't like a single location for them they are spread all over the place. The Sametime 8.5 Infocenter will tell you the location of the log files, but erhm, that document is incorrect, if you were running Sametime 8.5 beta 3 it would be correct but for shipping sametime it's incorrect.
Here is close to where you can actually find them (~~~~~ is short server name for the machine they are installed on):
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaDMProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaDMProfile1\logs\dmgr\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\ffdc\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\nodeagent\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MediaPNProfile1\logs\STMediaServer\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingDMProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingDMProfile1\logs\dmgr\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\STMeetingServer\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\STMeetingHttpProxy\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~MeetingPNProfile1\logs\nodeagent\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~ProxyDMProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~ProxyDMProfile1\logs\dmgr\*.*
C:\IBM\WebSphere\AppServer\profiles\~~~~~ProxyPNProfile1\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\STConsoleServer\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\nodeagent\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\ffdc\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\logs\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\logs\ffdc\*.*
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\logs\dmgr\*.*
Now in each of these locations, you aren't going to find a single log file, you will find lots of them, typically the ones to look in are the SystemOut.Log and SystemErr.Log, rad through the log files for the component you are having issues with to try and find the cause.
Comments
I would be more than happy to upgrade but we are not allowed to purchase any new hardware this year.
Posted by Mark Hughes At 12:42:20 PM On 01/06/2010 | - Website - |
Posted by Keith Brooks At 01:59:43 PM On 01/06/2010 | - Website - |
minimum 5 servers. with a mix of Domino, Websphere, LDAP, and DB2. (Chat, meeting, Console, Proxy, A/V...)
It couldn't be more simple...
Will see how long it will take to have it working correctly in production...
Posted by vince At 04:25:41 PM On 01/18/2010 | - Website - |
{ Link }
It only took us 2 hours of effort to set the server up + the time it took for our Server Management group to provision the servers required for this pilot.
Regards,
Ash Daga
Posted by Ashish Dag At 06:04:00 PM On 06/04/2010 | - Website - |