ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 183 of 238

Not logged in

Find | Login | Help

Full | Summary | Threaded | Collapse | Expand

1898 Entries

Goto page Previous 1, 2, 3 ... 182, 183, 184 ... 236, 237, 238 Next

Problems with ELOG and Internet Explorer, posted by Elaine Cristina Franchini dos Anjos on Fri Nov 4 16:51:32 2005

Hi,

We are facing a problem when using the Internet Explorer browser to edit
logbooks entries. The error occurs when we use the preview option.

After this, the connection becomes slow to display the preview and returns
"Server Not Found - Page cannot be displayed" or "Internal Server error" as result.
If we try to turn back to the edit page the browser retuns
"This page has been expired".

It happens at any time even we edit simple entries in Internet Explorer,
but never occurs in other browsers.

Software versions that are running :

Elog version 2.6.0-beta
Fedora Core release 1 (Yarrow)
Apache/2.0.54 (Unix) mod_ssl/2.0.54 OpenSSL/0.9.7g
(Elog is running under apache proxy)

Is there any bug report about this or there is something else
that I need to configure ?

Thanks in advance.

Elaine

Re: Problems with ELOG and Internet Explorer, posted by Stefan Ritt on Mon Nov 7 09:16:47 2005

Elaine Cristina Franchini dos Anjos wrote:

We are facing a problem when using the Internet Explorer browser to edit
logbooks entries. The error occurs when we use the preview option.

After this, the connection becomes slow to display the preview and returns
"Server Not Found - Page cannot be displayed" or "Internal Server error" as result.
If we try to turn back to the edit page the browser retuns
"This page has been expired".

It happens at any time even we edit simple entries in Internet Explorer,
but never occurs in other browsers.

Software versions that are running :

Elog version 2.6.0-beta
Fedora Core release 1 (Yarrow)
Apache/2.0.54 (Unix) mod_ssl/2.0.54 OpenSSL/0.9.7g
(Elog is running under apache proxy)

Is there any bug report about this or there is something else
that I need to configure ?

I tried on this forum with Internet Explorer 6.0 and could not reproduce the problem, and I never heared anybody else mentioning this problem. Can you reproduce the problem on the forum?

Re: Problems with ELOG and Internet Explorer, posted by Elaine Cristina Franchini dos Anjos on Mon Nov 7 18:55:57 2005

Hi Stefan,

Quote:

I tried on this forum with Internet Explorer 6.0 and could not reproduce the problem, and I never heared anybody else mentioning this problem. Can you reproduce the problem on the forum

I couldn't reproduce the problem in this forum too, and I'm using Internet Explorer to edit this entry now... :-D

I did some new tests and at this time I tried to submit new entries using the ELOG default port
without proxy, because I realized that this Forum doesn't use https (maybe uses proxy).

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.

Do you know problems like this ?
Is there anybody else using ELOG under https ?

My proxy configuration :

Quote:

1) http (default port 80):

# Redirect to ELOG - Logbook

Redirect permanent /elog https://antares.ccuec.unicamp.br:9696

2) https (I need to use other different port number) :

<VirtualHost 143.106.80.30:9696>
# Here be standard configuration for the Virtual Host
ServerName antares.ccuec.unicamp.br:9696
ServerAdmin suporte@ccuec.unicamp.br

# This be the path to the elog directory
# (This didn't seem to make any difference, but it be a good
# idea nonetheless)
DocumentRoot "/www/elog"

# Here be the setup for the SSL component of the Virtual Host
SSLEngine On
SSLCertificateFile /www/apache/conf/ssl.crt/server.crt
SSLCertificateKeyFile /www/apache/conf/ssl.key/server.key

# Here be the setup options for the Proxy module
ProxyRequests Off
ProxyPreserveHost On

# This be the root of the new Virtual Host, and it should be
# redirected to the port the elogd server is listening to
# (8081 on our poop deck).
<Location />
<Location />
ProxyPass http://antares.ccuec.unicamp.br:8081/
ProxyPassReverse http://antares.ccuec.unicamp.br:8081/
SSLRequireSSL
</Location>

