| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1505
|
Tue Nov 8 08:17:22 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0 | Re: Problems with ELOG and Internet Explorer |
| Elaine Cristina Franchini dos Anjos wrote: | | I edited and used preview many times and the ELOG worked fine without errors in IE. So, I think my problem is something configured in the proxy or https that Internet Explorer doesn't work very well in this circumstance. |
Have a look at your URL = ... statement in elogd.cfg
It should probably read
URL = https://antares.ccuec.unicamp.br:9696
ELOG uses redirection internally. To determine it's own address, it uses the URL statement. If you use Apache as an proxy together with https, you have to specify the URL under which you usually access ELOG from outside. If this is wrong, ELOG might try to redirect to http:// or something which might not be possible.
A good way to debug this is to run ELOG with the -v flag and carefully watch the HTTP traffic. You will see Location: ... statements which redirect the browser, then the browser will access the redirected URL (if it's correct), or you will see nothing (in case the browser tries to access a non-existing URL). |
|
1539
|
Sat Dec 3 23:32:13 2005 |
 | Jesse Wodin | jwodin@stanford.edu | Question | Linux | 2.6.0 | Upgrade from 2.3.8 to 2.6.0 logbook problem | Hi, I'd like to upgrade from an old version of elog 2.3.8 to 2.6.0. I installed the new version, and it runs fine, but it doesn't seem to see my old logbooks (the path in the conf file is correct). Do I have to upgrade my logbooks somehow?
THanks!
Jesse |
|
1540
|
Mon Dec 5 17:11:33 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0 | Re: Upgrade from 2.3.8 to 2.6.0 logbook problem |
| Jesse Wodin wrote: | | Hi, I'd like to upgrade from an old version of elog 2.3.8 to 2.6.0. I installed the new version, and it runs fine, but it doesn't seem to see my old logbooks (the path in the conf file is correct). Do I have to upgrade my logbooks somehow? |
No. The last change in the logbook format was for version 2.0.0. So something else must be wrong. Just creat one entry with your new elog, and see where it's created on the hard disk. Put your old logbooks there. If you start elogd manually with the "-v" flag, you will see it indexing all logbooks. Check that you see all your entries there. |
|
1541
|
Wed Dec 7 02:32:00 2005 |
| Jesse Wodin | jwodin@stanford.edu | Question | Linux | 2.6.0 | Re: Upgrade from 2.3.8 to 2.6.0 logbook problem | Thanks, you were right, it was just a permissions problem on the logbooks, which I had copied over as root.
j. |
|
1551
|
Thu Dec 15 13:08:35 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.6.0 | New ELOG version 2.6.0 | Dear ELOG users,
I'm happy to announce the release of ELOG version 2.6.0. After a long period of beta testing, all functions are now sufficiently stable for a public release. The major new feature is the introduction of the ELCode tags. They are similar to the well known BBCode tags, and let you format an elog entry. It is now also possible to embed inline images in an elog entry  , which are even sent in email notifications.
So have fun,
Stefan |
|
1552
|
Thu Dec 15 15:33:04 2005 |
 | Alex H | alex@synergie-inf.com | Other | Windows | 2.6.0 | Bad date format. | Hi Stefan,
I have two loogbook who are using the Type Derniere image = Date parameter, but I obtain a big
number instead of a formated date.
On my logbook "liste" (Look on the first attachement elog.gif please to watch the problem.)
I obtain this problem.
Here is the part of the elogd.cfg file for logbook "Liste" :
[Liste]
Theme = Bubble
Comment = Liste des routeurs / firewall clients
Type Dernière image = Date
List display = Client, Nom machine, Type, Equipment, Emplacement, Nom_admin, Pwd_admin, Maint, Derniere image
Link display = Client, Nom machine, Type, Equipment, Emplacement, Maint, Derniere image
Attributes = Client, Nom machine, Equipment, Type, Emplacement, Nom_admin, Pwd_admin, Maint, Derniere image
Extendable options = Client, Equipment
Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}
{1} Preset text = FWL1.txt
{2} Preset text = FWL2.txt
{3} Preset text = FWL4.txt
{4} Preset text = VPN1.txt
{5} Preset text = VPN2.txt
{6} Preset text =
Preset Author = $short_name
Options Maint = Oui, Non
Required Attributes = Client, Type, Equipment, Nom machine, Maint
Locked Attributes = Author
Page Title = ELOG - $Nom machine
Reverse sort = 0
Quick filter = Client, Type, Maint
Summary lines = 2
Entries per Page = 50
Case sensitive search = 1
On my logbook "Image Routeurs" (Look on the second attachement elog2.gif)
No Problem
Here is the part of the elogd.cfg file for logbook "Liste" :
[Image Routeurs]
Theme = Bubble
Comment = Image Routeurs
Type Derniere Image = Date
Attributes = Equipment ,Client, Derniere Image
List display = Equipment ,Client,Derniere Image
Preset Author = $short_name
Locked Attributes = Author
Page Title = ELOG - $Equipment
Sort Attributes = Equipment
Reverse sort = 0
Quick filter = Equipment, Client
Reverse sort = 1
Sort Attributes = Equipment
Summary lines = 1
Display mode = Summary
What is wrong with my configuration ?
Thanks for answer. |
| Attachment 1: elog.gif
|
|
| Attachment 2: elog2.gif
|
|
|
1553
|
Thu Dec 15 17:33:39 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Other | Windows | 2.6.0 | Re: Bad date format. |
| Alex H wrote: |
[Liste]
Type Dernière image = Date
[Image Routeurs]
Type Derniere Image = Date
|
Maybe your additional accent. The attribute list contains Derniere Image, but in your first logbook you say Type Dernière image with accent grave, so this are not the same words. |
|
1554
|
Mon Dec 19 09:41:08 2005 |
 | Alex H | alex@synergie-inf.com | Other | Windows | 2.6.0 | Re: Bad date format. |
| Stefan Ritt wrote: |
| Alex H wrote: |
[Liste]
Type Dernière image = Date
[Image Routeurs]
Type Derniere Image = Date
|
Maybe your additional accent. The attribute list contains Derniere Image, but in your first logbook you say Type Dernière image with accent grave, so this are not the same words. |
It's work now !
Thanks  ! |
|