Topic: Server manager access

[Paul Lakra]

Great Robert - I didn't think oflooking in the bug archives - I should have done. Your 2nd link definitely relates to my problem.

As recommended I keyed in the status check and got:

[root@lakra1 /root]# /etc/rc.d/init.d/httpd-e-smith status
httpd dead but subsys locked
[root@lakra1 /root]# /etc/rc.d/init.d/httpd-e-smith restart
cat: /var/run/httpd.pid: No such file or directory
Shutting down http:  usage: kill [ -s signal | -p ] [ -a ] pid ...
       kill -l [ signal ]
                                                           [ FAILED ]
Starting httpd:  Syntax error on line 205 of /etc/httpd/conf/httpd.conf:
Missing IP address
                                                           [ FAILED ]
[root@lakra1 /root]#

The error message was not one reported in the bug report but in for apenny in for a pound......

I edited /etc/httpd/conf/httpd.conf and found line 205 was:

Listen 80:

This followed lines which were:

Listen 127.0.0.1:80
Listen 192.168.0.99:80

I commented out line 205 and then got a similar error on line 221 which related to port 443. I also commented this line out. I then tried to restart the httpd process.

I got an OK for the process starting but it actually dies in about 5 seconds. I tried starting rather than restarting with the same effect.

I suspect those lines I commented out need to be there but right now I do not know which IP they should contain.

[robert]

Paul Lakra wrote:
>
> Great Robert - I didn't think oflooking in the bug archives -
> I should have done. Your 2nd link definitely relates to my
> problem.
>
> As recommended I keyed in the status check and got:
>
> [root@lakra1 /root]# /etc/rc.d/init.d/httpd-e-smith status
> httpd dead but subsys locked
> [root@lakra1 /root]# /etc/rc.d/init.d/httpd-e-smith restart
> cat: /var/run/httpd.pid: No such file or directory
> Shutting down http:  usage: kill [ -s signal | -p ] [ -a ]
> pid ...
>        kill -l [ signal ]
>                                                            [
> FAILED ]
> Starting httpd:  Syntax error on line 205 of
> /etc/httpd/conf/httpd.conf:
> Missing IP address
>                                                            [
> FAILED ]
> [root@lakra1 /root]#
>
> The error message was not one reported in the bug report but
> in for apenny in for a pound......
>
> I edited /etc/httpd/conf/httpd.conf and found line 205 was:
>
> Listen 80:
>
> This followed lines which were:
>
> Listen 127.0.0.1:80
> Listen 192.168.0.99:80
>
> I commented out line 205 and then got a similar error on line
> 221 which related to port 443. I also commented this line
> out. I then tried to restart the httpd process.
>
> I got an OK for the process starting but it actually dies in
> about 5 seconds. I tried starting rather than restarting with
> the same effect.
>
> I suspect those lines I commented out need to be there but
> right now I do not know which IP they should contain.

That's interesting. Might be a bug. There should be three ip addresses for both port 80 and port 443. One is localhost/loopback 127.0.0.1. Two is internal interface. Third should be external IP. If you do not have an external ip, that line should be left blank by the template that writes to httpd.conf rather than writing a faulty line.
You may want to try expanding the template for this conf file by typing:
/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf
and see what addresses and ports it comes up with. If it looks good, restart the http server. If it's still garbled, perhaps it is time for a bug report, in which of course you should be as specific as possible about the problem and include details about your configuration (also make sure you didn't make any mistakes while configuring your system, possibly even reconfigure your system if you're in doubt).

[Kevin Flanagan]

I have a bit of a strange one.  

I was installing some of the add ons, User panel etc, after that I found that I was locked out of server-manager.  "You are not allowed to view this page"

I searched here, found the note about permissions on the directory with the panels in it, did that, and am back in, but not quite done.

Server manager seems to have forgotten the configuraion of the system, hosts, users everything.  

Is it permissions still? I'd think so, but don't know where to go next.



TIA

[robert]

