nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Server disconnected errors

developer2008

MyTS server is TS6.7.1 on Solaris without LDAP.I am getting these "server disconneted" errors daily and have to restart server daily. Is it ok to restart the server daily and how to restrict the domains using a domain controller? Any help?

Find more posts tagged with

Comments

nipper

MyTS server is TS6.7.1 on Solaris without LDAP.I am getting these "server disconneted" errors daily and have to restart server daily. Is it ok to restart the server daily and how to restrict the domains using a domain controller? Any help?

This is bad. Very bad. I need to reboot by Win2003 server once a month or so, Solaris should be much more stable than that.

First open a case with support.

2nd, are you talking the TS server daemon itself that you need to restart ? What do the logs show ? What rev of Solaris are you running ?

developer2008

Yeah the TS server itself and the log shows "login daemon is down or invalid password" .Do you need to specify anything in authentication of iw.cfg> If you dont specify anything under authentication what will it be by default?

nipper

No, TS should be running as root. The processes are on the disk with the setiud flag active, so they will run as root.

Do you have SW that looks for setuid files or processes ?

If you do not specify anything on authentication, it should default to /etc/password

developer2008

>>>>>"Do you have SW that looks for setuid files or processes ? "

What SW are you talking about ?

Do you think by any chance leaving out [authentication] blank do any of these errors occur. I did check that there is /etc/passwd

nipper

some IT departments have programs that run, looking for other software that is setuid to run as root and will disable them or kill active processes running as root. That will break TS because some daemons must run as root.

Also, do you have a shadow password file ?

None of these issues should kill TS, so I am wondering about the integrity of the install.

developer2008

I did read about this shadow password file in the administration guide but I dont know where to look for it

nipper

Talk to your Solaris admin about it.

it should be

/etc/shadow

and readable only by root. One of the serious security Unix USED to have was a world readable encoded password. If you got on a system with a guest password, you could copy /etc/password to your local system and have it try to crack the root password.

This article may help

developer2008

That was really good article.We did open an issue and my solaris version is 5.10 .We do have /etc/shadow but i dont have access to it.Meanwhile can I look for anything else to understand the issue better

exemple3.png

chicka

I faced this issue but this issue was not faced after installing SP1 on TS 6.7.1 on Solaris. Please validate this with Interwoven Support team.