Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 28 of 237  Not logged in ELOG logo
icon5.gif   Search feature in ELOG, posted by Illam Pakkirisamy on Sun Aug 2 18:45:18 2020 

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

    icon2.gif   Re: Search feature in ELOG, posted by Andreas Luedeke on Mon Aug 3 13:25:50 2020 

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

 

icon5.gif   Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Thu Jul 30 17:11:05 2020 

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.

    icon2.gif   Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Fri Jul 31 15:42:55 2020 

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.

 

       icon2.gif   Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Fri Jul 31 21:40:02 2020 

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.

 

 

          icon2.gif   Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sat Aug 1 15:13:17 2020 

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.

             icon2.gif   Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Sun Aug 2 02:57:59 2020 

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.

 

                icon2.gif   Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sun Aug 2 09:06:46 2020 

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.

 

 

icon5.gif   Expanding column width when viewing in Summary mode, posted by Illam Pakkirisamy on Thu Jul 16 23:29:15 2020 

Hi,

I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it.  Is this possible and if so, how would I do it.

Thanks in advance for your help.

Illam

    icon2.gif   Re: Expanding column width when viewing in Summary mode, posted by Stefan Ritt on Fri Jul 17 09:18:18 2020 

You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.

Illam Pakkirisamy wrote:

Hi,

I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it.  Is this possible and if so, how would I do it.

Thanks in advance for your help.

Illam

 

       icon2.gif   Re: Expanding column width when viewing in Summary mode, posted by Illam Pakkirisamy on Sat Jul 18 17:19:31 2020 

Hi Stefan,

Thanks for your prompt follow up.  I did try commenting of the width statement for listtitle2 and also reducing it to 40% but it did not work.  I restarted elogd daemon and I don't see the columns changing.  I also tried putting a percentage number (40%) for listtitle1 just to try and no change either.  Appreciate your help.

Thanks.

Illam

Stefan Ritt wrote:

You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.

Illam Pakkirisamy wrote:

Hi,

I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it.  Is this possible and if so, how would I do it.

Thanks in advance for your help.

Illam

 

 

          icon2.gif   Re: Expanding column width when viewing in Summary mode, posted by David Pilgram on Sun Jul 19 13:14:36 2020 

Anyone who knows me knows I (ab)use elog a lot.   And this one is another of a long list of cheats and work arounds rather than modifying the code properly.

In summary mode, the top row are titles, and if they are long, they will dominate the width of that column.  Similarly if they are short, if entries under that title are either non-existant or even shorter.  Sometimes entries below the title will dominate, e.g. entries under "Date" title.

I assume your entries under the title in question are things like more than one word, such that they get split into two rows within that cell.  Sometimes that can look very untidy.  However, if you want the column wider than the title is given, you can pad out the title with " " (without the "").  Either on both sides for a centred title, or on the right for left justified.  Or between words if the title has more than one.  (Sorry for this edit, I hit submit button rather than preview).

Illam Pakkirisamy wrote:

Hi Stefan,

Thanks for your prompt follow up.  I did try commenting of the width statement for listtitle2 and also reducing it to 40% but it did not work.  I restarted elogd daemon and I don't see the columns changing.  I also tried putting a percentage number (40%) for listtitle1 just to try and no change either.  Appreciate your help.

Thanks.

Illam

Stefan Ritt wrote:

You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.

Illam Pakkirisamy wrote:

Hi,

I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it.  Is this possible and if so, how would I do it.

Thanks in advance for your help.

Illam

 

 

 

          icon2.gif   Re: Expanding column width when viewing in Summary mode, posted by Stefan Ritt on Mon Jul 20 08:37:17 2020 

I can think of two reasons why you don't see a change:

1) You modified the wrong file. The elog.css file is under elog/themes/default/elog.css. If you "install" elog, it might go into your installation directory. So check if you have more than one file with this name.

2) After the change, you did not reload the page in your browser.

Try to request the file directly in your browser with <url to elog>/logbook/elog.css then you will see the actual file your browser is using. Make sure your modification is present there.

Stefan

 

Illam Pakkirisamy wrote:

Hi Stefan,

Thanks for your prompt follow up.  I did try commenting of the width statement for listtitle2 and also reducing it to 40% but it did not work.  I restarted elogd daemon and I don't see the columns changing.  I also tried putting a percentage number (40%) for listtitle1 just to try and no change either.  Appreciate your help.

Thanks.

Illam

Stefan Ritt wrote:

You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.

Illam Pakkirisamy wrote:

Hi,

I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it.  Is this possible and if so, how would I do it.

Thanks in advance for your help.

Illam

 

 

 

             icon2.gif   Re: Expanding column width when viewing in Summary mode, posted by Illam Pakkirisamy on Thu Jul 23 21:19:24 2020 

Hi Stefan,

I have only one elog.css file in the default directory and the installation path is the same one that I'm using. Basically, I'm using off of the installed path.  I also tried, modifying the file and calling it elog_mod.css and then specified CSS=<path>/elog_mod.css and started the server again.  I did not see any changes.  Is there something else I'm missing here.

Thanks.
Illam

Stefan Ritt wrote:

I can think of two reasons why you don't see a change:

1) You modified the wrong file. The elog.css file is under elog/themes/default/elog.css. If you "install" elog, it might go into your installation directory. So check if you have more than one file with this name.

2) After the change, you did not reload the page in your browser.

Try to request the file directly in your browser with <url to elog>/logbook/elog.css then you will see the actual file your browser is using. Make sure your modification is present there.

Stefan

 

