ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 554 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 553, 554, 555 ... 806, 807, 808 Next

Sun Oct 17 22:47:39 2004

Re: ELOG e-mail notifications - their arrival time is wrong

Ok, i compiled the code below and ran it,
it prints out:

timezone: 134513644

but in BASH shell if i type DATE, then this is the output:
Mon Oct 18 09:44:00 NZDT 2004
so it does know about NZ time...

Anyone got ideas?

Thanks all.
G.


> > Date:  Mon, 11 Oct 2004 12:26:28 -3736512
> 
> The timezone offset (-3736512) is obtained from the "timezone" variable, which
> is initialized with the tzset() function inside elogd. See "man tzset" for
> details. It looks like if the timezone on your FreeBSD box is not correctly
> defined. 
> 
> Try to compile and execute following C program:
> 
> #include <stdio.h>
> #include <time.h>
> 
> main()
> {
>    tzset();
>    printf("timezone: %d\n", timezone);
> }
> 
> This should print something like "timezone: -3600". If not, you might consider
> defining the "TZ" environment variable. Maybe some FreeBSD expert knows some
> details about this.

67063

Tue May 3 17:35:57 2011

Soren Poulsen

soren.poulsen@cern.ch

Bug report

Linux

2.9.0-2413

Re: ELOG deamon stuck in find_thread_head()

soren poulsen wrote:

ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just gets stuck.

If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems.

I started in GDB and break with ctrl-C when the process gets stuck, to be told :

Program received signal SIGINT, Interrupt.
0x000000000040a968 in find_thread_head ()

I then made a core dump.

I put the files here: http://cern.ch/poulsen2/elog-error-report-110430.zip (they are too big to upload).

