ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 118 of 807

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6451 Entries

Goto page Previous 1, 2, 3 ... 117, 118, 119 ... 805, 806, 807 Next

Fri Mar 12 12:28:36 2010

Re: could not get the threaded display working

FX FRERE wrote:

I have been trying to get the display mode into threaded by default, it does not work on any of my logbooks. I saw related threads in this forum but none gave me a solution (unless the 2.7.8-2282 is available for download).

The display mode is taken from the configuration option "Display mode = ..." only the very first time a users accesses a logbook. When the user switches to any other mode (summary, full) by clicking on the according menu option, the new mode is stored in a cookie in the browser and overrides the "Display mode = ..." setting. Maybe that is what you see.

66756

Fri Mar 12 16:18:20 2010

Re: Last 3 days of log entries

> David send me his modification and I put it into the main source code, so it will be contained in the next Windows 
> version.

I made an interim 2.7.8-3 version which contains the fix and can be downloaded from the web site.

66757

Fri Mar 12 19:30:53 2010

Re: Fail to connect to SMTP server on WinXP but works on Win2K

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I have been running Elog for years on a Win2K machine with no email problems. I have been forced to move it to a WinXP machine and I always get this message under WinXP: "Error sending Email via "netsvr10.prod.company.com": Cannot connect to server"

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} NEW entry #0
28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} Email from <christophermeyer@fedex.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
28-Oct-2009 18:28:42 [609144@199.82.127.9] {Generals} 220 netsvr10.prod.company.com -- Server ESMTP (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit))

Here is an entry from today's elog.log under WinXP that does not work.

06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} NEW entry #0
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} READ entry #1612

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

06-Mar-2010 10:31:43 [117361@199.81.166.149] {Gbld} READ entry #1691
06-Mar-2010 10:39:10 [117361@199.81.166.149] {Gbld} NEW entry #0
06-Mar-2010 10:39:11 [117361@199.81.166.149] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com

The only idea I have is that your Windows firewall prevents outgoing network traffic on port 25 (SMTP). You should put an exception into the firewall rule. You can try that by opening a DOS box and entering

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

66758

Sat Mar 13 09:40:37 2010

Stefan Ritt wrote:

Mirza Ehsan wrote:

I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action.

I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.

If any one can help me in fixing this problem

I propose that you get 2.7.8 working. If the authentication fails, try do do password recovery, or recreated the accounts.

Thanks for the reply. I found problem with existing version. I opened log book group without opening log book details in configuration, that is why at submitting or opening elog was not able to find log book for that group and was getting lost.

Regarding moving to 2.7.8, I want to know that in this new version file location for pwd and log books will remain same or are changed. If changed then I have to change location manually. Also how I can perform password recovery.

66762

Mon Mar 15 09:29:11 2010

Invalid URL for groups beneath top groups in overview page

Hi,

I'm trying to implement top groups and started with the sample configuration shown in the 'Syntax of elogd.cfg' chapter of the documentation. But now I'm facing a problem with the links in the logbook selection page.

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

The selection page for the top groups is displayed correctly, but the URL for the groups beneath the top group is incorrect. The URL for the Linux PCs group for instance is http://localhost:8080/engineering/engineering/ . The URLs for the logbooks within the Linux PCs groups is correct (e.g. http://localhost:8080/Debian/)

Has anybody an idea what's going wrong in y configuration?

Bertram

Attachment 1: elogd.cfg

[global]
Port=8080
Logbook tabs = 1
Expand selection page = 0
;Main tab = "Overview"
Use Lock = 1
Default encoding = 1
Resolve host names = 0


Logfile = elogd.log
Logging level = 3

Logout to main = 1
Options Author = BMetz  
Admin user = BMetz

Password file = ./passwd
;Protect selection page = 0

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1


[Red Hat]
Comment = Red Hat Logbook
Time format = %Y-%m-%d 

[Debian]
Comment = Debian Logbook
Time format = %Y-%m-%d 

[Mandrake]
Comment = Mandrake Logbook
Time format = %Y-%m-%d 

[NT]
Comment = NT Logbook
Time format = %Y-%m-%d 

[XP]
Comment = VR11/VP11
Time format = %Y-%m-%d 

[Employees]
Comment = Employess
Time format = %Y-%m-%d 

[Purchases]
Comment = Purchases
Time format = %Y-%m-%d

66763

Mon Mar 15 11:21:30 2010

Re: Invalid URL for groups beneath top groups in overview page

Bertram Metz wrote:

Hi,

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

Has anybody an idea what's going wrong in y configuration?

Bertram

Thanks for reporting this bug. I fixed it in the intermediate release 278-4 which is ready for download.

66764

Mon Mar 15 13:20:17 2010

Re: Invalid URL for groups beneath top groups in overview page

Stefan Ritt wrote:

Bertram Metz wrote:

Hi,

Here's my group configuration:

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1

Has anybody an idea what's going wrong in y configuration?

Bertram

Thanks for reporting this bug. I fixed it in the intermediate release 278-4 which is ready for download.

Thanks for the quick bug fix.

Bertram

66768

Wed Mar 17 21:34:53 2010

Re: Fail to connect to SMTP server on WinXP but works on Win2K

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

Here is an entry from today's elog.log under WinXP that does not work.

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

My apologies. I just realized that my first answer to you was lost. I turned the firewall completely off with no luck. I also tried the telnet and it worked. So, it does not appear to be the firewall. I tried the VM's afterwards. Another puzzle is that the Win2K VM works on a WinXP host. It seems like it is only the WinXP elog that fails. I have tried to obtain some our company's IT help with no luck.

Goto page Previous 1, 2, 3 ... 117, 118, 119 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6