Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 208 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  68514   Mon Dec 19 12:28:47 2016 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows3.1.2Re: Elog crashes with null Username

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

  68515   Mon Dec 19 19:42:05 2016 Reply Alan Grantagrant@winnipeg.caBug reportWindows3.1.2Re: Elog crashes with null Username

Thanks for the speedy fix.

FYI, our other Elog instances which are running ealrier versions do not exhibit this problem, as I confirmed that entering null ID/password returns "Invalid Username or password" as expected. This may be why it wasn't mentioned by anyone else before. Maybe something got inadvertently dropped in the newer version.

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

  68517   Wed Dec 21 20:15:19 2016 Question rahul bhandarirbhandari@winnipeg.caInfoWindows3.1.2Elog source code giving errors when compiling about missing header files

I downloaded the source code from the git repository which contained the new fix that was made for the missing username-crash error. I tried compiling the elogd.c file using a GCC compiler and it gave an error about missing header files. It first gave an error about netdb.h file and when I commented that header file call, it gave further errors for other header files. I do not really understand why it gives an error about that.  

  68518   Thu Dec 22 09:41:35 2016 Reply Stefan Rittstefan.ritt@psi.chInfoWindows3.1.2Re: Elog source code giving errors when compiling about missing header files

You need the netdb.h header file to compile elog. I see that you compile under Windows. You have to make sure that your compiler installation comes with all header files. The netdb.h file is usually in /usr/include under Unix.

rahul bhandari wrote:

I downloaded the source code from the git repository which contained the new fix that was made for the missing username-crash error. I tried compiling the elogd.c file using a GCC compiler and it gave an error about missing header files. It first gave an error about netdb.h file and when I commented that header file call, it gave further errors for other header files. I do not really understand why it gives an error about that.  

 

  68520   Mon Jan 2 16:32:18 2017 Question Devrim Esenturkdevrim.esenturk@gmail.comQuestionWindowsV3.1.1-3f311c5Gmail email smtp settings

Hi all

I am trying to send email via Gmail smtp with no success. Elog uses port 25 which is not allowed. I need to use 587 or 465 ports to send mail. How can I change the port?

Have a good year all!

Devrim

  68555   Mon Jan 30 15:50:45 2017 Question Terry Almondterry.almond@stfc.ac.ukQuestionWindows2.8.1-2350Opening a Local File using <a href="file:///../filename.doc">text</a>

I've created an elog where users can then enter links to a file: for example they would enter:

<a href="file:///M:/Data/Inspection%20Reports/ABC123.doc">ABC123</a>

If they are running this on their desktops where everyones M drive is mapped to the same location, not a problem, the file opens perfectly.

The problem we have is some people work off of site and hence they run everything from a memory stick (USB drive), then once back in the office, copy the memory stick back on to the network.

Unfortunately when off of site the href link M: is no longer valid as the M drive doesn't exist.

Hence i've been trying to open a local file with the following syntax: 

<a href="file:///../ABC123.doc">ABC123</a>

It just won't open

Hence in my frustration i basically copied the word file ABC123.doc into every single directory on the memory stick thinking surely this must work, it must find it somewhere, unfortunately not.

What am i doing wrong?

 

  68556   Mon Jan 30 16:47:31 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.8.1-2350Re: Opening a Local File using <a href="file:///../filename.doc">text</a>

Linking to external files via "file:///..." is a bad idea, since only a pointer is stored in the elog. So if someone puts somehing on M: and the drive is removed, the file is physically gone. No way to retrieve it. Instead of puttting links to files, users should get trained to ATTACH the files to elog cntries (V3 of elog has a "Drop attachments here..." section. Only then the files are physically transferred into elog and accessible independed of your external memory stick.

Stefan

Terry Almond wrote:

I've created an elog where users can then enter links to a file: for example they would enter:

<a href="file:///M:/Data/Inspection%20Reports/ABC123.doc">ABC123</a>

If they are running this on their desktops where everyones M drive is mapped to the same location, not a problem, the file opens perfectly.

The problem we have is some people work off of site and hence they run everything from a memory stick (USB drive), then once back in the office, copy the memory stick back on to the network.

Unfortunately when off of site the href link M: is no longer valid as the M drive doesn't exist.

Hence i've been trying to open a local file with the following syntax: 

<a href="file:///../ABC123.doc">ABC123</a>

It just won't open

Hence in my frustration i basically copied the word file ABC123.doc into every single directory on the memory stick thinking surely this must work, it must find it somewhere, unfortunately not.

What am i doing wrong?

 

 

  68557   Mon Jan 30 16:56:34 2017 Reply Terry Almondterry.almond@stfc.ac.ukQuestionWindows2.8.1-2350Re: Opening a Local File using <a href="file:///../filename.doc">text</a>

Hi Stefan

Unfortunately this would become impractical for us as many of the test data files which we'd need to link too are Gb's in size, some over 100Gb, hence only the files needed to do a say an inspection of the equipment would be copied onto memory sticks. Currently we use an excel speadsheet to store hyperlinks to all of the files / directories we need - unfortunately some people forget to update this and it was asked could we do it using elog as people are familiar with this wonderful peice of software.

Hence why i'm now investigating - so is it actually posible?

Kind regards

Terry 

Stefan Ritt wrote:

Linking to external files via "file:///..." is a bad idea, since only a pointer is stored in the elog. So if someone puts somehing on M: and the drive is removed, the file is physically gone. No way to retrieve it. Instead of puttting links to files, users should get trained to ATTACH the files to elog cntries (V3 of elog has a "Drop attachments here..." section. Only then the files are physically transferred into elog and accessible independed of your external memory stick.

Stefan

Terry Almond wrote:

I've created an elog where users can then enter links to a file: for example they would enter:

<a href="file:///M:/Data/Inspection%20Reports/ABC123.doc">ABC123</a>

If they are running this on their desktops where everyones M drive is mapped to the same location, not a problem, the file opens perfectly.

The problem we have is some people work off of site and hence they run everything from a memory stick (USB drive), then once back in the office, copy the memory stick back on to the network.

Unfortunately when off of site the href link M: is no longer valid as the M drive doesn't exist.

Hence i've been trying to open a local file with the following syntax: 

<a href="file:///../ABC123.doc">ABC123</a>

It just won't open

Hence in my frustration i basically copied the word file ABC123.doc into every single directory on the memory stick thinking surely this must work, it must find it somewhere, unfortunately not.

What am i doing wrong?

 

 

 

ELOG V3.1.5-2eba886