I get into the same problem in other circumstances such as when opening some threads (maybe because they contain "Reply-to" references to non-existing messages, but I have problems reproducing this on the test installation.

I should maybe also submit the incriminating thread.

Soren

1. It appears that some times find_thread_head is called with message references that do not exist. That is not good.

I put in a little check like this before seeing if the message has an "in_reply_to" reference:

The line:

if (lbs->el_index[i].in_reply_to)

becomes:

if (i < *lbs->n_el_index && lbs->el_index[i].in_reply_to)

2. The trouble started when I deleted a message in the middle of a thread, which left the thread badly "connected" (references to a deleted message).

3. Also, when a thread is badly connected, it is a problem moving messages to a different logbook. ELOG complains that it cannot access the message (with the invalid reference). But ELOG should ignore it, since the message was deleted.

Soren

67086

Wed Jul 6 12:06:01 2011

Soren Poulsen

soren.poulsen@cern.ch

Bug report

Linux

2.9.0-2413

Re: ELOG deamon stuck in find_thread_head()

Soren Poulsen wrote:

soren poulsen wrote:

ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just gets stuck.

If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems.

I started in GDB and break with ctrl-C when the process gets stuck, to be told :

Program received signal SIGINT, Interrupt.
0x000000000040a968 in find_thread_head ()

I then made a core dump.

I put the files here: http://cern.ch/poulsen2/elog-error-report-110430.zip (they are too big to upload).

I should maybe also submit the incriminating thread.

Soren

1. It appears that some times find_thread_head is called with message references that do not exist. That is not good.

I put in a little check like this before seeing if the message has an "in_reply_to" reference:

The line:

if (lbs->el_index[i].in_reply_to)

becomes:

if (i < *lbs->n_el_index && lbs->el_index[i].in_reply_to)

2. The trouble started when I deleted a message in the middle of a thread, which left the thread badly "connected" (references to a deleted message).

Soren

It would be nice to have this corrected. The problem occurs when you select (read) a message which refers to another message via "In-reply-to", and this message does not exist.

Soren

67087

Wed Jul 6 12:36:33 2011

David Pilgram

David.Pilgram@epost.org.uk

Bug report

Linux

2.9.0-2413

Re: ELOG deamon stuck in find_thread_head()

Soren Poulsen wrote:

soren poulsen wrote:

ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just gets stuck.

If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems.

I started in GDB and break with ctrl-C when the process gets stuck, to be told :

Program received signal SIGINT, Interrupt.
0x000000000040a968 in find_thread_head ()

I then made a core dump.

I put the files here: http://cern.ch/poulsen2/elog-error-report-110430.zip (they are too big to upload).

I should maybe also submit the incriminating thread.

Soren

1. It appears that some times find_thread_head is called with message references that do not exist. That is not good.

I put in a little check like this before seeing if the message has an "in_reply_to" reference:

The line:

if (lbs->el_index[i].in_reply_to)

becomes:

if (i < *lbs->n_el_index && lbs->el_index[i].in_reply_to)

2. The trouble started when I deleted a message in the middle of a thread, which left the thread badly "connected" (references to a deleted message).

Soren

It would be nice to have this corrected. The problem occurs when you select (read) a message which refers to another message via "In-reply-to", and this message does not exist.

Soren

Soren, you're not alone! I've had similar problems, as did Sara Vanini (elog:67077).

In my case, it is because the "move" or "copy" function does not move all the messages in very long threads. To be more precise, elog will crash in the attempt to move a long thread - say over 40 replies, I don't know for sure. Sometimes it has already moved the entire thread before it crashes, sometimes not. I'd not flagged it up as an issue because I could not be sure it was not a memory issue with the old (>12 years) linux box I was using earlier this year, but it still happens on this new (to me, only 3 years old) linux box.

Whether it is the number of entries, the total memory size of the thread or some combination, I don't know.

I've found that in the "move" case, it has not deleted all the messages from the donor thread, so that there is a semi-thread still hidden there. Should one by chance select that semi-thread, (because it is found during a search) elog goes into infinate loop, which requires a reboot of this linux box to fix. Certainly the pinning down the issue to the missing entry referenced by an In reply to: explains this part of the issue. Of course, deletion of one entry within a thread, or other adjustments will do the same thing, just as you (Soren) point out above.

If it happens to me, I will go in to the yymmdda.log files and fix the problem, be it deleting the entries of the semi-thread, moving across missing entries from the donor to the acceptor logbooks, adjusting the Reply: and In reply to: lines, but that is quite a time consuming and error prone exercise.

67387

Mon Nov 26 17:12:32 2012

Andreas Luedeke

andreas.luedeke@psi.ch

Bug fix

Linux

2.9.2-2475

Re: ELOG crash related to Kerberos, SSL and Login users

Forget the previous post:
I cannot reproduce the problem with the latest version of elogd (2.9.2-2475).

67246

Thu Apr 12 08:57:51 2012

Christopher Lee wrote:

Firstly, as with some of the others recently, I am a complete newb when it comes to linux, Though I refuse to let that stop me and really want to get this working.

Pretty much I have a situation where I have been asked to install ELOG, though I am unable to use port 25 at all and also need to use GMAIL for the SMTP server?
It is also my undertanding from the documentation that ELOG only sends mail via port 25

So, I have setup iptables to forward everything from port 25 and a GMAIL IP address used in ELOG's global config for the SMTP, to a stunnel that redirects everything to GMAIL on port 465.
While getting that right took me almost two days, and that was with tons of help and more than half of it being spoon fed to me (though I have learnt SO SO MUCH from just that).
I am still unable to get ELOG to send emails, even if does now seem to connect

Below is a copy of the log from last night (I have spent most of the day trying to sort it out further, but I get the same error)

So I guess my question is, Is it possible to use GMAIL, with ELOG, based on my current conditions, and does anyone have any idea what I can do to go on from here, as I doubt I am the first one to head down this road?

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

10-Apr-2012 21:45:19 [Chris@1.2.3.4] {logbookA} Email from <chris@server.com> to chris@server.com, SMTP host 173.194.67.108:
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 220 mx.google.com ESMTP XXXXXXXX.XX^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA}
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} EHLO SERVER.COM^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-mx.google.com at your service, [152.106.18.2]^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-SIZE 35882577^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-8BITMIME^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-AUTH LOGIN PLAIN XOAUTH^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250 ENHANCEDSTATUSCODES^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} AUTH LOGIN^M
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Username:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} username@gmail.com
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Password:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} MYXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} 501 5.5.2 Cannot Decode response fl2sm792152wib.2

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Right now I am pretty stuck, and any advice would be greatly appreciated on how to move forward.

