Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 18 of 41  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
Category:Info
ID Date Icon Author Author Email Category OS ELOG Version Subject
  67099   Tue Aug 2 21:36:20 2011 Reply Alan Grantnetman311@mts.netInfoAll2.9.0Re: Elog client usage

Andreas Luedeke wrote:

Alan Grant wrote:

Andreas Luedeke wrote:

Alan Grant wrote:

What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option). [...]

[...] The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc

[...] I typed the following, observing case sensitivity, then press enter and at this point it just hangs:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11"
You wrote you want to upload a text file, then you need to add at the end "-m <file>". E.g. if the text-file is named "C:text.txt", then write:

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt
The "-n 1" is just to tell elog to upload plain text. If you do not specify "-m <file>" then it expects input from a pipe and therefore hangs. If you don't know what "input from a pipe" means then ALWAYS use the "-m <file>" option.
 
PS: if "Ticket date" is of the format "date" then it is sensitive to the formatting of the date string. "Jul26/11" is likely not a legal date format. Better do not specify it for the first test. Write instead:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt
PPS: do you really use a sub-directory "elog" instead of the default location "logbooks" for your ELOG logbook files? If not, then leave out this option, too.
elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt

 Andreas, thank you very much. I was able to get the stand alone function working fine on my site, including a number of add'l attributes and options (SSL, etc).

 

  67097   Wed Jul 27 04:36:40 2011 Cool Andreas Luedekeandreas.luedeke@psi.chInfoAll2.9.0Re: Elog client usage

Alan Grant wrote:

Andreas Luedeke wrote:

Alan Grant wrote:

What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option). [...]

[...] The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc

[...] I typed the following, observing case sensitivity, then press enter and at this point it just hangs:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11"
You wrote you want to upload a text file, then you need to add at the end "-m <file>". E.g. if the text-file is named "C:text.txt", then write:

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt
The "-n 1" is just to tell elog to upload plain text. If you do not specify "-m <file>" then it expects input from a pipe and therefore hangs. If you don't know what "input from a pipe" means then ALWAYS use the "-m <file>" option.
 
PS: if "Ticket date" is of the format "date" then it is sensitive to the formatting of the date string. "Jul26/11" is likely not a legal date format. Better do not specify it for the first test. Write instead:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt
PPS: do you really use a sub-directory "elog" instead of the default location "logbooks" for your ELOG logbook files? If not, then leave out this option, too.
elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt
  67096   Tue Jul 26 21:50:05 2011 Cool Alan Grantnetman311@mts.netInfoAll2.9.0Re: Elog client usage

Andreas Luedeke wrote:

Alan Grant wrote:

I have searched the Elog forum and docs at length for actual examples of how to use the Elog client and I apologize if I missed it somehwere but could someone please provide some actual examples of how the parmeters are used? I haven't had much success setting it up just going by the Elog command syntax quide.

What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option).

Also, I saw a Perl script contribution somewhere on the site which appears to offer the same functionality as the above util. Just wondering why there would be two methods, and which might be the best for me to use? Thank you.

I suppose you have your demon "elogd" running and you can connect to your logbook via the web interface?
Then you can use the "elog" command to upload a text file as one entry.
If you want to split the text file to one-entry-per-line, you need to write a batch script to do that.
The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc
 
The command line for "elog" has to define all "Required attributes" with "-a ..."
 
elog -h <host> -p <port> -l <logbook> -u <user> <password> -a <attribute>=<value> -n 1 -m <text-file>
 
<port> can be omitted if port 80 is used, "-u <user> <password>" can be omitted if anonymous entry creation is allowed.
Here's an example to write to the demo logbook at midas (local text file /tmp/hello.txt contains "hello world")
elog -h midas.psi.ch -l Linux+Demo -d elogs -a Author=nobody -a Type=Other -a Category=test -a "Subject=hello" -m /tmp/hello.txt

I hope this helps.

PS: please never refer to a location as "somewhere on the site".

 It seems straight forward enough but I must be missing something in my elog command string. I run the client utiltiy but it always hangs after pressing Enter from the cmd window. It could be the way I specifying the host or subdir but I'm not sure. I tried multiple variations.

Some more info: For the prototype I'm just running Elog locally. I installed it to my XP in "c:\program files\elog". I verified tht elogd process is running. With the Elog page already open (ref my attached cfg file) I typed the following, observing case sensitivity, then press enter and at this point it just hangs:

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11"

Note since all attributes are optional I only included "Ticket Date" for now until I can get this cmd working.

Please bear with me as I don't have an extensive technical background but I would be very grateful for any help as it's for a project at work. Soonest response would be greatly appreciated.

Thanks.

Alan

 

 

 

