Admin Index Server Problem

[baraqatax]

Guys, need your help.

I have problem with Admin Server Index which could not bind to port 5858 in PRD server. I got this message "SYSCNTL: Unable to bind to port [5858]" from admserv.log. Then I tried to change the port to 5828, but still the admin server index was failed to connect so I decided to change back the port to deafult 5858 port.

The strange thing is that when I view System Object status from admin.index, all the services weren't running, BUT the functionality of searching and indexing was running normally. After checking the configuration, I found inconsistency for admin server's port between opentext.ini (which has port 5828) and database kini table (which has port 5858).


Current situation is all the features in Livelink (upload, searching, indexing) SEEMS run normally eventhough the Admin Server Index couldn't bind to the 5858 port.

Do you have any idea what happens in my Livelink server?

 

[appnair]

I would first check if the RMI has any problem.You can do a function click on the default admin server and see if RMI has any problems.If it does not then classic reboot can be attempted which will free up any ports.If you understand networks very well you can see if some other process is binding on that port by doing netstat -an.

BTW 5858 is just an ephemeral port that OT chooses for installation you can choose any port that you seem fit.I would check if some other process is setup on the computer that is attacking the livelink admin server port.

Also there is no problem in running a resync on default which will write out database kini info to the admin server's file system.

Please if you can ,do not run any other virus scanners etc on that box if you don't want to be alwsy bothered with search problems.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[baraqatax]

I've checked the RMI & Document Conversion Service, the status is "Admin Server Error: Connect failed". Also, I've checked nestat -an from the server, there is no other process which binds the (5858) port and the 5858 port is unassigned.

I tried to resync the admin server, but still it could not connect. FYI, the Livelink 9.7.1 runs on physical server (Win Server 2003). Is the security patch from Windows may impact the Livelink?

This issue is really confusing me since the Livelink Admin GUI told me that the admin server is not running, but all the functionality (including searching & indexing) can be executed normally. Weird!

 

[appnair]

The admin server is responsible to keep all the other pieces running.If your update distributor or search engine now has a problem heaven forbid when you go and say you want to do maintenance then you will get the same error 'Admin' is having problems.Each of the about 18 processes runs windows executables that binds to different ports.So it is not unusual to see what you describe.For your peace of mind I would stress that you make sure that there are absolutely no errors and all the processes are running and healthy.It could be a recent windows patch,virus check etc etc that broke it.I would actually get OT support to assiste you as a non working admin server could potentially land you in deep trouble.BTW is the default admin server the box name itself or the IP address of the server.Do you have more than one admin server.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair