| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65734
|
Mon Feb 11 22:33:37 2008 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
| Stefan Ritt wrote: |
|
| Richard Ecclestone wrote: |
|
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ?
|
I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string. |
|
65737
|
Tue Feb 12 11:42:01 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
| Richard Ecclestone wrote: |
|
Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?
Where do we get version 2041 ?
|
The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code. |
|
65741
|
Fri Feb 15 06:59:52 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.2 | Re: move mxml code into elog's src directory |
| Jeff Stoner wrote: |
|
The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:
MXMLDIR = src/mxml
Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.
|
From your point of view that request is reasonable, but the reason of having mxml in a separate top level directory is that I use it in many different projects. If I would keep a copy of mxml in each project, I would have to update all of them manually if there is a bug. On the other hand the code of mxml changes very seldom. If you look at the history, it got ~5 changes last year, while elog itself had hundreds. And since I do not change the API, a bugfix in mxml should be to the benefit of all elog versions. It is like with other projects which depend on a number of packages. Like if you install Apache for example, you need a certain version of OpenSLL, a certain version of libcrypt, and so on. So think of mxml like another package you have to combine with elog. |
|
65745
|
Mon Feb 18 07:03:29 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | | Re: error "Cannot retrieve host name: No error" using command line in Windows |
| Dan Gawarecki wrote: |
|
I automatically install software on 3 machines in our lab, and at the end of the process, use eLOG to record relevant information for each machine (all running Windows XP) via the command line program elog.exe. 2 of the machines log their info correctly, but on third machine, I get the following error:
Cannot retrieve host name: No error
The error is not very clear (i.e., the error is "no error"?), and furthermore, operationally, the error makes no sense to me, for the three machines are supposedly configured the same.
|
The error is produced by the C routine "gethostbyname". This routine tries to obtain the IP address of your host max13 and fails. The error "no error" is the error passed to elog from the underlying operating system, so please blame Windows for that. I guess you have a problem that on the machine you get the error you have some DNS problem, so this machine does not know max13. Try to "ping" max13 or do a "nslookup max13" to verify this. Maybe you have to add your domain after max13, or put this machine explicitly into \Windows\System32\drivers\etc\hosts.
| Dan Gawarecki wrote: |
|
I am not sure which version of eLOG is being used, but the size of the elog.exe is 139,264.
I suggest a new option be added to display the version information, or display the version info whenever eLOG is execute, or display the version info when "-?" option is used.
|
I added some version information being displayed with the "-?" option. This feature will be contained in the next release. |
|
65746
|
Mon Feb 18 08:00:44 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.2 2041 | Re: elog crashing on startup |
| Jeff Stoner wrote: |
|
I create 14 of them, one for every 2 letters of the English alphabet and 0-9. The logbook name and Subdir change appropriately. When I start elog, it stays up for about 30 seconds, then crashes. No messages are recorded in syslog nor in the logfile. The only thing that looks suspicious are a couple lines in syslog:
Feb 15 17:11:05 iadopsutil04p elogd[23761]: elogd 2.7.2 built Feb 14 2008, 20:55:38
Feb 15 17:11:05 iadopsutil04p elogd[23761]: revision 2041
Feb 15 17:11:05 iadopsutil04p elogd[23761]: FCKedit detected
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot restore original GID/UID.
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Feb 15 17:11:05 iadopsutil04p elogd[23761]: Server listening on port 80 ...
This is obviously the child process responsible for the highlighted lines and it's coming from the cleanup function. Why it's getting called is beyond me.
Ideas?
|
The error message above come from the PID file /var/run/elogd.pid which cannot be removed. This file is only for information purpose, to tell any script which PID the elogd daemon has. If one elogd crashed in the past, the file might still be there although the program is not running, causing some error to show up, but which can normally be ignored.
The fact that elogd stays for about 30 seconds can only be contributed to the fact that you have very large logbooks, which are scanned during startup. You can check this by starting elogd interactively with the "-v" option. Then you will see the scanning process. The next thing is if you really get a crash, you can produce a core dump, so it can be analyzed to figure out where elogd has crashed. To my knowledge the only way you can do that is by having some logbooks with invalid data. Can you try your set-up with empty logbooks?
- Stefan |
|
65748
|
Mon Feb 18 17:51:49 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | | Re: error "Cannot retrieve host name: No error" using command line in Windows |
| Dan Gawarecki wrote: |
|
QUESTION: does command line ELOG connect differently than ELOG through the browser?
I ask this question for perhaps the A-V SW *is* blocking some port or whatever, and I will need to ask our IT department how to remove such a restriction.
|
ELOG connects in the same way as the browser, but it is a different program. I have seen some firewalls which explicitly exclude browsers in firewall rules. So it might well be that yours blocks ELOG but not your browser. So give it a try and disable it. |
|
65750
|
Thu Feb 21 08:04:50 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
| Richard Ecclestone wrote: |
|
I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.
Any ideas?
|
Yes. If you want this feature to work also for replies, you have to put following into your config file:
Preset ticket = TCK-#####
Preset on reply ticket = TCK-#####
|
|
65753
|
Thu Feb 21 14:36:32 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.2.2041 | Re: elog hand once mirror started |
| stephane wrote: |
|
Hello,
When I started elogd on the mirror server, I can access to the website on it until cron job started. Once cron job started, the elog mirror server hang and I can't obtain any response on it.
How can I solve this problem ?
|
With this information I cannot diagnose the problem. I would recommend you to run the elogd on the mirror server in interactive mode with the "-v" flag, so you see all net traffic. Maybe this sheds some light on the problem. |
|