• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk creates multiple httpd.include

C

cpes

Guest
Everytime vhost for domain is being reconfigured, plesk creates new httpd.include file. In use is just one. Others are unused.

-rw-r----- 2010-11-11 16:43 12894902080.94691100_httpd.include
-rw-r----- 2010-11-11 16:57 12894910330.37320000_httpd.include
-rw-r----- 2010-11-11 16:58 12894910930.22155300_httpd.include
-rw-r----- 2010-11-11 16:58 12894910970.12314600_httpd.include
-rw-r----- 2010-11-11 16:58 12894911010.07271600_httpd.include
-rw-r----- 2010-11-11 16:58 12894911050.21273700_httpd.include
-rw-r----- 2010-11-11 16:58 12894911090.22252400_httpd.include
-rw-r----- 2010-11-11 16:58 12894911130.26347700_httpd.include
-rw-r----- 2010-11-11 16:58 12894911170.61487200_httpd.include
-rw-r----- 2010-11-11 16:58 12894911210.59946800_httpd.include
-rw-r----- 2010-11-11 16:58 12894911250.64847700_httpd.include
-rw-r----- 2010-11-11 16:58 12894911290.71979900_httpd.include
-rw-r----- 2010-11-11 16:58 12894911330.82606000_httpd.include
-rw-r----- 2010-11-11 16:58 12894911370.86554700_httpd.include
-rw-r----- 2010-11-11 16:59 12894911410.95754100_httpd.include
-rw-r----- 2010-11-11 16:59 12894911450.87864000_httpd.include
-rw-r----- 2010-11-11 16:59 12894911490.80700100_httpd.include
-rw-r----- 2010-11-11 16:59 12894911530.74916300_httpd.include
-rw-r----- 2010-11-11 16:59 12894911570.80394000_httpd.include
-rw-r----- 2010-11-11 16:59 12894911610.82906900_httpd.include
-rw-r----- 2010-11-11 16:59 12894911650.78070400_httpd.include
-rw-r----- 2010-11-11 16:59 12894911690.72428200_httpd.include
-rw-r----- 2010-11-11 16:59 12894911730.68949200_httpd.include
-rw-r----- 2010-11-11 16:59 12894911770.69748200_httpd.include
-rw-r----- 2010-11-11 16:59 12894911810.73876900_httpd.include
-rw-r----- 2010-11-11 16:59 12894911850.79338000_httpd.include
-rw-r----- 2010-11-11 16:59 12894911890.79281000_httpd.include
-rw-r----- 2010-11-11 16:59 12894911930.81348700_httpd.include
-rw-r----- 2010-11-11 16:59 12894911970.71730200_httpd.include
-rw-r----- 2010-11-11 17:00 12894912010.73485400_httpd.include
-rw-r----- 2010-11-11 17:00 12894912110.01210800_httpd.include
-rw-r----- 2010-11-11 17:00 12894912150.09301300_httpd.include
-rw-r----- 2010-11-11 17:00 12894912190.13698700_httpd.include
-rw-r----- 2010-11-11 17:00 12894912230.11363600_httpd.include
-rw-r----- 2010-11-11 17:00 12894912270.23921400_httpd.include
-rw-r----- 2010-11-11 17:00 12894912310.22719000_httpd.include
-rw-r----- 2010-11-11 17:00 12894912350.21154300_httpd.include
-rw-r----- 2010-11-11 17:00 12894912390.21603400_httpd.include
-rw-r----- 2010-11-11 17:00 12894912430.18665900_httpd.include
-rw-r----- 2010-11-11 17:00 12894912470.23048600_httpd.include
-rw-r----- 2010-11-11 17:00 12894912510.24060700_httpd.include
-rw-r----- 2010-11-11 17:00 12894912550.22023500_httpd.include
-rw-r----- 2010-11-11 17:00 12894912590.20967400_httpd.include
-rw-r----- 2010-11-11 17:01 12894912630.19031400_httpd.include

Why is this good for? Why old httpd.include files are not deleted?

Thanks.
 
I have submitted request to developers. Let's wait their answer.
 
I just created a new post about this - my apologies.

I am having the same issue. Any news?
 
Bug under developers investigation now. I hope it will be fixed in the next Plesk update.
 
for the record I got the same issue....



I got a question regarding the creation of this files. (just for the plesk developers)

Is it generated from any template file ? or the system create it from another source?

yoel
 
By the way, this bug hasn't been resolved in Plesk 10.1.1. :/
 
This is not a demising issue, though it is an annoyance when working with virtual hosts.

There have been several micro updates but to no avail with this issue.

Please can we have some form of feedback on this?
 