Attachment 1: elogd.cfg
[global]
port = 8080
SMTP host = citygw
Display mode = summary
Self register = 1



[Tartan Tow Log]
Theme = default
Entries per page = 30
List Menu commands = New, Find, <a href=?cmd=Find>Print</a>
Menu commands = List, Edit, Duplicate, Delete, Back
Attributes = Ticket Date, Ticket Time, System Rec'd Date, System Rec'd Time, Ticket, Plate, Make, VIN, Pick Up Location, Officer, Violation, Work Type, Pick Up Date, Pick Up Time, Tow Unit, Drop Date, Drop Time, Drop Location, GOA, Cancel
List Display = ID, Ticket Date, Ticket Time, Ticket, Plate, VIN, Pick Up Location, Work Type, Pick Up Time, Drop Time, Drop Location, GOA
Summary lines = 0
Options Work Type = Rush Hour AM, Rush Hour PM, Street Work, Snow Route, ROPB, General
Options GOA = boolean
Options Cancel = boolean
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, ID, Ticket Date, Ticket, Plate, VIN, Pick Up Location, Work Type, Drop Location, Subtext


  67095   Fri Jul 22 10:31:27 2011 Cool Andreas Luedekeandreas.luedeke@psi.chInfoAll2.9.0Re: Elog client usage

Alan Grant wrote:

I have searched the Elog forum and docs at length for actual examples of how to use the Elog client and I apologize if I missed it somehwere but could someone please provide some actual examples of how the parmeters are used? I haven't had much success setting it up just going by the Elog command syntax quide.

What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option).

Also, I saw a Perl script contribution somewhere on the site which appears to offer the same functionality as the above util. Just wondering why there would be two methods, and which might be the best for me to use? Thank you.

I suppose you have your demon "elogd" running and you can connect to your logbook via the web interface?
Then you can use the "elog" command to upload a text file as one entry.
If you want to split the text file to one-entry-per-line, you need to write a batch script to do that.
The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc
 
The command line for "elog" has to define all "Required attributes" with "-a ..."
 
elog -h <host> -p <port> -l <logbook> -u <user> <password> -a <attribute>=<value> -n 1 -m <text-file>
 
<port> can be omitted if port 80 is used, "-u <user> <password>" can be omitted if anonymous entry creation is allowed.
Here's an example to write to the demo logbook at midas (local text file /tmp/hello.txt contains "hello world")
elog -h midas.psi.ch -l Linux+Demo -d elogs -a Author=nobody -a Type=Other -a Category=test -a "Subject=hello" -m /tmp/hello.txt

I hope this helps.

PS: please never refer to a location as "somewhere on the site".
  67081   Fri Jun 3 12:06:20 2011 Smile Andreas Luedekeandreas.luedeke@psi.chInfoLinux2.9.0-2414Re: elogd crashes when running mirror cron with SSL and KRB5
> When I run a mirror server and both logbooks using SSL/KRB5 then the cron job causes a segmentation fault.
>
> I haven't tried to check it with a simple configuration yet.
> My set-up: two elogd on same server, one running "german" on port 444, the other "english" on port 445.
> Both are behind an apache webserver configured reverse proxy, to hide the ports for external access.
> I'll try to reproduce the fault with a "minimal configuration" soon and report again.
>

I've tried to test a simpler configuration on my local PC but failed:
all simple set-ups I've tried worked fine.

I found that the mirror cron synchronization works fine in my production set-up when I remove the line:
Mirror user = luedeke

But I can have this line in my simple test set-up and it still works fine.
Anyway: bugs closed for me.
  67080   Thu Jun 2 21:28:19 2011 Reply Stefan Rittstefan.ritt@psi.chInfoWindows2.xRe: Is there maximum number of entries?

Hung Dao wrote:

Does anyone know whether ELOG has limit number of entries or it can create new entries as many as it can go?  Thanks.

The number of entries is not limited. But if there are very many entries, searching can get a bit slow. We have installations with ~100'000 entries and they work still fine. 

  67072   Tue May 31 17:38:57 2011 Question Hung Daohungtdao@yahoo.comInfoWindows2.xIs there maximum number of entries?

Does anyone know whether ELOG has limit number of entries or it can create new entries as many as it can go?  Thanks.

  67055   Sat Apr 23 14:32:38 2011 Reply PelleSorry, found it InfoLinux2,3.8Re: elog2sql - a script to convert elog logbooks to a MySQL database

> > I know this thread was started 2003 but if anyone have this MySQL export script please attach it to this thread. > > Thanks, > > Pelle

 

Sorry, found it in the contribution list https://midas.psi.ch/elogs/Contributions/5

ELOG V3.1.5-3fb85fa6