On Wed, 2007-10-31 at 15:13 +0530, rohit bhute wrote:
However, before I take it upstairs (for the admins to start fiddling
with Squid - I'm just the junior web dev), there are some points I
feel that take Squid out of the picture and ask me to look at the LAMP
tsk tsk. okay, listen up kiddies :P ( no offense meant ), in the
sysadmin business theres one thing that EVERYONE should REMEMBER. It's
like a directive from God :P
"Don't fix it if it ain't broken!"
Repeat it several times and _dont_ do this again.
Lets look at the facts:
Fact 1: Old Server ran PHP4, MySQL4
Fact 2: New server runs PHP5, MySQL5
Fact 3: App was probably coded in the PHP4 environment ( this is
actually an inference that I'm making out of your statements )
Fact 4: See 
Fact 5: PHP5 breaks many PHP4 apps :P
Fact 6: MySQL5 also is responsible for breaking stuff coded for MySQL4
( please read the release notes for further info ;) )
I hope you can understand what I'm getting at. Your app is probably
behaving weirdly because of the incompatibilities between PHP4 and PHP5.
I suspect MySQL ain't the source of the problem.
Now, a personal note. Take this as constructive criticism. Next time you
guys get the itch of upgrading stuff, please set up a box and test your
upgrades. If not that, atleast read the release notes of the softwares
whose major version numbers are changing ( PHP, MySQL, RHEL in this
case ). It'll give you a clue as to what you might expect. I really feel
you should downgrade to your older configuration. I seriously dont
understand why everyone wants bleeding edge stuff? RHEL3 is properly
supported by Redhat. If you can't afford the support, install CentOS.
Geez what were your seniors thinking??? :O
1. The Squid config hasn't changed (that I know
of) from before the
problem occurred to
now - it hasn't been changed in years. Period.
2. Other sites are "working fine".
3. This wasn't occurring before the upgrade.
Dinesh A. Joshi