| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1447
|
Tue Oct 11 09:24:12 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Mac OSX | 2.6.0beta5 | Re: Cannot submit admin password while logbook is named in Chinese |
| Exaos Lee wrote: | | Sorry for my poor English. The case is like this: When I set an admin password for my logbook which is named in Chinese, I cannot open the config page while the password is correct. It seems that the logbook named in Chinese cannot recieve the password submitted. If the logbook is named other than Chinese, everything is OK. I will repeat the problem and describe it more exactly. |
A way around that problem would be to use user level access (via the Password file = ... and Admin user = ... settings). Can you try if that works under a Chinese logbook? |
|
2120
|
Thu Jan 18 16:29:43 2007 |
 | Alexandre Lindote | alex@lipc.fis.uc.pt | Question | Linux | Mac OSX | 2.6.3-1762 | Synchronization using https | Hi,
I have an elog server running on a linux desktop machine inside our institutional firewall. It can be accessed from inside the firewall directly using http, but users from outside have to use https, with apache (and its ssl module) controlling the access.
I also set up another server on my laptop, just for backup purposes, and synchronized it inside the firewall (using a direct http connection). No problems there!
Now we want to have several servers set up (in different institutions), and have them synchronized automatically. For this I installed elog on a mac server (in another institution, so outside our firewall), also accessible only through https (again using apache).
I configured all the required mirror settings, but always get an error: "Remote server is not an ELOG server".
I've tried changing the status of the 2 machines (server-client), but get the same error...
I also tried different approaches for the Mirror server parameter, like
https://the.remote.server
https://the.remote.server:443
http://the.remote.server:443
but no luck...
Running elog with the -D flag off issued this message:
| Quote: | HTTP/1.1 401 Authorization Required
Date: Thu, 18 Jan 2007 15:22:10 GMT
Server: Apache/1.3.33 (Darwin) DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l
WWW-Authenticate: Basic realm="zeplin2"
Connection: close
Content-Type: text/html; charset=iso-8859-1
Authorization Required
This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.
Apache/1.3.33 Server at shalott.pp.rl.ac.uk Port 80
|
The servers have user level passwords, and I'm mirroring with Mirror user parameter set to the administrator...
Any ideas?
Thanks in advance
Alex |
|
2121
|
Thu Jan 18 20:19:22 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Mac OSX | 2.6.3-1762 | Re: Synchronization using https |
| Alexandre Lindote wrote: | | Now we want to have several servers set up (in different institutions), and have them synchronized automatically. |
Synchronization works such that the "client" elogd (the one on which the synchronization is started) "emulates" a browser and accesses the other elogd server. Since SSL is not built into elogd, it can only use the http protocol, not https. If you want secure synchronization, the only chance you have is to make a SSH tunnel on which you run the http protocol for synchronization. |
|
66578
|
Thu Nov 5 10:17:19 2009 |
| Diogo Alves | diogomiguelalves@gmail.com | Question | Linux | Mac OSX | 2.7.7 | Show dropdown menus as a function of selecting an option in another dropdown menu | Hello,
I'm having some difficulties in having a tasks manager up and running.
The total attributes list is:
- Attributes = List, Project, SubProject, SubSubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
I would like to have the interface display the following attribute when I click "New":
- List (Options = Personal, Work)
After choosing a List "Personal" I would like to have the following attributes available for edit:
- List (Options = Personal, Work)
- Project (Options = Dummy1)
- Title
- Priority (Options = ...)
- Context (Options = ...)
- Status (Options = ...)
- Due Date (datetime)
- Start Date (datetime)
- Alarm (datetime)
- Repeat (Options = ...)
After choosing the Project "Dummy1" I would like to have the following attributes available for edit:
- List (Options = Personal, Work)
- Project (Options = Dummy1)
- SubProject (Options = Dummy2)
- Title
- Priority (Options = ...)
- Context (Options = ...)
- Status (Options = ...)
- Due Date (datetime)
- Start Date (datetime)
- Alarm (datetime)
- Repeat (Options = ...)
where Dummy2 is an option of the SubProject attribute only because Dummy1 was the chosen option of attribute Project.
What happens is that when I choose Dummy1 from the Project attribute, the SubProject attribute is not displayed in order to be editable.
Is there a way around this?
Thank you.
Kind Regards,
Diogo
Here's the configuration file relative to the "Tasks" logbook:
================================================
Password file = passwords.pwd
Self register = 0
Admin user = someuser
Login user = someuser
Allow password change = 1
Theme = default
Comment = Task Manager
Attributes = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
List display = ID, Date, Author, List, Title, Priority
Show Attributes Edit = List
Options List = Personal{1}, Work{2}
Options Priority = High, Medium, Low, None
Options Context = @ Home, @ Work - IST
Options Status = Not Started, Start Delayed, Started, Started - On Hold, 1/4 Done, 1/4 Done - On Hold, 1/2 Done, 1/2 Done - On Hold, 3/4 Done, 3/4 Done - On Hold, Done
Options Repeat = Hourly, Daily, Weekdays, Weekend days, Weekly, Monthly, Yearly
{1} Show Attributes Edit = List, Project, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{1} Options Project = Dummy1{11}
{11} Show Attributes Edit = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{11} Options SubProject = DummyChild1
Extendable options = List, Project, SubProject, SubSubProject
Type Due Date = datetime
Type Start Date = datetime
Type Alarm = datetime
Required Attributes = List, Title
Reverse sort = 1
Default encoding = 0 ; ELcode
Thumbnail size = 500
|
|
66611
|
Fri Nov 13 17:03:03 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Mac OSX | 2.7.7 | Re: Show dropdown menus as a function of selecting an option in another dropdown menu |
| Diogo Alves wrote: |
|
Hello,
I'm having some difficulties in having a tasks manager up and running.
The total attributes list is:
- Attributes = List, Project, SubProject, SubSubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
I would like to have the interface display the following attribute when I click "New":
- List (Options = Personal, Work)
After choosing a List "Personal" I would like to have the following attributes available for edit:
- List (Options = Personal, Work)
- Project (Options = Dummy1)
- Title
- Priority (Options = ...)
- Context (Options = ...)
- Status (Options = ...)
- Due Date (datetime)
- Start Date (datetime)
- Alarm (datetime)
- Repeat (Options = ...)
After choosing the Project "Dummy1" I would like to have the following attributes available for edit:
- List (Options = Personal, Work)
- Project (Options = Dummy1)
- SubProject (Options = Dummy2)
- Title
- Priority (Options = ...)
- Context (Options = ...)
- Status (Options = ...)
- Due Date (datetime)
- Start Date (datetime)
- Alarm (datetime)
- Repeat (Options = ...)
where Dummy2 is an option of the SubProject attribute only because Dummy1 was the chosen option of attribute Project.
What happens is that when I choose Dummy1 from the Project attribute, the SubProject attribute is not displayed in order to be editable.
Is there a way around this?
Thank you.
Kind Regards,
Diogo
Here's the configuration file relative to the "Tasks" logbook:
================================================
Password file = passwords.pwd
Self register = 0
Admin user = someuser
Login user = someuser
Allow password change = 1
Theme = default
Comment = Task Manager
Attributes = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
List display = ID, Date, Author, List, Title, Priority
Show Attributes Edit = List
Options List = Personal{1}, Work{2}
Options Priority = High, Medium, Low, None
Options Context = @ Home, @ Work - IST
Options Status = Not Started, Start Delayed, Started, Started - On Hold, 1/4 Done, 1/4 Done - On Hold, 1/2 Done, 1/2 Done - On Hold, 3/4 Done, 3/4 Done - On Hold, Done
Options Repeat = Hourly, Daily, Weekdays, Weekend days, Weekly, Monthly, Yearly
{1} Show Attributes Edit = List, Project, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{1} Options Project = Dummy1{11}
{11} Show Attributes Edit = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{11} Options SubProject = DummyChild1
Extendable options = List, Project, SubProject, SubSubProject
Type Due Date = datetime
Type Start Date = datetime
Type Alarm = datetime
Required Attributes = List, Title
Reverse sort = 1
Default encoding = 0 ; ELcode
Thumbnail size = 500
|
There is one "feature" which causes this not to work. If an option is present several times (in your case "Show Attributes Edit"), the first one is taken which fulfills the current condition(s). So what happens is you select List=Personal, which triggers condition "1". Then you select "Dummy1", which triggers condition "11". Now elog goes top down, finds that List=Personal, so sets condition "1", then continues, finds {1} Show Attributes Edit = ... and takes this one. What I propose is to do the following:
Options List = Personal{1}, Work{2}
...
{3} Show Attributes Edit = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{3} Options SubProject = DummyChild1
{1} Show Attributes Edit = List, Project, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{1} Options Project = Dummy1{3}
Note that {3} Show Attributed Edit come before {1} Show Attributes Edit, so as soon as you select "Dummy1", the first "Show Attributes Edit" gets
activated which contains "SubProject".
|
|
66619
|
Tue Nov 17 16:44:43 2009 |
| Diogo Alves | diogomiguelalves@gmail.com | Question | Linux | Mac OSX | 2.7.7 | Re: Re: Show dropdown menus as a function of selecting an option in another dropdown menu |
| Stefan Ritt wrote: |
|
| Diogo Alves wrote: |
|
Hello,
I'm having some difficulties in having a tasks manager up and running.
The total attributes list is:
- Attributes = List, Project, SubProject, SubSubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
I would like to have the interface display the following attribute when I click "New":
- List (Options = Personal, Work)
After choosing a List "Personal" I would like to have the following attributes available for edit:
- List (Options = Personal, Work)
- Project (Options = Dummy1)
- Title
- Priority (Options = ...)
- Context (Options = ...)
- Status (Options = ...)
- Due Date (datetime)
- Start Date (datetime)
- Alarm (datetime)
- Repeat (Options = ...)
After choosing the Project "Dummy1" I would like to have the following attributes available for edit:
- List (Options = Personal, Work)
- Project (Options = Dummy1)
- SubProject (Options = Dummy2)
- Title
- Priority (Options = ...)
- Context (Options = ...)
- Status (Options = ...)
- Due Date (datetime)
- Start Date (datetime)
- Alarm (datetime)
- Repeat (Options = ...)
where Dummy2 is an option of the SubProject attribute only because Dummy1 was the chosen option of attribute Project.
What happens is that when I choose Dummy1 from the Project attribute, the SubProject attribute is not displayed in order to be editable.
Is there a way around this?
Thank you.
Kind Regards,
Diogo
Here's the configuration file relative to the "Tasks" logbook:
================================================
Password file = passwords.pwd
Self register = 0
Admin user = someuser
Login user = someuser
Allow password change = 1
Theme = default
Comment = Task Manager
Attributes = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
List display = ID, Date, Author, List, Title, Priority
Show Attributes Edit = List
Options List = Personal{1}, Work{2}
Options Priority = High, Medium, Low, None
Options Context = @ Home, @ Work - IST
Options Status = Not Started, Start Delayed, Started, Started - On Hold, 1/4 Done, 1/4 Done - On Hold, 1/2 Done, 1/2 Done - On Hold, 3/4 Done, 3/4 Done - On Hold, Done
Options Repeat = Hourly, Daily, Weekdays, Weekend days, Weekly, Monthly, Yearly
{1} Show Attributes Edit = List, Project, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{1} Options Project = Dummy1{11}
{11} Show Attributes Edit = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{11} Options SubProject = DummyChild1
Extendable options = List, Project, SubProject, SubSubProject
Type Due Date = datetime
Type Start Date = datetime
Type Alarm = datetime
Required Attributes = List, Title
Reverse sort = 1
Default encoding = 0 ; ELcode
Thumbnail size = 500
|
There is one "feature" which causes this not to work. If an option is present several times (in your case "Show Attributes Edit"), the first one is taken which fulfills the current condition(s). So what happens is you select List=Personal, which triggers condition "1". Then you select "Dummy1", which triggers condition "11". Now elog goes top down, finds that List=Personal, so sets condition "1", then continues, finds {1} Show Attributes Edit = ... and takes this one. What I propose is to do the following:
Options List = Personal{1}, Work{2}
...
{3} Show Attributes Edit = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{3} Options SubProject = DummyChild1
{1} Show Attributes Edit = List, Project, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{1} Options Project = Dummy1{3}
Note that {3} Show Attributed Edit come before {1} Show Attributes Edit, so as soon as you select "Dummy1", the first "Show Attributes Edit" gets
activated which contains "SubProject".
|
Thank you ... good to know about these elog features. Works fine now!!! |
|
66885
|
Fri Aug 27 23:11:45 2010 |
 | Glenn Horton-Smith | gahs@ksu.edu | Bug report | Linux | Mac OSX | 2.8.0 | Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined? | We have been experiencing corruption of logbook entries by elogd mirror synchronization. Has anyone else encountered this? Is there a known cause and/or workaround for it?
