Hi, first post. Red Hat RHAS3 update 4. Saturday I downloaded libol 0.3.16 and syslog-ng 1.6.8 tarballs, saw immediately that there were rpm spec files and made rpms (not without an initial couple of barfs about missing MySQL stuff), which I installed. Took me Sunday and Monday till 10:00 am to get my head round it, but it's fantastic, thanks a lot:) So then I downloaded 1.9.5 and eventlog-0.2.3+20050116+1856. There were no rpm spec files, so I wrote my own (half a morning on the basis of the above ones, anyone who wants them's welcome to them), installed them and syslog-ng 1.9.5 crashed without trace. Used strace and couldn't for the life of me see what was happening. I couldn't be bothered to begin with gdb and back traces, so I put the good rpm back, all's back to normal. If anyone wants me to go ahead with debugging, I will (dilettantishly to say the least, I'm not a C programmer), but would rather not - 1.6.8 works fine for me. Just thought I'd let people know :) Best, --Tonni -- mail: tonye@billy.demon.nl http://www.billy.demon.nl
Tony, I am seeing something similar -- 1.9.*, after compilation, simply segfaults after (during?) parsing of the config file. No clue as to what it's actually doing when it fails. I'd like to try out your specfiles though -- could you e-mail them to me? Paul Krizak 5900 E. Ben White Blvd. MS 625 Advanced Micro Devices Austin, Tx 78741 CAD Systems Engineering Phone: (512) 602-8775 Paul.Krizak@amd.com Tony Earnshaw wrote:
Hi, first post.
Red Hat RHAS3 update 4. Saturday I downloaded libol 0.3.16 and syslog-ng 1.6.8 tarballs, saw immediately that there were rpm spec files and made rpms (not without an initial couple of barfs about missing MySQL stuff), which I installed.
Took me Sunday and Monday till 10:00 am to get my head round it, but it's fantastic, thanks a lot:)
So then I downloaded 1.9.5 and eventlog-0.2.3+20050116+1856. There were no rpm spec files, so I wrote my own (half a morning on the basis of the above ones, anyone who wants them's welcome to them), installed them and syslog-ng 1.9.5 crashed without trace. Used strace and couldn't for the life of me see what was happening. I couldn't be bothered to begin with gdb and back traces, so I put the good rpm back, all's back to normal.
If anyone wants me to go ahead with debugging, I will (dilettantishly to say the least, I'm not a C programmer), but would rather not - 1.6.8 works fine for me.
Just thought I'd let people know :)
Best,
--Tonni
I am seeing something similar -- 1.9.*, after compilation, simply segfaults after (during?) parsing of the config file. No clue as to what it's actually doing when it fails.
Could you guys please backtrace the core and see if you get anything useful out of it? Paul, I'm still waiting for your reply :) Cheers, Roberto Nibali, ratz -- echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
Yes, sorry I got really busy and couldn't put together a trace. However I did end up figuring out the problem -- its the template-escape function in the program destination driver. Removing the template-escape() option from the config file lets everything run fine. Paul Krizak 5900 E. Ben White Blvd. MS 625 Advanced Micro Devices Austin, Tx 78741 CAD Systems Engineering Phone: (512) 602-8775 Paul.Krizak@amd.com Roberto Nibali wrote:
I am seeing something similar -- 1.9.*, after compilation, simply segfaults after (during?) parsing of the config file. No clue as to what it's actually doing when it fails.
Could you guys please backtrace the core and see if you get anything useful out of it? Paul, I'm still waiting for your reply :)
Cheers, Roberto Nibali, ratz
Paul Krizak wrote:
Yes, sorry I got really busy and couldn't put together a trace.
No worries, I was just curious.
However I did end up figuring out the problem -- its the template-escape function in the program destination driver. Removing the template-escape() option from the config file lets everything run fine.
I'll try to reproduce this then. Thanks for the input. Regards, Roberto Nibali, ratz -- echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
On Mon, 2005-08-29 at 22:59 +0200, Roberto Nibali wrote:
Paul Krizak wrote:
Yes, sorry I got really busy and couldn't put together a trace.
No worries, I was just curious.
However I did end up figuring out the problem -- its the template-escape function in the program destination driver. Removing the template-escape() option from the config file lets everything run fine.
I'll try to reproduce this then. Thanks for the input.
In the meanwhile I probably fixed this, as sent in another mail. Should be available by tomorrow. -- Bazsi
man, 29.08.2005 kl. 22.28 skrev Paul Krizak:
I am seeing something similar -- 1.9.*, after compilation, simply segfaults after (during?) parsing of the config file. No clue as to what it's actually doing when it fails.
You don't mention OS, distro, etc. I get no segfaults, everything compiles and seems to run on RHAS3, just sudden thrombosis on 1.9.5 syslog-ng startup. No segfault.
I'd like to try out your specfiles though -- could you e-mail them to me?
Ok, sent off list. Please give me feedback, that's why I mailed the list. Be aware that rpm 4.2.3-10 does *not* like the names eventlog-0.2.3+20050116+1856-1 and eventlog-devel-0.2.3+20050116+1856-1 for some reason, so you'd best change these to something handier. Best, --Tonni -- mail: tonye@billy.demon.nl http://www.billy.demon.nl
participants (5)
-
Balazs Scheidler
-
Paul Krizak
-
Paul Krizak
-
Roberto Nibali
-
Tony Earnshaw