Vphp install Schedule

Next Weeks Schedule (09/26):

09/26 Mon: Unix12 and Unix11
09/27 Tue: Unix9 and Unix8
09/28 Wed: Unix7 and Unix6
09/29 Thu: Unix5 and Unix4

Will be a fun week !

As promissed, Unix12 and Unix11 are running vPHP as of today...

[antic]

I assume this doesn't affect php on Windows machines? That is, no changes to the php config?

[Bevin]

I noticed that the error logs are filling up with 'LETS RUNG THOUGH OUR ARGUMENTS: ARGV[0] /usr/local/tmodelli/php/bin/php' over and over. It doesn’t particularly bother me but I’m curious to know if there is a reason for this?

Antic, this will not affect our Windows Servers, only the unix Servers.

Bevin, this is set to help us debug the domains that break when we install vPHP. They normally work just fine, but sometimes we have domains breaking so we have this debugging enable until we finish migrating the servers.

[Ram_Argid]

Originally Posted by Bevin

I noticed that the error logs are filling up with 'LETS RUNG THOUGH OUR ARGUMENTS: ARGV[0] /usr/local/tmodelli/php/bin/php' over and over. It doesn’t particularly bother me but I’m curious to know if there is a reason for this?

So when will the log files QUIT filling up with the "LETS RUNG THOUGH OUR ARGUMENTS..." junk?

Please submit a ticket about this. I need to know what server, providing your domain will be fine.

This has been fixed on UNIX14 (and most boxes, if not all) if you come across one I can easily remove this debugging.

[Brangwyn]

I don't suppose with all these now running this special vPHP version we can get fopen_URL reinstated could we? .. or has that already happened?

[admin]

I don't think this stops the issues fopen had it would only let us know who is getting hacked afterwards. Before it wrote everything as www or httpd now it writes as the user. I think it could still be risky to turn it back on. Since we made the change we may have had 2 ddos attacks from our boxs, before it was like once a week because of fopen.