Koozali.org: home of the SME Server

Cant access server-manager

Cant access server-manager
« on: October 29, 2010, 02:44:06 PM »
Hey, I'm using an SME-server mounted on a VMWare Workstation hosted by a windows 7.

I use a bridged connection between the SME-server and a virtual interface at windows side and I get SSH management access OK.

Eventhough, I seem to get access to the server-manager only rough the elinks.

Plus, I ran the commands bellow without problems:
>sv /t/service/httpd-e-smith
and
>sv /t/service/httpd

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Cant access server-manager
« Reply #1 on: October 29, 2010, 05:57:11 PM »
Hey, I'm using an SME-server mounted on a VMWare Workstation hosted by a windows 7.

I use a bridged connection between the SME-server and a virtual interface at windows side and I get SSH management access OK.

Eventhough, I seem to get access to the server-manager only rough the elinks.
Did you already look at the logfiles (/var/log/httpd/admin_error_log, /var/log/httpd/admin_access_log and /var/log/httpd/error_log and perhaps /var/log/httpd/access_log) to see if a connection is made from outside of your VMWare machine or perhaps something is not properly configured?

How did you configure your VMWare machine? Is it a server-gateway or a server-only configuration? If it is the first did you allow the external network access to the server-manager by enabling the ip in the remote management section of the Remote Management tab? If it is the latter are your virtual server (guest) and your PC (host) in the same subnet?

Plus, I ran the commands bellow without problems:
>sv /t/service/httpd-e-smith
and
>sv /t/service/httpd
Why did you run them, first of all they are faulty, second of all they will only restart your web server when executed properly:
Code: [Select]
sv t httpd-e-smith
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Re: Cant access server-manager
« Reply #2 on: October 29, 2010, 06:38:08 PM »
I've looI looked at the log files, the only one which had understandebla information was the error log, having repeated a warning:

