Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: DungaBee on January 17, 2007, 10:09:14 PM
-
Yesterday I installed all the upgrades to take me to SME 7.1. All was well and I could access the server manager via the web interface without a problem. My server is running in Server-Only mode.
Today my firewall died so as I was getting another put together, I thought it might be a good idea to have SME do the DHCP and DNS on my LAN so I do not need to put in static DHCP assignments and so on if the firewall software does not work as I want and I need to try something else.
So, I logged in via a keyboard and mouse I have connected to the machine and turned on DHCP. The machine rebooted and now I can not hit the Server Manager page by name or IP. Name I would expect not to work for now, but it should work by IP and it does not.
I can however get to the server manager using the text browser at the console. My network shares and so on are working ok on the server, but access to the Server Manager from my laptop or any machine on the LAN is not.
Any ideas?
Thanks in advance.
-
Did you put your server in server/gateway mode? Maybe this would solve your problem.
-
Did you put your server in server/gateway mode? Maybe this would solve your problem.
No. I only want the server to be a private file server on my LAN. I'd rather use separate devices for firewalling and file sharing.
I do not get how I can hit the Server Manager from SSH via the text browser, but not from another host on the same LAN. There must be some rule blocking those HTTP requests from anything by 'localhost' but I am not sure where to look/find that info.
-
This is a shot in the dark... but did you reboot your client machines or perform a 'repair' on their internet connections so they would get a fresh IP address from SME's DHCP server? Your clients may have assigned themselves addresses on a completely different network.
Also,
There must be some rule blocking those HTTP requests from anything by 'localhost'
Why are you coming at it from 'localhost' if you are trying to access it from another machine on your LAN?
John
-
Well there is a rule for that. Server manager console can be accessed from lan or internet if you enter correct permissions (under remote access/remote management).
Try connecting trough text browser as you did before and enter ip of your computer in remote management. Then try and see if it works.
-
This is a shot in the dark... but did you reboot your client machines or perform a 'repair' on their internet connections so they would get a fresh IP address from SME's DHCP server? Your clients may have assigned themselves addresses on a completely different network.
Also,
There must be some rule blocking those HTTP requests from anything by 'localhost'
Why are you coming at it from 'localhost' if you are trying to access it from another machine on your LAN?
John
I have done a repair as well as a reboot on the client machine, but that has not helped the connection to the server manager from the client machine.
Regarding localhost, what I meant was that I can access the Server Manager from the local machine by logging in to the console as 'admin' and then taking the menu option to connect to the Server Manager using a text browser. That at least proves that the HTTP server is listening and is not broken, there just has to be some other rule that is keeping the Server Manager from allowing me to connect from any other machine.
-
Are both http servers running?
/etc/rc7.d/httpd-e-smith status
/etc/rc7.d/httpd-admin status
If I remember correctly the httpd-e-smith configuration file contain a rewrite rule to forward it to http over SSL (https), it could be that the first one is down...
Did you try accessing the server-manager directly as https://server-name or ip/server-manager?
-
What is the ip of the SME eth0 interface ?
ifconfig
What is the ip of the computer your trying to view server-manage from ?
ipconfig
-
SME ifconfig
eth0 Link encap:Ethernet HWaddr 00:A0:CC:27:03:9F
inet addr:192.168.100.10 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:24227 errors:1 dropped:0 overruns:0 frame:0
TX packets:19691 errors:4 dropped:0 overruns:1 carrier:3
collisions:0 txqueuelen:1000
RX bytes:4439941 (4.2 MiB) TX bytes:2305074 (2.1 MiB)
Interrupt:10
My ipconfig
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.100.143
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.1
DHCP Server . . . . . . . . . . . : 192.168.100.1
DNS Servers . . . . . . . . . . . : 192.168.100.1
I have tried connecting both with the DNS name (which should work) and the IP and neither work.
I believe the HTTP daemons are running ok since I can log on via the console as 'admin' and then take the menu option to use the text browser to connect to the server manager.
I did look at the remote access portion of the server manager and added my local LAN to the 'allow' group. It was not in there, although I do not recall ever having to have it in there before or perhaps it was in there and then was lost. Here is the entry:
Network Subnet mask Number of hosts Remove
192.168.100.0 255.255.255.0 256
Is there something in the HTTPD config or in the log files I could look at?
Thanks again everyone.
-
httpd logs in server-manager via server-console ?
Are you using putty?
If so, create a tunnel.
On the SSH- Tunnels page put in..
Source port 443
Destination localhost:443
Click add then click open and login.
Now open your browser to https://localhost/server-manager
-
Yes. I am able to look at the HTTPD logs via the text browser, although they are not that easy to read. There are many lines of the same error:
8)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:04 2007] [crit] (28)No space left on device: mod_rewrite: cou
ld not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:07 2007] [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration
Failed[Thu Jan 18 01:04:10 2007] [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:12 2007] [crit] (2
8)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:15 2007] [crit] (28)No space left on device: mod_rewrite: cou
ld not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:18 2007] [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration
Failed[Thu Jan 18 01:04:21 2007] [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:23 2007] [crit] (2
8)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:26 2007] [crit] (28)No space left on device: mod_rewrite: cou
ld not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:29 2007] [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration
Failed[Thu Jan 18 01:04:32 2007] [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lockConfiguration Failed[Thu Jan 18 01:04:35 2007] [crit] (2
8)
That seems to imply a disk space issue, but
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/main-root
147G 69G 71G 50% /
/dev/md1 99M 25M 69M 27% /boot
none 58M 0 58M 0% /dev/shm
That shows there is plenty of disk.
I think we're getting closer though.
-
There's a fix in the forums for this.... do some searches for no access to http or something similar.
Edit...
http://forums.contribs.org/index.php?topic=33171.0
-
Thanks William!
I was also able to search and find the correct topics.
Kind Regards for the assistance. It's much appreciated.