| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66035
|
Wed Nov 5 20:37:37 2008 |
 | Glen MacLachlan | maclach@gwu.edu | Question | Linux | | Proxy Error |
A problem recently developed for our elog...after running without much problem the elog daemon was restarted on an ubuntu server running apache2. Now the server gives 502 Proxy Error messages:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elog.
Reason: Error reading from remote server
I did a force-reload of apache after making sure the modules are enabled. I also restarted elogd but to no avail. One symptom seems to be that the GET request is empty...that is before it was:
"GET /elog/sample_elog/etcetera HTTP/1.1"
but now it is just
"GET /elog HTTP/1.1"
Just started out of the blue...
Any ideas? |
|
66034
|
Wed Nov 5 11:52:12 2008 |
 | T. Ribbrock | emgaron+elog@ribbrock.org | Info | Linux | 2.7.5 | Re: Installation problems |
> > 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> > out that line).
> >
> > 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> > to "echo ").
>
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain.
I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old Debian
one and working my way up till 2.7.5). Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
directory, with a suitable note in the README or something like that? That script has not changed in a long time and
is still functional - and doing so would make it easier for people who would like to install elog on a Debian (or
Debian-based, e.g. Ubuntu) system. I'll attach the script.
Regards,
Thomas |
| Attachment 1: elog
|
#!/bin/sh
# Init script for ELOG.
# Copyright © 2003, 2005 Recai Oktaş <roktas@omu.edu.tr>
#
# Licensed under the GNU General Public License, version 2.
# See the file `http://www.gnu.org/copyleft/gpl.txt'.
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/elogd
NAME=elogd
DESC="ELOG daemon"
test -f $DAEMON || exit 0
set -e
# Admin should be able to lock some options.
if [ -f /etc/default/elog ]; then
. /etc/default/elog
fi
# To be in the safe side, the followings should be always defined.
PIDFILE=${PIDFILE:-/var/run/$NAME.pid}
CONFFILE=${CONFFILE:-/etc/elog.conf}
# Add the options to argument list only if defined previously. Since
# some options may also be present in the conffile, we couldn't preset
# those options which would otherwise overwrite the settings in the
# conffile. Also note that, all have reasonable compiled-in defaults.
ARGS="${PIDFILE+"-f $PIDFILE"} \
${CONFFILE+"-c $CONFFILE"} \
${LOGBOOKDIR+"-d $LOGBOOKDIR"} \
${RESOURCEDIR+"-s $RESOURCEDIR"} \
${PORT+"-p $PORT"} \
${HOST+"-n $HOST"} \
${VERBOSE+"-v"}"
# Always run as a daemon.
ARGS=`echo $ARGS -D`
case "$1" in
start)
echo -n "Starting $DESC: "
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $ARGS 2>&1
sleep 1
if [ -f "$PIDFILE" ] && ps h `cat "$PIDFILE"` >/dev/null; then
echo "$NAME."
else
echo "$NAME failed to start; check syslog for diagnostics."
exit 1
fi
;;
stop)
echo -n "Stopping $DESC: $NAME"
start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $ARGS 2>&1
echo "."
;;
reload)
# Do nothing since ELOG daemon responds to
# the changes in conffile directly.
;;
restart|force-reload)
$0 stop
sleep 1
$0 start
if [ "$?" != "0" ]; then
exit 1
fi
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0
# vim:ai:sts=8:sw=8:
|
|
66033
|
Wed Nov 5 10:32:07 2008 |
 | George B. | i93.borg@gmail.com | Bug report | Linux | 2.7.5 | Re: Installation problems |
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain.
That makes sense. Might be worth adding a short Debian section to the installation instructions page?
FYI, Elog is no longer in Debian as of 2008-05-12.
Thanks,
George. |
|
66032
|
Mon Nov 3 13:15:52 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5 | Re: Server derived time |
| Grant Jeffcote wrote: |
|
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
Many people want conditional attributes on the find page, so I cannot remove it. Before adding another parameter to disable this optionally, I would like to ask you to first try the "Show attributes edit = ..." option, which is not evaluated in the "find" page. Maybe you can achieve what you want with this option. |
|
66031
|
Mon Nov 3 07:33:08 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Standard login Screen - bottom text |
| Barend wrote: |
|
Stefan,
I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.
Barend
|
That's strange. I just tried myself following configuration file:
[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd
[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject
[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
and everything works fine as can be seen from the login screen:
so can you check if above file works for you? |
|
66030
|
Thu Oct 30 21:14:32 2008 |
| Barend | b.vandevrande@amtc2.com | Question | Windows | 2.7.5-2130 | Re: Standard login Screen - bottom text |
| Stefan Ritt wrote: |
|
| Barend wrote: |
|
Hi Stefan.
I have been "playing" around with this great tool and found an interesting "issue" ...
I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".
When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.
When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.
How can I apply my own Bottom Text to the Standard Login Screen ?
Thanks & Regards, Barend
|
By using the configuration option "Bottom Text Login = ..."
|
Stefan,
I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.
Barend
|
|
66029
|
Thu Oct 30 11:05:11 2008 |
 | T. Ribbrock | emgaron+elog@ribbrock.org | Question | All | 2.7.5-2130 | Re: (How) can I hide columns in List view? |
| Stefan Ritt wrote: |
|
[...]
The only way I see how you can achieve what you want is to define two separate logbooks, but serve them from the same directory (via the "Data dir" option). Both logbooks should share the same attribute definition, but use different "List display" options.
|
I take it you mean the "Subdir" option (the manual mentions "Data dir" as obsolete)? I tried it with that and it works like a charm - gives me now two logbooks, i.e. two tabs with the same data and two different views - which is precisely what we need. Thanks!
Regards,
Thomas |
|
66028
|
Thu Oct 30 09:44:25 2008 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Question | All | 2.7.5-2130 | Re: (How) can I hide columns in List view? |
Thanks for the response! BTW: I did get a notification - but thanks for the "personal heads-up"! 
| Stefan Ritt wrote: |
|
Indeed you got something wrong. The conditional attributes are meant for the input form, so you can turn some attributes on and off or choose different options for an attribute depending on the value of another attribute.
[...]
|
I see. In that case, could you maybe please give a quick explanation what "List conditions" is supposed to do? In conjunction with your statement above I'm now thoroughly confused as to what it should/could be used for... 
| Stefan Ritt wrote: |
|
[...]
The only way I see how you can achieve what you want is to define two separate logbooks, but serve them from the same directory (via the "Data dir" option). Both logbooks should share the same attribute definition, but use different "List display" options.
|
Ah, that's an idea - I'll look into that. Thanks a mil for the suggestion!
Regards,
Thomas |