Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 353 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  67209   Thu Mar 8 10:01:47 2012 Entry Olivier Callotolivier.callot@cern.chBug reportLinux2.9.0-2418Truncation of the displayed text in Summary view of the list of entries

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

  67210   Wed Mar 14 14:38:10 2012 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.0-2418Re: Truncation of the displayed text in Summary view of the list of entries

Olivier Callot wrote:

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

That's a feature

In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. 

  67212   Wed Mar 14 15:08:17 2012 Angy Olivier Callotolivier.callot@cern.chBug reportLinux2.9.0-2418Re: Truncation of the displayed text in Summary view of the list of entries

Stefan Ritt wrote:

Olivier Callot wrote:

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

That's a feature

In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. 

 Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway.

  67214   Wed Mar 14 16:04:04 2012 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.0-2418Re: Truncation of the displayed text in Summary view of the list of entries

Olivier Callot wrote:

Stefan Ritt wrote:

Olivier Callot wrote:

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

That's a feature

In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. 

 Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway.

Ok, I fixed that in revision 2442. 

  67070   Mon May 30 12:28:53 2011 Warning Andreas Luedekeandreas.luedeke@psi.chBug reportLinux2.9.0-2414elogd crashes when running mirror cron with SSL and KRB5
When I run a mirror server and both logbooks using SSL/KRB5 then the cron job causes a segmentation fault.

I haven't tried to check it with a simple configuration yet.
My set-up: two elogd on same server, one running "german" on port 444, the other "english" on port 445.
Both are behind an apache webserver configured reverse proxy, to hide the ports for external access.
I'll try to reproduce the fault with a "minimal configuration" soon and report again.


Debug output from GDB:

run -x -c /usr/local/elog/elogd_en.cfg
Starting program: /opt/elog-2.9.0/elog/elogd -x -c /usr/local/elog/elogd_en.cfg
elogd 2.9.0 built May 30 2011, 11:14:32 revision 2414
File "/var/run/elogd.pid" exists, using "/var/run/elogd.pid.445" instead.
Falling back to default group "elog"
Falling back to default user "elog"
User "elog" not found
Falling back to default user "nobody"
FCKedit detected
Falling back to default group "elog"
Falling back to default user "elog"
User "elog" not found
Falling back to default user "nobody"
ImageMagick detected
Indexing logbooks ... done
SSLServer listening on port 445 ...

Program received signal SIGSEGV, Segmentation fault.
0x0030b7b5 in SSL_write () from /lib/libssl.so.6
  67081   Fri Jun 3 12:06:20 2011 Smile Andreas Luedekeandreas.luedeke@psi.chInfoLinux2.9.0-2414Re: elogd crashes when running mirror cron with SSL and KRB5
> When I run a mirror server and both logbooks using SSL/KRB5 then the cron job causes a segmentation fault.
>
> I haven't tried to check it with a simple configuration yet.
> My set-up: two elogd on same server, one running "german" on port 444, the other "english" on port 445.
> Both are behind an apache webserver configured reverse proxy, to hide the ports for external access.
> I'll try to reproduce the fault with a "minimal configuration" soon and report again.
>

I've tried to test a simpler configuration on my local PC but failed:
all simple set-ups I've tried worked fine.

I found that the mirror cron synchronization works fine in my production set-up when I remove the line:
Mirror user = luedeke

But I can have this line in my simple test set-up and it still works fine.
Anyway: bugs closed for me.
  67084   Mon Jun 20 05:31:31 2011 Warning Andreas Luedekeandreas.luedeke@psi.chBug reportLinux2.9.0-2414segmentation fault when "restrict edit" is used and "new" is allowed for anonymous users
The simple config file below produces a segmentation fault when elogd is started,
http://localhost/Test/?cmd=New
is opened in the browser and then e.g. "Entry" is switched to "Problem".

gdb shows the following output:

(gdb) run -c /usr/local/elog/elogd.cfg
Starting program: /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
elogd 2.9.0 built Jun 20 2011, 04:57:23 revision 2414
Falling back to default group "elog"
Falling back to default user "elog"
FCKedit detected
Falling back to default group "elog"
Falling back to default user "elog"
ImageMagick detected
Indexing logbooks ... done
Server listening on port 80 ...

Program received signal SIGSEGV, Segmentation fault.
0x080a2940 in get_user_line (lbs=0xae3c1c0, user=0x0, password=0x0, full_name=0xbfca1690 "", email=0x0, email_notify=0x0,
last_logout=0x0, inactive=0x0) at src/elogd.c:24864
24864 if (!str[0] || !user[0])
Attachment 1: elogd.cfg
[global]
Authentication = File
Password file = passwd.txt
Restrict edit = 1

[Test]
Guest Menu commands = New, List, Login, Help
Guest List Menu commands = New, Login, Help
Comment = Test ELog
Attributes      = Author, Entry, Title
List display    = ID, Author, Entry, Title
Start page = ?rsort=When

# Author
Preset Author = $long_name
Locked Attributes = Author
# Entry
Options Entry = Problem{1}, Measurement{2}

  67085   Mon Jun 20 17:53:58 2011 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.0-2414Re: segmentation fault when "restrict edit" is used and "new" is allowed for anonymous users
You are the first one allowing guests to enter new entries, so this probes a code path which was never used before. I fixed the crash in SVN revision 2416, but it might be that there are more issues with that. Just keep reporting.
ELOG V3.1.5-3fb85fa6