Hi Andreas. 

It seems I didn't fully understand the comment by Stefan when he said "Have you tried to connect directly to elogd and not going through Apache?". My bad. 

I decided to rebuild elog 3.1.4 in Catalina (MacOS 10.15.1), XCode 11.2.1.  As in previous builds, I needed to add to the Makefile pointers to openssl:

CFLAGS += -I/usr/local/opt/openssl/include

LIBS += -L/usr/local/opt/openssl/lib

The make builds cleanly, no errors, no warnings.  After make/make install, elogd segfaults immediately.  I saw the same behavior with the version in gitlab.  I kept my (very) old build and was able to make install it without recompiling and it still works.

I'll crack out the debugger when I have a chance to get more information, but has anyone else seen this problem?  

> Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.

I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
Is is possible the corporate elog server is running behind apache or in some
other proxy config while the one you are having issues with is being connected
to directly by chrome?

-- rouilj

 Could you post an example of what you used?

> > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > 
> > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > Is is possible the corporate elog server is running behind apache or in some
> > other proxy config while the one you are having issues with is being connected
> > to directly by chrome?
>
> It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> URL to Google Chrome developers to see if it's a bug in the browser or not.

I just brought up the current head release of elog, and the problem is fixed. Looks like it 
was some sort of cookie issue IIRC the log entry.

So build a new elogd and you should be all set.

- rouilj

Hello:

I am running release 2.7.8 of elog. I am using the cloning/syncing features
to maintain a backup/slave and at some point it stopped cloning the password
file.

Operating systems/software:

   master: ubuntu 10.4 using locally compiled elog 2.7.8-2278
   slave: solaris 10 using locally compile elog 2.7.8 without SSL support

A sample run (hostname edited - available by private email if needed) is:

  $../elogd -C http://host.example.org:8080/ 
  Overwrite local "elogd.cfg"? [y]/n:  y

  Remote configuration successfully received.

  Option "Mirror server = http://host.example.org:8080/" added to config file.
  Option "URL = xxx" has been outcommented from config file.

  Retrieve remote password files? [y]/n:  y
  Received invalid response from elogd server at http://host.example.org:8080/Discussion/

Running with -v doesn't produce any useful diagnostics as to what the invalid response is.

Trussing the process (again with host name editing) shows:

send(3, 0xFFBEE890, 93, 0)                      = 93
   G E T   / D i s c u s s i o n / ? c m d = G e t P w d F i l e  
   H T T P / 1 . 0\r\n C o n n e c t i o n :   C l o s e\r\n H o s
   t :   h o s t . e x a m p l e . o r g : 8 0 8 0\r\n\r\n
poll(0xFFBEC070, 1, 30000)                      = 1
recv(3, 0x011057B0, 251000, 0)                  = 119
   H T T P / 1 . 1   4 0 4   N o t   F o u n d\r\n S e r v e r :  
   E L O G   H T T P   2 . 7 . 8 - 2 2 7 8\r\n C o n t e n t - T y
   p e :   t e x t / h t m l ; c h a r s e t = I S O - 8 8 5 9 - 1
  \r\n C o n n e c t i o n :   C l o s e\r\n\r\n

If logged in as myself I go to http://host.example.org:8080/Discussion/?cmd=GetPwdFile
I do get the data so this looks like a password/authentication issue.

I have added Mirror user = rouilj to elogd.cfg, and it is present in the cloned elogd.cfg
but still no joy. I also copied the passwd file to the clone and made sure that it was being
successfully found and opened during the clone operation.

So where do I go from here in trying to troubleshoot the problem?

-- rouilj

Does anybody have any ideas? Should I post a config or something?

-- rouilj