Hi all, I get messages like this

Attachment #16 of entry #0 not found
Please use your browser's back button to go back

always when clicking on an entry in summary or threaded view. I can only read entries when browsing them in full view. How can i fix this?
regards, Christian

> > Hi all, I get messages like this 
> > Attachment #16 of entry #0 not found 
> > Please use your browser's back button to go back 
> > always when clicking on an entry in summary or threaded view.  
> > I can only read entries when browsing them in full view. How can i fix this? 
> > regards, Christian 
>  
> I need some more information. Can you send me your elogd.cfg, and show  
> me the URLs your browser displays during your navigation? 
 
Well, this is my elog.conf: 
 
[global] 
logbook tabs = 1 
port = 8081 ; Automatically added in installation. 
Hosts allow = localhost, jazz.cocis.de, 127.0.0.1, 192.168. 
Hosts deny = ALL 
[debian] 
Theme = default 
Comment = debian logbook 
Attributes = Author, Type, Category, Subject 
Required Attributes = Author, Type 
Subst Author = $long_name 
Subst Email = $user_email 
Locked Attributes = Last Revision 
Subst on Edit Last Revision = $date by $long_name 
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other 
Options Category = General, Hardware, Software, Network, Other 
Page Title = ELOG - $subject 
Reverse sort = 1 
Quick filter = Date, Type 
Password file = /var/lib/elog/elogpasswd.pwd 
Admin user = admin 
Reverse sort = 1 
Restrict edit = 1 
Suppress Email to users = 1 
 
This is the URL after logging in: 
http://localhost:8081/debian/17?cmd=List&mode=summary 
 
When i click on one of the entrys, i get thar error message. 
URL: http://localhost:8081/debian/debian/17 
 
It says: "Attachment #17 of entry #0 not found 
  Please use your browser's back button to go back" 
 
regards, Christian 

Dear elog users & developers,

the subject line says it all: when using webserver authentication, how is it possible to restict access of users to any given elog? Only using the apche rules? Admin user and Login user do not seem to be doing anything for me. I am using elog as packaged by debian for buster, using an apache ssl proxy. Thank you for providing this software,

Christian

Dear all,

I figured it out. Current global config is (using kerberos instead)

[global]
port = 8081
Default encoding = 0
SSL = 0
Authentication = Kerberos
URL = https://my_url_here/
interface = 127.0.0.1
Password file = global.pwd
SMTP host = my_mail_host
Logfile = /var/log/elog.log
Logging level = 3
User = elog
Grp = elog

Best,

Christian

Hi all,

ELOG V3.0.0-21dc563

Our elogd dies alwways when searching for full text:

elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.

The only change we did was adding/editing entries.

Does anyone else encounter the same issue ?

I did not find any hint in release notes that this issue would be fixed in a later version

Please don't get me wrong, I am not complaining. Elog does a great job for us since years.

Christian

I would like to share my findings about the solution of our problem:

One of my collegues used elog in a way it was not intended for, he put an endry with 8021 lines of text.

So I grabbed the corresponding 160517a.log file from logdir, renamed it to a text file and created a new entry with the large textfile as attachment.

Since then, no more crash of elogs.

May this contribution be useful to other elog users...

Christian

Comiling elogd 2.0.4 under Solaris obviously fails with

gcc  -o elog elog.c -lsocket -lnsl
gcc  -o elogd elogd.c -lsocket -lnsl
elogd.c: In function `ss_file_find':
elogd.c:1372: `alphasort' undeclared (first use in this function)
elogd.c:1372: (Each undeclared identifier is reported only once
elogd.c:1372: for each function it appears in.)
make: *** [elogd] Error 1

because alphasort is an ucb'ism which does not exist under SYSV

... not very portable :-(

Just compiled elog-2.0.5 under Solaris 8 and 9  without any warnings/errors
but the elogd binary just core dumps:

# /opt/ELOG/bin/elogd -c /opt/ELOG/elogd.cfg 
Indexing logbook "demo"...
Bus Error (core dumped)

.. tracing elogd shows:

[ lines snipped ]
2964:   brk(0x005B8A68)                                 = 0
2964:   ioctl(1, TCGETA, 0xFFBEE6BC)                    = 0
Indexing logbook "demo"...
2964:   write(1, " I n d e x i n g   l o g".., 27)      = 27
2964:       Incurred fault #5, FLTACCESS  %pc = 0x000164C0
2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
2964:       Received signal #10, SIGBUS [default]
2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
2964:           *** process killed ***
#

... any glue ?