Skip to main content

php5-cli Installation on Debian 3.1

Major turmoil was caused while installing php5-cli package on our staging server. This is the pre-installation confirmation.
xxxx@hhhhh:~$ sudo apt-get install php5-cli
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
ca-certificates libapache2-mod-php5 libc6 libcurl3 libdb4.4 libidn11 libkrb53 libncurses5 libreadline5 libssl0.9.8 libxml2 locales
php5-common php5-curl php5-mysql readline-common tzdata
Suggested packages:
php-pear glibc-doc libcurl3-gssapi libldap2-dev krb5-doc krb5-user
Recommended packages:
libgpmg1 xml-core
The following packages will be REMOVED:
base-config initrd-tools kernel-image-2.4.27-2-386 ssh-krb5
The following NEW packages will be installed:
ca-certificates libdb4.4 libssl0.9.8 php5-cli readline-common tzdata
The following packages will be upgraded:
libapache2-mod-php5 libc6 libcurl3 libidn11 libkrb53 libncurses5 libreadline5 libxml2 locales php5-common php5-curl php5-mysql
12 upgraded, 6 newly installed, 4 to remove and 151 not upgraded.
Need to get 19.7MB of archives.
After unpacking 18.6MB disk space will be freed.
Do you want to continue? [Y/n]
Can't exactly remember how I managed to fix the break-ups, or even specifically what the problem(s) were, but I'll try to prepare for surprises on production machine.

After a few hours of deliberation, I decided to not install php5-cli on my Debian 3.1 and work-around.

Work Around

The work-around is to create the PDF's on my staging server by a remote SSH call from production server, let the PDF's be generated on STAG, and SCP them back to PROD. Wrote a tiny script with necessary commands, so this could pretty much be set & forget.

The only major glitch is that the STAG database is not up to date with the latest catalog/product information. So if new products are added to PROD or product descriptions changed, there is no automatic process in the work-flow which updates STAG, and hence ensures that PDFs generated are up to date.

I'm looking into setting up STAG as a MySQL replication slave to the PROD server and if there are not too many changes required on PROD itself, I'll probably end up implementing this for ensuring fresh data on STAG.

This setup might have to be reworked if we upgrade to Debian 4.0, but I think that won't be the case until we have a system wide upgrade to Network 3.0 (probably late 2008, considering we are still in process of implementing Network 2.0)


Popular posts from this blog

Paypal's Ridiculous Business Practices

In Q3-2005 we discovered the power of online sales and started to market Wapsol's products extensively online. Just as importantly we decided to get into the trading business for WLAN accessories (antennae, cable, connectors etc) which entails buying from manufacturers and selling on online-retail. Needless to say ebay's 26 worldwide markets were lucrative points of sales.

We used Paypal for collecting most of payments from customers outside Germany. The numbers ticked up fast and we were hecticly building up infrastructure for shipping, online-support, product-portfolio and payment-systems.

One morning as I woke up in Germany I found that Paypal decided to lock up our account without any specific reason. There were no disputes or complaints from buyers or anything that suggested provocation. They just locked it. In it a few thousands of dollars of cash-flow and the account was listed as a favored payment option for some 100 pending auctions - now customers couldn't pay for …

The Dream of the Information Age

If this beauty of a device meets it's mission of being owned by every kid on the planet, we are looking to a new dimension of the Information Age.
For full profile of the device, visit BBC's technology page.

SnagIT Problem Solved! (Hangs for minutes)

Here's the solution to the SnagIT sluggishness (hangs for several minutes)
I would try first turning off the magnifier window under tools > program preferences > program options. Uncheck the box to show magnifier windows. Click apply > ok and then try the capture again.Check your security software and make sure that Snagit is set as a safe application. A security program that consistently scans the process will cause a very slow response like you are seeing.Please also check your printers per this article:Answer Title: Slow SnagIt startupAnswer Link:, please review the steps here and try these as well:Answer Title: SnagIt crashes or hangs when launchedAnswer Link: me know what happens.