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

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

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

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.

Is anyone else seeing this? It's very confusing to new users.

Further work suggests that the type of pdf file might matter, as I have now seen the defunct daemon after
adding the first pdf file in an entry.

However, I have also found that image manipulation (rotation, size) generates a defunct daemon.

> Hi Stefan and Andreas
> 
> Yesterday I reported I had some issues with the latest elog: but now I can reproduce one.  
> elog 2.9.2-a738232
> 
> I started a new entry, and attached three pdf files.  I did not get the problem of not seeing the png thumnbnail
> this time, although that is annoying if you want/need to adjust the thumbnail image before submitting.
> 
> However, if I then look at the running processes, I have the following listed (ps -A)
> 
> 23677 tty1     00:00:04 elogd
> 23809 tty1     00:00:00 elogd <defunct>
> 23825 tty1     00:00:00 elogd <defunct>
> 23847 pts/0    00:00:00 ps
> 
> 23677 was when I started the elogd daemon, having killed off the previous daemon etc for test purposes.
> 
> 23809 and 23825 appeared after a couple of pdfs were added (second and third ones to be precise).  They can only
> be killed off by killing off the original running daemon.  It appears that attaching a second and further pdf
> attachments to any entry generates an elogd <defunct> in the processes list, although attaching a jpg in the
> middle of a list of pdfs didn't (but the next pdf did).  This is happening while adding attachments, that is the
> Submit button has yet to be pressed, so it seems to be generated  when the pdf file is being processed for some
> reason.
> 
> You can end up with quite a stack of these in the process list!
> 
> I never saw this behaviour with the previous version I was running, SVN2475 I think.
> 
> 
> By the way, I still cannot send an attachment over to this server (showing a screenshot) without the 502 error.

Hi Stefan and Andreas

Yesterday I reported I had some issues with the latest elog: but now I can reproduce one.  
elog 2.9.2-a738232

I started a new entry, and attached three pdf files.  I did not get the problem of not seeing the png thumnbnail
this time, although that is annoying if you want/need to adjust the thumbnail image before submitting.

However, if I then look at the running processes, I have the following listed (ps -A)

23677 tty1     00:00:04 elogd
23809 tty1     00:00:00 elogd <defunct>
23825 tty1     00:00:00 elogd <defunct>
23847 pts/0    00:00:00 ps

23677 was when I started the elogd daemon, having killed off the previous daemon etc for test purposes.

23809 and 23825 appeared after a couple of pdfs were added (second and third ones to be precise).  They can only
be killed off by killing off the original running daemon.  It appears that attaching a second and further pdf
attachments to any entry generates an elogd <defunct> in the processes list, although attaching a jpg in the
middle of a list of pdfs didn't (but the next pdf did).  This is happening while adding attachments, that is the
Submit button has yet to be pressed, so it seems to be generated  when the pdf file is being processed for some
reason.

You can end up with quite a stack of these in the process list!

I never saw this behaviour with the previous version I was running, SVN2475 I think.


By the way, I still cannot send an attachment over to this server (showing a screenshot) without the 502 error.

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.

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.