| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69134
|
Thu Apr 2 13:37:21 2020 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V3.1.4-a04faf9f | Re: Mirroring function for a full both-sides synchronization | The entry ID #0 was a bug in logging routine only, so in the elog logbook the ID is certainly not zero. But the logging bug has been fixed now, so please update your version of elog.
Then I tried to reproduce your problem. I set up two servers, the master listening at port 8080 and the slave listening at port 8081. I created two entries at the master, did manual synchronization, then created one entry on the slave, and did another synchronization on the master. I got both sides correctly transferred, no problem with ID zero. See attached screenshot. I used following elogd.cff on the master side:
[global]
port = 8080
password file = passwd
Mirror server = http://localhost:8081
Mirror simulate =1
[demo]
Theme = default
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
| Sergei Gavrilov wrote: |
|
Hello, dear ELOG's gurus.
Please help me to understand a problem with mirroring function.
It appears in ELOG V3.1.4-a04faf9f - the last official Windows release, as well as previous 3.1.3 Windows release, which I have checked for comparison.
When I'm using a manual configuration with "mirror server, cron, user" options for one (master) of two servers, it operates well, except the situation, when a new entry is submitted at the second (slave) server.
For example, for a new entry with a real ID#2 at Slave its logfile gives "NEW entry #0", so logfile of the master server gives "MIRROR: Error receiving message: Received wrong entry id "0"".
After that Master deletes this entry at Slave "MIRROR delete remote entry #2".
In case of mirror functions in both .cfg files (Master to Slave, Slave to Master) both servers hung on after the first mirror process.
Now let's imagine, what I want to do.
Master, as a main-operation global log, is off-operation, Slave automatically becomes a reserv-operation local log with full information from Master due to previous periodic mirroring.
Users work with Slave, submit new entries - all with #0 ID.
After repairing Master starts active mirroring and just deletes all new entries from Slave.
It seems, that the problem is not with mirroring, but with a new entry ID, as was mentioned in https://elog.psi.ch/elogs/Forum/68850
Were these ID#0/mirror problems resolved somehow or may be it is not a problem, but simply my errors in ELOG configuration?
Is there a chance to get an up-to-date Windows-release with working both-sides mirror function and all other addings after V3.1.4-a04faf9f ?
Best regards,
Sergei
|
|
| Attachment 1: Screenshot_2020-04-02_at_13.42.23_.png
|
|
|
68904
|
Mon Mar 4 13:35:13 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.4 | Re: Mirror synchronization and file servers | Sounds really strange to me. The remote server does not "know" that "S:\" is a network drive, so the syncing process should work exactly as before. The only idea I have is that the access to the network files take pretty long, and you run into a timeout during syncing. We had this in the past (for AFS netwhor shares, not Windows shares), where sometimes we have a blocking behaviour where the file access lasted 10-20 seconds, and the server process was simply blocked. Since then I do not recommend to put logbook on network shares.
Stefan
| Frank Baptista wrote: |
|
We have a number of temperature chambers – each has its own laptop running a local ELOG server, with unique logbook for each. Using the mirror feature, these individual logbooks periodically synchronize to a single remote desktop server, which has a copy of each of the logbooks. All of that works great, as long as each of the ELOG servers are storing the logbook(s) to their respective local hard drive.
I wanted the remote server to store its copy of the logbooks on the network file server. I changed the global options of the elogd.cfg file, adding the following:
Logbook dir = S:\SHARED\LOGBOOKS
That change worked fine on the remote desktop server – new logbook entries were now being stored on the network file server.
Unfortunately, I lost the ability to sync from the individual logbooks to the remote desktop server. During synchronization, I now get the following error message: “Error sending local entry: Error transmitting message".
Has anyone run into this? Does this make sense? Am I missing something? Is there a workaround? Is there a wrong time to drink beer? 
Thanks,
Frank
|
|
|
66349
|
Wed May 6 15:38:10 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Mirror Server Funktion |
| Andreas Wilke wrote: |
|
Ich möchte meine "lokale" ELOG Installation mit einem Server in der Firma synchronisieren.
Dazu habe ich in der entfernten Firewall ein Portmapping auf den ELOG Server in der Firma eingerichtet.
Wenn ich von meiner "lokalen" Maschine im Browser http://meinedomain.dyndns.xx:PORT aufrufe, kann ich auf den ELOG Server zugreifen.
Ich habe in meiner "lokalen" Installation in der Section [global] den Mirror-Server = http://meinedomain.dyndns.xx:PORT angeben.
Beim Synchornisieren bekomme ich jedoch den Hinweis "Fehler beim Zugriff auf entfertes Logbuch".......
|
Please let's stick to English. Let me try to understand your configuration. You have one elog server running and want to synchronize with itself? That does not work of course, synchronizing is done between two servers (normally on different computers). |
|
68068
|
Tue Aug 4 13:57:28 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | V3.1.1-f613012 | Re: Minor bug in the emails generated by elog. | Apostrophes are encoded as "'" inside the CKEditor used by elog, which sents the raw HTML text as email notification. You can test this by pressing the "Source" button at the top left menu in the CKEditor, then you see it. In my mail program (both Apple Mail and Thunderbird) this HTML enocding is correctly shown as the original apostroph, so I suspect that your mail program has an issue interpreting HTML encodings.
| David Pilgram wrote: |
|
In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon. So the text "I don't think..." appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit. It has been around in the past few versions of elog, but don't recall precisely when this started occurring. It was fine back in February, with v2.9.2 (presumably) running.
|
|
| Attachment 1: Screen_Shot_2015-08-04_at_14.01.09_.png
|
|
|
68899
|
Tue Feb 26 14:31:00 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.2 | Re: Migration from 3.1.2 version to 3.1.4 | To move an elog instance, just stop the old server, move the configuration file elogd.cfg and the logbook directory to the new server, and start the new server. If the URL of the server changes, you have to adjust it in elogd.cfg.
Stefan
| Vladimir Travalja wrote: |
|
Hi,
sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another.
The migration should be done from one server version (CentOS 6.10 to CentOS 7.6). Also we are talking about migration from one subdomain to another. Example subdomain1.example.com to subdomain2.example.com. Old elog application version is 3.1.2 and I would like to migrate to the latest version 3.1.4
Is the migration from one system to another possible? What are the prerequisites for migration?
Are there any instructions how to do it?
Thank you in advance and have yourself a lovely day,
Warmest regards
|
|
|
65657
|
Mon Nov 26 14:33:59 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
| lance wrote: |
|
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed" |
|
65658
|
Mon Nov 26 16:58:26 2007 |
| lance | lance1.hayward@yahoo.com | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
| Stefan Ritt wrote: |
|
| lance wrote: |
|
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed"
|
Stefan,
Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.
Once again thanks for the very speedy support.
Lance |
|
65742
|
Fri Feb 15 15:46:38 2008 |
| Richard Ecclestone | richard.ecclestone@cern.ch | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
| lance wrote: |
|
| Stefan Ritt wrote: |
|
| lance wrote: |
|
I am trying to create a trouble ticket system however when you do a reply you get a new message ID. I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.
Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.
Has anyone configured a trouble ticket system that I could look at to get some ideas?
|
First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:
- Use attributes Ticket and Status
- Preset Ticket with a running ticket number via
Preset ticket = TCK-#####
This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply
-
Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)
Options Status = open, closed
Preset Status = open
-
Once a ticked chain is closed, do the following:
- Go to the threaded list display
- Click on Select
- Select the trouble ticket chain
- Click on Edit
- Now change Status from "Open" to "Closed"
This will then modify the Status of the whole chain from "Open" to "Closed"
|
Stefan,
Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.
Once again thanks for the very speedy support.
Lance
|
Hi
I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.
Any ideas?
Cheers Richard |
|