Domains Showing as Numbers

Recently my domains have started showing as numbers, doing some research I found some other forum posts pointing me to the map.dom and map.alias files. I used the php-fpm config to determine the correct ID to domain mapping and fixed map.dom. Rebooting the server has had no effect in resolving the issue, this file seems to not be getting detected.

Upon performing a webmin config backup, I notice that there are a bunch of .acl files missing (relating to the missing domains).

My question, is there any way to easily rebuild all of this without having to recreate these domains?

SYSTEM INFORMATION
OS type and version: CentOS Linux 8.5.2111
Webmin version: 1.981
Virtualmin version: 6.17

UPDATE: I have manually recreated my map.alias and .acl files and still nothing - are there any other files I need to check/repair?

Hi,

What is the output of the following command where you’re seeing that issue:

ls -lsa /etc/webmin/virtual-server/domains

Hi mate,

ls -lsa /etc/webmin/virtual-server/domains
total 56
4 drwx------   2 root root 4096 Dec  9 17:12 .
4 drwx--x--x. 13 root bin  4096 Dec 10 01:32 ..
0 -rwx------   1 root root    0 Sep 18 04:00 15328500662081
0 -rwx------   1 root root    0 Sep 18 04:00 15328501092880
4 -rwx------   1 root root 3248 Dec  7 16:57 15328503155200
0 -rwx------   1 root root    0 Sep 18 04:00 153311687615294
4 -rwx------   1 root root 3668 Dec  1 03:32 159178327511621
0 -rwx------   1 root root    0 Oct 26 14:01 159403224429721
0 -rwx------   1 root root    0 Oct 26 14:01 16043047357075
4 -rwx------   1 root root 3066 Dec  9 17:12 160430619818725
0 -rwx------   1 root root    0 Oct 26 14:01 16054921502039329
0 -rwx------   1 root root    0 Oct 26 14:01 16059545652996820
4 -rwx------   1 root root 3301 Dec  6 14:37 16092940033661772
4 -rwx------   1 root root 3369 Dec  3 06:52 16092941413664336
4 -rwx------   1 root root 3083 Dec  7 17:32 1613008079237930
4 -rwx------   1 root root 1928 Nov  4 21:00 16145039581923202
4 -rwx------   1 root root 1889 Nov  4 21:00 16145040901926569
0 -rwx------   1 root root    0 Oct 26 14:01 16145042041930472
4 -rwx------   1 root root 3411 Dec  9 05:57 16158045002676475
4 -rwx------   1 root root 2089 Dec  6 17:37 16158046672680260
4 -rwx------   1 root root 3047 Nov 23 12:35 16170940461472290
0 -rwx------   1 root root    0 Sep 18 04:00 16310949643095250
4 -rwx------   1 root root 2681 Dec  5 13:02 1637470459103860

I’m assuming no responses means no-one knows? I guess I just have to recreate…

I am having the same issue. Can anyone speak to what is causing this and how to fix it?

ls -lsa /etc/webmin/virtual-server/domains
total 16
4 drwx------   2 root root 4096 Dec 24 10:19 .
4 drwx--x--x. 14 root root 4096 Dec 24 10:56 ..
0 -rwx------   1 root root    0 Dec 23 00:00 161746898016337
0 -rwx------   1 root root    0 Dec 23 00:00 161746921119350
0 -rwx------   1 root root    0 Dec 23 00:00 161746927020590
0 -rwx------   1 root root    0 Dec 23 00:00 161746931221710
0 -rwx------   1 root root    0 Dec 23 00:00 161746939223351
0 -rwx------   1 root root    0 Dec 23 00:00 161746943324604
0 -rwx------   1 root root    0 Dec 23 00:00 161747871819145
0 -rwx------   1 root root    0 Dec 23 00:00 161747891221463
0 -rwx------   1 root root    0 Dec 23 00:00 161747895323220
0 -rwx------   1 root root    0 Dec 23 00:00 161747914025604
0 -rwx------   1 root root    0 Dec 23 00:00 161748257531536
0 -rwx------   1 root root    0 Dec 23 00:00 161748535010648
0 -rwx------   1 root root    0 Dec 23 00:00 161748543611314
0 -rwx------   1 root root    0 Dec 23 00:00 161748549312057
0 -rwx------   1 root root    0 Dec 23 00:00 161748553113779
0 -rwx------   1 root root    0 Dec 23 00:00 161748561116556
0 -rwx------   1 root root    0 Dec 23 00:00 161748566217938
0 -rwx------   1 root root    0 Dec 23 00:00 161748570419312
0 -rwx------   1 root root    0 Dec 23 00:00 161748574420660
0 -rwx------   1 root root    0 Dec 23 00:00 161748583322860
0 -rwx------   1 root root    0 Dec 23 00:00 161748589224379
0 -rwx------   1 root root    0 Dec 23 00:00 161748596426010
0 -rwx------   1 root root    0 Dec 23 00:00 161748602927500
0 -rwx------   1 root root    0 Dec 23 00:00 161748606828804
0 -rwx------   1 root root    0 Dec 23 00:00 161748610529322
0 -rwx------   1 root root    0 Dec 23 00:00 161748617932409
0 -rwx------   1 root root    0 Dec 23 00:00 16174862231437
0 -rwx------   1 root root    0 Dec 23 00:00 16174862762763
0 -rwx------   1 root root    0 Dec 23 00:00 16174863344189
0 -rwx------   1 root root    0 Dec 23 00:00 16174867917377
0 -rwx------   1 root root    0 Dec 23 00:00 161749575026750
0 -rwx------   1 root root    0 Dec 23 00:00 161757817523199
0 -rwx------   1 root root    0 Dec 23 00:00 161759702210474
0 -rwx------   1 root root    0 Dec 23 00:00 161762621613008
0 -rwx------   1 root root    0 Dec 23 00:00 161762655415856
0 -rwx------   1 root root    0 Dec 23 00:00 161762909628527
0 -rwx------   1 root root    0 Dec 23 00:00 161826350412972
0 -rwx------   1 root root    0 Dec 23 00:00 162039777826719
0 -rwx------   1 root root    0 Dec 23 00:00 162051831413929
0 -rwx------   1 root root    0 Dec 23 00:00 162118190928016
0 -rwx------   1 root root    0 Dec 23 00:00 16231686085990
0 -rwx------   1 root root    0 Dec 23 00:00 16312894778127
0 -rwx------   1 root root    0 Dec 23 00:00 163310226327988
0 -rwx------   1 root root    0 Dec 23 00:00 16366755615942

