Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 440 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6460 Entries 
Goto page Previous  1, 2, 3 ... 439, 440, 441 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  66427   Fri Jun 26 17:04:23 2009 Reply weiluolwsy711@gmail.comQuestionLinux2.7.6Re: attached picture size changed

Stefan Ritt wrote:

weiluo wrote:

Hello everyone.
Here I found a problem recently with attaching screen-shot to the elog.
I am using "elog -f xxx/xxx.gif" to make elog entry. Recently I found my attached pictures were scaled to the half of the original size horizontally appearing in the log entry, the other half of the picture was filled with black. I need to click it once to magnify the picture to see it.
Does anyone know how to solve this problem? It bugs me a lot.

By the way, I saw some pictures were produced with the name "xxx.gif.png" in the logbook directory.
Thanks, and one of the modified picture is attached.


When you submit a picture, elogd calls the ImageMagick package to generate a thumbnail out of it, therefore you get the "xxx.gif.png" file (which represents the thumbnail). If you create your GIF images with the ROOT package, ImageMagick will give problems because ROOT does not use standard GIF encoding, therefor the black border on your pictures. You can turn off the thumbnail generation completely by specifying
Thumbnail size = 0

in the configuration file. This option was just introduced recently, so please update to SVN revision 2227 for this option to work.


Thanks a lot for the detailed explanation! It works!
  66449   Mon Jul 20 09:26:41 2009 Question lancelance1.hayward@yahoo.comBug reportWindows2.7.6Elog Crashes
Stefan,
 
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
 
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
 
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
 
I have attached the eventlog files for you if you have any ideas I would appreciate them.
 
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
 
Any help is much appreciated
 
 
Regards,
 
Lance
Attachment 1: Elog_crash_events.doc
  66450   Mon Jul 20 10:30:44 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.6Re: Elog Crashes

lance wrote:
Stefan,
 
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
 
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
 
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
 
I have attached the eventlog files for you if you have any ideas I would appreciate them.
 
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
 
Any help is much appreciated
 
 
Regards,
 
Lance

Using the Windows event log won't help much. I guess in your case elogd is driven into some kind of endless loop (does the CPU go to 100%???). There are only two possibilities to tackle this:

1) You find a way to reliably reproduce this problem, tell me how to do this. When I can reproduce it here, I can fix it easily.

2) You do debugging yourself. Under Linux this is simple, since you have debuggers on most systems. Under Windows however, you first have to install the Visual C++ development environment. I believe there is a free version (Express?) which you can use. You then run elogd under the debugger, and when it hangs you investigate where. This needs some basic knowledge about C++ development and I'm not sure if you have this, but maybe you can find someone around you who does. 

  66461   Mon Jul 27 01:39:18 2009 Smile Jay Johnstonejay.johnstone@gmail.comQuestionWindows2.7.6Changing Entry Time

Hi,

I am new to eLog, trying to make a logbook tool.  This is probably a question with a simple answer, but here it is...  I need to be able to edit the entry time for an entry as it is being made and also in Edit mode later.  We have field staff who use a paper log in the field and then come back to the computer later and create the log entries, and they need to be time stamped to reflect when an event happened, not when the entry is put into the log.

I'm guessing I'm missing something easy in my Config file, I've looked through the config examples and searched the forum but I couldn't come up with an example of how to make this work.

Thanks in advance!

Jay

  66462   Mon Jul 27 08:40:50 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.6Re: Changing Entry Time

Jay Johnstone wrote:

Hi,

I am new to eLog, trying to make a logbook tool.  This is probably a question with a simple answer, but here it is...  I need to be able to edit the entry time for an entry as it is being made and also in Edit mode later.  We have field staff who use a paper log in the field and then come back to the computer later and create the log entries, and they need to be time stamped to reflect when an event happened, not when the entry is put into the log.

I'm guessing I'm missing something easy in my Config file, I've looked through the config examples and searched the forum but I couldn't come up with an example of how to make this work.

Thanks in advance!

Jay

Hi Jay,

the entry time cannot be changed, because it should reflect the real time when the entry was made. What you can do in your case is to define a "datetime" attribute, which contains then the time stamp. You need something like this:

Attributes = Author, Field time, Subject

Type Field time = datetime

... 

  66463   Mon Jul 27 09:25:06 2009 Reply Jay Johnstonejay.johnstone@gmail.comQuestionWindows2.7.6Re: Changing Entry Time

Stefan Ritt wrote:

Jay Johnstone wrote:

Hi,

I am new to eLog, trying to make a logbook tool.  This is probably a question with a simple answer, but here it is...  I need to be able to edit the entry time for an entry as it is being made and also in Edit mode later.  We have field staff who use a paper log in the field and then come back to the computer later and create the log entries, and they need to be time stamped to reflect when an event happened, not when the entry is put into the log.

I'm guessing I'm missing something easy in my Config file, I've looked through the config examples and searched the forum but I couldn't come up with an example of how to make this work.

Thanks in advance!

Jay

Hi Jay,

the entry time cannot be changed, because it should reflect the real time when the entry was made. What you can do in your case is to define a "datetime" attribute, which contains then the time stamp. You need something like this:

Attributes = Author, Field time, Subject

Type Field time = datetime

... 

 Hi, Stefan,

Thanks for the quick reply, I've added that to my config and it does what we need.

Cheers, Jay

  66464   Mon Jul 27 10:20:14 2009 Entry T. Ribbrockemgaron+elog@ribbrock.orgBug reportLinux2.7.6Wrong error message if invalid attribute is used

I just ran into this little bug: I had defined a new logbook in my config file and suddenly got the message Attribute "Date" not allowed. While I did have several attributes starting with the word "Date" (e.g. "Date In Service", "Date Retired") I had no attribute "Date" in there. After some pondering and wildly commenting out lines, it finally dawned on me: I had used an attribute "ID" - which is also not allowed. However, it would be very helpful if the error message actually reflected that...

  66465   Mon Jul 27 10:49:19 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.6Re: Wrong error message if invalid attribute is used

T. Ribbrock wrote:

I just ran into this little bug: I had defined a new logbook in my config file and suddenly got the message Attribute "Date" not allowed. While I did have several attributes starting with the word "Date" (e.g. "Date In Service", "Date Retired") I had no attribute "Date" in there. After some pondering and wildly commenting out lines, it finally dawned on me: I had used an attribute "ID" - which is also not allowed. However, it would be very helpful if the error message actually reflected that...

Oops, just a typo. The message Attribute "Date" not allowed should read Attribute "ID" not allowed. Fixed in the current SVN version. 

Goto page Previous  1, 2, 3 ... 439, 440, 441 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6