Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 220 of 801  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  65750   Thu Feb 21 08:04:50 2008 Reply Stefan Rittstefan.ritt@psi.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

Richard Ecclestone wrote:

 

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?


Yes. If you want this feature to work also for replies, you have to put following into your config file:

Preset ticket = TCK-#####
Preset on reply ticket = TCK-#####
  65753   Thu Feb 21 14:36:32 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.2.2041Re: elog hand once mirror started

stephane wrote:

Hello,

When I started elogd on the mirror server, I can access to the website on it until cron job started. Once cron job started, the elog mirror server hang and I can't obtain any response on it.

How can I solve this problem ?

With this information I cannot diagnose the problem. I would recommend you to run the elogd on the mirror server in interactive mode with the "-v" flag, so you see all net traffic. Maybe this sheds some light on the problem.

  65754   Thu Feb 21 15:09:25 2008 Reply stephanestephane.brisson@synchrotron-soleil.frQuestionLinux2.7.2.2041Re: elog hand once mirror started

Stefan Ritt wrote:

stephane wrote:

Hello,

When I started elogd on the mirror server, I can access to the website on it until cron job started. Once cron job started, the elog mirror server hang and I can't obtain any response on it.

How can I solve this problem ?

With this information I cannot diagnose the problem. I would recommend you to run the elogd on the mirror server in interactive mode with the "-v" flag, so you see all net traffic. Maybe this sheds some light on the problem.

  Hello,

The server hang at this point :

ID362  : 45F505AF26644D7F71A2AF6E9822554D
Cache  : 45F505AF26644D7F71A2AF6E9822554D
Remote : 45F505AF26644D7F71A2AF6E9822554D
 

I can't stop the process with ctrl+c

 

Kind regards

 

Stéphane

  65755   Thu Feb 21 17:18:55 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.2.2041Re: elog hand once mirror started

stephane wrote:

 

  Hello,

The server hang at this point :

ID362  : 45F505AF26644D7F71A2AF6E9822554D
Cache  : 45F505AF26644D7F71A2AF6E9822554D
Remote : 45F505AF26644D7F71A2AF6E9822554D
 

I can't stop the process with ctrl+c

No, that does not help me to come to a conclusion. So I have no idea what's going on. When you do mirroring, you can start the synchronization from both server sides. Can you maybe try to do that from the "other" server? Maybe you have some firewall problem.

  65756   Fri Feb 22 06:32:48 2008 Reply stephanestephane.brisson@synchrotron-soleil.frQuestionLinux2.7.2.2041Re: elog hand once mirror started

Stefan Ritt wrote:

stephane wrote:

 

  Hello,

The server hang at this point :

ID362  : 45F505AF26644D7F71A2AF6E9822554D
Cache  : 45F505AF26644D7F71A2AF6E9822554D
Remote : 45F505AF26644D7F71A2AF6E9822554D
 

I can't stop the process with ctrl+c

No, that does not help me to come to a conclusion. So I have no idea what's going on. When you do mirroring, you can start the synchronization from both server sides. Can you maybe try to do that from the "other" server? Maybe you have some firewall problem.

How can I put the output in a file to send it to you ?

 

  65757   Fri Feb 22 08:38:38 2008 Reply stephanestephane.brisson@synchrotron-soleil.frQuestionLinux2.7.2.2041Re: elog hand once mirror started

stephane wrote:

Stefan Ritt wrote:

stephane wrote:

 

  Hello,

The server hang at this point :

ID362  : 45F505AF26644D7F71A2AF6E9822554D
Cache  : 45F505AF26644D7F71A2AF6E9822554D
Remote : 45F505AF26644D7F71A2AF6E9822554D
 

I can't stop the process with ctrl+c

No, that does not help me to come to a conclusion. So I have no idea what's going on. When you do mirroring, you can start the synchronization from both server sides. Can you maybe try to do that from the "other" server? Maybe you have some firewall problem.

How can I put the output in a file to send it to you ?

 

I solve my mirror problem. It came from old logbooks made with old elog version. I replicate these manually and exclude them from mirror.

Kind regards

Stéphane

  65759   Wed Feb 27 03:46:28 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.3Re: Problem updating from 2.7.2 to 2.7.3

Uwe wrote:

Hello,

I am trying to update from version V2.7.2-2041  to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!

The shared library msvcr71.dll should be part of the operating system and placed under c:\windows\system32\msvc71.dll. If not it can be downloaded from

http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSVCR71.dll/download.html

  65764   Sat Mar 1 14:53:16 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.3Re: German language

Salvatore wrote:

In der Config-Datei habe ich den Eintrag "language = german" vorgenommen. Was unter Windows funktioniert, verweigert mir Linux: Die Umstellung des Logs auf Deutsch. Wer kann helfen?

Salvatore

Das kann drei Ursachen haben:

1) Die Installation under Linux ist nicht vollstaendig. Die Datei resources/eloglang.german muss vorhanden und von elogd lesbar sein

2) Der linux-daemon braucht ein Neustart nach jeder Aenderung der Sprache

3) Nochmal ueberpruefen, ob der Eintrag "language = german" auch wirklich vorhanden im richtigen config file ist.

ELOG V3.1.5-3fb85fa6