Hi, Is there someone who installed syslog-ng on FreeBSD? I am doind it and have an error message. Indeed, I installed libol 0.2.17 and am installing syslog-ng.
I did $ ./configure in the syslog-ng 1.4.5. directory and it worked.
Then I did $ make and I have the following error message : --------------------------------------------------------------------------------------------------------------- ... gcc -DHAVE_CONFIG_H -I. -I/home/sbenoist/syslog-ng-1.4.5/src -I. -O2 -Wall -I/usr/local/include/libol -D_GNU_SOURCE -c syslog-names.c gcc -O2 -Wall -I/usr/local/include/libol -D_GNU_SOURCE -o syslog-ng main.o sources.o center.o filters.o destinations.o log.o cfgfile.o cfg-grammar.o cfg-lex.o affile.o afsocket.o afunix.o afinet.o afinter.o afuser.o afstreams.o afprogram.o utils.o syslog-names.o getopt.o getopt1.o -lfl /usr/local/lib/libol.a log.o: Undefined symbol `_strptime' referenced from text segment *** Error code 1 ---------------------------------------------------------------------------------------------------------------- For earlier versions , I mean 1.2.x, there is no error message.
So did someone encounter this problem?
Thanks, Sylvain
Is there someone who installed syslog-ng on FreeBSD?
according the manpage of strptime on a FreeBSD 3.3 system: HISTORY The strptime() function appeared in FreeBSD 3.0. so you must have an ancient FreeBSD version. Either grab the source of strptime from the CVS, or upgrade your OS. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Balazs Scheidler (bazsi@balabit.hu) wrote:
Is there someone who installed syslog-ng on FreeBSD?
according the manpage of strptime on a FreeBSD 3.3 system:
HISTORY The strptime() function appeared in FreeBSD 3.0.
so you must have an ancient FreeBSD version. Either grab the source of strptime from the CVS, or upgrade your OS.
I'm running syslog-ng on a FreeBSD 3.2-RELEASE machine. It does work but tends to start using alot of CPU time and after that stops logging. Maybe it's my dodgy config... Cheers, John
I'm running syslog-ng on a FreeBSD 3.2-RELEASE machine. It does work but tends to start using alot of CPU time and after that stops logging. Maybe it's my dodgy config...
I'm not using syslog-ng on FreeBSD. Could you provide me some more details? ktrace dump would be helpful. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Balazs Scheidler on Sat 29/07 19:45 +0200:
I'm running syslog-ng on a FreeBSD 3.2-RELEASE machine. It does work but tends to start using alot of CPU time and after that stops logging. Maybe it's my dodgy config...
I'm not using syslog-ng on FreeBSD. Could you provide me some more details? ktrace dump would be helpful.
Incidentally, the 1.4.5 release did fix some of the leak/CPU problems, but only made it a longer period of time before the process eventually uses all system resources; there's still a leak somewhere. I'll have more details within the next couple of weeks.
On Wed, 2 Aug 2000, Scott McDermott wrote:
Balazs Scheidler on Sat 29/07 19:45 +0200:
I'm running syslog-ng on a FreeBSD 3.2-RELEASE machine. It does work but tends to start using alot of CPU time and after that stops logging. Maybe it's my dodgy config...
I'm not using syslog-ng on FreeBSD. Could you provide me some more details? ktrace dump would be helpful.
Incidentally, the 1.4.5 release did fix some of the leak/CPU problems, but only made it a longer period of time before the process eventually uses all system resources; there's still a leak somewhere. I'll have more details within the next couple of weeks.
I've had lots of problems with the stability of syslog-ng on two debian installs, but look at the syslog-ng listing from top on a redhat 6.2 box: PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND 355 root 11 0 20952 20M 432 R 0 56.7 2.6 12616m syslog-ng It's been up and running for `expr 12616 / 60 / 24` == about 8 days with no problems, and it's logging both to the regular logfiles in /var/log plus archiving each host like this: # separate logs destination std { file("/var/log/HOSTS/$HOST/$FACILITY/$YEAR$MONTH/$FACILITY$YEAR$MONTH$DAY" owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes)); }; # log it log { source(net); source(local); destination(std); }; This is for around 50 hosts, so it's a not excactly a light load. It consumes most of the CPU since it's usually the only running process. This is syslog-ng 1.4.4, I forget which libol version (deleted the tarball). I wonder what's so magic about redhat? Any thoughts? -- Nate
I'm running syslog-ng on a FreeBSD 3.2-RELEASE machine. It does work but tends to start using alot of CPU time and after that stops logging. Maybe it's my dodgy config...
I'm not using syslog-ng on FreeBSD. Could you provide me some more details? ktrace dump would be helpful.
Incidentally, the 1.4.5 release did fix some of the leak/CPU problems, but only made it a longer period of time before the process eventually uses all system resources; there's still a leak somewhere. I'll have more details within the next couple of weeks.
I've had lots of problems with the stability of syslog-ng on two debian installs, but look at the syslog-ng listing from top on a redhat 6.2 box:
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND 355 root 11 0 20952 20M 432 R 0 56.7 2.6 12616m syslog-ng
It's been up and running for `expr 12616 / 60 / 24` == about 8 days with no problems, and it's logging both to the regular logfiles in /var/log plus archiving each host like this:
# separate logs destination std { file("/var/log/HOSTS/$HOST/$FACILITY/$YEAR$MONTH/$FACILITY$YEAR$MONTH$DAY" owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes)); };
# log it log { source(net); source(local); destination(std); };
This is for around 50 hosts, so it's a not excactly a light load. It consumes most of the CPU since it's usually the only running process.
This is syslog-ng 1.4.4, I forget which libol version (deleted the tarball). I wonder what's so magic about redhat? Any thoughts?
The last leak I fixed in 1.4.5 was caused by UDP destinations, if the receiving host was not accepting messages on the given port. (e.g. ICMP destination unreachable is returned) If you don't use udp() destinations it doesn't show up. I captured a bug at one of our servers, the central log host went down, and the client host didn't reestablish the connection for some reason. (it was trying as long as the loghost came up, and when it succeeded, it simply stopped logging there) I'll have to check it out, but didn't have too much time. ZORP is eating up all my time now. (it's a new generation proxy firewall suite, check it out at http://www.balabit.hu/zorp.en.phtml) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
On Thu, 3 Aug 2000, Balazs Scheidler wrote:
The last leak I fixed in 1.4.5 was caused by UDP destinations, if the receiving host was not accepting messages on the given port. (e.g. ICMP destination unreachable is returned) If you don't use udp() destinations it doesn't show up.
Actually, now that you mention it, the stable host isn't doing any TCP connections, but the unstable ones are doing TCP connections exclusively. The TCP connections would seem to the culprit. -- Nate
Nate Campi on Thu 3/08 22:16 -0700:
The last leak I fixed in 1.4.5 was caused by UDP destinations, if the receiving host was not accepting messages on the given port. (e.g. ICMP destination unreachable is returned) If you don't use udp() destinations it doesn't show up.
Actually, now that you mention it, the stable host isn't doing any TCP connections, but the unstable ones are doing TCP connections exclusively.
The TCP connections would seem to the culprit.
Simple TCP forwarding (no local logging) seems to work fine, if they are only forwarding from UDP sources. A syslog-ng process doing TCP receiving seems to leak, but I plan on doing some testing to gather more data within a couple of weeks.
participants (5)
-
Balazs Scheidler
-
John
-
Nate Campi
-
Scott McDermott
-
Sylvain Benoist