[notice] Apache configured -- resuming normal operations
[notice] caught SIGTERM, shutting down
[warn] RSA server certificate CommonName (CN) `nagiux.prologica.local' does NOT match server name!?
[notice] Digest: generating secret for digest authentication ...
[notice] Digest: done

Is it it?

I installed the SME-Server (on the VMWare) in server-only mode and it is in the same subnet as the virtual NIC (Network Interface Card) as the one emulated by the VMWare in the windows side, in which there is a physical NIC sharing it's internet connection with the VMWare subnet.

Avout the sv command, I ran those because I saw them in this forum, being sugested for the same problem I'm having.

[root@nagiux ~]# sv -v t httpd-e-smith
ok: run: httpd-e-smith: (pid 5835) 0s, normally down


I think it is very strange that I get SSH access from windows side but not HTTPS access

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Cant access server-manager
« Reply #3 on: October 29, 2010, 06:41:37 PM »
Do you see connections in the /var/log/httpd/*_access_log files from the external IP you are connecting from?

Are you able to connect from your host system to the normal webserver port on your virtual server (http://ip/)?
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Re: Cant access server-manager
« Reply #4 on: October 29, 2010, 06:58:37 PM »
Well, I re-checked the /var/log/httpd/admin-error-log and there were errors and warnings :(

[error] [client 127.0.0.1] Use of uninitialized value in hash element at /usr/lib/perl5/site_perl/CGI/FormMagick/HTML.pm line 306., referer: https://localhost/server-manager/navigation
[notice] caught SIGTERM, shutting down
[warn] Init: Session Cache is not configured [hint: SSLSessionCache]

About the /var/log/httpd/*-access-log files, They only had entries for the localhost except for a phew from some other IP address in the SME-server subnet which I guess is from some service within the SME
prologica.local 192.168.115.243 - - [27/Oct/2010:12:45:48 +0100] "GET /wpad.dat HTTP/1.1" 200 302 "-" "-"

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Cant access server-manager
« Reply #5 on: October 29, 2010, 07:12:48 PM »
Well, I re-checked the /var/log/httpd/admin-error-log and there were errors and warnings :(

[error] [client 127.0.0.1] Use of uninitialized value in hash element at /usr/lib/perl5/site_perl/CGI/FormMagick/HTML.pm line 306., referer: https://localhost/server-manager/navigation
[notice] caught SIGTERM, shutting down
[warn] Init: Session Cache is not configured [hint: SSLSessionCache]
That looks like something might have gone wrong (SIGTERM), but it could also be the result of your actions trying to restart your webserver, please post more context.
Is the httpd-admin service running? Please check using the following command (and post the output):
Code: [Select]
sv s httpd-admin
Are there any more error messages in your configuration files? Please check using the following command (and post the output):
Code: [Select]
httpd -t
httpd-admin -t

About the /var/log/httpd/*-access-log files, They only had entries for the localhost except for a phew from some other IP address in the SME-server subnet which I guess is from some service within the SME
prologica.local 192.168.115.243 - - [27/Oct/2010:12:45:48 +0100] "GET /wpad.dat HTTP/1.1" 200 302 "-" "-"
Please do not assume and post them. Also please answer as extensively as you can, without dropping data from your logs, the lines from the access_log and error_log should be timestamped.

The IP you are seeing is most likely an IP somewhere in your network accessing the server, local actions from SME Server are done using local loopback IP or localhost.

Is the time of above log entry perhaps the time you tried to access your server from your host machine?
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Re: Cant access server-manager
« Reply #6 on: October 29, 2010, 07:31:39 PM »
I guess it is ok
[root@nagiux ~]# httpd-admin -t
Syntax OK
[root@nagiux ~]# httpd -t
Syntax OK

From the file /var/log/httpd/access_log.20101027103404 (Last phew Lines):
prologica.local localhost - - [29/Oct/2010:17:42:42 +0100] "POST /server-common/cgi-bin/login HTTP/1.1" 200 387 "https://localhost/server-common/cgi-bin/login?redirect=1&back=https%3A%2F%2Flocalhost%2Fserver-manager" "ELinks/0.9.2 (textmode; Linux; 80x25)"
prologica.local localhost - - [29/Oct/2010:17:42:43 +0100] "GET /server-manager HTTP/1.1" 301 244 "https://localhost/server-common/cgi-bin/login" "ELinks/0.9.2 (textmode; Linux; 80x25)"
prologica.local localhost - - [29/Oct/2010:17:42:43 +0100] "GET /server-manager/ HTTP/1.1" 200 1561 "https://localhost/server-manager" "ELinks/0.9.2 (textmode; Linux; 80x25)"
prologica.local localhost - - [29/Oct/2010:17:42:46 +0100] "GET /server-manager/navigation HTTP/1.1" 200 6951 "-" "ELinks/0.9.2 (textmode; Linux; 80x25)"
prologica.local localhost - - [29/Oct/2010:17:42:48 +0100] "GET /server-manager/header.htm HTTP/1.1" 200 2093 "-" "ELinks/0.9.2 (textmode; Linux; 80x25)"
prologica.local localhost - - [29/Oct/2010:17:42:46 +0100] "GET /server-manager/initial.cgi HTTP/1.1" 200 2422 "-" "ELinks/0.9.2 (textmode; Linux; 80x25)"
prologica.local localhost - - [29/Oct/2010:17:43:07 +0100] "GET /server-manager/cgi-bin/review HTTP/1.1" 200 2989 "https://localhost/server-manager/navigation" "ELinks/0.9.2 (textmode; Linux; 80x25)"

From the /var/log/admin_access_log.20101027103404 (Last phew Lines):
127.0.0.1 - - [29/Oct/2010:17:42:33 +0100] "GET /server-manager HTTP/1.1" 307 283
127.0.0.1 - - [29/Oct/2010:17:42:34 +0100] "GET /server-common/cgi-bin/login?back=http%3a%2f%2flocalhost%2fserver-manager HTTP/1.1" 200 430
127.0.0.1 - - [29/Oct/2010:17:42:35 +0100] "GET /server-common/cgi-bin/login?redirect=1&back=https%3A%2F%2Flocalhost%2Fserver-manager HTTP/1.1" 200 1045
127.0.0.1 - - [29/Oct/2010:17:42:42 +0100] "POST /server-common/cgi-bin/login HTTP/1.1" 200 387
127.0.0.1 - admin [29/Oct/2010:17:42:43 +0100] "GET /server-manager HTTP/1.1" 301 244
127.0.0.1 - admin [29/Oct/2010:17:42:43 +0100] "GET /server-manager/ HTTP/1.1" 200 1561
127.0.0.1 - admin [29/Oct/2010:17:42:46 +0100] "GET /server-manager/navigation HTTP/1.1" 200 6951
127.0.0.1 - admin [29/Oct/2010:17:42:48 +0100] "GET /server-manager/header.htm HTTP/1.1" 200 2093
127.0.0.1 - admin [29/Oct/2010:17:42:46 +0100] "GET /server-manager/initial.cgi HTTP/1.1" 200 2422
127.0.0.1 - admin [29/Oct/2010:17:43:07 +0100] "GET /server-manager/cgi-bin/review HTTP/1.1" 200 2989

I'm guessing those are all from access using the elink.

The first Lines of the file /var/log/httpd/access_log.20101027103404:
prologica.local 192.168.115.243 - - [27/Oct/2010:12:45:48 +0100] "GET /wpad.dat HTTP/1.1" 200 302 "-" "-"
prologica.local 192.168.115.243 - - [27/Oct/2010:12:46:24 +0100] "GET /wpad.dat HTTP/1.1" 200 302 "-" "-"
prologica.local 192.168.115.243 - - [27/Oct/2010:12:46:29 +0100] "GET /wpad.dat HTTP/1.1" 200 302 "-" "-"