need to reboot server to access :10000

9 posts / 0 new
Last post
#1 Tue, 10/14/2014 - 03:14
stevenbaus73

need to reboot server to access :10000

hi, i have virtualmin setup on a digitalocean server. Every so often (basically everytime i want to use it i have to reboot the server. anyone have any ideas on why i would need to reboot the server each time so i caqn access :10000

maybe i missed something in the setup. All websites still work but i cant access the virtualmin admin site without rebooting, once i reboot it works next next i need it

Wed, 10/15/2014 - 06:25
zen4all

I have the same problem. On the 2 vps I have both are basically the same one has the problem and the other not. The systems are using Ubuntu 14.04 1024 MB RAM 1024 MB SWAP RAM 2 CPU Cores

Wed, 10/15/2014 - 10:13
andreychek

Howdy,

Is Virtualmin working for awhile, and then stops?

If so, I'm wondering if maybe the server is running out of RAM at some point, and then killing processes in order to free up RAM.

What is the output of this command:

dmesg | tail -30

Fri, 10/24/2014 - 12:23 (Reply to #3)
zen4all

Yes it is working for a while (1-3) days an then stops responding. Since the server was already running a minimum of processes, I upgraded the server to 3 cores and 2gb of RAM. Now I need a couple of day to see what happens.

Edit: I have been running the upgraded vps for a couple of days now and that seems to solve my problem. I guess I was asking to much of the system ;)

Tue, 10/28/2014 - 15:14
calderwood
calderwood's picture

I too am having a problem accessing the Virtualmin admin.

Server is running normally, usemin is accessible on port 20000. All access via 10000 says page not available. Via SSH webmin status is running.

# /etc/init.d/webmin status
Webmin (pid 11841) is running

This just started today. I have full SSH access to the server.

I saw aboe you requested dmesg ouput:

# dmesg | tail -30
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.
ip_conntrack: CT 10086860: table full, dropping packet.

David Calderwood - Euro-Pacific Digital Media

Tue, 10/28/2014 - 15:23 (Reply to #5)
andreychek

Howdy,

Well, I don't see any messages about the kernel needing to kill processes due to low RAM, though if Webmin is mysteriously dying, low RAM or resources is usually the cause.

What is the output of this command:

free -m

Tue, 10/28/2014 - 17:44 (Reply to #6)
calderwood
calderwood's picture
# free -m
             total       used       free     shared    buffers     cached
Mem:          4096       2127       1968          0          0          0
-/+ buffers/cache:       2127       1968
Swap:            0          0          0

Admin: https://epdigital.biz:10000/

David Calderwood - Euro-Pacific Digital Media

Thu, 10/30/2014 - 09:03
calderwood
calderwood's picture

The admin access issue was the SSL certificate. After Shellshock and POODLE updates, I created a new private key, and then had the SSL certificate re-keyed, and installed the new certificate on the default domain. Next, I used the Manage SSL function button to copy the new cert to Webmin. That showed as successful, but as I found out later reading through the logs, the SSL cert updated, but the new private key did not update in Webmin.

The fix: I turned off SSL in /etc/webmin/miniserv.conf, which then allowed me to access the admin panel without SSL. I then deleted all of the SSL files in the Webmin folder, then uploaded the new private key, cert and CA to Webmin, restarted apache and that seems to have fixed the error and I can now access the admin panel via SSL.

David Calderwood - Euro-Pacific Digital Media

Thu, 12/08/2016 - 17:08
MostHated

I am having this issue as well now. Below image is what I have. Does this mean I just need a bigger digital ocean VM? My sites are working fine, I just cannot access virtualmin. Is there a way I can keep it from bring killed?

http://i.imgur.com/7AhL8mB.png

Topic locked