Subject: RE: -linux/bin/ld: cannot find -lglib-2.0 - msg#00100

Previous Message by Date: click to view message preview

RE: -linux/bin/ld: cannot find -lglib-2.0

> > > static glib, syslog-ng tries to link to glib statically. > > > > Thanks for your answer. > > What do I have to do ? > > the static library is in the devel package usually, you need > to look for something like libglib-2.0.a Please excuse, but I still don't understand. libglib-2.0.la is in /usr/local/lib what do I have to do? I still have /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../../../i486-slackware -linux/bin/ld: cannot find -lglib-2.0 What lib is it exactly looking for ? in /usr/local/lib I also have the glib-2.0 directory which includes a header file. Thank you Philipp _______________________________________________ syslog-ng maillist - syslog-ng@xxxxxxxxxxxxxxxx https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

Next Message by Date: click to view message preview

io.c read() error?

      I am using syslog-ng 1.6.5 on a Gentoo Linux system running kernel 2.6.9.  I have recently modified an open source utility called NTsyslog to send Windows NT style event logs via TCP to my syslog-ng server.  Everything seems to work fine except I receive a io.c read() error for every event sent over the network via TCP.  Anyone have any ideas of what my problem might be?  Here are a few bits of info:     Logs that I see when TCP syslog communication is attempted:   Mar 30 10:43:48 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3038 Mar 30 10:43:48 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:43:48 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3038 Mar 30 10:43:48 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3039 Mar 30 10:43:48 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:43:48 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3039 Mar 30 10:49:05 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3066 Mar 30 10:49:05 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:49:05 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3066 Mar 30 10:49:05 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3067 Mar 30 10:49:05 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:49:05 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3067 Mar 30 10:53:59 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3077 Mar 30 10:53:59 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:53:59 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3077 Mar 30 10:53:59 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3078 Mar 30 10:53:59 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:53:59 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3078 Mar 30 10:58:53 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3092 Mar 30 10:58:53 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:58:53 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3092 Mar 30 10:59:16 src@lookout syslog-ng[3166]: AF_INET client connected from 192.168.11.19, port 3093 Mar 30 10:59:16 src@lookout syslog-ng[3166]: io.c: do_read: read() failed (errno 104), Connection reset by peer Mar 30 10:59:16 src@lookout syslog-ng[3166]: AF_INET client dropped connection from 192.168.11.19, port 3093     Afinet.c in syslog-ng 1.6.6 sources where io_read() is called:     /* af_inet source connection */ static int do_init_afinet_source_connection(struct log_handler *c,                                                  struct syslog_config *cfg,                                                  struct persistent_config *persistent) {             CAST(afsocket_source_connection, self, c);             if (self->client_addr) {                         CAST(inet_address_info, inet, self->client_addr);                           /* SOCK_STREAM */                         notice("AF_INET client connected from %S, port %i\n",                                inet->ip, inet->port);                         io_read(self->client,                                     make_log_reader(0, NULL, cfg->log_msg_size, 0, cfg->check_hostname ? LF_CHECK_HOSTNAME : 0, cfg->bad_hostname, c),                                     make_afsocket_source_close_callback(self));             }             else {                         /* SOCK_DGRAM */                         io_read(self->client,                                     make_log_reader(1, NULL, cfg->log_msg_size, 0, cfg->check_hostname ? LF_CHECK_HOSTNAME : 0, cfg->bad_hostname, c),                                     make_afsocket_source_close_callback(self));             }                         return ST_OK | ST_GOON; }   < -----END of CODE ---- >     I have been trying to find what values are passed to io_read() and make_log_reader() but I have been unsuccessfull.  Thanks in advance for any replies.     Alex S.     <p class=MsoNormal><span style='font-size:8.5pt'>This e-mail contains Omaha Public Power District's confidential and proprietary information and is for use only by the intended recipient.  Unless explicitly stated otherwise, this e-mail is not a contract offer, amendment, nor acceptance.  If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.</p>

Previous Message by Thread: click to view message preview

RE: -linux/bin/ld: cannot find -lglib-2.0

> > > static glib, syslog-ng tries to link to glib statically. > > > > Thanks for your answer. > > What do I have to do ? > > the static library is in the devel package usually, you need > to look for something like libglib-2.0.a Please excuse, but I still don't understand. libglib-2.0.la is in /usr/local/lib what do I have to do? I still have /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../../../i486-slackware -linux/bin/ld: cannot find -lglib-2.0 What lib is it exactly looking for ? in /usr/local/lib I also have the glib-2.0 directory which includes a header file. Thank you Philipp _______________________________________________ syslog-ng maillist - syslog-ng@xxxxxxxxxxxxxxxx https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

Next Message by Thread: click to view message preview

Syslog-ng 1.6.6 Redhat ES 3.0 - too many open files

I've sucessfully beaten down the memory leak issues I've been experiencing thanks to Balazs suggested patches. I am now experiencing a different sort of "leak".     I worked back from the log files to identify the problem, but not the cause. I restart syslog-ng weekly.  Towards the end of each week, I notice log messages: syslog-ng[15710]: STATS: dropped 12828 syslog-ng[15710]: Error initializing raw socket, spoof- source support disabled. (libnet_open_raw: SOCK_RAW allocation failed: Too many open files) syslog-ng[15710]: Error initializing raw socket, spoof- source support disabled. (libnet_open_raw: SOCK_RAW allocation failed: Too many open files) syslog-ng[15710]: Error initializing raw socket, spoof- source support disabled. (libnet_open_raw: SOCK_RAW allocation failed: Too many open files) A quick "lsof -c syslog-ng" revealed a few hundred open files.   I restarted syslog-ng and checked for open files - the number was about 25. In the past hour of monitoring, that number has jumped to over 70.  The "files" that appear to be increasing are these (from the output of lsof) : syslog-ng 17081 root   61u   raw                     51703353 00000000:00FF->00000000:0000 st=07 syslog-ng 17081 root   62u   raw                     51711769 00000000:00FF->00000000:0000 st=07 syslog-ng 17081 root   63u   raw                     51721047 00000000:00FF->00000000:0000 st=07 syslog-ng 17081 root   64u   raw                     51727149 00000000:00FF->00000000:0000 st=07 syslog-ng 17081 root   65u   raw                     51738764 00000000:00FF->00000000:0000 st=07 My syslog-ng.conf specifies only 4 real log file to write to, and one pipe(for mysql writing), and two UDP destinations (spoof enabled). CPU utilization on the machine is less than 5%, and there's plenty of free memory. Any thoughts?  I'd hate to have to restart syslog-ng daily.