Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 189 of 238  Not logged in ELOG logo
icon8.gif   Cannot submit admin password while logbook is named in Chinese, posted by Exaos Lee on Sun Oct 9 20:43:31 2005 
As the title.
    icon5.gif   Re: Cannot submit admin password while logbook is named in Chinese, posted by Stefan Ritt on Mon Oct 10 14:01:14 2005 

Exaos Lee wrote:
As the title.


There is no possibility to change an admin password. You probably mean that you logged in as admin and cannot change your own password, is that right? Do you use user level access via "password file = ..."? What is your elogd.cfg? I tried to switch language to German and I can change my own password via the config page.
       icon2.gif   Re: Cannot submit admin password while logbook is named in Chinese, posted by Exaos Lee on Mon Oct 10 19:33:05 2005 

Stefan Ritt wrote:

Exaos Lee wrote:
As the title.


There is no possibility to change an admin password. You probably mean that you logged in as admin and cannot change your own password, is that right? Do you use user level access via "password file = ..."? What is your elogd.cfg? I tried to switch language to German and I can change my own password via the config page.


Sorry for my poor English. The case is like this: When I set an admin password for my logbook which is named in Chinese, I cannot open the config page while the password is correct. It seems that the logbook named in Chinese cannot recieve the password submitted. If the logbook is named other than Chinese, everything is OK. I will repeat the problem and describe it more exactly.
          icon2.gif   Re: Cannot submit admin password while logbook is named in Chinese, posted by Stefan Ritt on Tue Oct 11 09:24:12 2005 

Exaos Lee wrote:
Sorry for my poor English. The case is like this: When I set an admin password for my logbook which is named in Chinese, I cannot open the config page while the password is correct. It seems that the logbook named in Chinese cannot recieve the password submitted. If the logbook is named other than Chinese, everything is OK. I will repeat the problem and describe it more exactly.


A way around that problem would be to use user level access (via the Password file = ... and Admin user = ... settings). Can you try if that works under a Chinese logbook?
icon12.gif   Some spell mistakes, posted by Exaos Lee on Sun Oct 9 20:49:41 2005 
I find some new strings from the warnings like this:

Quote:
Language error: string "HelpELCode" not found for language "chinese"


I have added these new string to the languages files in Chinese. I think:
"Enter name of hypelink" should be "Enter name of hyperlink".
    icon2.gif   Re: Some spell mistakes, posted by Stefan Ritt on Mon Oct 10 14:09:49 2005 

Exaos Lee wrote:
I find some new strings from the warnings like this:

Quote:
Language error: string "HelpELCode" not found for language "chinese"


I have added these new string to the languages files in Chinese. I think:
"Enter name of hypelink" should be "Enter name of hyperlink".


Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much.
       icon2.gif   Re: Some spell mistakes, posted by Exaos Lee on Mon Oct 10 19:26:35 2005 

Quote:
Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much.

Sorry. Wink I will mail you first next time.
icon4.gif   Install error on MacOS X, posted by Exaos Lee on Mon Oct 10 19:22:51 2005 makefile_modified.tgz
Executing "make" on MacOS X is OK, but "make install" failed due to the following error:
/usr/bin/install -m 0755 -d /usr/local/bin /usr/local/sbin /usr/local/man/man1/ /usr/local/man/man8/
/usr/bin/install -m 0755 -o bin -g bin elog elconv /usr/local/bin
install: bin: Invalid argument
make: *** [install] Error 67

The reason is that the account "bin" and group "bin" are missing on MacOS X. I also found that the following lines in "Makefile" doesn't work:
ifeq ($(OSTYPE),darwin)
CC = cc
endif

I have fixed this problem. The diff of Makefile as following:
diff Makefile.darwin Makefile.origin
====================================
24,25d23
< BINOWNER = bin
< BINGROUP = bin
30,31d27
< OSTYPE = $(shell uname)
<
40,43d35
< ifeq ($(OSTYPE),Darwin)
< OSTYPE=darwin
< endif
<
46,47d37
< BINOWNER = root
< BINGROUP = admin
89,90c79,80
<       $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elog elconv $(DESTDIR)
<       $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elogd $(SDESTDIR)
---
>       $(INSTALL) -m 0755 -o bin -g bin elog elconv $(DESTDIR)
>       $(INSTALL) -m 0755 -o bin -g bin elogd $(SDESTDIR)


