Could not connect to servers..

[lg1234]

Hi,

Could not connect to server..

We have livelink 9.5.0 installed in Solaris 9.

Yesterday is working.. and no changes were made to livelink.
All processes of livelink still work 'llserver & admserv' and I restarted livelink so many times but still having this error.

Does anyone can help me.

thanks.

 

[appnair]

a)Have you tried contacting OpenText support
b)Have you killed the processes comepletely in unix or are you relying on the shellscript to do that for you ?
c)From the same livelink machine can you thru some native method for eg(sqlplus) try to get to the database that ll needs to connect to?
d)Have you tried removing the patches from the patch directory and see if you can get basic livelink working and then re-applying patches one by one to rule out patch problems?
e)Do you have experience changing the debug lines in opentext.ini and trying to print out information?
f)Do you see trace logs if any in the logs directory?


Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[lg1234]

a) yes by email
b) I did both and even a reboot
c) yes database works
d) same problem
netstat -a |grep 2099
*.2099 *.* 0 0 49152 0 LISTEN
*.2099 *.* 0 0 49152 0 LISTEN

for 30 sec. after it disappear..

netstat -a | grep 2099
localhost.2099 localhost.63506 49152 0 49152 0 TIME_WAIT
localhost.2099 localhost.63508 49152 0 49152 0 TIME_WAIT
localhost.2099 localhost.63510 49152 0 49152 0 TIME_WAIT
localhost.2099 localhost.63512 49152 0 49152 0 TIME_WAIT

netstat -a | grep 2099
Exit 1

e) I don't know what to do for debug
f) I'm not sure which logs to look about it

thank you for responding.

 

[appnair]

In the path of your opentext install right under the main tree willl be a logs directory.In the same level will be a config directory.Inside there is a file called opentext.ini
(I don't know if they call it the same in unix)
make a copy of that file temporarily.
Inside there are sections

[general]
HaveValidatedSearchComponents=TRUE
HaveValidatedEnterpriseDataSource=TRUE
HaveValidatedReSyncPage=TRUE
HaveSeenModuleInstallPage=TRUE
dftConnection=NINEFIVESP1
AdminNewDBFlag=true
UploadDirectory=C:\OPENTEXT\temp\
NavigationOption=0
DisplayServerName=Nair's Livelink
adminpwd=LLjVQGt4I0juFWTxP31rf
version=13
LLIndexRequiresLogin=FALSE
LLIndexHTMLFile=llindex.html
DefaultRH=enterprise.home
DefaultContentRH=Enterprise.Home
Debug=0
continues....
[options]
wantLAPI=TRUE
WantDirectFetch=false
wantIcons=FALSE
errorMessageWantDebugInfo=FALSE
categoryNumToUpgrade=5
maxRightsString=250
wantByteServing=FALSE
wantDistributedSupport=FALSE
wantLogs=FALSE
wantSecureCookies=TRUE
wantTimings=TRUE
wantVerbose=TRUE
wantWeb=TRUE
EnableAgents=TRUE
EnableAgentsTrace=FALSE

Whenever you get into quandaries like this and are upto debugging it change Debug=2 or next level 11
Then say wantLogs=TRUE.Restart the server.Livelink will start throwing a lot of pertinent information in
thread1_out thread_2.out and connect_1.out in the logs directory .The numbers are dependent on the number of threads.The connects are showing you DB transactions and thraeds are showing you loading of ospaces or what not.Sometimes trace files occur and that is far most the most useful when trying a crash.One more thing if you run a prod server with debugg settings you will run out of space in no time,so sfater debug happens change it back out.





Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937