Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 84 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subject
  69192   Tue Aug 4 13:29:23 2020 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.4-2Re: "New User" option does not work when Authentication=Webserver

Unfortunately I locallly don't have Webserver authentication, so I cannot check or debug. If you send me a diff that works for you, I'm happy to incorporate it.

Stefan

Jan Just Keijser wrote:

Our setup uses "Authentication=Webserver" + no automatic user registration. Thus, logbook admins should add a user by clicking "Config"  and then "New user". However, no matter what they fill in in the "new user " dialog, as soon as they hit "Save" an error pops up saying that their username (the admin one, not the new one) already exists. I found the following code:

int save_user_config(LOGBOOK * lbs, char *user, BOOL new_user)
{
   char file_name[256], str[256], *pl, user_enc[256], new_pwd[80], new_pwd2[80], smtp_host[256],
       email_addr[256], mail_from[256], mail_from_name[256], subject[256], mail_text[2000], str2[256],
       admin_user[80], url[256], error[2000], sid[32];
   int i, self_register, code, first_user;
   PMXML_NODE node, subnode, npwd; 

   /* if we outsourced the authentication, use external username */
   getcfg(lbs->name, "Authentication", str, sizeof(str));
   if (stristr(str, "Webserver")) {
      /* do not allow HTML in user name */
      strencode2(user_enc, http_user, sizeof(user_enc));
   } else {
      strencode2(user_enc, user, sizeof(user_enc));
   }

 

which seems to be the culprit:  the admin user is logged using his/her Webserver (http_user) credentials and this overrides anything that he/she might fill in.  If I remove the "Authentication" check then I can create a new user without problems.  So, how to fix this? should the "Authentication=Webserver" check be extended with a self/auto registration check?

 

 

  69190   Mon Aug 3 13:25:50 2020 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsELOG V3.1.4-a04Re: Search feature in ELOG

That question screams: please read the manual! Find command: https://elog.psi.ch/elog/userguide.html#browse

Some simple examples:
https://elog.psi.ch/elogs/Forum/?mode=threaded&reverse=0&reverse=1&npp=20&Subject=Search
https://elog.psi.ch/elogs/Forum/?mode=summary&reverse=0&reverse=1&npp=8&Subject=category
Illam Pakkirisamy wrote:

Hi,

Is there a search feature in ELOG.  Basically, we have the topics broken up by categories but within the categories we would like to search by a key word based on the subject to get to a specific topic.

Thanks.
Illam

 

  69189   Sun Aug 2 18:45:18 2020 Question Illam Pakkirisamyillam@senseeker.comQuestionWindowsELOG V3.1.4-a04Search feature in ELOG

Hi,

Is there a search feature in ELOG.  Basically, we have the topics broken up by categories but within the categories we would like to search by a key word based on the subject to get to a specific topic.

Thanks.
Illam

  69188   Sun Aug 2 09:06:46 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V3.1.4-966Re: Missing log files when rsync to replacement server.

If nothing is specified elogd looks for logbooks in the current directory where it got started under ./logbooks/

No idea what happened to your 2020 logbook.

VUIIS SysAdmin wrote:

Thank-you. That is good information to have. 

What is the default if you you do not specify anything in elogd.cfg? I assume it is  /usr/local/elog otherwise it would not see the existing logbooks.

With a default Linux RPM install, where else would the logbooks be? Still looking for a 2020 directory on either server.

Bruce

Stefan Ritt wrote:

You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.

Stefan

VUIIS SysAdmin wrote:

On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.

On the old server after stopping elogd i get:

/usr/sbin/elogd -v 3

Cannot open "elogd.cfg": No such file or directory

Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.

My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.

 

 

  69187   Sun Aug 2 02:57:59 2020 Reply VUIIS SysAdminvuiis-sysadmin@vumc.orgQuestionLinuxELOG V3.1.4-966Re: Missing log files when rsync to replacement server.

Thank-you. That is good information to have. 

What is the default if you you do not specify anything in elogd.cfg? I assume it is  /usr/local/elog otherwise it would not see the existing logbooks.

With a default Linux RPM install, where else would the logbooks be? Still looking for a 2020 directory on either server.

Bruce

Stefan Ritt wrote:

You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.

Stefan

VUIIS SysAdmin wrote:

On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.

On the old server after stopping elogd i get:

/usr/sbin/elogd -v 3

Cannot open "elogd.cfg": No such file or directory

Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.

My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.

 

  69185   Sat Aug 1 15:13:17 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V3.1.4-966Re: Missing log files when rsync to replacement server.

You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.

Stefan

VUIIS SysAdmin wrote:

On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.

On the old server after stopping elogd i get:

/usr/sbin/elogd -v 3

Cannot open "elogd.cfg": No such file or directory

Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.

My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.

  69184   Fri Jul 31 21:40:02 2020 Reply VUIIS SysAdminvuiis-sysadmin@vumc.orgQuestionLinuxELOG V3.1.4-966Re: Missing log files when rsync to replacement server.

On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.

On the old server after stopping elogd i get:

/usr/sbin/elogd -v 3

Cannot open "elogd.cfg": No such file or directory

Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.

My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.

 

Stefan Ritt wrote:

Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you might have a wrong path in elogd.cfg

VUIIS SysAdmin wrote:

I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.

rsync -av root@old.elog.server:/usr/local/elog /usr/local/
 

On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.

 

Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd

Bothe servers a fully updated CentOS 7.

 

 

  69183   Fri Jul 31 15:42:55 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V3.1.4-966Re: Missing log files when rsync to replacement server.

Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you might have a wrong path in elogd.cfg

VUIIS SysAdmin wrote:

I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.

rsync -av root@old.elog.server:/usr/local/elog /usr/local/
 

On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.

 

Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd

Bothe servers a fully updated CentOS 7.

 

ELOG V3.1.5-3fb85fa6