On the subject of configuration:
What operation mode are you using? 'Server only', right? From what you told me, I gather that a windows machine is the gateway for your LAN. Did you specify that machine's ip address as the gateway ip when you configured your sme-server. And is it in the same subnet? You probably also need to specify that gateway machine as the primary domain name server, but I'm not sure about that.
Also, what's the entry for ExternalIP in /home/e-smith/configuration?
It may well be a blank (because the gateway machine never told your sme-server), in which case httpd.conf will be set to listen to
127.0.0.1:80
local_ip:80 (in your case 192.168.1.99:80)
AND
[blank]:80     <-that conflicting line you mentioned

[robert]

Kevin Flanagan wrote:
>
> I have a bit of a strange one.  
>
> I was installing some of the add ons, User panel etc, after
> that I found that I was locked out of server-manager.  "You
> are not allowed to view this page"
>
> I searched here, found the note about permissions on the
> directory with the panels in it, did that, and am back in,
> but not quite done.
>
> Server manager seems to have forgotten the configuraion of
> the system, hosts, users everything.
>
> Is it permissions still? I'd think so, but don't know where
> to go next.
>
>
>
> TIA
For anyone reading this. I was writing my previous post in response to Paul Lakra just when the post quoted here was posted. So, my previous post is not in response to Kevin, which may save you some headaches figuring out the connection betweeen these posts: there isn't any.
By the way, Kevin: I really have no idea. I think this is a good one for a new thread.

[Paul Lakra]

Ok Robert here is the latest.

I expanded the .conf file from the template as you suggested but it created a file identical to the original and the fault remained.

I then read your second email and decided to reconfigure as a server only (it was configured as adial up gateway.) On doing this the problem was fixed and the offending lines 205 and 220 of the .conf file are both blank. I am sure something else must be different becasue I had commented the lines out before. I have not managed to compare the two .conf files completely yet but I will try and do this.

I did also put the IP of my Windows gateway as the Internet gateway and the primary domain name server. I did all thee things at once so I am not sure which fixed the problem. I will try going back to teh gateway mode but now the SME server can see the internet I am going to install the two upgrade blades first.

[robert]

Paul Lakra wrote:
>
> Ok Robert here is the latest.
>
> I expanded the .conf file from the template as you suggested
> but it created a file identical to the original and the fault
> remained.
>
> I then read your second email and decided to reconfigure as a
> server only (it was configured as adial up gateway.) On doing
> this the problem was fixed and the offending lines 205 and
> 220 of the .conf file are both blank. I am sure something
> else must be different becasue I had commented the lines out
> before. I have not managed to compare the two .conf files
> completely yet but I will try and do this.
>
> I did also put the IP of my Windows gateway as the Internet
> gateway and the primary domain name server. I did all thee
> things at once so I am not sure which fixed the problem. I
> will try going back to teh gateway mode but now the SME
> server can see the internet I am going to install the two
> upgrade blades first.

