ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69148
|
Mon May 4 14:55:53 2020 |
 | David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | V3.1.4-80633ba | Re: Record ID corruption | Hi Frank,
There are two interesting points about the log file.
1. Entry 5658 is timestamped later than 5659, but is earlier in the entry list. It also is "In Reply to" 5659. despite 5659 having not been written (or at least timestamped) at the time that 5658 is. Might this be a feature of the draft function? I've not upgraded my elog for a long time now so my version doesn't have the feature - so I cannot test the idea of more than one entry being worked upon at the same time.
2. Entry 5657 says it is "In Reply to" 5656, but entry 5656 does not reference 5657 in the "Reply to" line, as it should Again, this might be a feature of the draft function
Could someone be confusing a draft entry with a real one? Or two attempts to make an entry?
On the idea of large number of entries, elog doesn't handle deleting of a thread of more than 40 replies well - it crashes after deleting the 40th. This leaves an orphan thread that causes other issues. Do you have enough information to decided that this event always happens after x replies?
| Frank Baptista wrote: |
|
Hi David,
Thanks for the quick response! Well, I'd have to say that the sequence is as tangled as it looks in the logbook -- I've attached a copy of the log file for your reading pleasure.
This one is definitely a "head-scratcher" for me...it definitely seems like it is more prevalent on log entries with many replies.
Thanks,
Frank
| David Pilgram wrote: |
|
Hi,
I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file. It would be very interesting to see what the 200428a.log file looks li looks like with these entries: in the screenshot they appear to be shown in time order, but do the "Reply to" and "In reply to" liknes in each entry (in the .log file) show a linear progression through the entires, a branch a branch or indeed this same order as the screenshot. If the duplicated entry sequential to 5657 (i.e 5658) then I would suspect something akin to my pointer's double click when I only made a single click, so fast that then second e second entry were created before the "No branches" checking part of the program had been reached. Not so sure about such an event here unless entry 5658 were already open but not closed?
Regards,
David.
| Frank Baptista wrote: |
|
Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.
What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 56 5656, 5659, 5657, 5658, 5660, 5661....
Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.
Has anyone else encountered this?
Thanks,
Frank
|
|
|
|
|
69147
|
Sun May 3 22:43:12 2020 |
| Frank Baptista | caffeinejazz@gmail.com | Question | Windows | V3.1.4-80633ba | Re: Record ID corruption | Hi David,
Thanks for the quick response! Well, I'd have to say that the sequence is as tangled as it looks in the logbook -- I've attached a copy of the log file for your reading pleasure.
This one is definitely a "head-scratcher" for me...it definitely seems like it is more prevalent on log entries with many replies.
Thanks,
Frank
| David Pilgram wrote: |
|
Hi,
I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file. It would be very interesting to see what the 200428a.log file looks li looks like with these entries: in the screenshot they appear to be shown in time order, but do the "Reply to" and "In reply to" liknes in each entry (in the .log file) show a linear progression through the entires, a branch a branch or indeed this same order as the screenshot. If the duplicated entry sequential to 5657 (i.e 5658) then I would suspect something akin to my pointer's double click when I only made a single click, so fast that then second e second entry were created before the "No branches" checking part of the program had been reached. Not so sure about such an event here unless entry 5658 were already open but not closed?
Regards,
David.
| Frank Baptista wrote: |
|
Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.
What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 56 5656, 5659, 5657, 5658, 5660, 5661....
Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.
Has anyone else encountered this?
Thanks,
Frank
|
|
|
| Attachment 1: 200428a.log
|
$@MID@$: 5653
Date: Tue, 28 Apr 2020 00:02:42 -0400
Reply to: 5654
In reply to: 5652
Clock #: N31419
Type: Test
Category: Update
Perform OPM?:
ATMS Correct?:
Station Down?:
Test End?: No
Production Status: Production
Attachment:
Encoding: HTML
========================================
<p>CYCLE 14 @ COLD -54 C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 14 @ COLD -54 C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>Cycle 13 @ Hot; +85°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>Cycle 13 @ Cold; -54°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>Cycle 13 @ Cold; -54°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>Cycle 12 @ Hot; +85°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>Cycle 12 @ Hot; +85°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>Cycle 12 @ Cold; -54°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>Cycle 12 @ Cold; -54°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 11 OF 25 @ HOT +85°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 11 OF 25 @ HOT +86°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 11 OF 25 @ HOT +86°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 11 OF 25 @ COLD -54°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 10 OF 25 @ RAMPING TO COLD.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 10 @ HOT +85°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 10 @ COLD -54°C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 10 @ COLD, -55C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 9 @ HOT, +85C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 9 @ HOT, +85C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 9 @ COLD, -54C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 8 @ HOT, +85C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 8 @ HOT, +85C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 8 @ HOT, +86C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 8 @ COLD, -54C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 8 @ RAMPING TO COLD, -38C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 7 @ HOT, +85C.</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 7 @ HOT,+85C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 7 @ COLD, -54C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 7 @ COLD, -54C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 6 @ HOT, +85C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 6 @ HOT, +85C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 176);">
<p>CYCLE 6 @ COLD, -54C</p>
<table align="center" cellspacing="1" style="border-image:none; border:1px solid rgb(72, 96, 144); width:98%">
<tbody>
<tr>
<td style="background-color: rgb(72, 96, 144);">Quote:</td>
... 7288 more lines ...
|
|
69146
|
Sun May 3 18:05:32 2020 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | V3.1.4-80633ba | Re: Record ID corruption | Hi,
I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file. It would be very interesting to see what the 200428a.log file looks like with these entries: in the screenshot they appear to be shown in time order, but do the "Reply to" and "In reply to" liknes in each entry (in the .log file) show a linear progression through the entires, a branch or indeed this same order as the screenshot. If the duplicated entry sequential to 5657 (i.e 5658) then I would suspect something akin to my pointer's double click when I only made a single click, so fast that then second entry were created before the "No branches" checking part of the program had been reached. Not so sure about such an event here unless entry 5658 were already open but not closed?
Regards,
David.
| Frank Baptista wrote: |
|
Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.
What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 5656, 5659, 5657, 5658, 5660, 5661....
Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.
Has anyone else encountered this?
Thanks,
Frank
|
|
|
69145
|
Sun May 3 15:58:24 2020 |
 | Frank Baptista | caffeinejazz@gmail.com | Question | Windows | V3.1.4-80633ba | Record ID corruption | Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.
