Plesk creates multiple httpd.include

[Mr.BB]

We also have this issue on Debian 6 64-bit

We also have this issue on Debian 6 64-bit with Plesk 10.3

-rw-r----- 1 root www-data 2461 Jul 6 20:18 13099798810.83108200_httpd.include
-rw-r----- 1 root www-data 3307 Jul 6 20:18 13099798830.94690800_httpd.include
-rw-r----- 1 root www-data 3307 Jul 6 20:18 13099798840.93538000_httpd.include
-rw-r----- 1 root www-data 4157 Jul 6 20:18 13099798850.65937500_httpd.include
-rw-r----- 1 root www-data 4403 Jul 6 20:18 13099798860.55934100_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 20:30 13099806200.94440300_httpd.include
-rw-r----- 1 root www-data 4541 Jul 6 20:31 13099806710.43914500_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 20:31 13099806820.57311000_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855400.86788400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855420.50031100_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855430.61501700_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855440.73348600_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855450.89646400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855470.06145400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855480.29254000_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855490.47837800_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855500.67399000_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855510.85363700_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855530.01315200_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855540.20834400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855550.41594900_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855560.58693700_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855570.80649200_httpd.include
-rw-r----- 1 root www-data 5244 Jul 6 22:02 13099861700.19691300_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 22:03 13099861900.28893900_httpd.include
-rw-r----- 1 root www-data 4541 Jul 6 22:07 13099864200.15376300_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 22:07 13099864600.70705000_httpd.include

 

[EduardoG]

Same proble here with a clean install of plesk 10.3.
Bug still unresolved for more than 7 months, why?
If so many of us are having the same issue, for sure is a bug!

 

[TairkH]

We have same problem here on plesk 10.2 we using centos 5.6

 

[IgorG]

Same proble here with a clean install of plesk 10.3.
Bug still unresolved for more than 7 months, why?
If so many of us are having the same issue, for sure is a bug!

Could you please clarify how it is affect correct operation of your Plesk? Why do you think that it is critical bug?

 

[toomanylogins]

Webfusion customers have this problem

I've got this problem with Plesk 10.2 we are using a webfusion vps. Webfusion our UK hosting company.

 

[StefanieW]

we have same problems, using centos 5.6 . last server was a fresh install with plesk 10.3 and centos 6, other server updated from 9.5.4 to 10.1 .... to 10.3 and have also multiple httpd.include files

 

[FollowTheMedia]

Same problem here. It's not a major bug, but it's a little bit annoying because it floods my directories with 6 KB files.

 

[vincenzot]

Hello,

same bug with latest of plesk installation 10.3.1 MU4.

Plesk 10.3.1 + CloudLinux5

 

[Teezy]

Http.include files

Anyone know where that number is generated from?

Also this does not appear to be a bug to me, because the new include file it creates, plesk is updating '/usr/local/psa/admin/conf/vhosts_bootstrap.conf' with the new file to look at for each domain. If it was a bug it wouldn't know to update this file?

In addition the fact that they have not fixed it yet further makes me believe that this is how its suppose to function and its just bad coding on their part. They should of just setup a symbolic link which updates to the new file, keeping the primary file name intact.

Cheers

Teezya

 

[hardlink]

Hi, I was on Plesk 9 and upgraded to Plesk 10.3.1 with CBM 10.3.0.

Is there a work around for this issue? Can we just delete the extra files?

HOW TO REPLICATE PROBLEM
I created a vhost.conf file in...
/var/www/vhosts/mydomain.net/conf/vhost.conf
and then ran
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain mydomain.net
and after a few times of modifying and reconfiguring later I have found lots of http files.

ACTUAL RESULT
13193732760.83460100_httpd.include 13193771450.45927700_httpd.include 13193775220.87584500_httpd.include 13193767390.93092700_httpd.include 13193772790.36747800_httpd.include 13193780110.09689400_httpd.include webalizer.conf vhost.conf

I know this is a minor bug but it's an ongoing one!

Thanks,

Chris

 

[hardlink]

Answered my own question... You CAN just delete all of the httpd.include files, apart from the newest one.

Here's an option if you want to automate it...

