Can you post your elog configuration file (elog.cfg)?

Hi Stefan,

I'm experiencing problems importing XML (.csv is not working at all for me).

My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"

- During "preview" I see that all entries are listed.

- During the import I get the "wrong date format" error.

- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.

- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.

- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.

Any suggestion what could be wrong? Is it the missing date-value?

 I cannot answer for Windoze, BUT there is more to this if you use Linux.

(Sorry for re-entry, I spotted a cut-and-paste error from first time around)

If you want to make a new logbook in linux manually, you need to do the following:

0.  Stop the elogd daemon.

1.  Edit elogd.cfg as Stefan said.  This will be in two parts - at the top, and then a block of entries which is what you normally see when you go to the "config" section of any logbook.  Easiest to copy and paste an existing block, only remember to put in a new header in the square brackets at the top - the name of your new logbook.  While most of the elogd.cfg is the same as in the documentation, the additional headers etc are pretty self-explanatory, and you only see these because you're editing the file raw rather than through the elog interface.  Once restarted, you can then edit the config for the new logbook in the usual way.

2.  Create a new subdirectory in your logbooks directory *with the same name* as the name you added in when editing elogd.cfg.

3.  Give that subdirectory the correct ownership and permissions.

4.  Only then, start elogd again.

As a windows user, which of the above you need to do: create the subdirectory (I imagine so) and/or anything else (I don't know).  I don't use Windows - apart from AutoCAD and one other javascript based program that non-the-less has windows dependancies (!).

David.

Just modify your configuration file elogd.cfg manually with an editor and add your logbooks there, then restart elogd.

/Stefan 

Each time a attempt to CREATE A LOGBOOK on any of my logbook groups, I get an ELOG ERROR page presenting saying FORBIDDEN ATTRIBUTE DATE.

I have, up until recently been able to add new logbooks.

Can anybody help me on this.

Paraic Fahey

I'm also not familiar with Debian, all I know is that the former maintainer was Recai Oktas. See here for example:

elog:1002

 Some computer programs/OS work with the computer clock as is.  Some make adjustment for Daylight Saving.  Some - Windows comes to mind, actually adjust the computer clock back and forth as Daylight saving ends and begins respectively.  I know this because I have a dual boot computer (I use windoze for AutoCAD and one other Windows-only Java based utility[!]), and when British Summer Time starts, my Linux automatically moves the screen clock forward.  But when I subseqently boot into Windoze, it sets the computer clock forward one hour, so when I then boot back into Linux, the clock is one hour fast.

I therefore suggest again you check what your computer clock *really* is, not what the OS reports it as being, as often they think they're being clever and automatically put in Daylight Saving.

Another test - Stefan and Andreas will be shuddering hard tonight - will be to set your computer clock to December, and see if the effect is still there or has disappeared.