Re: [qmailtoaster] [isoqlog] Segmentation fault / log files deletion, how to?

2007-06-14 Thread Harry Zink




What's the easiest way to delete, comprehensively, all logfiles that  
isoqlog uses?


I'm constantly getting the segmentation fault errors, no one else on  
the list (except two other people) appear affected by it, so I want  
to see if it's something about my log-files, and just toast them all  
and see what happens.


Can someone at least help with some convenient and effective way to  
get rid of all the log files, please?


Harry

-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] [isoqlog] Segmentation fault / log files deletion, how to?

2007-06-14 Thread Jake Vickers

Harry Zink wrote:




What's the easiest way to delete, comprehensively, all logfiles that 
isoqlog uses?


I'm constantly getting the segmentation fault errors, no one else on 
the list (except two other people) appear affected by it, so I want to 
see if it's something about my log-files, and just toast them all and 
see what happens.


Can someone at least help with some convenient and effective way to 
get rid of all the log files, please?


I've never really looked at how isoqlog was executed, but here's the 
cron.sh:



#!/bin/sh

VPOPMAIL=/home/vpopmail/domains
ISOQLOG=`which isoqlog`
ISODOMAINS=/etc/isoqlog/isoqlog.domains
RM=`which rm`
TOUCH=`which touch`
CHOWN=`which chown`
CHMOD=`which chmod`

# Remove old domains
[ -f $ISODOMAINS ]  $RM -rf $ISODOMAINS

# Regenerate the file
for i in `ls $VPOPMAIL`; do
echo $i  $ISODOMAINS;
done

# Execute the program
$ISOQLOG 1/dev/null 2/dev/null

# Correct permissions
$CHOWN -R apache:apache /usr/share/toaster/htdocs/isoqlog
Which looks like it deletes the domains list, isoqlog.domains and then 
regenerates the file via a ls command of /home/vpopmail/domains.
From looking at the config in /etc/isoqlog it looks like it's using the 
send log files to generate the HTML:

logstore = /var/log/qmail/send
So I would try moving those files somewhere else and then seeing if it 
still gives you the error.





smime.p7s
Description: S/MIME Cryptographic Signature


Re: [qmailtoaster] [isoqlog] Segmentation fault / log files deletion, how to?

2007-06-14 Thread Johannes Weberhofer, Weberhofer GmbH

Harry,

have you tried to increase the softlimit in the affected 
/var/qmail/supervise/*/run file. This could prevent strange errors like segfaults.

Johannes

Harry Zink wrote:




What's the easiest way to delete, comprehensively, all logfiles that 
isoqlog uses?


I'm constantly getting the segmentation fault errors, no one else on the 
list (except two other people) appear affected by it, so I want to see 
if it's something about my log-files, and just toast them all and see 
what happens.


Can someone at least help with some convenient and effective way to get 
rid of all the log files, please?


Harry

-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--


|-
|  weberhofer GmbH   | Johannes Weberhofer
|  information technologies
|  Austria, 1080 Wien, Blindengasse 52/3
|
|  phone : +43 (0)1 5454421 0| email: [EMAIL PROTECTED]
|  fax   : +43 (0)1 5454421 19   | web  : http://weberhofer.at
|  mobile: +43 (0)699 11998315
|---


-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] [isoqlog] Segmentation fault / log files deletion, how to?

2007-06-14 Thread Harry Zink
Assume I am a total blithering idiot and don't know how to do  
that... :-)


What do I edit?


On Jun 14, 2007, at 4:28 AM, Johannes Weberhofer, Weberhofer GmbH wrote:


Harry,

have you tried to increase the softlimit in the affected /var/ 
qmail/supervise/*/run file. This could prevent strange errors like  
segfaults.


Johannes

Harry Zink wrote:
What's the easiest way to delete, comprehensively, all logfiles  
that isoqlog uses?
I'm constantly getting the segmentation fault errors, no one else  
on the list (except two other people) appear affected by it, so I  
want to see if it's something about my log-files, and just toast  
them all and see what happens.
Can someone at least help with some convenient and effective way  
to get rid of all the log files, please?