E-smith/SME uses templates for configuration files. If you restart a server, it will first produce a new configuration file from the template and use that to start the server. This means that any edits you make to the conf file rather than to its template (they're in /etc/e-smith/templates) will be overwritten. The reason why the template produced a conf file that didn't work is because it looks like you configured your system wrong. You can't configure the system as a gateway if it isn't physically hooked up as a gateway. When you set it up the first time in server and gateway mode, how did you configure your external interface? Where did you expect it to get its IP address from if it's not connected to any network?
I urge you to Read The F* Manual, read all the faqs, read the info on this website about customizing the system that discusses templates and also to read all bug reports.

[Paul Lakra]

Hey Robert - keep your hair on! You must be having a bad day. I'm not as daft as all that.

I actually did take the trouble to download the manual and I printed it out and I read it cover to cover before I even put the CD into the machine to install it. The manual is actually very weak in the area of dial up modems and I do not find there is too much on the e-smith site.

My initial configuration was for a gateway using a dial up modem. I thought the machine should be quite comfortable that way wether or not it was connected to the internet because dial up is by its nature intermittent. I also cannot see why a gateway machine cannot sit happily on the network offering to be a gateway. Even if it has no internet connection providing no other machines try and use it as such. I also do not see any problems over IP addresses. All my machines have preset addresses including the SME server so there is no need for a DNS server or its address. I have run networks for years without a DNS server.

Also if you run through the configuration on SME 5 the dialogs advise against entering IP addresses in these areas. As far as I could I followed the instructions to the letter and as I said right at the beginning the Server Manager worked fine for a couple of weeks. I still think something happened while I was trying to configure different user names and also I was playing with the dial up connection and rebooting the server.

Have a good day Robert.

[robert]

Paul Lakra wrote:
>
> Hey Robert - keep your hair on! You must be having a bad day.
> I'm not as daft as all that.
>
You are absolutely right! My girlfriend was just telling me the same thing. So I guess I am having a bad day.
The points you make are all valid and as you said the server had no problem with the configuration you entered in the beginning. It looks like something somewhere got broken along the way, but unless you can repeat the problem we'll never know if it's a bug or anything else.
I hope your can set up your server to do all the things you want it to do now that it seem to be working again. Try starting a new topic about that internet connection you were having trouble with. Maybe someone with the same set-up has already solved the problem.

> Have a good day Robert.
You have a good day too!
(P.S. Your etiquette is certainly better than mine.
Now let's see if I can get some work done today. Maybe that will improve my mood.

[robert]

Hi Paul,
OK, I thought I owed you one, so I delved into some old logs and found that my ExternalIP (the one that's in /home/e-smith/configuration) was originally set to a non-routable address (192.168.65.17). This looks like a 'bogus' setting designed to prevent the sort of problem you were having with a missing ExternalIP. When the external interface gets assigned a 'real' IP address (usually by an ISP), this triggers an event in /etc/e-smith/events that's called 'ip-change', which will first set the value for ExternalIP in the main configuration and then use that variable to configure any applicable services. My external IP changes quite often because my ISP provides rather short DHCP leases, and the ip-change event always handles that situation well.
My guess is that in your situation the ip-change event should never have occured. The ip-change event is run with the IP address for the external interface as its argument. So it's 'ip-change 234.5.6.7' for instance. It seems like on your machine the ip-change event was run without an argument (or with an empty argument), which would set the ExtrenalIP to an empty value and then fill in that empty value in all applicable conf files, such as httpd.conf. Which in turn would lead to the problems you were experiencing.
Come to think of it, you may have inadvertently set off the ip-change event with an empty value when you configured the server. I haven't checked how the configuration script parses these kind of entries, but it might just be that if you enter one or a couple of spaces for your external interface's IP, instead of interpreting that as no entry, it's interpreted as an entry of "   ".
Would you be willing to test that theory? I'm running a rather unusual set-up here, so my testing is probably not as conclusive as yours. If the theory is correct, I think we've got ourselves a nice catch.
Sincerely,
Robert

[robert]

Hi Paul,
Please disregard the last part of my previous post, because I just came up with a brilliant idea (ahem)! Instead of taking wild guesses at what may have happened, why don't we look in your logs to see what actually did happen!
On the assumption that the event 'ip-change' ran with an empty argument, you may search your /var/log/messages log file for such an entry. One way to do that would be:
less /var/log/messages |grep " ip-change"   (<-mind the leading space)
On my machine, this returns several lines of the form
[something, date, time, something] Running event: ip-change 345.11.22.33
where the last bit's an IP address from my ISP's IP pool.
Let's see if you get a line back that says
[something, date, time, something] Running event: ip-change [blank]
If it's not in /var/log/messages, see if logrotate left some logs in the var/log/ directory that are called messages.1, messages.2, etc. and search for the line there.
If you do find an ip-change event with an empty argument, you can find in the appropriate log file when and why it occured. If you don't, I'm not sure where else we may look.
Regards,
Robert