Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.

I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0

elog -h localhost -p 8080 -l test -f  file1.png -f file2.png -e 249 -v -x

This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.

Can anyone provide some tips? I am not sure if its a problem with the client or server.

Thank you in advance!

Joseph

Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.

I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0

elog -h localhost -p 8080 -l test -f  file1.png -f file2.png -e 249 -v -x

This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.

Can anyone provide some tips? I am not sure if its a problem with the client or server.

Thank you in advance!

Joseph

We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000... 

68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...

Is this a know bug we can find a fix for? We are using:  elogd 2.9.2 built Jul 14 2015, 18:58:06 revision

Thank you all for your kind responses. Please consider this thread resolved: no bug in elog

Hi,

I try to configure the elog as servers log book.  I need to devide the text entry area by 2 section: 1 for issue so I can put in detail what is the issue of my servers.  the other section below the 1st one for solution.  is it posible to do so?

Joseph.

Hi,

I try to configure the elog as servers log book.  I need to devide the text entry area by 2 section: 1 for issue so I can put in detail what is the issue of my servers.  the other section below the 1st one for solution.  is it posible to do so?

Joseph.

I update my elog from version 2.7.5 to 2.7.6 and mistakenly replace configuration file. so i have to reconfigure everything from ground up.  when my elog back online, old log messages are not show up. is there a way to import old log messages from old log book to new one.

thanks

I have been trying to build and run elog under Mac OS  X 10.2.6, without sucess.  I 
understand that this is not one of the 'supported' platforms, but I hope that there is someone   
here who might know the work-around to my problem.

I've tried building elog 2.2.5, 2.3.6, 2.3.7, and 2.3.8.  I've tried using the compiler that comes 
in the Mac OS X 10.2 box, as well as the gcc-based compiler supplied in Apple's Dec 2002 
developer update (gcc 3.1), and the June '03 update as well (gcc 3.3).

elog builds without error in all cases I tried.

When I run it, it will correctly serve the demo notebook.  However, when the user clicks on the 
test message to display it in full, there is a seg fault.

I suspect that the trouble might be with something defined in time.h.

I've run it in gdb, and the result is appended to this message.  This is for gcc 3.3 and elog 
2.3.8.


I would greatly appreciate any hints or suggestions.

Cheers, Joe

---

[satsuma:~/Documents/elog_build/elog-2.3.8] jgiaime% gdb ./elogd
GNU gdb 5.3-20030128 (Apple version gdb-282) (Fri Jun 13 03:33:07 GMT 2003)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "powerpc-apple-darwin".
Reading symbols for shared libraries .. done
(gdb) run
Starting program: /Users/jgiaime/Documents/elog_build/elog-2.3.8/elogd 
Reading symbols for shared libraries . done
Indexing logbook "demo" ... ok
Server listening on port 8080...

Program received signal EXC_BAD_ACCESS, Could not access memory.
0x00005870 in el_retrieve (lbs=0x1, message_id=50, date=0xbfff2500 "demo", 
attr_list=0x0, attrib=0x365620, n_attr=1, text=0xbfff2280 "1", textsize=0x1, 
in_reply_to=0x0, reply_to=0x0, attachment=0x0, encoding=0x0, locked_by=0x0) at src/
elogd.c:2775
2775    {
(gdb) up
#1  0x0001d9b4 in interprete (lbook=0x1 <Address 0x1 out of bounds>, path=0xbfff2280 
"1") at src/elogd.c:12279
12279       show_elog_message(lbs, dec_path, command);
(gdb) up
#2  0x0001db10 in decode_get (logbook=0xbffff340 "demo", string=0x3a300a "1") at src/
elogd.c:12325
12325     interprete(logbook, path);
(gdb) up
#3  0x00020080 in server_loop (tcp_port=836736, daemon=-1073732640) at src/
elogd.c:13398
13398             decode_get(logbook, p);
(gdb) up
#4  0x00021134 in main (argc=1, argv=0xbffff850) at src/elogd.c:13832
13832     server_loop(tcp_port, daemon);
(gdb) up
Initial frame selected; you cannot go up.
(gdb)