Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Tue May 18 21:17:35 2010
|
| Stefan Ritt wrote: |
Ok, now I got it! The problem was that you used "Guest menu commands = ..." and I did not. So the behavior is different with that option, which is why I could not reproduce your problem initially. Now I could reproduce it and the cleanest fix is this:
--- elogd.c (revision 2294)
+++ elogd.c (working copy)
@@ -15704,7 +15704,7 @@
fgets(pwd, sizeof(pwd), stdin);
while (pwd[strlen(pwd) - 1] == '\n' || pwd[strlen(pwd) - 1] == '\r')
pwd[strlen(pwd) - 1] = 0;
- } else if (status != 200 && status != 302) {
+ } else if (status != 200 && status != 302 && status != 404) {
xfree(buffer);
*strchr(str, '?') = 0;
which is just accept the 404 response and not abort the cloning process. |
Yup. My settings are:
Guest menu commands = List, Last 10, Find, Login, Help
Guest List Menu commands = List, Last 10, Find, Login, Help
Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
the password file?
-- rouilj |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by Stefan Ritt on Wed May 19 09:57:50 2010
|
| John Rouillard wrote: | Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
the password file? |
Well, why don't you give it a try and let me know if the is any problem left? |
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Thu May 20 03:37:59 2010
|
| Stefan Ritt wrote: |
| John Rouillard wrote: | Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
the password file? |
Well, why don't you give it a try and let me know if the is any problem left? |
Sorry to report that it fails same as originally with:
Received invalid response from elogd server at http://example.org:8080/Discussion/
However there was a fuzz of 12 lines when I applied the patch, but I think it got the right line.
-- rouilj |
|
Re: attachment filename bug & Makefile issue, posted by A. Martin on Thu May 20 04:33:07 2010
|
> > If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt." Also, this effects
> > the file's displayed "Uploaded" time. It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"
>
> Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext.
> For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers
> followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however
> 0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can
> easily remove the interpretation of the date, it would break the synchronization functionality and I would have to
> find some other method to pass the file date/time, which would be quite some work. So if it's not too important for
> you, I would like to keep it as it is.
>
Thank you for your response.
I can certainly use another filename, but I'm curious why elog doesn't convert the filename "000000_000000_file.txt" to
"YYMMDD_HHMMSS_000000_000000_file.txt" when it gets uploaded. All other files are automatically prepended with this
string. Manually renaming the file and then editing the elog entry via text editor seems to fix the file.
thanks,
amartin |
|
Re: cannot start elog, posted by Stefan Ritt on Tue Jun 1 13:17:18 2010
|
| harley wrote: |
|
I have v2.7.7 of elog running on a OSX system running 10.6 I configured and installed about a year ago. It's a wonderful thing to have.
I acquired another system running 10.6 to dedicate to the elog app. I downloaded 2.7.8 and performed the following steps:
extract tarball in the desired directory
run
tar -xzvf elog-x.x.x.tar
switch to the new elog-x.x.x directory edit Makefile and elogd.cfg files as needed
to create executables
run
make
to create directories & files
run
make install
When I try to execute elog as a daemon:
elogd -c ~vulcanstaff/ELOG-Workspace/elog/elogd.cfg -D
I get the following message:
-bash: elogd: command not found
I'm not understanding why elogd cannot be found. The same message occurs when I try to test the installation with elogd -p 8080 from the sbin directory where elogd is installed.
I'm using the same Makefile and elogd.cfg files that work on the old system. My elogd and elogd.cfg files appear to be in the correct directories indicated in the Makefile:
#############################################################
#
# Directories for installation, modify if needed
#
ifndef PREFIX
PREFIX = ~vulcanstaff/ELOG-Workspace
endif
ifndef MANDIR
MANDIR = $(ROOT)$(PREFIX)/man
endif
ELOGDIR = $(ROOT)$(PREFIX)/elog
DESTDIR = $(ROOT)$(PREFIX)/bin
SDESTDIR = $(ROOT)$(PREFIX)/sbin
RCDIR = $(ROOT)$(PREFIX)/etc/rc.d/init.d
# flag for SSL support
USE_SSL = 1
# flag for crypt() support
USE_CRYPT =
#############################################################
Again, this works on the old system. Perhaps I've looked at it for too long, but I can't figure out what's going on. Assistance is greatly appreciated.
-harley
|
Some Linux systems don't have the current directory (".") in the search path, so you have to start it with
./elogd -c ....
or explicitly with
/usr/sbin/elogd -c ...
|
|
Re: alphabetize Quick Filter items?, posted by Dennis Seitz on Thu Jun 3 06:14:50 2010
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
Hi Stefan,
I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.
We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.
I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?
Thanks again for a *very* useful logging system!
Dennis
|
The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items
Options Type = C, D, A, B
they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like
Options Type = A, B, C, D
I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.
- Stefan
|
Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!
|
Ok, I implemented
Sort attribute options = 1
in the current SVN revision.
|
I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?
Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D? |
|
Re: change design part of the discussion board, posted by Stefan Ritt on Tue Jun 8 09:02:03 2010
|
| Heinzmann wrote: |
|
Hello Stefan,
If I would like to change the design of the attached part of the discussion board like:
deleting OS: (including blue box) Linux Windows Mac OSX All Other (including green box)
Where and how could I do this?
Thank you
|
Well, the official forum at midas.psi.ch cannot be changed by you. But if you installed a local logbook similar to the one here, you simple go and edit the configuration file elogd.cfg. Please read the documentation for further information. |
|
Re: Deamon on Debian, posted by Stefan Ritt on Tue Jun 8 09:21:16 2010
|
| Marco Rojas wrote: |
|
Hi,
I have been using ELOG for a while and I love it. It is a default installation on Debian Lenny and ELOG 2.7.8. I am having problems with the deamon script, I can stop the service by doing /etc/init.d/elog stop but I can't started. When I do /etc/init.d/elog start I get this error: "Starting ELOG daemon: elogdCannot open "elogd.cfg": No such file or directory"
Somewhere there is a bad path to the elogd.cfg which is in "/usr/local/elog"
I would appreciate any help I can get.
Thank you.
Here is the scrip:
[code]
#!/bin/sh
# Init script for ELOG.
# Recai Oktas <roktas@omu.edu.tr>
PATH=/sbin:/bin:/usr/sbin:/usr/local/bin
DAEMON=/usr/local/sbin/elogd
NAME=elogd
DESC="ELOG daemon"
# Always run as daemon.
ARGS="-D"
# Admin might change some command line options without touching this script.
if [ -f /etc/default/elog ]; then
. /etc/default/elog
fi
test -f $DAEMON || exit 0
set -e
case "$1" in
start)
echo -n "Starting $DESC: $NAME"
start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
stop)
echo -n "Stopping $DESC: $NAME"
start-stop-daemon --oknodo --stop --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
reload)
# Do nothing since ELOG daemon responds to
# the changes in conffile directly.
;;
restart|force-reload)
echo -n "Restarting $DESC: $NAME"
start-stop-daemon --stop --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
sleep 1
start-stop-daemon --start --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
echo "."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0
[/code]
|
Unfortunately the Debian distribution was not done by me, so I only can guess:
- Is the executable existing under /usr/local/sbin/elogd ?
- In the start) section, I cannot find any reference to /usr/local/elog, so you maybe need something like
ARGS="-D -c /usr/local/elog/elogd.cfg"
|
|