Topic: Server Manager Not Available

[AlistairH]

Today I've been installing available updates on three SME 7.1 servers at a client's. These machines, upgraded from version 6.5 have been rock solid since they were installed over a year ago and I've never had to look at them.

Therein lies the problem in that my lack of experience is holding me back on where to look to correct the following problem:

One of the servers seems to have stopped the web server-manager. When ever I try to access it I get a server not found or DNS error web page. The server is definitely available as I can ping it and all users have network access to the i-bays.

Can someone point me in the right direction as to where to look to sort it?

Please note that I'm only in this client's office once a week so apologies in advance if I do not get back to you today.

Thanks

Alistair

[skydivers]

Are both http servers running?

Code:
/etc/rc7.d/httpd-e-smith status

Code:
/etc/rc7.d/httpd-admin status

[AlistairH]

Are both http servers running?

Code:
/etc/rc7.d/httpd-e-smith status

Code:
/etc/rc7.d/httpd-admin status

Sorry for taking so long to get back to you. I'm only ever at this client once a week.

I couldn't get the above commands to work, assuming I'm not doing something stupid which is always a distinct possibility.

When logged in as root, both these commands produced the following message...

Code: [Select]

no such file or directory

I cd'd down into the rc7.d directory and did an ls which returned, amongst other things:

Code: [Select]

S86httpd-admin
S86httpd-e-smith

Not sure what the S86 means

From here, doing

Code: [Select]

httpd-e-smith status produced a bash error message:

Code: [Select]

command not found

Doing the same with httpd-admin simply lists the syntax help for httpd-admin. From this I tried:

Code: [Select]

httpd-admin -k start

Which didn't give me any feedback at all, but checking from another machine did not make the server-manager interface available.

Code: [Select]

httpd-admin -k restart

only gave me the following feedback:

Code: [Select]

httpd not running, trying to start

I'm now at a loss what to do next and still seeking guidance.

Unfortunately, I won't be around for another week. The server itself is providing the functionality the users' need. It's just that I cannot get to the server-manager web interface. As a result, I cannot modify user accounts, upgrade software etc. I'm sure there are command line ways of doing so but I am not familiar with them so I'd dearly like to get this sorted out. Even if it does take a week to exchange each forum message.

Thanks for your patience

Alistair

[skydivers]

You should take it to the bugtracker.

In the meanwhile you can try to make/update some users by using the console. Log in as admin with putty. From their on you could try to reach the server-manager.

[cactus]

Are both http servers running?

Code:
/etc/rc7.d/httpd-e-smith status

Code:
/etc/rc7.d/httpd-admin status

[...]

When logged in as root, both these commands produced the following message...

Code: [Select]

no such file or directory

I cd'd down into the rc7.d directory and did an ls which returned, amongst other things:

Code: [Select]

S86httpd-admin
S86httpd-e-smith

Not sure what the S86 means

The S86 determines the startup sequence of all things in the list.

What happens when you issue the commands with the S86 infront like so:

Code: [Select]

/etc/rc7.d/S86httpd-e-smith status
/etc/rc7.d/S86httpd-admin status

[AlistairH]

Hi cactus

Putting the S86 in front as you describe simply results in a 'command not found' error message.

[Confucius]

try it with :

Code: [Select]


service httpd-admin restart


[cactus]

Hi cactus

Putting the S86 in front as you describe simply results in a 'command not found' error message.

Strange, my SME Server 7.1 does the following OK:

Code: [Select]

[root@homer ~]# /etc/rc7.d/S86httpd-e-smith restart
Restarting httpd-e-smith                                   [  OK  ]
[root@homer ~]#

[AlistairH]

Sorry for the long delay in posting a resolution to this. I was never able to establish what was wrong but I got everything back to normal by booting to the installation CD and choosing the upgrade option. The installation process didn't do much and finished a few seconds later but it seemed to kick start things again and I can now access the server manager through a browser.

As the issue was not a major one, I doubt that I'll ever establish the cause. Thanks to all for your input anyway.

[TrevorB]

As the issue was not a major one, I doubt that I'll ever establish the cause.

Hmmm...  To make sure you don't have this issue again..

These machines, upgraded from version 6.5 have been rock solid since they were installed over a year ago and I've never had to look at them.

Then very likely they do NOT have all of the correct repositories available and you WILL encounter this error again

Note:
A system installed from the SME 7.1 CD will have the 5 repositories above enabled. A system installed from the SME 7.0 iso and updated to 7.1 or later will only have the 3 SME Server repositories enabled. After updating from SME 7.0 to SME 7.1.x you should enable the Centos - os & Centos - updates repositories in server-manager.

You can check this by

Code: [Select]

db yum_repositories show base
db yum_repositories show updatesIf the status on either/both is disabled, the please read the Updating from SME 7.0 or 7.1 to SME 7.2 section of the FAQ

Trevor B

[AlistairH]

Thanks for that Trevor. I'll check next time I'm visiting that client's site - probably next Tuesday.

Cheers