| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68373
|
Thu Aug 4 16:40:14 2016 |
 | Chris Smyth | chris.smyth@comcast.net | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | how do I compile elogd with USE_SSL=1?
| Andreas Luedeke wrote: |
|
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
| Dawang wrote: |
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
68374
|
Thu Aug 4 21:53:37 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
| |
|
how do I compile elogd with USE_SSL=1?
| Andreas Luedeke wrote: |
|
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
| Dawang wrote: |
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
68375
|
Tue Aug 9 04:23:07 2016 |
| Chris Smyth | chris.smyth@comcast.net | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
| Andreas Luedeke wrote: |
|
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
| |
|
how do I compile elogd with USE_SSL=1?
| Andreas Luedeke wrote: |
|
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
| Dawang wrote: |
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
|
68377
|
Tue Aug 9 14:01:04 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You need to download the source file package of ELOG and compile it. If you don't know what a Makefile is, then it is likely futile for you to attempt to compile ELOG.
Or in other words: you cannot use SSL.
| Chris Smyth wrote: |
|
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
| Andreas Luedeke wrote: |
|
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
| |
|
how do I compile elogd with USE_SSL=1?
| Andreas Luedeke wrote: |
|
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
| Dawang wrote: |
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
|
|
68378
|
Tue Aug 9 14:08:20 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You've already named your solution: drop the very old ELOG version and download the new one. Obviously it was compiled with USE_SSL and you can use it right away.
Since you probably don't even have the source files of the old version, you'll have no chance to make it work with that. Just use ELOG 3.1.0.
| Chris Smyth wrote: |
|
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
| Andreas Luedeke wrote: |
|
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
| |
|
how do I compile elogd with USE_SSL=1?
| Andreas Luedeke wrote: |
|
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
| Dawang wrote: |
|
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
|
|
1976
|
Tue Oct 10 23:29:53 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | Other | 2.6.2-1714 | Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8 |
| Steve Jones wrote: |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root, simply one with and one without the "-D" |
The "one where it errors out" does not look like an error. It does the "fork()" at the end and the main thread ends, that's how it's supposed to be. |
| Quote: | Ok, I got it. I've attached the TRUSS output where we follow the fork. It appears that elogd cannot open any of the specified files then gives up. What was throwing me is no error output, even to STDERR. When I run the same but without the -D flag the files are opened fine.
There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn mode also sets to nobody and works fine. |
|
| Quote: |
I just compiled SVN1723 and tried the generic elogd.cfg -- of course *that works!*. Something in my complex config that causes elog to barf when it is attempting to fork the daemon process. To me the TRUSS output indicates that elog can't seem to find any logfile to work on -- very bizarre.
|
|
|
1977
|
Wed Oct 11 00:19:05 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | Other | 2.6.2-1714 | Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8 |
| Steve Jones wrote: |
| Steve Jones wrote: |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root, simply one with and one without the "-D" |
The "one where it errors out" does not look like an error. It does the "fork()" at the end and the main thread ends, that's how it's supposed to be. |
| Quote: | Ok, I got it. I've attached the TRUSS output where we follow the fork. It appears that elogd cannot open any of the specified files then gives up. What was throwing me is no error output, even to STDERR. When I run the same but without the -D flag the files are opened fine.
There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn mode also sets to nobody and works fine. |
|
| Quote: |
I just compiled SVN1723 and tried the generic elogd.cfg -- of course *that works!*. Something in my complex config that causes elog to barf when it is attempting to fork the daemon process. To me the TRUSS output indicates that elog can't seem to find any logfile to work on -- very bizarre.
Stefan, you might find this interesting. I went ahead and removed all references to pre-existing logbook directories and restarted with TRUSS tracing the program. Elogd managed to go into daemon mode but the minute it received a request it generated a segmentation fault. Notice that even though elog could not open the logging directory it went ahead and went into polling mode. I have no idea what "/var/run/syslog_door" is. Working on isolating.
4190: seteuid(60001) = 0
4190: stat("/sysadm/www/elog/cr-elogd.cfg", 0xFFBC9558) = 0
4190: stat("/usr/lib/locale/english/english.so.2", 0xFFBC85C0) Err#2 ENOENT
4190: stat("/sysadm/www/elog/resources/eloglang.", 0xFFBC9348) Err#2 ENOENT
4190: listen(3, 5, 1) = 0
4190: fstat(4, 0xFFBC9318) = 0
4190: time() = 1160518513
4190: getpid() = 4190 [1]
4190: putmsg(4, 0xFFBC89D0, 0xFFBC89C4, 0) = 0
4190: open("/var/run/syslog_door", O_RDONLY) = 7
4190: door_info(7, 0xFFBC8908) = 0
4190: getpid() = 4190 [1]
4190: door_call(7, 0xFFBC88F0) = 0
4190: close(7) = 0
4190: open("crlogbooks/logs/elogaccess.log", O_RDWR|O_APPEND|O_CREAT, 0644) Err#2 ENOENT
4190: poll(0xFFBC7640, 1, 1000) = 0
4190: poll(0xFFBC7640, 1, 1000) (sleeping...)
4190: poll(0xFFBC7640, 1, 1000) = 0
4190: poll(0xFFBC7640, 1, 1000) = 0
4190: poll(0xFFBC7640, 1, 1000) = 1
4190: accept(3, 0xFFBEF300, 0xFFBC9830, 1) = 7
4190: time() = 1160518516
4190: poll(0xFFBC7640, 1, 6000) = 1
4190: recv(7, " G E T / H T T P / 1".., 100000, 0) = 610
4190: Incurred fault #6, FLTBOUNDS %pc = 0x0001EA1C
4190: siginfo: SIGSEGV SEGV_MAPERR addr=0xFF3EFE30
4190: Received signal #11, SIGSEGV [default]
4190: siginfo: SIGSEGV SEGV_MAPERR addr=0xFF3EFE30
4190: *** process killed ***
|
|
1978
|
Wed Oct 11 08:18:14 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.6.2-1714 | Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8 |
| Steve Jones wrote: | | There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn mode also sets to nobody and works fine. |
The elogd program opens the port (which might be below 1024 and thus needs privileges), then either become daemon or not, then changes to the user and group specified in elogd.cfg. So this behaviour should be the same on both cases.
| Steve Jones wrote: | | I just compiled SVN1723 and tried the generic elogd.cfg -- of course *that works!*. Something in my complex config that causes elog to barf when it is attempting to fork the daemon process. |
That's a good starting point. Take your config file, strip one option after the other, and see which is the offending one. This helps us tracking down the problem.
| Steve Jones wrote: | | I have no idea what "/var/run/syslog_door" is. |
I have not either. But one thing which is different in the daemon mode that all output is redirected to the syslog facility via the function call redirect_to_syslog();. This routine was not written by myself so I don't know 100% what it's doing, just under Linux it works fine. Try to outcomment this function and try again. |
|
|
ELOG V3.1.5-3fb85fa6 | |