Webmin issues

[mike]

Hi

Firstly, many thanks to Ian for creating this site, it has given me the confidence to have a go myself...very much a noobie with linux.

I had an earlier attempt at getting my server up and running, but trashed it some how when trying to get the scripts for drive spin down working.

I have decided to start a 'fresh' install - so far so good! Ubuntu 10.04 gone on fine, putty working fine, VNCserver & TightVNC working fine. I did get webmin up and running first time and set up a cron job to run the StartVNC script.

Rebooted - putty still ok, TightVNC still ok (cron job must have worked!) but now cannot log into webmin unless I do a reinstall. It seems that if I reboot the server, then I can no longer use webmin to access the server. There must be a simple oversight on my part, any ideas?

cheers
mike

[fpp]

Normally Webmin will set itself up to run at boot.

I've seen it "turn itself off" once, after applying updates (through the Web UI, not apt-get). It was still there but didn't start at boot time.

One way to check it to run it manually, then access the Web UI : in the "Webmin" menu click "Webmin configuration".
Check the state of the "Start at boot time" radio button. If it's not on "Yes", select that and press the button.

[Ian]

Hi Mike and welcome to the forum. It's good to read that you've now the confidence to take the plunge, Hopefully you'll not regret it.

Possibly your issues with webmin are something simple. So, let's start with the basics. How are you trying to access webmin, using the servername (eg. https://mediaserver.home:10000/) or are you using the ip address (eg. https://192.168.1.1:10000/)? If you're trying the former do you have more success with the latter? If using the latter then double-check that the ip address you're using for your server is correct. You can find out the ip address either using the interface for your router or by typing the following in a Putty session:

Code: Select all

ifconfig

and look for the number next to "inet addr:"

To check webmin has started successfully issue the following command:

Code: Select all

ps -ef |grep webmin

Do you see something along the following lines in the result?:

root 1961 1 0 07:51 ? 00:00:00 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf

Ian.

[mike]

Hi Ian

Thanks for the quick responses!

I've tried logging on with both the server name and IP address. I have checked the IP address for my server is correct.

when running the ps -ef |grep webmin command, I get the following output:

mike 1659 1638 0 10:50 pts/0 00:00:00 grep --color=auto webmin

the spacing might be a bit off but I hope that means something to you as I haven't got a scoobydoo.

mike

p.s. I'll check your ideas when I next get into webmin fpp thanks

[Ian]

Mike,

From the output you posted it looks like webmin is not being started at boot after all. Try fpp's tips and if you have no success please issue the following command and post the results:

Code: Select all

sudo cat /var/webmin/miniserv.error

You can start webmin manually by issuing the following command:

sudo /etc/init.d/webmin start

[mike]

Hi again

Fpps ideas were right on the money!!

After installing webmin, I chose to update the modules so this may have been the cause. Either way the start at boot time option was set to 'no'. Changed the option, saved, rebooted and 'viola' I now have access to webmin.

Many thanks both for you input.

regards
Mike

[fpp]

Glad to be of help. That's exactly what happened to me.
It may have been specific to that series of Webmin upgrades (there were several at once) : I did another upgrade later on, and was very careful to check the option before rebooting, but it had stayed put this time...

[Ian]

Glad to be of help. That's exactly what happened to me.
It may have been specific to that series of Webmin upgrades (there were several at once) : I did another upgrade later on, and was very careful to check the option before rebooting, but it had stayed put this time...

I see they've released some updates to Webmin and one of the changes is: "Fixes a problem on Debian and Ubuntu systems in the Webmin Configuration module that prevents Webmin from being started at boot time"

If you go into Webmin you'll see them at the bottom of the home screen.

Ian.

[phour19]

Normally Webmin will set itself up to run at boot.

I've seen it "turn itself off" once, after applying updates (through the Web UI, not apt-get). It was still there but didn't start at boot time.

One way to check it to run it manually, then access the Web UI : in the "Webmin" menu click "Webmin configuration".
Check the state of the "Start at boot time" radio button. If it's not on "Yes", select that and press the button.

Thanks fpp
Worked for me, with one other step. At first when I clicked on "yes" to start up at boot it would automatically change back to "no". Then I read below where Ian said there are new updates for Webmin. I had to click on "system info" and update Webmin. Once I did that I went back and clicked yes again. This time when I clicked yes it stayed and has been working ever since.

[djfourmoney]

I wanted to jump on this issue as its not the same but still a problem with Webmin.

I also want to thank Ian for this walkthrough otherwise (and still might) jump back to WHS. I have WHS 2012 running at home, but I built a file server for Occupy Los Angeles since there is so much video and imagines coming into the media tent and no place to put it and share with the public.

Anyway, the issue I have is -

The workstation connected to the router (Cradlepoint 3G/4G MBR100) works with Webmin, but when I tried two other laptops connected to the router wireless to the same router the Webmin browser interface will not come up (404 error).

I haven't tried TightVNC yet but we've had a power outage a few times (generators running out of fuel, solar system not up yet) and I have to reset the VNC Server anyway.

I believe Port 80 or another port is blocked. Otherwise I don't know what it could be. I haven't tried using the IP Address, I could do that. Not today though, I have things to do around here plus I need to sort out the HD issues (40GB currently).

Do you have any suggestions?