Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: clnsupport on September 12, 2007, 08:59:40 AM
-
Hi all,
I’ve basically killed m my /server-manager/ please help.
What I did:
I opened /server-manager/ and typed in an ip range under remote management BUT had some finger problems and put a .(dot) at the end of the ip (something like 41.0.0.0. ) and now I cant get back into my /server-manager/.
I’ve read the forum and tried this post
http://forums.contribs.org/index.php?topic=33171.0
but it didn’t work. Ive also replaced my httpd.conf file rom a backup but that also didn’t fix it.
I cant access the server-manager via ssh and it look like my httpd won’t start
PLEASE help!
-
I dont actually think you killed the server manager. I think there was a bad update round about two days ago... My server-manager doesn't start either...
-
not sure if its just an update because i replicated it on a spare PC and it did the same without doing any updates. i need to know what file(s) to edit to get back into server-manager. I've edited /etc/httpd/conf/httpd.conf and fixed the ip probelm in the file. i could start httpd and it ran for a little bit but then it stopped again. then i did a signal-event domain-modify but it replaced the edited file with the faulty one.
-
Have you tried yum update httpd ?
-
yes, didn't fix it. Did it fix our problem?
when i look at the service status:
[root@testserver ~]# /etc/init.d/httpd status
httpd (pid 15627) is running...
[root@testserver ~]# /etc/init.d/httpd status
httpd dead but pid file exists
[root@testserver ~]# /etc/init.d/httpd status
httpd dead but pid file exists
The error log:
[root@testserver ~]# tail /var/log/httpd/error_log
[Wed Sep 12 05:55:21 2007] [notice] Digest: done
[Wed Sep 12 05:55:21 2007] [warn] RSA server certificate CommonName (CN) `testserver.test.co.za' does NOT match server name!?
[Wed Sep 12 05:55:21 2007] [warn] pid file /var/run/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Sep 12 05:55:21 2007] [crit] (17)File exists: unable to create scoreboard "/var/run/httpd.scoreboard" (name-based shared memory failure)
[Wed Sep 12 05:55:23 2007] [warn] RSA server certificate CommonName (CN) `testserver.test.co.za' does NOT match server name!?
[Wed Sep 12 05:55:23 2007] [notice] Digest: generating secret for digest authentication ...
[Wed Sep 12 05:55:23 2007] [notice] Digest: done
[Wed Sep 12 05:55:23 2007] [warn] RSA server certificate CommonName (CN) `testserver.test.co.za' does NOT match server name!?
[Wed Sep 12 05:55:23 2007] [warn] pid file /var/run/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Sep 12 05:55:23 2007] [crit] (17)File exists: unable to create scoreboard "/var/run/httpd.scoreboard" (name-based shared memory failure)
-
Try running "console" from putty(ssh) and Reconfigure your server... To ensure all name entries are correct...
-
didn't work. what file must i edit to get rid of the ip (41.0.0.1.) giving me problems. every time i reconfigure the server it puts the ip back in /etc/httpd/conf/httpd.conf !!!
-
when i go in with 'console' and go to 'Access sever manager' i get "connection refused"
-
[root@test init.d]# tail /var/log/httpd/error_log
[Wed Sep 12 06:04:51 2007] [warn] pid file /var/run/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Sep 12 06:04:51 2007] [crit] (17)File exists: unable to create scoreboard "/var/run/httpd.scoreboard" (name-based shared memory failure)
[Wed Sep 12 06:04:51 2007] [warn] RSA server certificate CommonName (CN) `testserver.test.co.za' does NOT match server name!?
[Wed Sep 12 06:04:52 2007] [notice] Digest: generating secret for digest authentication ...
[Wed Sep 12 06:04:52 2007] [notice] Digest: done
[Wed Sep 12 06:04:52 2007] [warn] RSA server certificate CommonName (CN) `testserver.test.co.za' does NOT match server name!?
[Wed Sep 12 06:04:52 2007] [warn] pid file /var/run/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Sep 12 06:04:52 2007] [notice] Apache configured -- resuming normal operations
[Wed Sep 12 06:12:13 2007] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:980 (127.0.0.1) failed
[Wed Sep 12 06:12:59 2007] [notice] caught SIGTERM, shutting down
-
The config file for the server-manager is /etc/httpd/admin-conf/httpd.conf.
To remove this address:
db configuration show httpd-admin
You should have something like this:
PermitPlainTextAccess=no
TCPPort=980
TKTAuthSecret=XXXXXXXXXXXXXXX
ValidFrom=X.X.X.X/255.255.255.255,41.0.0.0./255.255.255.255
access=localhost
status=enabled
You have your 41.0.0.0. IP which is not correct, and you may have some other addresses which are correct (X.X.X.X/255.255.255.255 here).
Just type
db configuration setprop httpd-admin ValidFrom 'X.X.X.X/255.255.255.255'
expand-template /etc/httpd/admin-conf/httpd.conf
sv t /service/httpd-admin
And your config should be back.
You should also report it in the bug tracker, the address should be checked before commiting this in the config
-
Thanks, that sorted me out. i'll report the bug
-
Edit: removed as reply was irrelevant and a proper solution was already posted.
-
Thanks, that sorted me out. i'll report the bug
Bug raised here...
http://bugs.contribs.org/show_bug.cgi?id=3388
-
I dont actually think you killed the server manager. I think there was a bad update round about two days ago... My server-manager doesn't start either...
Any pointers as to where to find a solution to this bad update? It knocked my server manager out too, and I don't have a clue how to get it back.
-- JJ
UPDATE: I checked the ValidFrom= setting in the httpd-admin configuration settings, and it was completly empty. I updated it as described above, rebuilt the templates, restarted httpd-admin, and the server manager came back. I'll stick the details into a bug, in case it is useful.
-
Any pointers as to where to find a solution to this bad update? It knocked my server manager out too, and I don't have a clue how to get it back.
-- JJ
Your best bet is to file a bug report as the developers do not have time to read every mail message. Please describe what version you have and what updates you issued. The developers will be glad to follow up and resolve the issue.