Portal won’t start ??

posted in: Technical | 2

I have come across a horrible little *feature* that occurs sometimes with WebSphere Portal where the server fails to start and writes absoutely nothing to the log … Just a tad annoying when you are trying to work out why it didn’t start in the first place.

Sometimes this is due to a tranlog problem which is pretty straight forward to resolve:
backup / delete the directory –
< profile root >/tranlog/cellname/nodename/servername

normally this will do the trick and a restart works – if it doesn’t do the following
rename the log folders (or delete them)

< profile root >/logs

to fix the issue that I had seen I had to rename the ffdc, nodeagent and portal server log directories

restart the servers in question and as if by magic it starts 🙂

I have experienced this at Portal 6.1.5 but I have had reports that this also appears to be a problem on 6.1.0.2 as well

2 Responses

  1. Andrew Frayling

    I was the 6.1.0.2 victim, but I didn't need to rename the nodeagent log directory, just the tranlog, ffdc and portal server log directories.

    We were seeing the issue on a vertically clustered server and node01 would start without any problems without renaming any log directories, but node02 wouldn't start until the above directories were renamed.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.