Thanks in Advance

As far as I know GMAIL requires SSL for its SMTP connection, which ELOG does not (yet) support. But you can set up your own SMTP server easily. Should be easier than your iptables work.

67247

Thu Apr 12 14:38:09 2012

Christopher Lee

chris@chrisandclaire.org

Stefan Ritt wrote:

Christopher Lee wrote:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

As far as I know GMAIL requires SSL for its SMTP connection, which ELOG does not (yet) support. But you can set up your own SMTP server easily. Should be easier than your iptables work.

It does require SSL, though thats where stunnel came in.(Thanks to Sergio for all the help and getting me that far, as well as with all the iptable help :D) .

I was however finally able to get it working just a few minutes ago using GMAIL as the SMTP.

I was able to telnet into smtp.gmail.com over the stunnel, and when I repeated the process that elog goes through from information that I grabbed with TCPdump, everthing would work, until it got to the password that ELOG sends and that was created using : /usr/local/sbin/elogd -t password -c /usr/local/elog/elogd.cfg. When I tried to decode the password, it also gave me errors.

I encoded the password myself, and when I changed the one in [global] to match the one I created instead, ELOG was able to connect and send mail (What I still dont understand is that when I encode my own username to use on telnet, it fails, but the one I got from the tcpdump from elog works.. so its a mixture of the ELOG encoded username, and my own encoded password).

I dont know if it would help if I type up the rest of what we did to get it working here for anyone else for future reference. It does require iptables and stunnel to be installed. Though its a single entry into iptables, and small addition to stunnel.conf once they are running.

67248

Sat Apr 14 11:10:14 2012

Christopher Lee

chris@chrisandclaire.org

To get it to work required a working installation of IPTABLES and STUNNEL

First is to add the following details into elogd.cfg

/usr/local/elog/elogd.cfg wrote:

SMTP username = username@gmail.com
SMTP host = 173.194.67.108
SMTP Password =

This SMTP IP address is a virtual host from Googles SMTP, Any IP Address could technically be used.

Next is to redirect all traffic to port 25 and the above IP address, to STUNNEL.

Quote:

sudo iptables -t nat -A OUTPUT -p tcp -d 173.194.67.16 -dport 25 -j DNAT --to 127.0.0.1:10555

You can select any port other than 10555 if required. Next you need to modify the STUNNEL config file and add the following.

/etc/stunnel/stunnel.conf wrote:

[elogssl]
client = yes
accept = 10555
connect = smtp.gmail.com:465

Last was the password. For some reason sudo /usr/local/sbin/elogd -t <password> -c /usr/local/elog/elogd.cfg created a password that was unreadable by google.
To recreate your own run the following command:

Quote:

perl -MMIME::Base64 -e 'print encode_base64("\000not.my.re\@l.password")'

Replace "\000not.my.re\@l.password" with the GMAIL password, remember to escape with a \ any @ signs you might have.
Copy the output and add that into the elogd.cfg file in the SMTP Password syntax.

kill the STUNNEL PID if it is running and restart it to to load the new details, also remember to save your IPTABLES for next reboot

And that should be it, so now ELOG uses a port other than 25, and also redirects via SSL to a SMTP like GMAIL.

Goto page Previous 1, 2, 3 ... 553, 554, 555 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6