XML password files, replication & FreeBSD, posted by G on Tue Apr 12 01:05:20 2005 
|
Ok this really is 2 questions.
1)
I have been running ELOG on FreeBSD no problem for a year now,
but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
with a few warnings (see attached logs).
But has issues with password files, now it shows message "Can't open
passwords.pwd" for all my logbooks. It did convert the password files to
xml format. I had a good hard look at file permissions and config file with
no luck. So I went back a version and compiled 2.5.7-1 which works just
fine with old password files. So something with XML & FreeBSD?...
2)
Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
just fine, also seems to copy over all logbook entries.
But once I look through them there's a fault with one of the fields it
copies over, so entries never show up.
It should be:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain
But once cloned it looks like this:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain
For some reason it looses the "m" so line 4 instead of having
"hh:mm" has "hh: m"
Cheers,
GL. |
Re: XML password files, replication & FreeBSD, posted by Stefan Ritt on Tue Apr 12 09:30:51 2005
|
> I have been running ELOG on FreeBSD no problem for a year now,
> but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
> with a few warnings (see attached logs).
> But has issues with password files, now it shows message "Can't open
> passwords.pwd" for all my logbooks. It did convert the password files to
> xml format. I had a good hard look at file permissions and config file with
> no luck. So I went back a version and compiled 2.5.7-1 which works just
> fine with old password files. So something with XML & FreeBSD?...
Hard to say. The simplest would be if I could debug this.
> Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
> just fine, also seems to copy over all logbook entries.
> But once I look through them there's a fault with one of the fields it
> copies over, so entries never show up.
>
> It should be:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
>
> But once cloned it looks like this:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
>
>
> For some reason it looses the "m" so line 4 instead of having
> "hh:mm" has "hh: m"
Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
contains a ":". This character is not allowed in attributes. Unfortunately I did
not document this (and even didn't know this until now... (;-) ). So you should
use the new option
Type Work done at = datetime
this gives you at the entry mask fields for day/month/year/hour/minute to fill
out, so you don't have to write it directly into the attribute. Another option
would be to use
Comment Work done at = Please enter as (dd/mm/yy hh:mm)
which just displays a comment below the attribute in the entry mask.
- Stefan |
|
Re: XML password files, replication & FreeBSD, posted by G on Wed Apr 13 00:40:55 2005
|
> > I have been running ELOG on FreeBSD no problem for a year now,
> > but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
> > with a few warnings (see attached logs).
> > But has issues with password files, now it shows message "Can't open
> > passwords.pwd" for all my logbooks. It did convert the password files to
> > xml format. I had a good hard look at file permissions and config file with
> > no luck. So I went back a version and compiled 2.5.7-1 which works just
> > fine with old password files. So something with XML & FreeBSD?...
>
> Hard to say. The simplest would be if I could debug this.
Anything I could send you to help debug this?
>
> > Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> > When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
> > just fine, also seems to copy over all logbook entries.
> > But once I look through them there's a fault with one of the fields it
> > copies over, so entries never show up.
> >
> > It should be:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> >
> > But once cloned it looks like this:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> >
> >
> > For some reason it looses the "m" so line 4 instead of having
> > "hh:mm" has "hh: m"
>
> Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
> contains a ":". This character is not allowed in attributes. Unfortunately I did
> not document this (and even didn't know this until now... (;-) ). So you should
> use the new option
>
> Type Work done at = datetime
>
> this gives you at the entry mask fields for day/month/year/hour/minute to fill
> out, so you don't have to write it directly into the attribute. Another option
> would be to use
>
> Comment Work done at = Please enter as (dd/mm/yy hh:mm)
>
> which just displays a comment below the attribute in the entry mask.
>
> - Stefan
Ok, i see, the problem for me now is that this attribute name has been in use for
half a year or so by me. So now I have 100's of logbook entries with the old name
in them, if I change it's name then all old logbook entries will show up with that
field blank. I'm not sure if there's an easy way to change that attribute's name in
100's of entries in 10's of logbooks, because I wouldn't want to try doing that by
hand.. Any ideas? (i'm no good at scripting something like that 4 sure)
Thanks,
G. |
|
Re: XML password files, replication & FreeBSD, posted by Stefan Ritt on Wed Apr 13 09:06:46 2005
|
> Ok, i see, the problem for me now is that this attribute name has been in use for
> half a year or so by me. So now I have 100's of logbook entries with the old name
> in them, if I change it's name then all old logbook entries will show up with that
> field blank. I'm not sure if there's an easy way to change that attribute's name in
> 100's of entries in 10's of logbooks, because I wouldn't want to try doing that by
> hand.. Any ideas? (i'm no good at scripting something like that 4 sure)
find . -name "*a.log" -exec perl -pi -e 's|Work done at (dd/mm/yy hh:mm):|Work done at:|g' {} \;
Looks a bit cryptic, but searches for all *a.log files, and starts perl to replace
all occurences of "Work done at (dd/mm/yy hh:mm)" with "Word done at:". Better try
this first with a copy of your logbook. After you successfully changed that, you
have to modify the attribute list in elogd.cfg accordingly, like
Attirbutes = ..., Work done at, ...
Please note that after each manual modification of the logbook files, you have to
restart elogd. |
|
logbook clone, posted by Emiliano Gabrielli on Thu Apr 14 12:38:04 2005
|
When I create a new logbook (I used an existing one as a template) elog
does not works anymore...
- The problem is on elog user's file.. It seems elogd can't read it
anymore:
Cannot open file arco.users: Success
Please use your browser's back button to go back
- Here are some informations:
sparcserv:/usr/share/elog# ps U elog
PID TTY STAT TIME COMMAND
5165 ? Ss 0:08 /usr/sbin/elogd -f /var/run/elogd.pid
-c /etc/elog.conf -d /var/lib/elog -s /usr/share/elog -p 8080 -n
sparcserv:/usr/share/elog# id elog
uid=106(elog) gid=106(elog) gruppi=106(elog)
sparcserv:/usr/share/elog# ls -lha arco.us*
-rw------- 1 elog elog 1,8K 2005-03-24 12:21 arco.users
-rw-r--r-- 1 elog elog 473 2005-03-23 10:41 arco.users_bak
sparcserv:/usr/share/elog#
giving the arco.users file chmod a+wr does *not* make it work ...
re-chmod-ing to -rw------- AND restarting the daemon solves the problem
and everything works nice ...
any idea?
|
|
Re: logbook clone, posted by Stefan Ritt on Fri Apr 15 22:26:06 2005
|
> When I create a new logbook (I used an existing one as a template) elog
> does not works anymore...
Fixed in CVS. |
|
Mail not sent but message says it has been sent, posted by Mikael Salonvaara on Sun Apr 17 09:35:30 2005
|
If my email host refuses to send the email (476 connections denied), we
still get the message that the email has been sent - and no error message.
How do I or can I send authentication information to the email server? |
|
Re: Mail not sent but message says it has been sent, posted by Stefan Ritt on Mon Apr 18 09:04:21 2005
|
> If my email host refuses to send the email (476 connections denied), we
> still get the message that the email has been sent - and no error message.
>
> How do I or can I send authentication information to the email server?
This is not implemented right now, since the SMTP server at our institute does
not use authentication, so I could not test it. If you give me access to a
SMTP server with authentication, I could implement it. |
|