Harry
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: qmailtoaster-list- 
[EMAIL PROTECTED]
For additional commands, e-mail: qmailtoaster-list- 
[EMAIL PROTECTED]


--


|-
|  weberhofer GmbH   | Johannes Weberhofer
|  information technologies
|  Austria, 1080 Wien, Blindengasse 52/3
|
|  phone : +43 (0)1 5454421 0| email: [EMAIL PROTECTED]
|  fax   : +43 (0)1 5454421 19   | web  : http://weberhofer.at
|  mobile: +43 (0)699 11998315
|---


-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: qmailtoaster-list- 
[EMAIL PROTECTED]




---
Antoine De Saint-Exupery
True happiness comes from the joy of deeds well done, the zest of  
creating things new.






Re: [qmailtoaster] [isoqlog] Segmentation fault / log files deletion, how to?

2007-06-14 Thread Harry Zink


On Jun 14, 2007, at 4:13 AM, Jake Vickers wrote:

So I would try moving those files somewhere else and then seeing if  
it still gives you the error.


Moved them out, restarted qmail, and so far the segfaults seem to  
have gone away.


---
George E. Nichols
The universal aptitude for ineptitude makes any human accomplishment  
an incredible miracle.





Re: [qmailtoaster] [isoqlog] Segmentation fault

2007-01-22 Thread Alexey Loukianov

Eric Shubes wrote:

Sorry, I'm stumped.
Anyone have an idea?


As always when coupling with bugs, we need to know whether is it 
reproducible or not. Correct decision will be to targzip the logs 
causing the sigfault, and send them to the developers, so they will be 
able to check if error will show up on their system.


Another question is who is the maintainer of isoqlog source code? It 
seems to me that Erik, Nick or Jean-Paul wouldn't waste their time 
finding up and correcting the bugs in foreign code. So, most probably 
complaints should go to the author of isoqlog, with a digest about the 
results of that complaints sent to this list for us to track the bug 
being fixed.



--
Best regards,
Alexey Loukianov  mailto:[EMAIL PROTECTED]
System Engineer,
IT Department,
Lavtech Corp.

-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[qmailtoaster] [isoqlog] Segmentation fault

2007-01-11 Thread Wojciech Gabor
I have isoqlog-toaster-2.1-1.3.2 on Centos-4.4

