Re: New ELOG version with XML and CSV import/export, posted by Charles Duncan on Mon Mar 29 17:44:32 2004
|
> 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- |
Moving eLog from Server to Server..., posted by Charles Duncan on Sat Jun 11 02:29:01 2005
|
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- |
Re: Moving eLog from Server to Server..., posted by Charles Duncan on Mon Jun 13 18:45:45 2005
|
| 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. |
|
Re: Moving eLog from Server to Server..., posted by Charles Duncan on Wed Jun 15 00:20:56 2005
|
| 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. |
|
Re: Moving eLog from Server to Server..., posted by Charles Duncan on Wed Jun 15 18:59:23 2005
|
| 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. |
|
Re: Error message: "Attachment #6 of entry #0 not found", posted by Charles Duncan on Tue Oct 18 18:13:57 2005
|
> > 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- |
|
Re: Error message: "Attachment #6 of entry #0 not found", posted by Charles Duncan on Wed Oct 19 15:44:07 2005
|
> > > 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-
I downloaded the source from the new web site.
-Charles- |
Error Message in HTML or Java Script alert, posted by Carsten Elftmann on Mon Oct 13 11:42:07 2008
|
Hello,
I have there a problem with the error message at required attributes.
I have two logbooks with identical settings,
in one the errror message appears as Javascript Alert,
in the other one as html-page, and after using the back button the entered text disapear.
Same I have in this forum.
I restart the Server, and tested it in one Firefox session.
Any idea?
Thanks
Carsten |
|