Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 645 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  1375   Thu Aug 4 22:59:12 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0b3Re: Email subject garbaged when set?

Chris Green wrote:
The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.


This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047. All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly. One could of course put a switch into elog to encode it or not. But as soon as you want to send some non-ASCII characters (like the Norwegian as described in the thread mentioned above) you have a problem. Maybe you can configure your email client correctly to interprete the encoded subject?
  1374   Thu Aug 4 22:35:57 2005 Reply Stefan Rittstefan.ritt@psi.chInfoLinux2.6.0Re: "full" only changes color

Kees Bol wrote:
I thougt when choosing the full-view the text would appear along with the other attributes.


That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine.
Attachment 1: summary.jpg
summary.jpg
Attachment 2: full.jpg
full.jpg
  1373   Thu Aug 4 21:44:53 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6Re: Login twice

Carl Shirey wrote:
Yes Here is a copy of the elog.cfg.


I tried with your config file and it worked fine. So can you tell me:

  • At what URL do you access your logbook? Do you just type http://localhost:8080 or anything else
  • Do you use any proxy or stunnel?
  • What is the URL in your browser showing on the first and second login?

You might want to consider to put a
URL = http://<your host>:8080/
into your config file.
  1372   Thu Aug 4 21:36:21 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.0Re: Creating logbook by copying an existing one crashes elog

Chris Howe wrote:
Trying to create a new logbook from an existing one causes elog to crash.


I (hopefully) fixed that bug. The fix will be included in 2.6.0-beta4.
  1371   Thu Aug 4 20:35:48 2005 Reply Stefan Rittstefan.ritt@psi.ch Windows2.60 beta3Resolution (i think) - Re: Problems with beta 3 (Follow-on to CVS/XML msg 1296)

PJ Meyer wrote:
think I figured it out- had to make explict most of the default settings: resource, logbook, url, theme, css and so on.

so this is done.


I'm not satisfied with this solution, I rather would like to fix the problem at the source. So can you remove the explicit directory settings, then stip down the config file to the bare minimum where the problem happens, then send me this file so that I can reproduced it. Do yo use SSL, stunnel or a proxy?

- Stefan
  1370   Thu Aug 4 20:32:56 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux 2.5.9+r16Re: problem with list display attribute

John Habermann wrote:
I not sure if this has been found and fixed as I did find something to do with the list display attribute in the forums but wasn't sure if it was the same thing.

There seems to be a bug with the List Display attribute in that it drops the last attribute of the list. So in my example if I want to display the Subject in my list I have to add a dummy attribute after it otherwise the Subject will not be displayed. The comma after Subject is not enough, but all you have to do is to add 1 letter and then you will see the subject in List view. If you don't all I see is the Date and Author fields and then the Text field in my Summary view in the log book.

List Display = Date,Author,Subject,t

I am running elog 2.5.9+r1674-1 on Debian sarge.


I tried with the current 2.6.0-beta3 and it worked fine. Can you send me your full elogd.cfg in order to reproduce the problem?
  1369   Thu Aug 4 20:29:23 2005 Reply Stefan Rittstefan.ritt@psi.ch   Re: Notify email recipient of attachments without including?

Chris Green wrote:
Hi,

Our elog is going to be taking some large attachments. I've disabled the attachments from going out in the email, but I'd like email recipients to know that the post has attachments associated with it. Is there a mechanism to do this already, or would it be an enhancement? I'm looking for something like:

Email Notify Attachments = 0 | 1 | 2

Where 0 = no notification,
1 = number only,
2 = list

... independent of whether attachments are included with the email itself.

Thanks,
Chris.


I added Email Format = 64 for only attachment names. So you could set Email Format = 111 to get everything except the full attachments.
  1368   Thu Aug 4 11:19:53 2005 Reply Emiliano GabrielliAlberT@SuperAlberT.itBug reportLinux | Windows2.60b3Re: Response is very slow with beta3

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
for every image elog has to serve one can see something similar to the above ... lot of time lost in selects.. then a lot of data (serving an image I suppose), then a lot of time in select again and again ... untill everything is sent, in a couple of minutes or more Crying


Maybe an issue related to the dns search you introduced in order to guess the correct host name ?? ..


This is strange to me, since I did not change anything which could slow down the server this much. The dns search your mentioned is only evaluated once on startup of elogd, so it cannot be the cause. The select() statements with Timeouts are normal. If there is no HTTP request (elogd is idling), the select should time out after one second, to be able to check a changed config file for example. If a HTTP request arrives, the select() call is immediately terminated and the request served.

There is however some problem with DNS server which I saw on midas.psi.ch. If the DNS host name resolution is slow due to a slow DNS server, this could slow down elogd considerably significantly, but only occasionally. I saw elogd hanging on midas.psi.ch like once or twice a day for ~30 seconds.

I order to address this problem, I imlemented a global flag "resolve host names = 0|1". The default is "0", which means that elogd does not contact the DNS server, and rather save the raw IP address in log files etc.

Can you check the CVS version and see if it makes any difference?


No, ok it appears to be a very strange problem related to my JS calendar filter ... I'll change it's state to beta in contributions, but the very strange thing is that it works fine when no stunnel is used ...
ELOG V3.1.5-3fb85fa6