I don't know if that works. Why don't you just try?

Hi,

I am currently trying to configuring elog top groups, which are supposed to separate from each other. However, I would like to have a common logbook that should be visible in each group. Is there a way to share logbooks among Top Groups for example

Top Group Electronics = Elec1, Elec_EEE, Ele2

Top Group Processing  = P_AA1, PPP2, Elec_EEE

Top Group Monitoring = Mon1, Mon2, Mon3, Mon4

Top Group Data = Data1, PPP2, Data2

I would like logbook to be viewed:

• Electronics:
  • Elec1
  • Elec_EEE
  • Ele2
• Processing:
  • P_AA1
  • PPP2
  • Elec_EEE
• Monitoring:
  • Mon1
  • Mon2
  • Mon3
  • Mon4
• Data:
  • Data1
  • PPP2
  • Data2
  • Mon3
  • Mon4

Could you please suggest me if it is possible to set in this way (Color codes t show the common sharing).

Many thanks and regards,

satyajit

Yes I think I recall the incident in the Forum you're talking about from previous searches I've done on hanging however so far I haven't used Reply To's in this elog instance. Nevertheless, you explained it very well and it's good points to keep in mind should I ever use them, thank you David.

Well, having the config and data files only help if I can reproduce the hanging. If if you give me your files and a step-by-step instruction on how to reproduce the hanging, I can give it a try. But if it happens randomly after a while, it will be very hard for me to reproduce and fix it without the exaclty same user access pattern which of course I don't have.

I could begin debugging with C++. In the interim, if you think it will help, I can also provide you with my Config and log files, and the section of redacted data encompassing the time of the hang - just let me know. Regarding CPU usage, I have noted that in the past and have never seen very high CPU usage during an Elog hang. The VM itself remains responsive.

I have experience of elog hanging (under linux).  I'll describe my situation, although it may not apply to you.  I still use elog 2.9.2 but I am unaware of this issue ever being resolved although I have mentioned it in the past.  (Possibly because I'm one of the few who has this situation).  I certainly recall other person had this as the problem, and my reply on this forum solved their problem.  The cause is the following:

1.  A thread with a large number of replies - something over 40 I think.

2.  This long thread is deleted from the first entry.  This will crash elog,

3.  Once restarted, the later entries of the deleted thread (which survived the deletion attempt when elog crashed) are accessed.  This will cause elog to go into an endless loop and hang.  Until I learnt better, I had to reboot the computer.  Under linux kill -9 (process) does the job, but kill (process) does not.

The problem lays with the first entry that survived the attempt at deletion.  It has an "In reply to" line in the entry in the yymmdda.log file, referring to an entry that has now been deleted.  Manually editing the yymmdda.log file to remove that line does the trick, and then the surviving entries can be accessed and deleted.

A good work-around is that if you are about to delete a long thread is to delete it in sections, starting at the end.  It is useful to note the entry number or some other way to find it again after the last section is deleted, as of course it will now be back in with the even older entries.  Or have two tabs on your browser accessing the same thread.

If you want to move the long thread to another logbook, to avoid the problem, Copy the thread, and then do the deletion in stages.  Moving a long thread does the same computer crash/computer hang, although the Copying part is done fine, the deletion part is the problem.

You don't have to have a large number of replies to an entry to cause the hang in controlled conditions.  Just edit the yymmdda.log file of a new entry adding in a "In reply to" line referring to an earlier entry number that does not exist is enough to cause the problem when you try and access the thread.

If this is the cause of your issue, the problem is to find the orphan thread that is causing the hang, especially after all this time.  Also, you may have more than one orphan thread.  Even though I am aware of the problem, I do occasionally find orphan threads in my logbooks.  In my case I use the ticketing system, and searching by ticket number will find an orphan thread without hanging the computer, but if you then click on any entry found - hang.

There is a related issue, which I think I have now resolved.  If the entry in the "Reply to" field in the yymmdda.log file does not exist, that is a later entry (not earlier, as above), elog will cause a duplicate entry, always in bold, with entry no 0 to appear in the listings.  This entry is an artifact that appears in the listings, not a real entry in a yymmdda.log file.  Again, finding the rogue entry is the tricky bit.

I have experience of elog hanging (under linux).  I'll describe my situation, although it may not apply to you.  I still use elog 2.9.2 but I am unaware of this issue ever being resolved although I have mentioned it in the past.  (Possibly because I'm one of the few who has this situation).  I certainly recall other person had this as the problem, and my reply on this forum solved their problem.  The cause is the following:

1.  A thread with a large number of replies - something over 40 I think.

2.  This long thread is deleted from the first entry.  This will crash elog,

3.  Once restarted, the later entries of the deleted thread (which survived the deletion attempt when elog crashed) are accessed.  This will cause elog to go into an endless loop and hang.  Until I learnt better, I had to reboot the computer.  Under linux kill -9 (process) does the job, but kill (process) does not.

The problem lays with the first entry that survived the attempt at deletion.  It has an "In reply to" line in the entry in the yymmdda.log file, referring to an entry that has now been deleted.  Manually editing the yymmdda.log file to remove that line does the trick, and then the surviving entries can be accessed and deleted.

A good work-around is that if you are about to delete a long thread is to delete it in sections, starting at the end.  It is useful to note the entry number or some other way to find it again after the last section is deleted, as of course it will now be back in with the even older entries.  Or have two tabs on your browser accessing the same thread.

If you want to move the long thread to another logbook, to avoid the problem, Copy the thread, and then do the deletion in stages.  Moving a long thread does the same computer crash/computer hang, although the Copying part is done fine, the deletion part is the problem.

You don't have to have a large number of replies to an entry to cause the hang in controlled conditions.  Just edit the yymmdda.log file of a new entry adding in a "In reply to" line referring to an earlier entry number that does not exist is enough to cause the problem when you try and access the thread.

If this is the cause of your issue, the problem is to find the orphan thread that is causing the hang, especially after all this time.  Also, you may have more than one orphan thread.  Even though I am aware of the problem, I do occasionally find orphan threads in my logbooks.  In my case I use the ticketing system, and searching by ticket number will find an orphan thread without hanging the computer, but if you then click on any entry found - hang.

There is a related issue, which I think I have now resolved.  If the entry in the "Reply to" field in the yymmdda.log file does not exist, that is a later entry (not earlier, as above), elog will cause a duplicate entry, always in bold, with entry no 0 to appear in the listings.  This entry is an artifact that appears in the listings, not a real entry in a yymmdda.log file.  Again, finding the rogue entry is the tricky bit.