Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 377 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  67006   Fri Feb 4 00:11:09 2011 Question T. Ribbrockemgaron+elog@ribbrock.orgQuestionOther2.8.1Strange problem with dates - need debugging help

I have just installed elog 2.8.1 on my OpenBSD 4.8 server (I've added the necessary Makefile patch to "Contributions"). Everything seems to work fine, however, I ran into a very odd problems with the dates of the logbook entries: When I start a new entry, the current date/time is displayed correctly. When I submit the entry and look at it again, the date has changed to some value in 1996 . I've checked the actual logbook file and there, the entry has a Date line like this:

Date: Thu, 03 Feb 2011 23:53:28 -13049141
 

The "-13049141" looks very suspicious to me - but I have no idea whatsoever why this happens. I had elogd running with -v, but that did not give me any hints. Any ideas how to debug/resolve this would be much appreciated...

 

  67007   Fri Feb 4 10:20:12 2011 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.8.1Re: Strange problem with dates - need debugging help

T. Ribbrock wrote:

I have just installed elog 2.8.1 on my OpenBSD 4.8 server (I've added the necessary Makefile patch to "Contributions"). Everything seems to work fine, however, I ran into a very odd problems with the dates of the logbook entries: When I start a new entry, the current date/time is displayed correctly. When I submit the entry and look at it again, the date has changed to some value in 1996 . I've checked the actual logbook file and there, the entry has a Date line like this:

Date: Thu, 03 Feb 2011 23:53:28 -13049141
 

The "-13049141" looks very suspicious to me - but I have no idea whatsoever why this happens. I had elogd running with -v, but that did not give me any hints. Any ideas how to debug/resolve this would be much appreciated... 

The problem is most probably related to the time zone. elogd contains a function:


/* workaround for wong timezone under MAX OSX */
long my_timezone()
{
#if defined(OS_MACOSX) || defined(__FreeBSD__)
   time_t tp;
   time(&tp);
   return -localtime(&tp)->tm_gmtoff;
#else
   return timezone;
#endif
}
 
from which you can see that there is a different behavior between different Linux flavors and OSX/FreeBSD. Maybe you need an additional
 
|| defined(__OpenBSD__)
 
if the pre-compiler directive __FreeBSD__ is not defined on your system. The result of the function should be the time zone in seconds relative to GMT. So for central Europe, it should give "-3600".
 
Let me know if you find something out, I can then include it in the distribution.
 
Best regards,
 
  Stefan
  67008   Fri Feb 4 11:52:45 2011 Agree T. Ribbrockemgaron+elog@ribbrock.orgQuestionOther2.8.1Re: Strange problem with dates - need debugging help

Stefan Ritt wrote:

The problem is most probably related to the time zone. elogd contains a function:

/* workaround for wong timezone under MAX OSX */
long my_timezone()
{
#if defined(OS_MACOSX) || defined(__FreeBSD__)
   time_t tp;
   time(&tp);
   return -localtime(&tp)->tm_gmtoff;
#else
   return timezone;
#endif
}
 
from which you can see that there is a different behavior between different Linux flavors and OSX/FreeBSD. Maybe you need an additional
 
|| defined(__OpenBSD__)
 
if the pre-compiler directive __FreeBSD__ is not defined on your system.
[...]
 

 BINGO! That was it - thank you! I've added the || defined(__OpenBSD__) in the place you described above and now the dates are correct. While I was at it, I also had a look at what other ifdefs there are for FreeBSD and the only other one I found was also in elogd.c:

#if defined (_BSD_VA_LIST_) && defined (__FreeBSD__)

I'm far from being a C programmer, but I did some quick and dirty compile tests with various ifdefs set and apparently, _BSD_VA_LIST_ is not set on OpenBSD, so I guess that this statement does not need modification. I will keep my eyes peeled for strange behaviour, though...

Cheerio,

Thomas

P.S.: One thing I noticed is that the OpenBSD variant of gcc throws these warnings when compiling elogd.c:

gcc -g -funroll-loops -fomit-frame-pointer -W -Wall -DHAVE_SSL -I../mxml -o elogd src/elogd.c crypt.o regex.o mxml.o strlcpy.o -lcrypto -lssl
/tmp//ccHhMZfy.o(.text+0xd2f): In function `int_vasprintf':
src/elogd.c:826: warning: vsprintf() is often misused, please use vsnprintf()
/tmp//ccHhMZfy.o(.text+0xae8): In function `xstrdup':
src/elogd.c:736: warning: strcpy() is almost always misused, please use strlcpy()
/tmp//ccHhMZfy.o(.text+0x13c7): In function `my_shell':
src/elogd.c:1197: warning: sprintf() is often misused, please use snprintf()
/tmp//ccHhMZfy.o(.text+0xf0ae): In function `el_correct_links':
src/elogd.c:5178: warning: strcat() is almost always misused, please use strlcat()

I'm not certain whether this is specific to this gcc variant, but I seem to remember that the OpenBSD folks added some extra warnings and suchlike as part of their overall code audit, so I thought I'd mention it.

  67731   Tue Dec 16 01:15:40 2014 Question Eric Quinteroericq@caltech.eduBug reportLinux2.8.1Strange Behavior in "Find" Function

Hi all,

We've been happily using ELOG for years, but ran into an odd problem when replacing the old Solaris server that ran the ELOG with a newer box running Ubuntu. 

Basically, when I try to search the log, the URL seems to be malformed. I.e. the form produces the query string:

?mode=summvry&reverse=0&reverse=1&npp=35&m&y&Authorthor=ericq

Instead of a functional one like:

?mode=summary&reverse=1&npp=35&Author=ericq

We're running v2.8.1, since we like using the global write password mode; our log is viewable here: http://nodus.ligo.caltech.edu:8080 Any ideas what could've gone wrong? Installation was pretty straightforward, the code compiled happily on the ubuntu machine. 

Incidentally, I notice this logbook is running V3, using CKeditor. Any hints when these might be available for public use?

Thanks!

  67732   Wed Dec 17 14:40:19 2014 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.8.1Re: Strange Behavior in "Find" Function
Eric Quintero wrote:

Hi all,

We've been happily using ELOG for years, but ran into an odd problem when replacing the old Solaris server that ran the ELOG with a newer box running Ubuntu. 

Basically, when I try to search the log, the URL seems to be malformed. I.e. the form produces the query string:

?mode=summvry&reverse=0&reverse=1&npp=35&m&y&Authorthor=ericq

Instead of a functional one like:

?mode=summary&reverse=1&npp=35&Author=ericq

We're running v2.8.1, since we like using the global write password mode; our log is viewable here: http://nodus.ligo.caltech.edu:8080 Any ideas what could've gone wrong? Installation was pretty straightforward, the code compiled happily on the ubuntu machine. 

Incidentally, I notice this logbook is running V3, using CKeditor. Any hints when these might be available for public use?

Thanks!

Old versions are not supported any more. I only can fix bugs in the current version. Probably the bug you report is already gone (just give it a try). If you need the global write password mode, you can enable guest read access to your logbook and define a single use with the write password, that's then almost equivalent.

/Stefan

 

 

  66959   Fri Nov 26 12:31:42 2010 Question Christoph Kukulieskukulies@physik.rwth-aachen.deQuestionLinux2.8.0-2344New User in Config Menu ?

I see only Save Back Change Password Remove User in Config Menu.

How can I create a New User?

[global]
Port=8880
SSL=1
;Self register = 1
Password file = passwd
admin user = kuku
SMTP host = smtp.mydomain

[Demo]

Attributes = Author, Status

 

The documentation is mentioning a Config Menu and a New User item there.

 

--

Christoph


 

  66960   Fri Nov 26 12:36:53 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.8.0-2344Re: New User in Config Menu ?

Christoph Kukulies wrote:

I see only Save Back Change Password Remove User in Config Menu.

How can I create a New User?

[global]
Port=8880
SSL=1
;Self register = 1
Password file = passwd
admin user = kuku
SMTP host = smtp.mydomain

[Demo]

Attributes = Author, Status

 

The documentation is mentioning a Config Menu and a New User item there. 

You have to be admin user to see that Config Menu.

Admin user = kukulies             (or whatever your login name is)

  66961   Fri Nov 26 16:22:05 2010 Reply Christoph Kukulieskukulies@physik.rwth-aachen.deQuestionLinux2.8.0-2344Re: New User in Config Menu ?

Stefan Ritt wrote:

Christoph Kukulies wrote:

I see only Save Back Change Password Remove User in Config Menu.

How can I create a New User?

[global]
Port=8880
SSL=1
;Self register = 1
Password file = passwd
admin user = kuku
SMTP host = smtp.mydomain

[Demo]

Attributes = Author, Status

 

The documentation is mentioning a Config Menu and a New User item there. 

You have to be admin user to see that Config Menu.

Admin user = kukulies             (or whatever your login name is)

 Thanks. You see in the elogd.cfg above that there is

admin user = kuku

 Aaah, case sensitive ! !

 

--

Christoph

 

 

ELOG V3.1.5-3fb85fa6