Illam Pakkirisamy wrote:

Hi Stefan,

Thanks for your prompt follow up.  I did try commenting of the width statement for listtitle2 and also reducing it to 40% but it did not work.  I restarted elogd daemon and I don't see the columns changing.  I also tried putting a percentage number (40%) for listtitle1 just to try and no change either.  Appreciate your help.

Thanks.

Illam

Stefan Ritt wrote:

You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.

Illam Pakkirisamy wrote:

Hi,

I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it.  Is this possible and if so, how would I do it.

Thanks in advance for your help.

Illam

 

 

 

 

icon5.gif   How to change name of record Id from $@MID@$., posted by John on Wed Jul 22 18:11:56 2020 

Hi Everyone,

I tried using this $@MID@$ in JS as a variable and cannot doit. I researched a little and found no answer on special character usage. If anyone knows, please lemme know. I also tried breifly in Elogd to change it to something like just MID, but need a better editor as  (Kate) is not saving the program back in correct iso (character) format. So I thought I'd pose the question in the meanwhile.

Thanks, John

    icon2.gif   Re: How to change name of record Id from $@MID@$., posted by Stefan Ritt on Wed Jul 22 19:10:08 2020 

No idea what you are talking about. $@MID@$ is used in the database files to indicate the start of a new message. It is not used on any elog web page. If you want to put the message ID on your web page, you should use the variable "$message id" as written in the documentation. You say JS, where is your JS running? You wrote a JS program to work on the raw elog database files? Or you wrote an extension to run in your browse? You have to be a bit clearer.

Stefan

John wrote:

Hi Everyone,

I tried using this $@MID@$ in JS as a variable and cannot doit. I researched a little and found no answer on special character usage. If anyone knows, please lemme know. I also tried breifly in Elogd to change it to something like just MID, but need a better editor as  (Kate) is not saving the program back in correct iso (character) format. So I thought I'd pose the question in the meanwhile.

Thanks, John

 

icon5.gif   Expanding column width when viewing in Summary mode, posted by Illam Pakkirisamy on Thu Jul 16 23:26:43 2020 

Hi,

I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it.  Is this possible and if so, how would I do it.

Thanks in advance for your help.

Illam

icon1.gif   bug in elog.spec, posted by Janusz Szuba on Mon Jul 6 19:09:48 2020 

Hi, 

in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?

best

Janusz

    icon2.gif   Re: bug in elog.spec, posted by Laurent Jean-Rigaud on Mon Jul 6 20:19:21 2020 elog.specelog-3.1.4-2.CNES.el6.src.rpm

Hi,

You rights, CFLAGS should not be in specfile to take care of distrib env.

Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.

With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,

rpm -i elog-.....src.rpm

rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec

 

I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.

Bye,

Laurent

 

Janusz Szuba wrote:

Hi, 

in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?

best

Janusz

 

       icon2.gif   Re: bug in elog.spec, posted by Janusz Szuba on Tue Jul 7 11:22:45 2020 

Thanks for the answer, I will try with your specfile

best

Janusz

Laurent Jean-Rigaud wrote:

Hi,

You rights, CFLAGS should not be in specfile to take care of distrib env.

Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.

With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,

rpm -i elog-.....src.rpm

rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec

 

I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.

Bye,

Laurent

 

Janusz Szuba wrote:

Hi, 

in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?

best

Janusz

 

 

icon1.gif   change Cell Style, posted by Lahreche Abdelmadjid on Tue Jun 30 11:39:12 2020 

Hi All,

I hope to change the Cell Style backround color into background point.

because my color printer don't work.

can some one give me the code to do that.

Regards.

 

    icon2.gif   Re: change Cell Style, posted by Andreas Luedeke on Tue Jun 30 17:12:10 2020 

You should edit the CSS style file: /usr/local/elog/themes/default/elog.css

Just change all fields "background-color:" to your desired color; e.g. "#FFFFFF" for white.
 
Lahreche Abdelmadjid wrote:

Hi All,

I hope to change the Cell Style backround color into background point.

because my color printer don't work.

can some one give me the code to do that.

Regards.

 

 

       icon2.gif   Re: change Cell Style, posted by Lahreche Abdelmadjid on Wed Jul 1 09:08:17 2020 

I would like to change the backround cilor of a cell and not sheet.

also don't use color, but system of point (to print it in monochome printer)

Andreas Luedeke wrote:

You should edit the CSS style file: /usr/local/elog/themes/default/elog.css

Just change all fields "background-color:" to your desired color; e.g. "#FFFFFF" for white.
 
Lahreche Abdelmadjid wrote:

Hi All,

I hope to change the Cell Style backround color into background point.

because my color printer don't work.

can some one give me the code to do that.

Regards.

 

 

 

icon5.gif   Update, posted by Lahreche Abdelmadjid on Tue Jun 30 13:42:13 2020 

Hi,

 

How to do the last update with out losing any data ?

 

Regards

    icon2.gif   Re: Update, posted by Andreas Luedeke on Tue Jun 30 17:15:18 2020 
When you update from a version 2.* to a version 3.* then all elog entry files will be moved in subfolder for each year. But non of the entries are lost.
Only if you afterwards try to start an old version 2.* with the newly converted data directories, then the old version will not find any of the entries.
I've updated the ELOG version many times now. The only data I once lost was a modified CSS style file and a "hand modified" configuration of the ckeditor.
 
Lahreche Abdelmadjid wrote:

Hi,

 

How to do the last update with out losing any data ?

 

Regards

 

ELOG V3.1.5-3fb85fa6