Howdy,
Sounds like /tmp is mounted with “noexec”, which is preventing the installation from continuing 
Setting the tmp partition to use the “noexec” option is not a default for any distro I’m familiar with, so that was likely added in manually. You’ll need to remove that option in order for Virtualmin to install.
-Eric
Hello Eric,
This is my new Centos installation (external rented dedicated server).
I don’t know if this is by default or if it has been modified.
How can I fix this please?
Yeah, CentOS doesn’t add that in – your provider may have though.
To disable it, you’ll need to do two things:
Edit /etc/fstab, and remove the noexec option from the line that sets up /tmp. That’ll make sure the mount options are correct next time you reboot.
To change the current options /tmp is mounted with, you cna type: mount -o remount,exec /tmp
You’ll want to do both of those steps – one fixes things now, the other makes sure they stay fixed later 
-Eric
Ah, okay, I understand, thank you.
Should I have to remount it as noexec after installation?
I track /tmp updates twice a day in my present server (the old one).
Below is a typical report.
Thank you,
WARNING: [“MyDomain.com”] /tmp/backup-config-manifests/acl
[Inodes: 426007 - 393239, Sizes: 7685 - 8122, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/apache
[Inodes: 425986 - 393218, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/at
[Inodes: 425997 - 393229, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/bind8
[Inodes: 425987 - 393219, Sizes: 1462 - 1494, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/cron
[Inodes: 425998 - 393230, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/logrotate
[Inodes: 425989 - 393221, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/mailcap
[Inodes: 425990 - 393222, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/mount
[Inodes: 425988 - 393220, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/net
[Inodes: 425991 - 393223, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/pam
[Inodes: 425992 - 393224, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/postfix
[Inodes: 425993 - 393225, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/procmail
[Inodes: 425995 - 393227, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/proftpd
[Inodes: 425994 - 393226, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/spam
[Inodes: 425999 - 393231, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/sshd
[Inodes: 425996 - 393228, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/status
[Inodes: 426002 - 393234, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/syslog
[Inodes: 426000 - 393232, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/time
[Inodes: 426001 - 393233, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/useradmin
[Inodes: 426003 - 393235, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/virtual-server
[Inodes: 426004 - 393236, Sizes: 2373 - 2424, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/webalizer
[Inodes: 426005 - 393237, Sizes: 3880 - 3991, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]
WARNING: ["MyDomain.com"] /tmp/backup-config-manifests/webmin
[Inodes: 426006 - 393238, Times: Jun 24 03:00 2009 - Jun 25 03:00 2009]Howdy,
Whether or not you re-set the “noexec” option is up to you – it’s an option a few people set for additional security, but as you’re seeing, it can interfere with things. I don’t have it set on my system
As for the report you’re seeing – I don’t personally track updates in /tmp.
It’s pretty common for apps, including Webmin/Virtualmin, to modify files in /tmp, so I’d imagine those are all harmless.
-Eric
LABEL=/tmp1 /tmp ext3 defaults,nosuid,noexec,nodev 1 2
changed to
LABEL=/tmp1 /tmp ext3 defaults,nosuid,nodev 1 2
mount -o remount,exec /tmp
./install.sh is working hard now!
ps aux is displaying tasks I guess are from qmail while it is not running (by virtualmin default)
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
Is it safe to uninstall Qmail? I will not use it. Postfix (your default starting mail server) is OK.
I remember some mail problems about installed qmail despite it was not started.
I have installed afp and bfd for firewall from www.rfxn.com
This is what I am using in my old server. Here, if I enter in Linux Firewall I see
Webmin has detected 2 IPtables firewall rules currently in use, which are not recorded in the save file /etc/sysconfig/iptables. These rules were probably setup from a script, which this module does not know how to read and edit.
If you want to use this module to manage your IPtables firewall, click the button below to convert the existing rules to a save file, and then disable your existing firewall script.
but I don’t see such warning in the new server.
Is there something I have to check or to care about?
Thank you!
The processes you’re seeing there are actually part of the mailman mailing list software, rather than qmail.
As far as the firewall stuff goes – I’m not sure I’d worry about it. It’s probably not all that important that rules added by afp and bfd get saved so that they survive a reboot. But that’s all personal preference
-Eric
Good morning all!
I’ve been comparing network settings and seem to be okay.
On my registrar I’ve set ns1.AAAA.com and ns2.AAAA.com nameservers pointing to two IP for this purpose.
At new server I only have Root Zone in Bind while at the old server there are also
Zone 0 (/var/named/named.empty)
$TTL 3H
@ IN SOA @ mail.com. (
0 ; serial
1D ; refresh
1H ; retry
1W ; expire
3H ) ; minimum
NS @
Zone 0000::1 (/var/named/named.loopback)
$TTL 1D
@ IN SOA @ mail.com. (
0 ; serial
1D ; refresh
1H ; retry
1W ; expire
3H ) ; minimum
NS @
PTR localhost.
and
127.0.0.1 (/var/named/named.loopback)
$TTL 1D
@ IN SOA @ mail.com. (
0 ; serial
1D ; refresh
1H ; retry
1W ; expire
3H ) ; minimum
NS @
PTR localhost.
From Virtualmin I have created the virtual host AAAA.com
and changed/added
AAAA. IN SOA ns.AAAA.com. mail.com. (
ns IN A xxx.81
ns1 IN A xxx.81
ns2 IN A xxx.82
By default this record: @ IN NS AAAA.com.
I’ve added
AAAA. IN NS ns1.AAAA.com.
AAAA. IN NS ns2.AAAA.com.
I don’t know much about networks, I am just copying some previous named files.
I get some errors from intoDNS.com checking AAAA.com
Can you help me please?
Thanks!
For future reference, you should probably start a new thread
However, let’s see here…
The domain aaaa.com has two nameservers listed at the registrar:
ns1.anything.com
ns2.anything.com
Now, using “dig” to resolve that domain name, I see:
dig @ns1.anything.com ns1.anything.com
;; AUTHORITY SECTION:
anything.com. 21600 IN NS a.ns.anything.com.
anything.com. 21600 IN NS b.ns.anything.com.
anything.com. 21600 IN NS ns1.anything.com.
anything.com. 21600 IN NS ns2.anything.com.
;; ADDITIONAL SECTION:
a.ns.anything.com. 3600 IN A 66.114.124.147
b.ns.anything.com. 3600 IN A 66.114.124.148
ns2.anything.com. 21600 IN A 204.228.229.165So, it looks like you have a.ns.anything.com and b.ns.anything.com setup as NS records, in addition to ns1.anything.com and ns2.anything.com.
While I don’t have a good understanding of your setup there, I’m not sure why you’d need those other two names (the a. and b. addresses) – you may be able to remove them.
-Eric
Okay, let’s start a new thread.
I was bracking my brain trying to understand your post.
Sorry, I put AAAA just to hide the real domain name.
How can I send you the real name?
What about those three zones? I believe they were created by Virtualmin.
Heh, amusingly, I thought that at first… but just to be sure, I went to intodns.com and entered aaaa.com – and it listed a series of issues that sounded like what you were describing.
So I thought “wow, he’s got a short domain name”, and started tossing out answers
I guess what that means is that whoever owns aaaa.com should post here so we can fix their DNS issues too!
Anyhow, I’ll follow up in the other thread.
-Eric