ErrorLog /www/apache/logs/error_log
TransferLog /www/apache/logs/access_log </VirtualHost>

Thanks in advance.

Elaine

Re: Problems with ELOG and Internet Explorer, posted by Stefan Ritt on Tue Nov 8 08:17:22 2005

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).

Re: Problems with ELOG and Internet Explorer, posted by Elaine Cristina Franchini dos Anjos on Fri Jan 13 18:43:08 2006

Hi Stefan,

I couldn't solve this problem yet...
I have been tried a lot of configurations, but our Elog doens't work well in IE with https Crying

It works very well to read, list, find the messages, delete, and so on...
But all users have problems with edit and preview commands when they are using IE + https.

When we use Elog in IE without https, everything works fine. ?)

We are using :
httpd-2.0.54
Fedora Core release 1 (Yarrow)
elog-2.6.0

The redirect directive in httpd.conf:

<VirtualHost xxx.xxx.xx.xx>
    ServerAdmin our.email.address
    DocumentRoot /www/apache/htdocs
    ServerName our.server.name

    # Rules to new  elog 2.6.0 
    Redirect / https://our.server.name:9898

    ErrorLog logs/error_log
    CustomLog logs/access_log common
</VirtualHost>

The proxy directives in ssl.conf:
(We used the http://midas.psi.ch/elogs/contributions/11 message like reference.
Thanks a lot for the contribution!!! Happy

)

<VirtualHost xxx.xxx.xx.xx:9898>
   # Here be standard configuration for the Virtual Host
   ServerName our.server.name:9898
   ServerAdmin our.email.address
   RequestHeader set Front-End-Https "On"

   # This be the path to the elog directory
   # (This didn't seem to make any difference, but it be a good
   #  idea nonetheless)
   DocumentRoot "/www/src/elog-2.6.0"

   # Here be the setup for the SSL component of the Virtual Host
   SSLEngine On
   SSLCertificateFile /www/apache/conf/ssl.crt/server.crt
   #SSLCertificateKeyFile /www/apache/conf/ssl.key/server.pem
   SSLCertificateKeyFile /www/apache/conf/ssl.key/server.key

   # Here be the setup options for the Proxy module
   ProxyRequests Off
   ProxyPreserveHost On

   # This be the root of the new Virtual Host, and it should be
   # redirected to the port the elogd server is listening to
   # (8082 on our poop deck).

   <Location />
        ProxyPass  http://our.server.name:8082/
        ProxyPassReverse  http://our.server.name:8082/
        SSLRequireSSL
   </Location>

   ErrorLog /www/apache/logs/error_log
   TransferLog /www/apache/logs/access_log
</VirtualHost>

And the URL is configured in elogd.cfg like your suggestion (Thanks ! Happy

)

URL = https://our.server.name:9898

The elgod.cfg is attached to this message to add more details about our configuration.

Thanks in advance.

Regards,

Elaine

Stefan Ritt wrote:

Elaine Cristina Franchini dos Anjos wrote:

Have a look at your URL = ... statement in elogd.cfg
It should probably read

URL = https://antares.ccuec.unicamp.br:9696

Re: Problems with ELOG and Internet Explorer, posted by Stefan Ritt on Wed Jan 18 13:31:32 2006

Have you tried another browser, like Firefox? Do you have the same problems with Firefox? Can you try the following:

Start elogd manually with the "-v" flag, like

elogd -c <your config path> -v -p 8080

and watch the output carefully. When you submit an entry, elogd does redirection. You will see that in the HTTP header you have an entry like

...
Location: https://...
...

This location is taken from the URL statement of your config file. If it's wrong (like if you mixed http:// and https://), your browser will try to load the page from a non-existion location.

Attribute substitution in email configuration, posted by Adam Blandford on Wed Jan 18 02:22:44 2006

In the logbook config file I am not able to use attribute substitution in the <string> tag for

Use Email Heading = <string>

Attribute substitution does work however for

Use Email Subject = <string>

e.g.

Use Email Subject = ELOG $logbook entry; $Category: $Subject

will result in an email subject of: "ELOG Forum entry; Bug Report; Attribute substitution in email configuration"

