Thanks Matthew!! Appreciate the info.<br>In the past, the person who normally installs syslog-ng would just download it from <a href="http://sunfreeware.com">sunfreeware.com</a> and update all the libraries and and install it without any compiling. It always worked right out of the box except for the config file:))<br>
<br> I will look for the documentation and start reading. I normally do that anyway but was under a pretty strict timeline.<br><br>Thanks again!!<br><br><div class="gmail_quote">On Fri, Jan 7, 2011 at 2:35 PM, Matthew Hall <span dir="ltr"><<a href="mailto:mhall@mhcomputing.net">mhall@mhcomputing.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">On Fri, Jan 07, 2011 at 10:01:30AM -0500, Zeek Anow wrote:<br>
> I just upgraded to syslog-ng Solaris 10 on a Sun server. When I went to test<br>
> my syslog-ng.conf file I am getting the following error:<br>
><br>
> ld.so.1: syslog-ng: fatal: relocation error: file<br>
> /.alt.Solaris10/usr/local/sbin/syslog-ng: symbol g_malloc_n: referenced<br>
> symbol not found<br>
><br>
> It looks as though something is missing from a library or maybe a path is<br>
> not set correctly. Here are the packages I installed:<br>
><br>
> libiconv-1.13.1-sol10-sparc-local<br>
> glib-2.25.13-sol10-sparc-local<br>
> libintl-3.4.0-sol10-sparc-local<br>
> libgcc-3.4.6-sol10-sparc-local<br>
> pcre-8.10-sol10-sparc-local<br>
> eventlog-0.2.12-sol10-sparc-local<br>
> libpcap-1.1.1-sol10-sparc-local<br>
> tcpdump-4.1.1-sol10-sparc-local<br>
> syslogng-3.1.2-sol10-sparc-local<br>
><br>
> I had originally installed gcc-3.4.6-sol10-sparc-local too, but then<br>
> uninstalled all packages and then reinstalled everything except<br>
> gcc-3.4.6-sol10-sparc-local. The instructions says one or the other.<br>
><br>
> Anyone have any ideas on how to fix this?<br>
><br>
> Thanks<br>
<br>
</div></div>When I ran into these issues I had a fiew different causes, but I was<br>
using Linux, however these could apply in either case.<br>
<br>
1) libdbi's build breaks your CFLAGS and this caused it to generate a<br>
corrupt output .so file<br>
2) PKG_CONFIG_PATH was not right<br>
3) some ./configure options related to libraries were not right<br>
<br>
The g_* symbols are usually in glib, so start your investigation there.<br>
<br>
Validating that the content of config.log makes sense is good.<br>
<br>
Make sure there are no other copies of libs sitting around, this hit me<br>
because my company compiles to a prefix and the linker got some screwed<br>
up old system libs in place of the prefix libs.<br>
<br>
Have a look at the symbols in the libs with nm, test the link with ldd,<br>
watch execution with truss / dtrace / dtruss / etc.<br>
<br>
HTH,<br>
Matthew.<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
<br>
</blockquote></div><br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>