John Gregory - Fri, 2012/06/22 - 00:38

TKL noobie here. Just did my first restore (Joomla 1.6) to a bare metal server. Worked well. Except... I can't access Webmin on the restored server. I can access PHPMyAdmin (https://192.168.0.168:12322) and the Webshell (https://192.168.0.168:12320), but no Webmin. It's not listening on port 12321. Any ideas how to resolve this? 

root@joomla16 ~# netstat -lp --inet
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:pop3 *:* LISTEN 1171/dovecot
tcp 0 0 *:imap2 *:* LISTEN 1171/dovecot
tcp 0 0 *:www *:* LISTEN 1228/apache2
tcp 0 0 *:ssh *:* LISTEN 893/sshd
tcp 0 0 *:smtp *:* LISTEN 1027/master
tcp 0 0 *:https *:* LISTEN 1228/apache2
tcp 0 0 *:12320 *:* LISTEN 1202/shellinaboxd
tcp 0 0 *:imaps *:* LISTEN 1171/dovecot
tcp 0 0 *:12322 *:* LISTEN 1228/apache2
tcp 0 0 *:pop3s *:* LISTEN 1171/dovecot
tcp 0 0 localhost:mysql *:* LISTEN 790/mysqld
udp 0 0 192.168.0.168:ntp *:* 1050/ntpd
udp 0 0 localhost:ntp *:* 1050/ntpd
udp 0 0 *:ntp *:* 1050/ntpd     

P.S. I have been using TKL for over a year and am very happy.

Forum: 
Support
Jeremy Davis's picture

Jeremy Davis - Fri, 2012/06/22 - 10:38

But Webmin runs on it's on micro-webserver so perhaps you could try starting it (not sure if this will work...)

service webmin start

If it doesn't please post back the error that you get.