Developers have considered this bug as minor bug and promised that it will be removed by daily maintenance script in the one of next Plesk release.
 
why isn't this fixed yet?

We are running the latest version of plesk 10 and this still hasn't been fixed yet ?

-rw-r----- 1 root apache 368 Jun 16 09:55 13082397200.68982900_httpd.include
-rw-r----- 1 root apache 5525 Jun 16 09:55 13082397200.68982900_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 13:22 13083385350.64038400_httpd.include
-rw-r----- 1 root apache 5525 Jun 17 13:22 13083385350.64038400_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 13:23 13083385970.58186300_httpd.include
-rw-r----- 1 root apache 5525 Jun 17 13:23 13083385970.58186300_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 13:34 13083392690.90485800_httpd.include
-rw-r----- 1 root apache 5593 Jun 17 13:34 13083392690.90485800_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 15:16 13083453770.34541000_httpd.include
-rw-r----- 1 root apache 5597 Jun 17 15:16 13083453770.34541000_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 20 05:42 13085701540.37345600_httpd.include
-rw-r----- 1 root apache 5597 Jun 20 05:42 13085701540.37345600_httpd_ip_default.include
-rw-r--r-- 1 root psacln 357 Jun 20 05:42 vhost.conf
-rw-r--r-- 1 root root 23982 Jun 16 09:55 webalizer.conf

It seems that updates are happening every few weeks .. I'm surprised that this hasn't been looked at yet!
 
Developers can't reproduce it on 10.2 version. But we will check it again.
 
Some more info

IgorG here is some more information for you:

OS: CentOS release 5.6 (Final)
Plesk Version: 10.2.0 CentOS 5 1011110331.11
Command that creates extra includes: /usr/local/psa/admin/bin/httpdmng --reconfigure-all
Extra includes created in: /var/www/vhosts/<yourdomain>/conf/

ls -la
total 164
drwxr-x--- 2 root psaserv 4096 Jun 21 02:32 .
drwxr-xr-x 20 root root 4096 Jun 18 11:02 ..
-rw-r----- 1 root apache 368 Jun 16 09:55 13082397200.68982900_httpd.include
-rw-r----- 1 root apache 5525 Jun 16 09:55 13082397200.68982900_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 13:22 13083385350.64038400_httpd.include
-rw-r----- 1 root apache 5525 Jun 17 13:22 13083385350.64038400_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 13:23 13083385970.58186300_httpd.include
-rw-r----- 1 root apache 5525 Jun 17 13:23 13083385970.58186300_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 13:34 13083392690.90485800_httpd.include
-rw-r----- 1 root apache 5593 Jun 17 13:34 13083392690.90485800_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 17 15:16 13083453770.34541000_httpd.include
-rw-r----- 1 root apache 5597 Jun 17 15:16 13083453770.34541000_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 20 05:42 13085701540.37345600_httpd.include
-rw-r----- 1 root apache 5597 Jun 20 05:42 13085701540.37345600_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 20 05:54 13085708960.38067500_httpd.include
-rw-r----- 1 root apache 5597 Jun 20 05:54 13085708960.38067500_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 20 11:34 13085912950.93205400_httpd.include
-rw-r----- 1 root apache 5597 Jun 20 11:34 13085912950.93205400_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 20 11:36 13085913610.59547900_httpd.include
-rw-r----- 1 root apache 5597 Jun 20 11:36 13085913610.59547900_httpd_ip_default.include
-rw-r----- 1 root apache 368 Jun 21 02:32 13086451640.97422000_httpd.include
-rw-r----- 1 root apache 5597 Jun 21 02:32 13086451640.97422000_httpd_ip_default.include
-rw-r--r-- 1 root psacln 357 Jun 20 05:42 vhost.conf
-rw-r--r-- 1 root root 23982 Jun 16 09:55 webalizer.conf
 
I'm seeing this bug too with Plesk 10.2 on Debian 64 bit. It's causing no end of grief with the migration manager, because it thinks there's more IP addresses in use than there actually are, and sometimes old and no longer existent IPs which throws the "only one IP per subscription allowed" error when migrating subs.
 
still not fixed!

Just installed latest plesk 10.2 micro updates and this bug is still not fixed as of July 4 2011.
 
I'm seeing this bug too with Plesk 10.2 on Debian 64 bit. It's causing no end of grief with the migration manager, because it thinks there's more IP addresses in use than there actually are, and sometimes old and no longer existent IPs which throws the "only one IP per subscription allowed" error when migrating subs.

Ok. Thank you. I have forwarded it to developers.
Could someone please describe other issues that were caused by this problem?
 
Back
Top