I’ve asked @Jamie to follow up when he has time. But, I’m pretty confident there is discussion of this problem and ways to fix it in the forums somewhere. It’s come up a few times, though I really thought the bug that leads to it happening was fixed.

Do you think you could run out of disk space when running Virtualmin config check?

Yes, you would just have to recover those Virtualmin domains config files from a back up. Those are just records. If you have no backups the only way is to re-import each domain using Add Servers ⇾ Import Virtual Server page.

The cause could be filesystem corruption that is creating those zero length files? Webmin and Virtualmin themselves have checks that should prevent this from happening, even if the system is out of disk space.

Awesome! Thanks so much, I’ll try reimport tonight. I’ve used virtualmin for years and never encountered this issue, it’s a strange one and came out of nowhere. I’m avoiding the backup restore because they are so old as I didn’t detect the issue for a while so I don’t want to overwrite any DB’s or files.

Merry Christmas!

P.S. Regarding being covered in other topics, unfortunately I searched and only found 2 other articles that were unsolved. There may be others but I could not locate them.

You don’t have to restore the whole backup (and, I wouldn’t in this circumstance). The config files are in the backup, and the backup is just a tarball. You can untar/ungzip the backup file(s) and dig out the domain config files.

But, if your domains weren’t very customized from the defaults you’ve setup, re-importing is also fine.

1 Like

@Joe What files from the backup do we need to restore to get this back? When I unzip the backup, I don’t see the files that are needed? I’m sorry for being so uninformed when it comes to this, but I don’t want to turn a partially working system into a non-functioning system. Maybe if you could post the steps and files to restore?

Here is what I get for files from the virtualmin backup (both of these are downloaded onto my mac first to look at the files easier):