Use Email Heading = A new entry has been submitted by $long_name on $remote_host on $date

will result in an email heading of: "A new entry has been submitted by $long_name on $remote_host on $date"

Not sure if this functionality is intended or is a bug. An comment/feedback/suggestion would be appreciated.

Re: Attribute substitution in email configuration, posted by Stefan Ritt on Wed Jan 18 13:06:50 2006

Adam Blandford wrote:

Not sure if this functionality is intended or is a bug.

It was not implemented, however you call this Wink

I added that in the current SVN version, so it will be contained in the next release.

Email based on not attribute value, posted by Chris Warner on Tue Jan 17 14:09:17 2006

Is it possible to send an email if an attribute is not equal to a specific value?

For instance, I have a server logbook that several people are able to write to. There is one person that is ultimately responsible for this server. I would like to generate an email any time that someone other than the System Administrator creates a new entry.

Thanks,

Chris Warner

Re: Email based on not attribute value, posted by Stefan Ritt on Wed Jan 18 12:49:39 2006

Chris Warner wrote:

For instance, I have a server logbook that several people are able to write to. There is one person that is ultimately responsible for this server. I would like to generate an email any time that someone other than the System Administrator creates a new entry.

No, but there is a trick you can use. Put following into your config file:

Attributes = Author, ...
Preset Author = $long_name
Locked Attributes = Author
Options Author = Admin{1}, other{2}
{1}Suppress default = 1

Replace "Admin" with the name of the administrator. The "Author" field gets automatically set to the author name, and it's locked, so there will no be drop-down box which lets you select between "Admin" and "other". Now if the author is equal to "Admin", the condition {1} becomes true, and the "Supress default is executed. This check the "suppress email notificatio" box at the bottom, so normally no email gets sent from the administrator.

localhost definition problem, posted by Jason Koglin on Tue Jan 17 01:01:05 2006

I've been running elog on my laptop for about a year. I have had a problem several times now when I have had a bad crash of my computer that afterwards elog does not run correctly. The problem appears to be that "localhost" (e.g., http://localhost:8080/) gets changed to a domain name (http://sylvester.columbia.edu:8080/) which is not registered. I only want it to access this elog database locally on my machine and do not even want to set it up as a web server.

I freshly installed it and when I type in http://localhost:8080/ it sends me to http://localhost:8080/demo/ . If I click on the first and only entry it sends me to http://sylvester.columbia.edu:8080/demo/1 and an error occurs loading the page. However if I type in http://localhost:8080/demo/1 it brings up the first entry correctly, but with no formatting because presumably it is looking in the wrong place for the default theme.

How do I fix this since this time reinstalling and rebooting hasn't fixed the problem?

Thanks,

Jason.

Re: localhost definition problem, posted by Stefan Ritt on Wed Jan 18 12:37:19 2006

Hi Jason, how is going? Long time no hear!

What you need is following line in your config file:

URL = http://localhost:8080/

This is because elog does not know its "own" address, and therefore tries to figure this out over the network. Your laptop probably has the name "syslvester", and you run it inside columbia.edu, so it "thinks" it can reach itself via http://sylvester.columbioa.edu:8080. The URL statement above overrides this "guess".

Best regards,

Stefan

Problem selecting ports, posted by Chris Warner on Fri Jan 13 03:21:32 2006

I had problems getting elog to run on port 8080 (or many others). I have it installed on Redhat Enterprise Linux rel 4. The only way I was able to get it working was using port 80. I would like to run it on a different port if possible but I'm not sure what is wrong.

Any Ideas

Re: Problem selecting ports, posted by Chris Warner on Tue Jan 17 13:59:58 2006

Nevermind. this was an iptables issue.

Chris Warner wrote:

LDAP, posted by Carl Shirey on Thu Jan 12 16:53:30 2006

I know you want to make ELOG a stand alone program. But is there a way to still make a stand alone but have the option work with LDAP?
FYI
Elog works great we us it for our shift carryover and we have about 25 people useing it and I have heard no complants with it.
Thanks

Re: LDAP, posted by Stefan Ritt on Thu Jan 12 17:02:21 2006