Details
We have two elog servers set up with identical elogd.cfg and password files, except that one server has "Mirror server" pointing to the other host. There are three logbooks defined. (Their names are DoubleChooz, BigBrotherTable, and FlushingTable.) When the mirror synchronization happens, whether by "Mirror cron" or by an administrator hitting the "Synchronize all logbooks" link, it often happens that entries requiring synchronization are corrupted on both servers (not just the one to which the entry was copied). This is particularly likely to happen if entries have been made on both servers since the previous sync.
Looking at the logbook files themselves, we see that the corrupted entries will have attributes from the wrong logbooks. E.g., we'll see an empty "Barometer: " line in a DoubleChooz logbook file, where "Barometer" is an attribute that is only in the FlushingTable logbook, or we will see there are unexpected DoubleChooz logbook attributes in the FlushingTable files.
Strangely, the entries will not be identical on the two machines after syncing, and they stay non-identical on further syncs.
Most disturbingly, data is lost from entries that were perfectly valid before the sync, on both servers.
This was happening with elogd 2.7.8, and continued to happen after upgrading to 2.8.0. Both servers are running Linux. One is a 32-bit machine and another 64-bit, in case that might matter (but read on).
I made copies of both servers' files and ran two elogd servers on my Mac on different ports, compiled from a fresh checkout of 2.8.0, and the same behavior was observed as I repeatedly made test entries and synchronized. This suggests it isn't specific to Linux architecture, 64-bit or otherwise.
|
|
66890
|
Fri Sep 3 14:43:16 2010 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Comment | Linux | Mac OSX | 2.8.0 | Re: Synchronizing mirror causes corruption of logbook entries with multiple logbooks defined? |
| Glenn Horton-Smith wrote: |
|
We have been experiencing corruption of logbook entries by elogd mirror synchronization. Has anyone else encountered this? Is there a known cause and/or workaround for it? [...]
I made copies of both servers' files and ran two elogd servers on my Mac on different ports, compiled from a fresh checkout of 2.8.0, and the same behavior was observed as I repeatedly made test entries and synchronized. This suggests it isn't specific to Linux architecture, 64-bit or otherwise.
|
We plan to use ELOG with mirror servers in a larger scale here, so I'm interested to know more about your problem.
Could you boil down your configuration to a minimum that still allows a reproduction of the problem and post those configurations as attachments?
Then I would try to reproduce it here. Best case I'll find a bug fix, worst case I'll reconsider the use of mirror servers ;-) |
|