The modified Makefiles have been attached.
icon5.gif   Display Attribute no longer works in Beta 5?, posted by Ulrich Trüssel on Fri Oct 7 08:53:00 2005 Display_Attribute_with_260-b2.jpgDisplay_Attribute_with_260-b5.jpgelogd.cfg
Just changed from Beta 2 to Beta 5:

I'm using Display Attribut = [elog:$logbook/$message id] as a reference link for other entries (ex.: Display Referenz = [elog:$logbook/$message id]). also see the attached elogd.cfg file.

With Beta 2 (not testet with Beta 3 or 4!) this worked very well -> see attached Display Attribute with 260-b2.jpg file.

With Beta 5 is seems no longer to work -> see attached Display Attribute with 260-b5.jpg file.

ANy ideee what's wrong in my elogd.cfg??? Thanks!
    icon2.gif   Re: Display Attribute no longer works in Beta 5?, posted by Stefan Ritt on Mon Oct 10 13:57:20 2005 

Ulrich Trüssel wrote:
I'm using Display Attribut = [elog:$logbook/$message id] as a reference link for other entries (ex.: Display Referenz = [elog:$logbook/$message id]). also see the attached elogd.cfg file.


This option has been changed on July 25th from "Display <attribute>" to "Change <attribute>" which is a more appropriate expression. The documentation has also been updated.
icon1.gif   The Chinese Language,Demo Configuration and Help Files, posted by Exaos Lee on Sun Oct 9 20:18:23 2005 chinese_trans.tar.gz
Hi, Stefan,
The days from Oct.1~7 are our Nation Day's vacation, so I delayed the translation to Chinese. I just finished these files today:

  1. eloglang.zh_CN-GB2312 : This is for simplified Chinese using GB2312 encoding.
  2. eloglang.zh_CN-UTF-8 : This is for simplified Chinese using UTF-8 encoding.
  3. eloghelp.zh-CN.html : Help file for elog in simplified Chinese.
  4. elcode_zh-CN.html : The help file for ELCode in simplified Chinese.
  5. elogd-zh_CN-GB2312.cfg : Demo configuration file for simplified Chinese with GB2312 encoding.
  6. elogd-zh_CN-UTF-8.cfg : Demo configuration file for simplified Chinese with UTF-8 encoding.

I have to provide the language files in different encodings because the elogd cannot creat new logbook file named in Chinese with GB2312 encoding under MacOS X. The default charset under MacOS X is UTF-16, and elogd works with UTF-8 while processing Chinese contents and logbooks named in Chinese.

I want to make elogd display the date in Chinese format. Please tell me howto.
Thanks.
    icon2.gif   Re: The Chinese Language,Demo Configuration and Help Files, posted by Stefan Ritt on Mon Oct 10 12:53:46 2005 

Exaos Lee wrote:
I want to make elogd display the date in Chinese format. Please tell me howto.


Thank you for the files.

If you specify

Language = zh_CN

Then elogd looks for a file "eloglang.zh_CN" for the translation, for a file "eloghelp_zh.html"
for the help, and does a

setlocale("zh_CN");

to switch to Chinese date format. To retrieve the date, elogd calls strftime("%x");
icon8.gif   "Error: Cannot find hostname", posted by Exaos Lee on Sun Oct 9 20:39:50 2005 
I usually access hosts in LAN with their IPs. But elogd seems to prefer hostnames to IPs. I cannot ask each one to add the hostname to their system config file while they visit my host. I encounter several problems which seems to be related to the hostname resolution:
  • I can visit remote elog service through IP and port, but cannot submit entry and cannot open the config page remotely. For example, my powerbook's name is "exaos-pb-12" and its IP is 10.10.2.96. I run elogd on my PB and try to access it through URL http://10.10.2.96:8080/ on host 10.10.2.99. While I submit a new entry or open the config page, my firefox alway blames: "exaos-pb-12.local could not be found. Please check the name and try again."
  • Sometimes, all the images, colors are missing. It looks like that my firefox cannot find the correct URL of these images or CSS files. It might be the same problem of "cannot find hostname".
    icon2.gif   Re: "Error: Cannot find hostname", posted by Stefan Ritt on Mon Oct 10 08:03:57 2005 