Carl Shirey wrote:

I added your vote to the "PAM" authentication on the wishlist, since PAM contains an LDAP module.

Re: LDAP, posted by Chris Warner on Fri Jan 13 02:37:10 2006

Stefan Ritt wrote:

Carl Shirey wrote:

I added your vote to the "PAM" authentication on the wishlist, since PAM contains an LDAP module.

Please Add my vote too. I think that would be great.

Thread sort / display order, posted by Michael Husbyn on Tue Nov 22 17:38:24 2005

Is there a way to choose the display order in threaded mode.

Eg:

1 Test
2 Version 2.0 Testing 1
3 Version 2.5 Testing 2
4 Version 2.3 Testing 3

But the preferred sort order (not the ID) is something like this:
1 Test
2 Version 2.0 Testing 1
4 Version 2.3 Testing 3
3 Version 2.5 Testing 2

Example of parameter perhaps:
Thread order = Field1, $id

Or is this something too difficult to implement? Or already there?

Best regards
Michael Husbyn

Re: Thread sort / display order, posted by Stefan Ritt on Thu Jan 12 16:06:16 2006

Michael Husbyn wrote:

In summary mode, you can sort by clicking on a column header. You will then see something like

http://.../?sort=Field1

in the address bar. If you now switch to threaded display, this vanishes of course, but you can put a

Start page = ?sort=Field1

into your config file. Use sort for ascending order, rsort for descending order.

Page browsing links in Find mode broken, posted by Yoshio Imai on Wed Jan 11 15:54:28 2006

Hi!

We are having problems with the "Find" mode in the latest revision. When we used "Find" to search for specific texts, and the results span more than one page (say, 2 for example), the page links in the command bar on top point to the ELOG pages rather than the find result pages. This means that, when I click onto "Previous" from find result page 2 (which is the first page getting displayed), I get to logbook page 1 (entries 1 to 20) and not to the previous page of find results. I think this didn't happen in earlier versions. Could you check that? It also happens here in the Forum.

Thanks

Yoshio

Re: Page browsing links in Find mode broken, posted by Stefan Ritt on Wed Jan 11 21:06:06 2006

Thanks for reporting this bug, I fixed it in revision 1597.

Side effects from debugging, posted by Yoshio Imai on Thu Jan 12 11:32:19 2006

Stefan Ritt wrote:

Thanks for reporting this bug, I fixed it in revision 1597.

Thanks for your quick reaction! Unfortunately, there is one side effect. As far as I understand, you fixed the bug by preserving the command attributes

http://www.logbook.domain/logbook/pageN?command

when browsing with the Goto page links, so that when a filter is applied, it is still active upon page change. However, the same is true for all other commands, including the

?id=NNN

command which is active when clicking List from single entry view. If you click onto, e.g. Previous in this mode, the elogd has a conflict in that it is required to display one page and having to highlight an entry that resides on another.

http://www.logbook.domain/logbook/pageN?id=NNN

The highlighting supersedes, and the page browse links are effectively disabled. Is there a way to keep the bug fix but disable the side effects, e.g. selectively not preserving the

?id=NNN

upon page browsing? Maybe you could implement a "blacklist" of not-to-be-preserved commands, in case there are other problems like this one.

Thanks for the work (I saw the timestamp!)

Yoshio

Side effects from debugging, posted by Yoshio Imai on Thu Jan 12 11:38:13 2006

Addendum: in the Forum, I found a very strange effect: When deliberately highlighting an entry (http://midas.psi.ch/elogs/Forum/?id=1858), the Elog server no longer keeps the page partitioning, but displays ALL entries of the logbook. I don't know if these problems are related, but maybe you could check (we use the "Full" mode for the list view, in case that matters). I have tried to reproduce the problem with our logbook in threaded mode, but we don't seem to have this problem there.

Yoshio

Side effects from debugging, posted by Stefan Ritt on Thu Jan 12 15:50:51 2006

Both problems have been fixed in revision 1598.

Goto page Previous 1, 2, 3 ... 182, 183, 184 ... 236, 237, 238 Next

ELOG V3.1.5-3fb85fa6