Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 762 of 807  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  510   Thu Mar 25 18:20:15 2004 Warning Charles DuncanCharles@YorkU.CAQuestionLinux2.5.1-1 Debian LinuxRe: Elog Utility
> I am trying to use the Elog Utility to import a few thousand entries. So 
> far I have run into a few problems.
> 
> a) Cannot get elog utility to speak to elogd on port 8080. Even though I 
> use the -p 8080 option with elog. I was able to get it to work when I 
> moved my server to port 80.
> 
> b) I cannot get elog to work with and attributes or logbooks that contain 
> spaces. Please refer the the following example:
> 
> elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac 
> Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP 
> Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
> a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor 
> Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard 
> Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY: 
> Change Description"
> 
> This line executes fine. Except only Hostname, Manufacturer, Memory and 
> text are populated in the record. All the rest of the fields are blank.
> 
> c) the only way I was able to get the transaction to work was by reducing 
> the size of the log book to a single word (ie WSC2).
> 
> Do I have to reduce all my attributes to single words? Or am I missing 
> something simple to use as a delimiter for entry??
> 
> Thanks in advance
> 
> -Charles-

As a followup, this occurs not only in the Linux environment, but also under 
Windows XP. I get the same results...

-Charles-
  513   Sat Mar 27 18:52:16 2004 Warning Charles DuncanCharles@YorkU.CAQuestionLinux2.5.1-1 Debian LinuxRe: Elog Utility
> > a) Cannot get elog utility to speak to elogd on port 8080. Even though I 
> > use the -p 8080 option with elog. I was able to get it to work when I 
> > moved my server to port 80.
> 
> That problem has been fixed in revision 1.16 from Feb. 19th. Please get the
> newest version from release 2.5.2 issued today.
> 
> > b) I cannot get elog to work with and attributes or logbooks that contain 
> > spaces. Please refer the the following example:
> > 
> > elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac 
> > Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP 
> > Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
> > a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor 
> > Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard 
> > Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY: 
> > Change Description"
> 
> There was also some bug which has been fixed, plus you need following syntax:
> 
> elog -h ... -p 8080 -a "Station Number=CC001" ...
> 
> note the "" are around the whole attribute=value string, not only the attribute.

Steve,

Thank you for the updates!!!

everything works great... -p 8080 and all my attribs get set. 

The only part that does not work is -l "Log Book" the -l variable has to stay as 
one word. If I submit 2 words (in quotes) it only looks for a logbook of the first 
word and fails.

-Charles-
  515   Mon Mar 29 17:44:32 2004 Idea Charles DuncanCharles@YorkU.CAInfoAll2.5.2Re: New ELOG version with XML and CSV import/export
> Version 2.5.2 of ELOG has been released today. It contains CSV (comma
> separated values) import and export, as well as XML export (through the
> "Find" page). Since these features are new, I would appreciate some feedback
> on how this works in different environments. I made sure I can import data
> from Excel and Outlook (like my address book), but I have no experience with
> other applications.
> 
> As with the XML export, I'm not sure if the format I chose is a good one.
> People working more with XML should tell me if it should be changed.

I was able to find the export feature under find. Could you let me know where 
the import feature is? Or how I turn it on.

-Charles-
  1190   Sat Jun 11 02:29:01 2005 Question Charles DuncanCharles@YorkU.CAQuestionLinux Moving eLog from Server to Server...
I am moving my eLog system from one server to another.

I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?

The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...

Do I have to do some sort of conversion to move the pwd file from one server to another?

Or should I try using the sync command for the move? does sync also move the pwd file??

-Charles-
  1192   Mon Jun 13 18:45:45 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux Re: Moving eLog from Server to Server...

Quote:

Stefan Ritt wrote:

Charles Duncan wrote:
I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file??


Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it.


I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.

I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).

Are the password files not compatible between the 2 versions?

All my logbook entries appear to be there in full.

btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view.
  1193   Wed Jun 15 00:20:56 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux Re: Moving eLog from Server to Server...

Charles Duncan wrote:

Quote:

Stefan Ritt wrote:

Charles Duncan wrote:
I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file??


Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it.


I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.

I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).

Are the password files not compatible between the 2 versions?

All my logbook entries appear to be there in full.

btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view.


I wanted to add that the elog.pwd file did transfer when I used the "elogd -C <url>" command, but the passwords and accounts were not recognized. Also I edited my elog.conf file to contain the absolute address of my elog.pwd file.
  1194   Wed Jun 15 18:59:23 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux Re: Moving eLog from Server to Server...

Charles Duncan wrote:

Charles Duncan wrote:

Quote:

Stefan Ritt wrote:

Charles Duncan wrote:
I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file??


Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it.


I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.

I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).

Are the password files not compatible between the 2 versions?

All my logbook entries appear to be there in full.

btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view.


I wanted to add that the elog.pwd file did transfer when I used the "elogd -C <url>" command, but the passwords and accounts were not recognized. Also I edited my elog.conf file to contain the absolute address of my elog.pwd file.


I fixed it... I merely backed out of the XML format of the elog.pwd and reverted to common passwd format. Everyone can log in now... great product.
  1472   Tue Oct 18 18:13:57 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux2.6.0beta2Re: Error message: "Attachment #6 of entry #0 not found"
> > This is the URL after logging in: 
> > http://localhost:8081/debian/17?cmd=List&mode=summary 
> >  
> > When i click on one of the entrys, i get thar error message. 
> > URL: http://localhost:8081/debian/debian/17 
> >  
> > It says: "Attachment #17 of entry #0 not found 
> >   Please use your browser's back button to go back" 
> 
> Ah, now I recognize the error. Please update to the newest beta5, it's fixed there.
> 
> - Stefan

Stefan,

where can we get Beta5, I can only find Beta4 on all the download locations.

-Charles-
ELOG V3.1.5-3fb85fa6