What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 5656, 5659, 5657, 5658, 5660, 5661....
Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.
Has anyone else encountered this?
Thanks,
Frank
|
|
69143
|
Tue Apr 21 09:13:45 2020 |
| Daniel Pfuhl | daniel.pfuhl@medizin.uni-leipzig.de | Request | Linux | Windows | Mac OSX | All | Other | 3.1.4 | Re: CSS for HTML Mails | Hi Stefan,
I pulled the code from the repository but was not able to build it.
Sorry, I'm not a developer. Is there a good documentation you can recommend on how to do this for a Windows installation incl. how to setup a build environment?
No chance to get a more recent Windows version already precompiled? ^^
Regards,
daniel
| Stefan Ritt wrote: |
|
a04faf9f is pretty old: https://bitbucket.org/ritt/elog/commits/a04faf9fa9ca74657240cdc827bd2d0ae48a9df1
It's from September 2018, where the change with the CSS has been made on Decemb er 2018. You have to pull the current version from the git repository and recompile the program yourself.
/Stefan
| Daniel Pfuhl wrote: |
|
Hmm, I'm pretty sure that we are on the latest version already.
We use ELOG V3.1.4-a04faf9f
I downloaded a fresh install binary for Windows and compared the checksums:
SHA256: 0A98485134E0D43959CB6734F977B02DC9FA884D6994CE3BA141664451FDA5E5
SHA256: 0A98485134E0D43959CB6734F977B02DC9FA884D6994CE3BA141664451FDA5E5
same same.
Or do I have to change to config in order to include the CSS in the HTML?
regards,
daniel
| Stefan Ritt wrote: |
|
The CSS has been embedded in the email end of 2018, so just upgrade your server.
https://bitbucket.org/ritt/elog/commits/5165daf35cc1fb066071827719079fe0c9aa5ffb
/Stefan
| Daniel Pfuhl wrote: |
|
Hi there,
we extensively use Logbuch as a change documentation platform.
E-Mail notifications for new entries are very important for us.
Since we store sensible data in our logbooks the server is protected by a firewall.
After the firewall was activated the HTML mails are not rendered by the Outlook Mail clients we use - when they are located in an "external" net behind the firewall. I assume that's because of the css stylesheet which is linked in the source code of the HTML mail.
Is there any chance to include the CSS information in the HTML code? Otherwise we would need to make the CSS accessable from anywhere which requires in turn that the path of the CSS file can be customized.
Any idea how to solved this issue?
Best regards,
daniel
|
|
|
|
|
|
69142
|
Thu Apr 16 11:12:32 2020 |
| Stefano Lacaprara | stefano.lacaprara@pd.infn.it | Bug report | Linux | ELOG V3.1.3- | ... subject erased ... | > I found two potential memory leaks which I fixed in the git version, so you can try again.
Just tested, and it works! Many thanks for very quick patch!
>
> Another possibility, which is actually preferred, is to limit the size of the subject filed to a reasonable number. You can do that with following
option
>
> Format subject = 0, attribname, attribvalue, 80, 200
Yes, that is a good suggestion, I'll implemented it.
Many thanks again!
Best,
Stefano
>
> This shows the subject line with a width of 80 characters, but does only allow 200 characters to be entered there.
>
> Best,
> Stefan |
|
69141
|
Thu Apr 16 11:03:03 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | ELOG V3.1.3- | ... subject erased ... | I found two potential memory leaks which I fixed in the git version, so you can try again.
Another possibility, which is actually preferred, is to limit the size of the subject filed to a reasonable number. You can do that with following option
Format subject = 0, attribname, attribvalue, 80, 200
This shows the subject line with a width of 80 characters, but does only allow 200 characters to be entered there.
Best,
Stefan |
|
69140
|
Thu Apr 16 10:27:18 2020 |
| Stefano Lacaprara | stefano.lacaprara@pd.infn.it | Bug report | Linux | ELOG V3.1.3- | Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate v | > indeed, I'll try to move to ELOG V3.1.4-80633ba
>
> > My try on this server ->> see the subject
I've tried with elog-3.1.4-2 and git version, and I still have the same problem.
If I compile with make debug, it works.
Is there anything I can do to help debug the problem?
thanks for your help
S
compiling git master w/o debug, but running in gdb
gdb ~/elog/elogd
(gdb) run -f /var/run/elog.pid -c /etc/elog.conf -d /var/lib/elog/logbooks -s /usr/share/elog -v 3 -x
... [opening elogbook demo with an entry with lorem ipsum as sujbject]
*** buffer overflow detected ***: /root/elog/elogd terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7ffff781b7e5]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7ffff78bd15c]
/lib/x86_64-linux-gnu/libc.so.6(+0x117160)[0x7ffff78bb160]
/lib/x86_64-linux-gnu/libc.so.6(+0x1166c9)[0x7ffff78ba6c9]
/lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0x80)[0x7ffff781f6b0]
/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x139b)[0x7ffff77f250b]
/lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x84)[0x7ffff78ba754]
/lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7ffff78ba6ad]
/root/elog/elogd[0x44c86a]
/root/elog/elogd[0x4799e0]
/root/elog/elogd[0x496018]
/root/elog/elogd[0x4962a6]
/root/elog/elogd[0x49864e]
/root/elog/elogd[0x49b1f8]
/root/elog/elogd[0x4038c7]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7ffff77c4830]
/root/elog/elogd[0x404509]
======= Memory map: ========
00400000-004d5000 r-xp 00000000 ca:01 273573 /root/elog/elogd
006d4000-006d5000 r--p 000d4000 ca:01 273573 /root/elog/elogd
006d5000-0076c000 rw-p 000d5000 ca:01 273573 /root/elog/elogd
0076c000-018e7000 rw-p 00000000 00:00 0 [heap]
7ffff5783000-7ffff5799000 r-xp 00000000 ca:01 651589 /lib/x86_64-linux-gnu/libgcc_s.so.1
7ffff5799000-7ffff5998000 ---p 00016000 ca:01 651589 /lib/x86_64-linux-gnu/libgcc_s.so.1
7ffff5998000-7ffff5999000 rw-p 00015000 ca:01 651589 /lib/x86_64-linux-gnu/libgcc_s.so.1
7ffff5999000-7ffff5c56000 rw-p 00000000 00:00 0
7ffff5cda000-7ffff66c7000 r--s 00000000 ca:03 1305745 /var/lib/sss/mc/initgroups
7ffff66c7000-7ffff66df000 r-xp 00000000 ca:01 652670 /lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff66df000-7ffff68de000 ---p 00018000 ca:01 652670 /lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff68de000-7ffff68df000 r--p 00017000 ca:01 652670 /lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff68df000-7ffff68e0000 rw-p 00018000 ca:01 652670 /lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff68e0000-7ffff68e4000 rw-p 00000000 00:00 0
7ffff68e4000-7ffff68ec000 r-xp 00000000 ca:01 651532 /lib/x86_64-linux-gnu/libnss_sss.so.2
7ffff68ec000-7ffff6aeb000 ---p 00008000 ca:01 651532 /lib/x86_64-linux-gnu/libnss_sss.so.2
7ffff6aeb000-7ffff6aec000 r--p 00007000 ca:01 651532 /lib/x86_64-linux-gnu/libnss_sss.so.2
7ffff6aec000-7ffff6aed000 rw-p 00008000 ca:01 651532 /lib/x86_64-linux-gnu/libnss_sss.so.2
7ffff6aed000-7ffff6af8000 r-xp 00000000 ca:01 652680 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff6af8000-7ffff6cf7000 ---p 0000b000 ca:01 652680 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff6cf7000-7ffff6cf8000 r--p 0000a000 ca:01 652680 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff6cf8000-7ffff6cf9000 rw-p 0000b000 ca:01 652680 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff6cf9000-7ffff6cff000 rw-p 00000000 00:00 0
7ffff6cff000-7ffff715b000 r--p 00000000 ca:01 134295 /usr/lib/locale/locale-archive
7ffff715b000-7ffff715e000 r-xp 00000000 ca:01 652668 /lib/x86_64-linux-gnu/libdl-2.23.so
7ffff715e000-7ffff735d000 ---p 00003000 ca:01 652668 /lib/x86_64-linux-gnu/libdl-2.23.so
7ffff735d000-7ffff735e000 r--p 00002000 ca:01 652668 /lib/x86_64-linux-gnu/libdl-2.23.so
7ffff735e000-7ffff735f000 rw-p 00003000 ca:01 652668 /lib/x86_64-linux-gnu/libdl-2.23.so
7ffff735f000-7ffff757a000 r-xp 00000000 ca:01 651557 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ffff757a000-7ffff7779000 ---p 0021b000 ca:01 651557 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ffff7779000-7ffff7795000 r--p 0021a000 ca:01 651557 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ffff7795000-7ffff77a1000 rw-p 00236000 ca:01 651557 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ffff77a1000-7ffff77a4000 rw-p 00000000 00:00 0
7ffff77a4000-7ffff7964000 r-xp 00000000 ca:01 652683 /lib/x86_64-linux-gnu/libc-2.23.so
7ffff7964000-7ffff7b64000 ---p 001c0000 ca:01 652683 /lib/x86_64-linux-gnu/libc-2.23.so
7ffff7b64000-7ffff7b68000 r--p 001c0000 ca:01 652683 /lib/x86_64-linux-gnu/libc-2.23.so
7ffff7b68000-7ffff7b6a000 rw-p 001c4000 ca:01 652683 /lib/x86_64-linux-gnu/libc-2.23.so
7ffff7b6a000-7ffff7b6e000 rw-p 00000000 00:00 0
7ffff7b6e000-7ffff7bcc000 r-xp 00000000 ca:01 651645 /lib/x86_64-linux-gnu/libssl.so.1.0.0
7ffff7bcc000-7ffff7dcc000 ---p 0005e000 ca:01 651645 /lib/x86_64-linux-gnu/libssl.so.1.0.0
7ffff7dcc000-7ffff7dd0000 r--p 0005e000 ca:01 651645 /lib/x86_64-linux-gnu/libssl.so.1.0.0
7ffff7dd0000-7ffff7dd7000 rw-p 00062000 ca:01 651645 /lib/x86_64-linux-gnu/libssl.so.1.0.0
7ffff7dd7000-7ffff7dfd000 r-xp 00000000 ca:01 652669 /lib/x86_64-linux-gnu/ld-2.23.so
7ffff7fd9000-7ffff7fde000 rw-p 00000000 00:00 0
7ffff7ff7000-7ffff7ff8000 rw-p 00000000 00:00 0
7ffff7ff8000-7ffff7ffa000 r--p 00000000 00:00 0 [vvar]
7ffff7ffa000-7ffff7ffc000 r-xp 00000000 00:00 0 [vdso]
7ffff7ffc000-7ffff7ffd000 r--p 00025000 ca:01 652669 /lib/x86_64-linux-gnu/ld-2.23.so
7ffff7ffd000-7ffff7ffe000 rw-p 00026000 ca:01 652669 /lib/x86_64-linux-gnu/ld-2.23.so
7ffff7ffe000-7ffff7fff000 rw-p 00000000 00:00 0
7fffffe68000-7ffffffff000 rw-p 00000000 00:00 0 [stack]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
Program received signal SIGABRT, Aborted.
0x00007ffff77d9428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) where
#0 0x00007ffff77d9428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1 0x00007ffff77db02a in __GI_abort () at abort.c:89
#2 0x00007ffff781b7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7ffff793349f "*** %s ***: %s terminated\n") at
../sysdeps/posix/libc_fatal.c:175
#3 0x00007ffff78bd15c in __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7ffff7933430 "buffer overflow detected") at fortify_fail.c:37
#4 0x00007ffff78bb160 in __GI___chk_fail () at chk_fail.c:28
#5 0x00007ffff78ba6c9 in _IO_str_chk_overflow (fp=<optimized out>, c=<optimized out>) at vsprintf_chk.c:31
#6 0x00007ffff781f6b0 in __GI__IO_default_xsputn (f=0x7ffffff36d90, data=<optimized out>, n=1499) at genops.c:455
#7 0x00007ffff77f250b in _IO_vfprintf_internal (s=s@entry=0x7ffffff36d90, format=<optimized out>, format@entry=0x4b66bf "Style %s %s",
ap=ap@entry=0x7ffffff36ec8) at vfprintf.c:1632
#8 0x00007ffff78ba754 in ___vsprintf_chk (
s=0x7ffffff376a0 "Style Subject Lorem ipsum dolor sit amet, ut solum conceptam dissentiet per, affert argumentum te pro. Dicta tractatos
intellegebat an ius. Mei munere soleat voluptatum cu, at vidit scriptorem consect"..., flags=1, slen=1500, format=0x4b66bf "Style %s %s",
args=args@entry=0x7ffffff36ec8) at vsprintf_chk.c:82
#9 0x00007ffff78ba6ad in ___sprintf_chk (s=<optimized out>, flags=<optimized out>, slen=<optimized out>, format=<optimized out>) at sprintf_chk.c:31
#10 0x000000000044c86a in display_line ()
#11 0x00000000004799e0 in show_elog_list ()
#12 0x0000000000496018 in interprete ()
#13 0x00000000004962a6 in decode_get ()
#14 0x000000000049864e in process_http_request ()
#15 0x000000000049b1f8 in server_loop ()
#16 0x00000000004038c7 in main () |
|