| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69184
|
Fri Jul 31 21:40:02 2020 |
 | VUIIS SysAdmin | vuiis-sysadmin@vumc.org | Question | Linux | ELOG V3.1.4-966 | Re: 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.
|
|
|
|
69187
|
Sun Aug 2 02:57:59 2020 |
| VUIIS SysAdmin | vuiis-sysadmin@vumc.org | Question | Linux | ELOG V3.1.4-966 | Re: 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.
|
|
|
|
67057
|
Thu Apr 28 11:20:40 2011 |
 | Wolfgang Bayer | w.bayer@gsi.de | Question | Windows | 2.9.0-2396 | Options <...> vs ROptions <...> | According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and
ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution? |
|
67058
|
Fri Apr 29 11:20:50 2011 |
| Wolfgang Bayer | w.bayer@gsi.de | Request | Windows | 2.9.0-2396 | Filter on attribute value for list items | Hello @all,
for a logbook I have also to set up a guest access. As I want to have a login page first opening the logbook, I created a second logbook entry in the elog.cfg that points to the same subdir as the original logbook. The idea of this guest access is, that users who have no login rights can read selected items with selected attributes. Therefor I restricted the guest account with all available "Guest"-commands in the elog.cfg.
But this is not sufficient. Let's suppose I have an attribute called 'Accessibility' with options 'public' and 'private'. What I am searching for is a filter command for the list display, i.e. if an entry has the accessibility flag 'public', a guest sees this entry in the list and can access it. But if the entry has the accessibility flag private, the entry should not be displayed for guests but for users, that are logged in.
I read the administrator guide carefully, but I didn't found a command that provides for that. Does such a filtering command for the list exist? If not, is it possible to implement one?
Best regards,
Wolfgang Bayer |
|
67366
|
Tue Oct 30 22:47:15 2012 |
| David Wallis | wallis@aps.anl.gov | Question | Linux | 2.9.2 | Elogd hangs while uploading bmp attachment | I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.
When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.
ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.
Is this a known problem, or have I missed something that needs to be installed on the RHEL server? |
|
67368
|
Wed Oct 31 16:08:40 2012 |
| David Wallis | wallis@aps.anl.gov | Question | Linux | 2.9.2 | Re: Elogd hangs while uploading bmp attachment |
| David Pilgram wrote: |
|
| David Wallis wrote: |
|
I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.
When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.
ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.
Is this a known problem, or have I missed something that needs to be installed on the RHEL server?
|
When I saw this problem come in, I was reminded of problems I have of elog crashing. So I tried attaching a .bmp file to an entry. In my case it did not crash, but it did not run ImageMagick either - it just gave a link as it it were a zip or tar file - that is to say no .png image had been generated and shown. As I've never attached a .bmp file before, I don't know whether elog allows for them to be processed and a thumbnail made, a quick look in the documentation didn't enlighten me, but then I didn't look for that long either. (I'm running 2.9.2 svn 2475, under Slackware 13 which is a version post some image processing issues I reported to Stefan - might that explain why in my case?).
I have found that sometimes elog will crash, but effectively after it has done the action - so if it crashes when asked to move files from one logbook to another, you find the entries have been moved. In my case, I believe the crashes are due to memory issues, nothing I can state for certain.
It would possibly help Stefan and Andreas if you can tell whether the .bmp file appears in the relivent logbook directory (usually a subdirectory of ....../logbooks) - it will have been renamed as yymmdd_hhmmss_{filename}.bmp - except, of course, the date and time will be showing not these symbols - and if the entry with which you have tried to attach this .bmp file been written - using a text viewer on the file yymmdda.log (obviously the day will be today, i.e. the one just updated as you tried the entry. I have come across orphan attachment files in directories in my time, possibly from when elog crashed part way through an action.
(If I am stating the obvious, apologies, I don't know your level of experience with elog or linux, so trying to cover all possible levels)
|
Thanks for the info, David.
I do not see any *.bmp files in the logbook directory when this happens. The hang happens when the "Upload" button is hit, so there is no logbook entry yet either. |
|
67371
|
Wed Oct 31 18:04:47 2012 |
| David Wallis | wallis@aps.anl.gov | Question | Linux | 2.9.2 | Re: Elogd hangs while uploading bmp attachment |
| David Pilgram wrote: |
|
| David Wallis wrote: |
|
| David Pilgram wrote: |
|
| David Wallis wrote: |
|
I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.
When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.
ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.
Is this a known problem, or have I missed something that needs to be installed on the RHEL server?
|
When I saw this problem come in, I was reminded of problems I have of elog crashing. So I tried attaching a .bmp file to an entry. In my case it did not crash, but it did not run ImageMagick either - it just gave a link as it it were a zip or tar file - that is to say no .png image had been generated and shown. As I've never attached a .bmp file before, I don't know whether elog allows for them to be processed and a thumbnail made, a quick look in the documentation didn't enlighten me, but then I didn't look for that long either. (I'm running 2.9.2 svn 2475, under Slackware 13 which is a version post some image processing issues I reported to Stefan - might that explain why in my case?).
I have found that sometimes elog will crash, but effectively after it has done the action - so if it crashes when asked to move files from one logbook to another, you find the entries have been moved. In my case, I believe the crashes are due to memory issues, nothing I can state for certain.
It would possibly help Stefan and Andreas if you can tell whether the .bmp file appears in the relivent logbook directory (usually a subdirectory of ....../logbooks) - it will have been renamed as yymmdd_hhmmss_{filename}.bmp - except, of course, the date and time will be showing not these symbols - and if the entry with which you have tried to attach this .bmp file been written - using a text viewer on the file yymmdda.log (obviously the day will be today, i.e. the one just updated as you tried the entry. I have come across orphan attachment files in directories in my time, possibly from when elog crashed part way through an action.
(If I am stating the obvious, apologies, I don't know your level of experience with elog or linux, so trying to cover all possible levels)
|
Thanks for the info, David.
I do not see any *.bmp files in the logbook directory when this happens. The hang happens when the "Upload" button is hit, so there is no logbook entry yet either.
|
Hi David,
Which svn version of elog are you running - what does it say at the very bottom of the page (this forum says ELOG V2.9.0-2435); there *is* and issue about loading files and thumbnails with svn 2473, but it may also be in one or two prior to that (I found it with 2473, anyway). Also, is elog running (taking CPU time) and not responding to anything after you try this (and you have to kill the daemon and restart), or crashing out at that point? I've had both behaviours at one time or another, for reasons I now understand, not related (I think) to this one, but the more evidence, the better chance that someone will find the problem.
David.
|
I'm running ELOG V2.9.2-2455.
The elogd process continues to run, but no longer responds to requests.If, for example, I open a new browser tab and try to load the logbook, I eventually get a timeout. There is no ImageMagick "convert" process running. |
|
67373
|
Wed Oct 31 18:51:31 2012 |
| David Wallis | wallis@aps.anl.gov | Question | Linux | 2.9.2 | Re: Elogd hangs while uploading bmp attachment |
| Andreas Luedeke wrote: |
|
| David Wallis wrote: |
|
I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.
When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.
ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.
Is this a known problem, or have I missed something that needs to be installed on the RHEL server?
|
Hi David,
I've just tested it on my server running ELOG V2.9.0-2414, Scientific Linux 5.7 (RHEL 5.?) with ImageMagick 6.2.8: the attachment is uploaded but no preview is generated. No problem with the server.
What was the behaviour of your Solaris system? Did it upload? Did it create a preview?
BMP files are - in my experience - often very large. Could it be a file size problem? Did you try with a small BMP image?
Kind Regards
Andreas
 ⇄
Detect language » English
|
Hi Andreas,
Bmp attachments worked fine on the Solaris server. Was running 2.9.2 with ImageMagick 5.5.7.
I don't think it's a file size issue, the image I'm testing with is only about 3 MB. |
|