drwx------@ 26 tage  staff        832 Dec 26 12:09 .
drwx------@ 80 tage  staff       2560 Dec 26 12:09 ..
-rw-r--r--   1 tage  staff          0 Nov 11 12:07 virtualmin_chroot
-rwx--x--x@  1 tage  staff       8833 Nov  2 13:39 virtualmin_config
-rw-r--r--   1 tage  staff          0 Nov  2 13:08 virtualmin_custom
-rw-r--r--   1 tage  staff          0 Nov  2 13:08 virtualmin_custom_linkcats
-rw-r--r--   1 tage  staff          0 Nov  2 13:08 virtualmin_custom_links
-rw-r--r--   1 tage  staff          0 Nov 11 12:07 virtualmin_custom_shells
-rw-r--r--   1 tage  staff      20480 Nov 11 12:07 virtualmin_email
-rw-r--r--   1 tage  staff          2 Nov 11 12:07 virtualmin_mailserver
-rw-r--r--   1 tage  staff        136 Nov 11 12:07 virtualmin_mailserver_dkim
-rwx------   1 tage  staff       1675 Sep 15 13:21 virtualmin_mailserver_dkimkey
-rw-r--r--   1 tage  staff         20 Nov 11 12:07 virtualmin_mailserver_grey
-rw-r--r--   1 tage  staff       9666 Sep 22  2016 virtualmin_mailserver_greyclients
-rw-r--r--   1 tage  staff        188 Sep 22  2016 virtualmin_mailserver_greyrecipients
-rw-r--r--@  1 tage  staff      28389 Nov 10 21:12 virtualmin_mailserver_maincf
-rw-r--r--   1 tage  staff       6343 Mar 26  2021 virtualmin_mailserver_mastercf
-rw-r--r--   1 tage  staff         20 Nov 11 12:07 virtualmin_mailserver_ratelimit
-rw-r-----   1 tage  staff       5755 Aug 28 12:19 virtualmin_mailserver_ratelimitconfig
-rw-r--r--   1 tage  staff      10240 Nov 11 12:07 virtualmin_resellers
-rw-r--r--   1 tage  staff      10240 Nov 11 12:07 virtualmin_scheds
-rw-r--r--   1 tage  staff      10240 Nov 11 12:07 virtualmin_scripts
-rw-r--r--@  1 tage  staff      20480 Nov 11 12:07 virtualmin_templates
-rw-r--r--   1 tage  staff          0 Nov  2 13:08 virtualmin_templates_global
-rw-r--r--   1 tage  staff      10240 Nov 11 12:07 virtualmin_templates_plans
-rw-r--r--@  1 tage  staff  175104000 Nov 11 12:07 virtualmin_templates_skel_0

and here is what I get from a test domain backup unzipped:

drwx------@ 21 tage  staff   672 Dec 26 12:08 .
drwx------@ 80 tage  staff  2560 Dec 26 12:09 ..
-rw-r--r--@  1 tage  staff  6148 Dec 26 12:08 .DS_Store
-rw-r--r--   1 tage  staff    21 Jun  8  2021 .awstats-htpasswd
drwxrwxrwx  27 tage  staff   864 Nov 11 11:41 .backup
-rw-r--r--   1 tage  staff     5 Nov 11 11:41 .backup.lock
-rw-r--r--   1 tage  staff    21 Jun  8  2021 .stats-htpasswd
-rw-r--r--   1 tage  staff    41 Nov 11 11:41 .virtualmin-src
drwxr-xr-x  15 tage  staff   480 Nov 11 04:18 awstats
drwxr-x---   6 tage  staff   192 Jun  8  2021 cgi-bin
drwxr-xr-x   6 tage  staff   192 Jun  8  2021 etc
drwxr-xr-x   5 tage  staff   160 Jun  8  2021 fcgi-bin
drwxr-xr-x   2 tage  staff    64 Jun  8  2021 homes
drwxr-x---   4 tage  staff   128 Jun  8  2021 logs
drwxr-x---  29 tage  staff   928 Nov 11 04:12 public_html
-rw-r--r--   1 tage  staff  3749 Oct 24 07:32 ssl.ca
-rwx------   1 tage  staff  1935 Oct 24 07:32 ssl.cert
-rwx------   1 tage  staff  5686 Oct 24 07:32 ssl.combined
-rwx------   1 tage  staff  7391 Oct 24 07:32 ssl.everything
-rwx------   1 tage  staff  1704 Oct 24 07:32 ssl.key
drwxr-x---   2 tage  staff    64 Jun 17  2021 tmp

Any help would be excellent. Thank you for being here and answering questions. :slight_smile:

The file you are looking for on that archive must be named as domain.name_virtualmin, with approximate size of 3kB.

The other way to restore Virtualmin config file for a domain is using Virtualmin CLI:

virtualmin restore-domain --source /backups/dom.com.tar.gz --domain dom.com --feature virtualmin --fix

However, the downside is that Virtualmin restore sub-command checks for a virtual server information file which is currently empty, and would fail with the following error:

setquota: Bad inode hardlimit: /: Unknown decimal unit. Valid units are k, m, g, t.

It fails as restore command requires at the moment at least user= and dom= set on Virtualmin domain config file (i.e. a file that is found in /etc/webmin/virtual-server/domains directory).

@Jamie, it makes it impossible to restore domain config in this case scenario. I would suggest, when the local Virtualmin domain config file is corrupt, read and use the one that is on the backup, as it already contains an id=, which we can easily associate with local domain.

1 Like

Mate… You are awesome! This resolved my issue :slight_smile:

Check out this change and let me know if it fixes the issue : https://github.com/virtualmin/virtualmin-gpl/commit/faaa8801f038e4977fb663b73f447ab99ab23b0b

I will comment on the commit.

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.

@Jamie, I’m starting to think that this issue could be a result of increased buffer size for read/write operations? We have it set for 32 MiB right now. Which is ridiculously large for any regular operations with config files. For uploads/downloads it may even be too small. But for normal config files read/write operations it is certainly too much!

Could we separate those?

@pearing So, you have around 50 domains, right? How much RAM do you have available?