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
|
|
|
|
|
|
Re: testing the client: unclear it worked, posted by Stefan Ritt on Fri Jul 31 08:34:35 2020
|
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test test
Message successfully transmitted, ID=5
~$
| Jose Caballero wrote: |
|
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose
|
|
|
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.
|
|
|
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.
|
|
|
|
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.
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
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
|
|