Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 78 of 238  Not logged in ELOG logo
icon5.gif   New entries remotely?, posted by Daniel Roldan on Tue Jul 29 16:20:16 2014 

 Hi all,

I would like to create a new entry remotely.

I would like that when the macro run, the macro automatically create a new entry in my Elog.

I was searching, but i don't saw any thing about this.

Is possible to do a new entry remotely?

 

Thanks for all.

    icon2.gif   Re: New entries remotely?, posted by Stefan Ritt on Tue Jul 29 16:53:18 2014 

Daniel Roldan wrote:

 Hi all,

I would like to create a new entry remotely.

I would like that when the macro run, the macro automatically create a new entry in my Elog.

I was searching, but i don't saw any thing about this.

Is possible to do a new entry remotely?

 

Thanks for all.

Use the "elog" command line utility as described here under tips & tricks: http://midas.psi.ch/elog/userguide.html

icon5.gif   Unable to resize images in browser, posted by Matthew Deller on Tue Feb 18 21:32:27 2014 
I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.

Output when running elog with verbose option shows buffer overflow when resize attempted:
[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated

Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick?
    icon2.gif   Re: Unable to resize images in browser, posted by Stefan Ritt on Fri Feb 21 13:09:48 2014 

Matthew Deller wrote:
I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.

Output when running elog with verbose option shows buffer overflow when resize attempted:
[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated

Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick?


What happens if you execute the command manually, like

$ identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png

The "identify" command just checks the size in pixels of your image and expects something like 800x600. Let me know if this command returns something completely different.

/Stefan
       icon2.gif   Re: Unable to resize images in browser, posted by Matt Deller on Thu Jun 19 09:35:20 2014 

Stefan Ritt wrote:

Matthew Deller wrote:
I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.

Output when running elog with verbose option shows buffer overflow when resize attempted:
[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated

Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick?


What happens if you execute the command manually, like

$ identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png

The "identify" command just checks the size in pixels of your image and expects something like 800x600. Let me know if this command returns something completely different.

/Stefan


Sorry for very late reply. I recently rebuilt our server. Elog 2-9-2, new machine, new OS (Ubuntu 14.04), new version of ImageMagick (6.7.7-10), but I'm having the same unresolved problem. identify -format from the command line returns 645x860 (as it should). Any ideas?

-Matt
icon5.gif   Strange Error, Service hangs when record is deleted., posted by Chuck Brost on Wed Jun 11 19:18:06 2014 

I have 4 services running on a Windows Server 2008 R2 machines, 4 separate logs, only one of them is doing this, but that could be because only one of them is trying to delete records once they are posted, I cannot say.

On that one log, everything runs fine until they try to delete a record, and they are doing it under the admin login, but the service hangs.  anyone trying to log in get the 404 error that the page is not available.  to clear it I have to open Manage/Services and then Task Manager.  First I kill the process for that log book, then I can restart the service and everything is back.. trying to stop the service and then start it, or just restart the service, this does no good, in fact, it will hang at stopping the service.. it is not responding at all.  this happened to the same log when I had this on the original Windows Server 2003, so it is not new.. they just don't delete things for a long time, then they seem to do it every week, more than once.. and usually at night or on the weekend. (are they just doing it to mess with me?  Maybe, but I do not think so since it would not get me in trouble if I were busy, out of town or just not home and could not get to it until the next business day and they know this..

Any ideas what could cause this?

My Configuration is as follows, with only the names changed to protect the guilty:

[global]
port = 8081
SSL = 1

css = solar.css
password file = PWFILE
self register = 0
login expiration = 0
restrict edit = 1

Allow Password change = 0
List Menu Commands = New, Find, Select, Config, Help
Menu Commands = List, New, Edit, Delete, Reply, Help
Enable Attachments = 0
show attachments = 0
display mode = summary

admin users = admin,ME
login users = user,ME,user2,user3
deny config = user,ME,user2,user3
deny delete = user,ME,user2,user3
deny edit = user,ME,user2,user3

Welcome Title = <p><font size=6 color=white> S---- T------ Furnace Logs</font><br><font size=3 color=white> These logs are C---------- Confidential: </font> <font size=3 color=55ff55> Green </font>
Attributes = Badge, Run, Recipe, Mod, Rebraze, W.O., Operation, Item, Qty
Options Mod = Boolean
Options Rebraze = Boolean

list display = date, Badge, Run, Recipe, Mod, Rebraze, W.O., Operation, Item, Qty

Options Recipe = AN001, AN002, AN003, AN004
Extendable Options = Recipe
Required Attributes = Badge, Recipe, W.O., Operation, Item, Qty
default encoding = 1
allowed encoding = 1
allow HTML = 0
suppress default = 3
suppress email on edit = 3
display email recipients = 0

[V8]
Theme = default
Comment = V8 Furnace Log Data Owner: B. Sands
Preset Run = V8-%Y-####
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date


[V9]
Theme = default
Comment = V9 Furnace Log Data Owner: B. Sands
Preset Run = V9-%Y-####
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date

[V10]
Theme = default
Comment = V10 Furnace Log Data Owner: B. Sands
Preset Run = V10-%Y-####
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date

[V11]
Theme = default
Comment = V11 Furnace Log Data Owner: B. Sands
Preset Run = V11-%Y-####
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date

[V12]
Theme = default
Comment = V12 Furnace Log Data Owner: B. Sands
Preset Run = V12-%Y-####
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date

[V13]
Theme = default
Comment = V13 Furnace Log Data Owner: B. Sands
Preset Run = V13-%Y-####
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date

[Freezer]
Theme = default
Comment = Freezer Furnace Log Data Owner: B. Sands
Preset Run = Fre-%Y-####
Preset recipe = None
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date

[MyTest]
Theme = default
List Menu Commands = New, Find, Select, Config, CSV Import, Help

Comment = MyTest Log
Preset Run = MT-%Y-####
Locked Attributes = Run
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date


 

icon5.gif   Passing html code for table using elog command, posted by Remington Tyler Thornton on Thu May 22 21:39:55 2014 

Hey,

I am testing out automated entries using elog on the command line. The file I pass has html code for a table; the resulting entry shows the html code for the table instead of generating the table. Is there a way to make elog parse the code to show a formatted table?

Thanks  in advance.

    icon2.gif   Re: Passing html code for table using elog command, posted by Andreas Luedeke on Mon May 26 09:55:06 2014 

Remington Tyler Thornton wrote:

Hey,

I am testing out automated entries using elog on the command line. The file I pass has html code for a table; the resulting entry shows the html code for the table instead of generating the table. Is there a way to make elog parse the code to show a formatted table?

Thanks  in advance.

 

 
English (auto-detected) » English
 

The elog command has the option "-n <n>" to tell elog, what type of text it should expect.

[-n 0|1|2]               Encoding: 0:ELcode,1:plain,2:HTML
 
English (auto-detected) » English
 
You'll find it explained in the documentation https://midas.psi.ch/elog/userguide.html#misc

It is necessary for elog to know the type of encoding, otherwise it would not show non-html content correctly.

icon1.gif   A couple of observations, posted by David Pilgram on Fri Mar 28 14:29:24 2014 
Hi Stefan and Andreas,

When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.

The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
to it but the change in layout wasn't warmly welcomed.

Also, shame that moving from Subversion means that the increments are no longer in easy numerical order.  So I
believe that I am commenting on the latest possible version available, a738232.

A question.  My logbooks directory is now 1.8GB.  Yes, there are a lot of attachments etc to bulk it out, but
it's all plain text comments.  Is there a limit as to the size, or total number of entries?  Elog takes a
notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
be caused by this.  Anyone any thoughts?

I don't know how I managed it, but I got elog to generate two entries with the identical ID no.  The new entries
were different as well.  The log file faithfully had recorded the two separate replies to the entry having the
same ID no as well.   Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
copy.  I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
it appears, it appears in two or three places within the list of threaded entries.
    icon2.gif   Re: A couple of observations, posted by David Pilgram on Fri Mar 28 14:55:16 2014 
I tried to attach a screenshot showing this, but kept getting a 502 bad gateway error.
The message in the red banner is
Error sending Email via <i>"psquad.psi.ch"</i>
with that html showing, by the way.
> Hi Stefan and Andreas,
> 
> When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
> a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.
> 
> The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
> to it but the change in layout wasn't warmly welcomed.
> 
> Also, shame that moving from Subversion means that the increments are no longer in easy numerical order.  So I
> believe that I am commenting on the latest possible version available, a738232.
> 
> A question.  My logbooks directory is now 1.8GB.  Yes, there are a lot of attachments etc to bulk it out, but
> it's all plain text comments.  Is there a limit as to the size, or total number of entries?  Elog takes a
> notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
> be caused by this.  Anyone any thoughts?
> 
> I don't know how I managed it, but I got elog to generate two entries with the identical ID no.  The new entries
> were different as well.  The log file faithfully had recorded the two separate replies to the entry having the
> same ID no as well.   Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
> copy.  I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
> it appears, it appears in two or three places within the list of threaded entries.
icon5.gif   Generation of .png files for attachments, posted by David Pilgram on Fri Mar 28 14:15:18 2014 
Hi Stefan and Andreas,

With the latest incremental version of elog (a738232), I have noticed that when attaching a pdf file, the
.png thumbnail is not generated when the "upload" button is pressed - there is just the usual small line saying
what the latest attachment is.  If this happens, a subsequent attachment will force the generation of the
thumbnail for the *previous* attachment, and again no thumbnail for the latest attachment.

Submitting the comment will also generate the thumbnail.

As of yet, I cannot find any consistent pattern to this.  Also, it's hardly a disaster, but I have been fooled
when attaching a pdf file that subsequently turned out to be damaged and thus unreadable.
icon4.gif   Problem with ELOG, posted by Markus Grosse-Kock on Thu Mar 13 11:34:58 2014 

Hi,

we have a problem. After windows updates, the elog service doesn´t start:

 

What can we do?

Best regards,

Markus

    icon6.gif   Re: Problem with ELOG, posted by Markus Grosse-Kock on Thu Mar 13 12:39:41 2014 

Markus Grosse-Kock wrote:

Hi,

we have a problem. After windows updates, the elog service doesn´t start:

 

What can we do?

Best regards,

Markus

After I uninstalled the software and reinstalled, the function is working again.

Thanks.

Best regards,

Markus

icon5.gif   XML import Error, posted by Donald on Thu Feb 27 15:15:55 2014 new__2.xml

Hi

 

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book.  I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8  I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

 

[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type

    icon2.gif   Re: XML import Error, posted by Andreas Luedeke on Mon Mar 3 15:42:29 2014 

Donald wrote:

Hi

 

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book.  I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8  I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

 

[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type

Hi Donald,
yes, the import function gave me some headache in the past, too.
 
English (auto-detected) » English
 
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)

I hope this helps.

       icon2.gif   Re: XML import Error, posted by Donald on Tue Mar 4 19:48:02 2014 new__2.xml

Andreas Luedeke wrote:

Donald wrote:

Hi

 

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book.  I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8  I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

 

[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type

Hi Donald,
yes, the import function gave me some headache in the past, too.
 
English (auto-detected) » English
 
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)

I hope this helps.

 Hi Andreas

That worked,  thank you so much. now I'm on to a new error. 

Now every time i try to do the import it crashed the elogd. 

OS is windows server 2008 R2.  I have the elogd installed as a service.

here is the even log:

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86

I have attached the Data file I'm using to generate the fault every time.  same config as before.   Any Ideas?

 

          icon2.gif   Re: XML import Error, posted by Donald on Tue Mar 11 15:17:36 2014 

Donald wrote:

Andreas Luedeke wrote:

Donald wrote:

Hi

 

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book.  I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8  I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

 

[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type

Hi Donald,
yes, the import function gave me some headache in the past, too.
 
English (auto-detected) » English
 
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)

I hope this helps.

 Hi Andreas

That worked,  thank you so much. now I'm on to a new error. 

Now every time i try to do the import it crashed the elogd. 

OS is windows server 2008 R2.  I have the elogd installed as a service.

here is the even log:

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86

I have attached the Data file I'm using to generate the fault every time.  same config as before.   Any Ideas?

 

 Anyone have any luck reproducing the error? or have suggestions on how to fix it?

ELOG V3.1.5-3fb85fa6