Also you could have a look in /var/log to see if there is a log folder/file for Webmin. If so post (ie copy/paste) or attach (to your first post - you can't attach to replies).

It may also be useful to have a look at your TKLBAM restore log (it should also be somewhere in /var/log).

John Gregory - Fri, 2012/06/22 - 22:16

Thanks for the help JedMeister. I just tried starting it.

root@joomla16 ~# service webmin start
* Starting webmin

That looks good I guess... but still couldn't access Webmin

There is no Webmin folder/file in /var/log

root@joomla16 /var/log# ls
apache2   boot      cron-apt         debug    dmesg.1.gz  fsck      lpr.log    mail.log   messages   mysql.log       ntpstats       syslog.1        user.log
apt       boot.log  daemon.log       dmesg    dpkg.log    kern.log  mail.err   mail.warn  mysql      mysql.log.1.gz  pycentral.log  tklbam-restore  wtmp
auth.log  btmp      dbconfig-common  dmesg.0  faillog     lastlog   mail.info  mailman    mysql.err  news            syslog         udev
root@joomla16 /var/log#

The tklbam-restore log mentions the webmin-dovecot package I installed. Everything looks "normal" to my untrained eye.

Is this a port problem? Do I need to play with iptables?

TIA, John

Jeremy Davis's picture

Jeremy Davis - Sat, 2012/06/23 - 07:27

Have you rebooted following the restore? I'm guessing that you probably have, but just in case...

Failing that, test to see if Webmin is listening now (with netstat again), also ceck that Webmin is running after a restart (service webmin status). If not check again that it is listening after starting it (although it should start when rebooted - if not we've got some serious issues somewhere...)

As for IPTables, unless you had them configured before then you shouldn't need to touch them (they are disabled by default).

IIRC Webmin keeps lots of stuff in /etc/webmin (or similar) so perhaps have a look in there and see if there is an error log there somewhere...

John Gregory - Sat, 2012/06/23 - 20:05

Thanks again JedMeister. Just rebooted again. No love. "Service webmin status" doesn't display any results, even after starting webmin. See below. And netstat confirms that webmin isn't listening on port 12321. Guess I have a pretty messed up system. I'll take a peek in /etc/webmin

root@joomla16 ~# service webmin start
 * Starting webmin                   
root@joomla16 ~# service webmin status
root@joomla16 ~# netstat -lp --inet
Active Internet connections (only servers)                                 
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 *:www                   *:*                     LISTEN      1274/apache2    
tcp        0      0 *:ssh                   *:*                     LISTEN      973/sshd        
tcp        0      0 *:smtp                  *:*                     LISTEN      1057/master     
tcp        0      0 *:https                 *:*                     LISTEN      1274/apache2    
tcp        0      0 *:12320                 *:*                     LISTEN      1248/shellinaboxd
tcp        0      0 *:imaps                 *:*                     LISTEN      1217/dovecot     
tcp        0      0 *:12322                 *:*                     LISTEN      1274/apache2    
tcp        0      0 *:pop3s                 *:*                     LISTEN      1217/dovecot     
tcp        0      0 localhost:mysql         *:*                     LISTEN      812/mysqld
tcp        0      0 *:pop3                  *:*                     LISTEN      1217/dovecot
tcp        0      0 *:imap2                 *:*                     LISTEN      1217/dovecot    
udp        0      0 192.168.0.168:ntp       *:*                                 1074/ntpd
udp        0      0 localhost:ntp           *:*                                 1074/ntpd
udp        0      0 *:ntp                   *:*                                 1074/ntpd

Santiago Gonzalez's picture

Santiago Gonzalez - Wed, 2012/10/24 - 13:48

I've got the same problem. After restoring the last backup (the backup was on Turnkey 11.3) on the new Turnkey 12.0 I cannot access webmin and is not listening on port 12321

Any ideas?

Regards. Santiago

Santiago Gonzalez's picture

Santiago Gonzalez - Wed, 2012/10/24 - 14:23

I found the problem. After the restore webmin starts listen in the default port 10000 so you have to access with that port number and change in webmin configuration to the 12321 port

Regards. Santiago

Jeremy Davis's picture

Jeremy Davis - Wed, 2012/10/24 - 23:26

Sounds like a bug. Thanks for working it out and posting back. I have filed a bug report.

Jeremy Davis's picture

Jeremy Davis - Sun, 2012/11/11 - 23:08

Perhaps double check that that is installed... If it is, maybe try removing it and reinstalling it (should be available in the TKL repo).

Jarrod Igou's picture

Jarrod Igou - Fri, 2013/01/18 - 19:33

I've run into this same exact issue today. I'm using the Core appliance as my base, and downloaded/installed the 12.0 .OVF file at http://www.turnkeylinux.org/core

When I first brought the appliance up, I was able to access Webmin. From there, I used TKLBAM to restore an 11.3 backup onto the 12.0 machine, and now Webmin isn't running. Shellinabox is up and running just fine. (netstat -lp --inet confirms this)

I've tried port 10000, and it's not there; I've checked various Webmin cron module locations, and they all appear to be fully-populated with files.

I see the same error in miniserv.error that Iain did....but I've checked various Webmin locations and see what appear to be Webmin Cron Module files.

As I've compared Webmin data from a fresh Core image and the "broken" one I have, I'm seeing that the "broken" one is referencing Webmin 1.600 in various places, while the version on the one that's working is 1.590. That reminds me that I may have upgraded the Webmin on my old 11.3 server....could that be what's happening?

<time passes>

OK, I've just downloaded an 11.3 Core OVF from Sourceforge and fired it up. It worked fine until I restored the backup of my old 11.3 onto it - as soon as that was complete, Webmin gave me an error message along the lines of "You don't have any modules you can access". I was able to log out of Webmin and log back in (using root), but I still had no modules. After restarting the server, Webmin is now dead (as documented above).

Others who have had this problem - had you updated / upgraded Webmin on the original appliance that you tried to restore?

Jarrod


Jeremy Davis's picture

Jeremy Davis - Mon, 2013/01/21 - 23:59

To remove Webmin and all the modules currently installed (through package management - if you have installed additional modules another way you will have to reinstall them manualy) do this:

dpkg --get-selections > webmin-packages.txt
apt-get --purge remove webmin
apt-get update
dpkg --set-selections < webmin-packages.txt
apt-get dselect-upgrade

And that should remove all the currently installed Webmin packages (and all the associated config files) and reinstall them.

Jarrod Igou's picture

Jarrod Igou - Mon, 2013/01/21 - 18:36

That took care of the issue!

I DID need to run "apt-get update" in the middle (after "apt-get --purge remove webmin") to update the repositories so Webmin could be reinstalled. It popped up an error message directing me down that route, so it's not anything obscure.

Upon reinstall, Webmin fired up at the default port of 10000 and came in with the "Old Webmin" theme selected; I simply clicked into the Webmin Configuration panel and updated both the port and the theme.

Thanks, Jeremy!


Jeremy Davis's picture

Jeremy Davis - Tue, 2013/01/22 - 00:04

And thanks for the feedback about 'apt-get update' I added it to my post above so if anyone else stumbles across this thread it'll just work for them.

Ideally it would be good to get to the bottom of why this occurs, but in the meantime at least there is a quick repair available.

Add new comment