Some logfiles in /var/log/qmail/send make sementation fault of isoqlog. 
Where looking for solve? 
I was looking by strace but no interesting things found.
code
(...)
close(4)= 0
munmap(0x2a968fd000, 4096)  = 0
open(/var/log/qmail/send/current, O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=140401, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x2a968fd000
read(4, @400045a69d3e16dce5cc delive..., 4096) = 4096
read(4,  qp 8341 uid [EMAIL PROTECTED]..., 4096) = 4096
read(4, e 0/[EMAIL PROTECTED]..., 4096) = 4096
read(4, s: local 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
read(4, n./[EMAIL PROTECTED]_66.249.9..., 4096) = 4096
read(4, 20c new msg [EMAIL PROTECTED]..., 4096) = 4096
read(4, p 10054 uid [EMAIL PROTECTED]..., 4096) = 4096
read(4, id_0+0+1/[EMAIL PROTECTED]..., 4096) = 4096
read(4, 749620 to local zjo.lo.pl-stypen..., 4096) = 4096
read(4, c.com qp 11314 uid [EMAIL PROTECTED]..., 4096) = 4096
read(4, [EMAIL PROTECTED]@400045..., 4096) = 4096
read(4, 5b09cc status: local 0/20 remote..., 4096) = 4096
read(4, 00045a69f2400314354 new msg 8749..., 4096) = 4096
read(4, 4 status: local 1/20 remote 0/60..., 4096) = 4096
read(4, 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
read(4, 8749620: bytes 66510 from speed..., 4096) = 4096
read(4, +0+1/[EMAIL PROTECTED] ..., 4096) = 4096
read(4, 6a0390fb4512c new msg [EMAIL PROTECTED]..., 4096) = 4096
read(4, [EMAIL PROTECTED] deliv..., 4096) = 4096
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
/code  
 
-- 
Tuptus
System uptime: 41 years 8 months 2 weeks 2 days 15 hours 45 minuts


-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] [isoqlog] Segmentation fault

2007-01-11 Thread Eric \Shubes\
Wojciech Gabor wrote:
 I have isoqlog-toaster-2.1-1.3.2 on Centos-4.4
 
 Some logfiles in /var/log/qmail/send make sementation fault of isoqlog. 
 Where looking for solve? 
 I was looking by strace but no interesting things found.
 code
 (...)
 close(4)= 0
 munmap(0x2a968fd000, 4096)  = 0
 open(/var/log/qmail/send/current, O_RDONLY) = 4
 fstat(4, {st_mode=S_IFREG|0644, st_size=140401, ...}) = 0
 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
 0x2a968fd000
 read(4, @400045a69d3e16dce5cc delive..., 4096) = 4096
 read(4,  qp 8341 uid [EMAIL PROTECTED]..., 4096) = 4096
 read(4, e 0/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, s: local 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, n./[EMAIL PROTECTED]_66.249.9..., 4096) = 4096
 read(4, 20c new msg [EMAIL PROTECTED]..., 4096) = 4096
 read(4, p 10054 uid [EMAIL PROTECTED]..., 4096) = 4096
 read(4, id_0+0+1/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, 749620 to local zjo.lo.pl-stypen..., 4096) = 4096
 read(4, c.com qp 11314 uid [EMAIL PROTECTED]..., 4096) = 4096
 read(4, [EMAIL PROTECTED]@400045..., 4096) = 4096
 read(4, 5b09cc status: local 0/20 remote..., 4096) = 4096
 read(4, 00045a69f2400314354 new msg 8749..., 4096) = 4096
 read(4, 4 status: local 1/20 remote 0/60..., 4096) = 4096
 read(4, 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, 8749620: bytes 66510 from speed..., 4096) = 4096
 read(4, +0+1/[EMAIL PROTECTED] ..., 4096) = 4096
 read(4, 6a0390fb4512c new msg [EMAIL PROTECTED]..., 4096) = 4096
 read(4, [EMAIL PROTECTED] deliv..., 4096) = 4096

What do the 4096 bytes of this point in the log contain? Anything peculiar?
Is the log file it's choking on a 'normal' (*.s) file?

 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
 +++ killed by SIGSEGV +++
 /code  
  


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] [isoqlog] Segmentation fault

2007-01-11 Thread Wojciech Gabor
Dnia czwartek, 11 stycznia 2007 22:00, Eric Shubes napisał:
 Wojciech Gabor wrote:
  I have isoqlog-toaster-2.1-1.3.2 on Centos-4.4
 
  Some logfiles in /var/log/qmail/send make sementation fault of isoqlog.
  Where looking for solve?
  I was looking by strace but no interesting things found.
  code
  (...)
  close(4)= 0
  munmap(0x2a968fd000, 4096)  = 0
  open(/var/log/qmail/send/current, O_RDONLY) = 4
  fstat(4, {st_mode=S_IFREG|0644, st_size=140401, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
  0) = 0x2a968fd000
  read(4, @400045a69d3e16dce5cc delive..., 4096) = 4096
  read(4,  qp 8341 uid [EMAIL PROTECTED]..., 4096) = 4096
  read(4, e 0/[EMAIL PROTECTED]..., 4096) = 4096
  read(4, s: local 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
  read(4, n./[EMAIL PROTECTED]_66.249.9..., 4096) = 4096
  read(4, 20c new msg [EMAIL PROTECTED]..., 4096) = 4096
  read(4, p 10054 uid [EMAIL PROTECTED]..., 4096) = 4096
  read(4, id_0+0+1/[EMAIL PROTECTED]..., 4096) = 4096
  read(4, 749620 to local zjo.lo.pl-stypen..., 4096) = 4096
  read(4, c.com qp 11314 uid [EMAIL PROTECTED]..., 4096) = 4096
  read(4, [EMAIL PROTECTED]@400045..., 4096) = 4096
  read(4, 5b09cc status: local 0/20 remote..., 4096) = 4096
  read(4, 00045a69f2400314354 new msg 8749..., 4096) = 4096
  read(4, 4 status: local 1/20 remote 0/60..., 4096) = 4096
  read(4, 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
  read(4, 8749620: bytes 66510 from speed..., 4096) = 4096
  read(4, +0+1/[EMAIL PROTECTED] ..., 4096) = 4096
  read(4, 6a0390fb4512c new msg [EMAIL PROTECTED]..., 4096) = 4096
  read(4, [EMAIL PROTECTED] deliv..., 4096) = 4096

 What do the 4096 bytes of this point in the log contain? Anything
 peculiar? Is the log file it's choking on a 'normal' (*.s) file?

It's normal *.s files. 
This error is with some files, not all.
I make strace -o ~/rob/isoqlog.trace -s 4096 isoqlog and I found that this 
fault is until read logfile. Isoqlog stop read in random place.
-- 
Wojciech Gabor
System uptime: 41 years 8 months 2 weeks 2 days 16 hours 15 minuts

Cudowna kobieta to taka, która nie wymaga cudów.

-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] [isoqlog] Segmentation fault

2007-01-11 Thread Eric \Shubes\
Wojciech Gabor wrote:
 Dnia czwartek, 11 stycznia 2007 22:00, Eric Shubes napisał:
 Wojciech Gabor wrote:
 I have isoqlog-toaster-2.1-1.3.2 on Centos-4.4

 Some logfiles in /var/log/qmail/send make sementation fault of isoqlog.
 Where looking for solve?
 I was looking by strace but no interesting things found.
 code
 (...)
 close(4)= 0
 munmap(0x2a968fd000, 4096)  = 0
 open(/var/log/qmail/send/current, O_RDONLY) = 4
 fstat(4, {st_mode=S_IFREG|0644, st_size=140401, ...}) = 0
 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
 0) = 0x2a968fd000
 read(4, @400045a69d3e16dce5cc delive..., 4096) = 4096
 read(4,  qp 8341 uid [EMAIL PROTECTED]..., 4096) = 4096
 read(4, e 0/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, s: local 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, n./[EMAIL PROTECTED]_66.249.9..., 4096) = 4096
 read(4, 20c new msg [EMAIL PROTECTED]..., 4096) = 4096
 read(4, p 10054 uid [EMAIL PROTECTED]..., 4096) = 4096
 read(4, id_0+0+1/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, 749620 to local zjo.lo.pl-stypen..., 4096) = 4096
 read(4, c.com qp 11314 uid [EMAIL PROTECTED]..., 4096) = 4096
 read(4, [EMAIL PROTECTED]@400045..., 4096) = 4096
 read(4, 5b09cc status: local 0/20 remote..., 4096) = 4096
 read(4, 00045a69f2400314354 new msg 8749..., 4096) = 4096
 read(4, 4 status: local 1/20 remote 0/60..., 4096) = 4096
 read(4, 0/20 remote 0/[EMAIL PROTECTED]..., 4096) = 4096
 read(4, 8749620: bytes 66510 from speed..., 4096) = 4096
 read(4, +0+1/[EMAIL PROTECTED] ..., 4096) = 4096
 read(4, 6a0390fb4512c new msg [EMAIL PROTECTED]..., 4096) = 4096
 read(4, [EMAIL PROTECTED] deliv..., 4096) = 4096
 What do the 4096 bytes of this point in the log contain? Anything
 peculiar? Is the log file it's choking on a 'normal' (*.s) file?
 
 It's normal *.s files. 
 This error is with some files, not all.
 I make strace -o ~/rob/isoqlog.trace -s 4096 isoqlog and I found that this 
 fault is until read logfile. Isoqlog stop read in random place.

Sorry, I'm stumped.
Anyone have an idea?

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]