#List all files as they are currently
ls /var/www/vhosts/*/conf/*_httpd.include
#Delete them all
rm -f /var/www/vhosts/*/conf/*_httpd.include
#Recreate a single copy of them all
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all

 

[Kirill K]

Anyone know where that number is generated from?

This number is hardcoded inside Plesk code. It is equal to 5.

In addition the fact that they have not fixed it yet further makes me believe that this is how its suppose to function and its just bad coding on their part. They should of just setup a symbolic link which updates to the new file, keeping the primary file name intact.

It will be implemented in one of the next updates.

 

[Kirill K]

We also have this issue on Debian 6 64-bit with Plesk 10.3

-rw-r----- 1 root www-data 2461 Jul 6 20:18 13099798810.83108200_httpd.include
-rw-r----- 1 root www-data 3307 Jul 6 20:18 13099798830.94690800_httpd.include
-rw-r----- 1 root www-data 3307 Jul 6 20:18 13099798840.93538000_httpd.include
-rw-r----- 1 root www-data 4157 Jul 6 20:18 13099798850.65937500_httpd.include
-rw-r----- 1 root www-data 4403 Jul 6 20:18 13099798860.55934100_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 20:30 13099806200.94440300_httpd.include
-rw-r----- 1 root www-data 4541 Jul 6 20:31 13099806710.43914500_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 20:31 13099806820.57311000_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855400.86788400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855420.50031100_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855430.61501700_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855440.73348600_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855450.89646400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855470.06145400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855480.29254000_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855490.47837800_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855500.67399000_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855510.85363700_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855530.01315200_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855540.20834400_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855550.41594900_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855560.58693700_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 21:52 13099855570.80649200_httpd.include
-rw-r----- 1 root www-data 5244 Jul 6 22:02 13099861700.19691300_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 22:03 13099861900.28893900_httpd.include
-rw-r----- 1 root www-data 4541 Jul 6 22:07 13099864200.15376300_httpd.include
-rw-r----- 1 root www-data 4835 Jul 6 22:07 13099864600.70705000_httpd.include

Plesk saves only 5 last config files, other will be removed during execution of Plesk daily maintenance script.
For example, it works on Plesk 10.4:

# ls /var/www/vhosts/domain.test/conf/ |wc -l
18
# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php
# ls /var/www/vhosts/domain.test/conf/ |wc -l
5
#

 

[Lars Diersmann]

Same

Hello all,

The Same Problem still exists in Pllesk 10.4.4MU15


Thanks Lars

 

[IgorG]

Hello all,

The Same Problem still exists in Pllesk 10.4.4MU15


Thanks Lars

I can't confirm it:

[root@plesk10 ~]# cat /root/.autoinstaller/microupdates.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<patches>
<product id="plesk" version="10.4.4" installed-at="20111110T011622">
<patch version="15" timestamp="" installed-at="20120201T053538" />
</product>
</patches>

[root@plesk10 ~]# ls /var/www/vhosts/plesk104.abezborodova.ru/conf/ |wc -l
12

[root@plesk10 ~]# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php

[root@plesk10 ~]# ls /var/www/vhosts/plesk104.abezborodova.ru/conf/ |wc -l
5

As you can see all looks fine on MU#15

 

[EgidijusS]

I can confirm the same issue with Plesk 10.3.0 on CentOS 5.6.

 

[IgorG]

I can confirm the same issue with Plesk 10.3.0 on CentOS 5.6.

Use latest Plesk version.

 

[EgidijusS]

I'm reading this forum everyday since 10.4.4 was realized and see how much problems people have. Yes my system is old, but it works without errors. And I will not upgrade system until see that all major problems are fixed. As I see version 10.4.x is more buggy, than all previous I think together. Due to a lot of features ("strange" changes, It's my view) Plesk goes very unstable system with a lot of problems. A lot of people talks about that in forum.

 

[IgorG]

Nobody ever wrote on the forums about the good things. Only about problems. Look at the cPanel forum. There are messages only about problems too.
And we produce microupdates for Plesk every week and make it better and better. It is strange do not use the system, which is constantly improved on weekly base.

 

[EgidijusS]

YES, it is good to hear that system is improved every week. Another issue that there is problems with age of half year or even more. So, in my view, at the moment Plesk 10.4.4 is in ~ RC1 maybe RC2 stage - no more. We can use it for testing purposes only, but not in production.

But we are going to off topic. Not the place, not the time. Let's wait for solution on topic.