Exaos Lee wrote:
I usually access hosts in LAN with their IPs. But elogd seems to prefer hostnames to IPs. I cannot ask each one to add the hostname to their system config file while they visit my host. I encounter several problems which seems to be related to the hostname resolution:
  • I can visit remote elog service through IP and port, but cannot submit entry and cannot open the config page remotely. For example, my powerbook's name is "exaos-pb-12" and its IP is 10.10.2.96. I run elogd on my PB and try to access it through URL http://10.10.2.96:8080/ on host 10.10.2.99. While I submit a new entry or open the config page, my firefox alway blames: "exaos-pb-12.local could not be found. Please check the name and try again."
  • Sometimes, all the images, colors are missing. It looks like that my firefox cannot find the correct URL of these images or CSS files. It might be the same problem of "cannot find hostname".


In such a situation you describe it might help to use

URL = http://10.10.2.96:8080/

in the configuration file. This way elogd uses also IP numbers for redirection. Please let me know if that works.
       icon2.gif   Re: "Error: Cannot find hostname", posted by Exaos Lee on Mon Oct 10 10:52:02 2005 
Yes, the "URL" works. Thanks!
icon3.gif   ELOG repository moved from CVS to Subversion, posted by Stefan Ritt on Fri Oct 7 17:18:32 2005 
The elog repository has been moved from CVS to Subversion for various reasons. Those people who accessed the CVS repository in the past now have to do it in one of two different ways:
  • Use the new ViewCVS gateway. This gateway now can also directly produce tarballs for the current repository snapshot
  • Use anonymous Subversion access:

    svn checkout svn+ssh://svn@savannah.psi.ch/afs/psi.ch/project/meg/svn/elog/trunk elog
    svn@midas.psi.ch's password: svn
    (you might have to enter the password several times...)
    svn checkout svn+ssh://svn@savannah.psi.ch/afs/psi.ch/project/meg/svn/mxml/trunk mxml
    svn@midas.psi.ch's password: svn
    (you might have to enter the password several times...)
If there is any problem accessing the new repository, please let me know.
    icon2.gif   Re: ELOG repository moved from CVS to Subversion, posted by Exaos Lee on Sat Oct 8 05:08:40 2005 
Hi, Stefan,
I cannot checkout due to the following error:
------------
$ svn checkout svn+ssh://svn@savannah.psi.ch:/afs/psi.ch/project/meg/svn/elog/trunk elog
ssh: savannah.psi.ch:: Name or service not known
svn: Connection closed unexpectedly
------------

It seems that my PC cannot find the host savannah.psi.ch within CIAE. Maybe it's the problem of our DNS server. Anyway, what is the IP of savannah?
       icon2.gif   Re: ELOG repository moved from CVS to Subversion, posted by Stefan Ritt on Sat Oct 8 08:44:22 2005 

Exaos Lee wrote:
Hi, Stefan,
I cannot checkout due to the following error:
------------
$ svn checkout svn+ssh://svn@savannah.psi.ch:/afs/psi.ch/project/meg/svn/elog/trunk elog
ssh: savannah.psi.ch:: Name or service not known
svn: Connection closed unexpectedly
------------

It seems that my PC cannot find the host savannah.psi.ch within CIAE. Maybe it's the problem of our DNS server. Anyway, what is the IP of savannah?


Sorry, was my mistake. In the command you have to use savannah.psi.ch, not savannah.psi.ch: (with the colon). So the full command is

$ svn checkout svn+ssh://svn@savannah.psi.ch/afs/psi.ch/project/meg/svn/elog/trunk elog
icon1.gif   error when searching for POST, posted by Guenter Nowak on Mon Sep 26 11:03:52 2005 
is this an elog bug?
calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elogs/Linux Demo/.

Reason: Error reading from remote server



--------------------------------------------------------------------------------

Apache/2.0.46 (Red Hat) Server at midas.psi.ch Port 80


doing the same thing on my elog installation (ELOG V2.5.9-2) gives the error

Die Seite kann nicht angezeigt werden.
Die gewünschte Seite ist zurzeit nicht verfügbar. Möglicherweise sind technische Schwierigkeiten aufgetreten oder Sie sollten die Browsereinstellungen überprüfen.

--------------------------------------------------------------------------------

Versuchen Sie Folgendes:

... (some text skipped, guenter)

Fehler: Server oder DNS kann nicht gefunden werden
Internet Explorer

if if dont type all letters in uppercase no problem occurs

thanks
guneter
    icon2.gif   Re: error when searching for POST, posted by Stefan Ritt on Wed Oct 5 13:07:51 2005 

Guenter Nowak wrote:
calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error

Proxy Error


This bug has been fixed in the current CVS version.
ELOG V3.1.5-3fb85fa6