Skip to main content

Stupidity

A requirement came to me that we need to enable timeout in php-curl with timeout values being in millisecond. We cant even wait for a second to curl to terminate. Php uses native curl in unix systems. The curl supports this feature in version>7.19. For our OS the curl version is 7.15. Ofcourse we can install 7.19 using rpm or source

But php had a wrapper module curl.so, so all php-curl method call will go to curl.so which inturn will call native curl. So curl.so is not aware of the timeout_ms in feature and started throwing php errors. 

A hack would be to replace curl.so with the one which supports timeout_ms from other version of OS. 
But nobody is interested in this change because if something crashes in production, it would be huge effort and loss. 

I downloaded the Source RPMS(RPM are binary and Source RPMS will have the source code and SPEC file). The SPEC file will take care of configure, make and install part (which we have to do manually if we install from source). I could not find any difference in any file of php SRPM between our OS and newer version of the same distro. 

Since we need this change within week, we decided to upgrade our OS. Upgrading OS can break something which wont be in our sight. We started a sequence of tests in the newer version of OS and came up with a schedule and approval from concerned leads.
Then I was asked why cant we recompile php by my manager during an informal meet. I was pretty much sure recompiling php wont work because both SRPMS dont differ by any means(stupidity 1).

Reality:
There is a file interface.c in php source code which adds features based on the curl version.

#if LIBCURL_VERSION_NUM > 0x071002
REGISTER_CURL_CONSTANT(CURLOPT_TIMEOUT_MS);
#endif  

Next my assumption was if I have correct curl(dynamic libraries) before installing php, php-curl would detect the feature automatically(stupidity 2).

This didnt work, php threw an error dependency module libcurl.so.3 not found despite libcurl.so.4 module present(new version).

Lets understand the process of C compilation before understanding this issue
C  preprocesses all source file, header files and compiles them and links static libraries to form binary. Hereafter we dont need the header files to run binaries. 

The same thing happens once we build rpm, we need curl-devel(similar to curl.h files)to build rpm and we dont need them once binary is created. They are called build dependency. 

This php module is built with curl-devel version<7.19. So it requires dynamic library libcurl.so.3 while running. I have to just rebuild php with the latest version of curl-devel to detect libcurl.so.4. 

We were almost prepared for a big change in our infrastructure without looking for an available easier option. 

Comments

Popular posts from this blog

The FB outage

 This outage has caused considerable noise everywhere. It was quite discomforting for me because during the whole conversation nobody bothered to understand the gravity of the issue. I don't expect end users to understand the issue. But this is going to be a blogpost for all of those in the tech field, Such an event can happen how much ever chaos engineering, best of the tech jargon we implement in the stack To all my Site Reliability Engineer friends, Site Up is our first priority. I myself said many a times outage is news and SREs should prevent outage. But I'm afraid this is leading to a cult in the industry who despises outages and takes no learnings from it. I don't know what has happened in Facebook. I can explain a scenario which may or may not be right but that can definitely show the gravity of the issue. Let's draw a probable Facebook architecture Disclaimer I don't work at Facebook. So this might not be how facebook routes traffic. This is based on my exp

How we have systematically improved the roads our packets travel to help data imports and exports flourish

This blog post is an account of how we have toiled over the years to improve the throughput of our interDC tunnels. I joined this company around 2012. We were scaling aggressively then. We quickly expanded to 4 DCs with a mixture of AWS and colocation. Our primary DC is connected to all these new DCs via IPSEC tunnels established from SRX. The SRX model we had, had an IPSEC throughput of 350Mbps. Around December 2015 we saturated the SRX. Buying SRX was an option on the table. Buying one with 2Gbps throughput would have cut the story short. The tech team didn't see it happening. I don't have an answer to the question, "Is it worth spending time in solving a problem if a solution is already available out of box?" This project helped us in improving our critical thinking and in experiencing the theoretical network fundamentals on live traffic, but also caused us quite a bit of fatigue due to management overhead. Cutting short the philosophy, lets jump to the story.

More on Memory

 A post almost after 2 years!!! One common question I get asked is, "what is the reference I follow for troubleshooting an issue at hand". I would not be able to give an answer to the question directly as most of the times, I won't have even a single reference material handy. It's not a self boasting article. It's an article describing how knowledge we gather at random places help during an issue. Let's dissect a memory usage issue in Linux I faced recently and see how the triage shaped up. One of our processes was getting repeated ENOMEM when it was trying to call malloc for some reason despite the box had plenty of unused RAM. Lets see how the triage went through I didn't understand in my Operating systems course what a virtual memory is. I did convincing myself that virtual memory is physical memory + swap(in a way correct but not completely) I attended an interview in 2013, where the Director of the division asked me when you do malloc do you get physi