Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 345 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6453 Entries 
Goto page Previous  1, 2, 3 ... 344, 345, 346 ... 805, 806, 807   Next  
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  67584   Tue Oct 15 14:14:07 2013 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindows2.9.2Re: Error: Attribute <date> not supplied.

Barend wrote:

Stefan/Andreas,

When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."

The configuration file uses:

Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
 

The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.

As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.

But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.

 

Is this a bug -or- do I have to change the configuration?

 

Thanks & regards, Barend

Hi Barend,

I can reproduce your point. 

I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line.  True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.

Another way is if you *preview* your entry, you can then submit it and that works.  This seems to work by bring up a different page where you can edit all those Fixed Attributes.  (I'm not sure that Preview is meant to do that, but it does and it's a work-around).

Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way.  But I see that you don't want the opportunity for these to be changed.

I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).

 

So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination.

  67586   Thu Oct 17 14:23:06 2013 Reply Oliver Kirsebomoliver.kirsebom@gmail.comQuestionLinux2.8.0Re: automated email notification did not work for me

Stefan Ritt wrote:

Jianglai Liu wrote:

Hi,

I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.

According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:

SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
 

I then used "elogd -t" to encode the password into the configuration file.

But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"

If I switched to use my university email servers, similar things happened.

SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu

I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"

I also switched to use one of my old work server

SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu

and ended up with the same error message.

I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.

Thanks much!

elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.

 Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver

  67587   Thu Oct 17 14:27:56 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.8.0Re: automated email notification did not work for me

Oliver Kirsebom wrote:

Stefan Ritt wrote:

Jianglai Liu wrote:

Hi,

I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.

According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:

SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
 

I then used "elogd -t" to encode the password into the configuration file.

But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"

If I switched to use my university email servers, similar things happened.

SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu

I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"

I also switched to use one of my old work server

SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu

and ended up with the same error message.

I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.

Thanks much!

elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.

 Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver

Didn't have time yet for this. 

  67588   Tue Oct 22 10:54:51 2013 Reply Barendoffice@amtc2.comQuestionWindows2.9.2Re: Error: Attribute <date> not supplied.

David Pilgram wrote:

Barend wrote:

Stefan/Andreas,

When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."

The configuration file uses:

Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
 

The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.

As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.

But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.

 

Is this a bug -or- do I have to change the configuration?

 

Thanks & regards, Barend

Hi Barend,

I can reproduce your point. 

I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line.  True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.

Another way is if you *preview* your entry, you can then submit it and that works.  This seems to work by bring up a different page where you can edit all those Fixed Attributes.  (I'm not sure that Preview is meant to do that, but it does and it's a work-around).

Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way.  But I see that you don't want the opportunity for these to be changed.

I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).

 

So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination.

 

Hi David, Thanks for the reply. I'll review the options and decide what is the best option to move forward. Regards, Barend
  67591   Mon Oct 28 11:21:19 2013 Question Alexander Nozikaltavir@gmail.comQuestionLinux2.9.2-2455Attachment file names encoding
Hello,
I am trying to move elog from old FreeBSD system to a new Ubuntu server and stuck with attachment encoding problem. The elog entries as well as attachments &#1072;&#1096;&#1076;&#1091; &#1090;&#1092;&#1100;&#1091;&#1099; are mostly in koi8-r or cp1251 encoding. While it is relatively easy to configure log entries to display correctly, I still can't manage to deal with attachments. In old elog all attachments with Cyrillic file names are "not found" by elog web interface while files are present in the directory (though previous admin could have done something with the encoding).

If I am creating a new elog with default koi8-r charset, then new cyrrilic attachments are uploaded and displayed normally but after download the file name encoding is broken. Does elog do something with attachment name encoding?
  67592   Tue Oct 29 12:04:44 2013 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2-2455Re: Attachment file names encoding

Alexander Nozik wrote:
Hello,
I am trying to move elog from old FreeBSD system to a new Ubuntu server and stuck with attachment encoding problem. The elog entries as well as attachments &#1072;&#1096;&#1076;&#1091; &#1090;&#1092;&#1100;&#1091;&#1099; are mostly in koi8-r or cp1251 encoding. While it is relatively easy to configure log entries to display correctly, I still can't manage to deal with attachments. In old elog all attachments with Cyrillic file names are "not found" by elog web interface while files are present in the directory (though previous admin could have done something with the encoding).

If I am creating a new elog with default koi8-r charset, then new cyrrilic attachments are uploaded and displayed normally but after download the file name encoding is broken. Does elog do something with attachment name encoding?


You should be able to figure this out:
As an administrator you can have a look what are the real file names on the file system.
With your browser you can see what are the names of the attachment. Like in this forum, the entry https://midas.psi.ch/elogs/Forum/67571 has an attachment https://midas.psi.ch/elogs/Forum/131008_181353/import.xml
If the two match you don't have an encoding but some file system problem. If they don't match, then we are one step further in solving your problem Smile
Thought, the file name in the URL has to be URL encoded (see e.g. http://www.w3schools.com/tags/ref_urlencode.asp), which is of course different from the encoding of the file system.
  67593   Wed Oct 30 10:15:13 2013 Reply Alexander Nozikaltavir@gmail.comQuestionLinux2.9.2-2455Re: Attachment file names encoding
Thank you for reply.

I am not very experienced linux user so it could be a problem with the file system. Let me just describe what I do and what I see as a result.

I created a new elog just for the testing purpose, it has "Charset = koi8-r" line in the config file. Than I post a new entry to this elog with russian text and a file with russian file name from windows (so I expect that charset is cp1251). Now I open this entry. The text is fine and the filename is fine on the page (the same russian text I expect to see), but when I try to download it, the actual file name is broken and to restore it I need koi8-r -> cp1252 transformation. The file itself is readable.
If I look in the actual logbook directory, then in the entry file the file name is readable (entry file encoding is koi8-r), but the attachment file name contains many "?" and not readable by file system.

So first my question is what happened to the file name incoding in a logbook directory, and the second one: what should I do to make attachments download as they were uploaded?

Thank you in advance.
  67594   Wed Oct 30 17:57:38 2013 Angy Fabio Sellagaia-gc@altecspace.itQuestionLinux2.9.2-1kerberos authentication NOT working

Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

 
⇄
Detect language » Italian
 

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

Goto page Previous  1, 2, 3 ... 344, 345, 346 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6