Skip to main content

Building an RPM: debuginfo package not being created

(Very short version, for the benefit of the frustrated: comments in RPM SPEC files don't do what you think).

I was building an RPM for NXLOG ( because I needed to get a debuginfo package in order to help diagnose a memory leak from the vendor's supplied SPEC file. NXLOG helpfully includes a script in its source-code. What I expected to see near the end of the build was the following output:

Wrote: /home/cameron/src/rpm/SRPMS/nxlog-ce-2.8.1248-1.src.rpm
Wrote: /home/cameron/src/rpm/RPMS/x86_64/nxlog-ce-2.8.1248-1.x86_64.rpm
Wrote: /home/cameron/src/rpm/RPMS/x86_64/nxlog-ce-debuginfo-2.8.1248-1.x86_64.rpm

However, it wasn't building the debuginfo package (that line was missing).

Firstly, make sure you have the redhat-rpm-config package installed, and a debuginfo package should be built by default. If not, then something may be disabling it (such as something in ~/.rpmmacros). But I didn't get the debuginfo package.

Second, check the SPEC file. In this particular case, there was a line at the top that said the following:

#%define debug_package 1

Anyone would think that that's a comment... and unfortunately, you'd be only partly correct. What we really needed was to either remove the line altogether, or write it as:

#%%define debug_package 1

This is due to the macros being evaluated as part of the proprocessing stage (the macros don't intepret the comment lines). In a multiline-macro, this would cause only the first line to be commented. Thank goodness for Aaron D. Marasco's comment regarding this on Stack Overflow.

But why would removing the line entirely make it work? Because in any recent rpm environment, the debuginfo stuff should be built automatically, from about Fedora 9 onwards (not sure if that would include RHEL 5, but it does cover RHEL 6). The automatic building of debuginfo packages was announced in 2003. That's what the 'redhat-rpm-config' package is reponsible for. Otherwise, you might need to include the %define debug_package 1

Note that disabling the debuginfo from your SPEC file should only really be done with good reason (eg. it doesn't make sense to provide debuginfo packages).

Hope that helps,


Popular posts from this blog

ORA-12170: TNS:Connect timeout — resolved

If you're dealing with Oracle clients, you may be familiar with the error message
ERROR ORA-12170: TNS:Connect timed out occurred I was recently asked to investigate such a problem where an application server was having trouble talking to a database server. This issue was blocking progress on a number of projects in our development environment, and our developers' agile post-it note progress note board had a red post-it saying 'Waiting for Cameron', so I thought I should promote it to the front of my rather long list of things I needed to do... it probably also helped that the problem domain was rather interesting to me, and so it ended being a late-night productivity session where I wasn't interrupted and my experimentation wouldn't disrupt others. I think my colleagues are still getting used to seeing email from me at the wee hours of the morning.

This can masquerade as a number of other error strings as well. Here's what you might see in the sqlnet.log f…

Getting MySQL server to run with SSL

I needed to get an old version of MySQL server running with SSL. Thankfully, that support has been there for a long time, although on my previous try I found it rather frustrating and gave it over for some other job that needed doing.

If securing client connections to a database server is a non-negotiable requirement, I would suggest that MySQL is perhaps a poor-fit and other options, such as PostgreSQL -- according to common web-consensus and my interactions with developers would suggest -- should be first considered. While MySQL can do SSL connections, it does so in a rather poor way that leaves much to be desired.

UPDATED 2014-04-28 for MySQL 5.0 (on ancient Debian Etch).

Here is the fast guide to getting SSL on MySQL server. I'm doing this on a Debian 7 ("Wheezy") server. To complete things, I'll test connectivity from a 5.1 client as well as a reasonably up-to-date MySQL Workbench 5.2 CE, plus a Python 2.6 client; just to see what sort of pain awaits.

UPDATE: 2014-0…

From DNS Packet Capture to analysis in Kibana

UPDATE June 2015: Forget this post, just head for the Beats component for ElasticSearch. Beats is based on PacketBeat (the same people). That said, I haven't used it yet.

If you're trying to get analytics on DNS traffic on a busy or potentially overloaded DNS server, then you really don't want to enable query logging. You'd be better off getting data from a traffic capture. If you're capturing this on the DNS server, ensure the capture file doesn't flood the disk or degrade performance overmuch (here I'm capturing it on a separate partition, and running it at a reduced priority).

# nice tcpdump -p -nn -i eth0 -s0 -w /spare/dns.pcap port domain

Great, so now you've got a lot of packets (set's say at least a million, which is a reasonably short capture). Despite being short, that is still a massive pain to work with in Wireshark, and Wireshark is not the best tool for faceting the message stream so you can can look for patterns (eg. to find relationshi…