| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1761
|
Tue Mar 7 21:41:28 2006 |
 | Haitao Yu | htyu@phys.columbia.edu | Question | Linux | 2.6.1 | large attachment seems to hang elogd? |
Hello,
I am trying to attach somewhat large file (4-15MB files tested) with my messages but it seems to hang the elogd server for a really long time (30-100minutes). The file upload was done pretty soon (within a few seconds), then the elogd process seems to be busy doing something, using around 50MB of memory and 95% of CPU time, and stop respond to the requests. I can read the logbook with another copy of elogd running on another port, and I can see (and download) the uploaded file. I am wondering what could cause the problem --- and could it be related to the problem of not setting up the SMTP server right? Thanks for any suggestion!
Haitao
P.S. I read in some old message that if we want to upload very large files, we have to change the WEB_BUFFER_SIZE in elogd.c, however this parameter is no longer in v2.6.1. Is there something similiar I have to change? |
|
1767
|
Thu Mar 9 21:10:18 2006 |
| Edmundo T Rodriguez | edrodrig@chpnet.org | Question | Linux | 2.6.1 | Problem submitting entries in ELOG after migrating from Windows to Linux |
I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...
ELOG v2.6.1 application came up find!.
I can login with No problems.
I can see previous logs entries, sort, etc.
But, I can NOT create any new-log (new entries) in any logbook. I get this message:
-----------------------------------------------------------------------------------
New entry cannot be written to directory
"/eLOGv261/logbooks/Administration/"
Please check that it exists and elogd has write access and disk is not full
Please use your browser's back button to go back
-----------------------------------------------------------------------------------
The previous logbooks where in ...
\Program Files\ELOG\logbooks\Administration
\MainFrame
\Unix
\OpenVMS
\RDBMS
New logbooks are in the following place ...
/eLOGv261/logbooks/Administration
/MainFrame
/Unix
/OpenVMS
/RDBMS
How can it read old log entries and I NOT create new ones?
I am sure I missing something. Can I know what?
Also, It will be good to have an entry in the ELOG web-site
explaining any migration steps from Window to Linux and reverse!
Please, help.
Thank you! |
|
1768
|
Fri Mar 10 06:12:55 2006 |
 | Steve Jones | steve.jones@freescale.com | Question | Linux | 2.6.1 | Re: Problem submitting entries in ELOG after migrating from Windows to Linux |
| Edmundo T Rodriguez wrote: | I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...
ELOG v2.6.1 application came up find!.
I can login with No problems.
I can see previous logs entries, sort, etc.
But, I can NOT create any new-log (new entries) in any logbook. I get this message:
-----------------------------------------------------------------------------------
New entry cannot be written to directory
"/eLOGv261/logbooks/Administration/"
Please check that it exists and elogd has write access and disk is not full
Please use your browser's back button to go back
-----------------------------------------------------------------------------------
The previous logbooks where in ...
\Program Files\ELOG\logbooks\Administration
\MainFrame
\Unix
\OpenVMS
\RDBMS
New logbooks are in the following place ...
/eLOGv261/logbooks/Administration
/MainFrame
/Unix
/OpenVMS
/RDBMS
How can it read old log entries and I NOT create new ones?
I am sure I missing something. Can I know what?
Also, It will be good to have an entry in the ELOG web-site
explaining any migration steps from Window to Linux and reverse!
Please, help.
Thank you! |
| Steve Jones wrote: | The first place to look is at the permissions set on the existing directories and .log files plus the Owner and Group. (Not knowing how the files got from Windows to Linux is a little problematic but the translation of permissions is not straightforward.) Compare the settings with how you have eLog starting up on your linux box. Typically, when run as a daemon, it starts as ROOT then becomes the USER/GROUP that you specify in the .cfg file. It is likely that you will find a permission mismatch. As to why you can read but not write, with a permission mask of 744 and .log files owned by root but elogd running as nobody, you would be able to read the logs but not change them. Sounds like the permissions are similar on the directories as well. Perhaps you could post the info back here.
|
|
|
1769
|
Mon Mar 13 12:51:36 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? |
Hi!
I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug?
Yoshio |
|
1770
|
Mon Mar 13 12:57:33 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? |
| Yoshio Imai wrote: | | I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug? |
Some how it got screwed up, such that ID 1741 did not have a back-link to 1739. I have no clue how this could have happened, but I fixed it by manually editing the log file. |
|
1771
|
Mon Mar 13 13:19:09 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? |
| Stefan Ritt wrote: | | I have no clue how this could have happened, but I fixed it by manually editing the log file. |
I also have never come across anything like this in our logbooks (approx. 10000 entries), so it doesn't look like a bug. |
|
1778
|
Thu Mar 23 14:49:07 2006 |
| Lars Jorgensen | lars.jorgensen@jppol.dk | Request | Linux | | Re: implement 'hide attribute' and 'sort attribute' |
> > Only the sorting (of the entry mask!) is missing! :)
>
> Ok, I put that on my wish list. So once the second or third person asks for it, I will
> implement it (;-)
I'm asking! :-)
I have a few Extendable Options attributes, and it would be extremely nice if they got sorted as users put them
in. So that when you select the drop-down box, alle options are sorted.
Lars |
|
1779
|
Thu Mar 23 21:52:03 2006 |
| Steve Jones | steve.jones@freescale.com | Request | Linux | | Re: implement 'hide attribute' and 'sort attribute' |
> > > Only the sorting (of the entry mask!) is missing! :)
> >
> > Ok, I put that on my wish list. So once the second or third person asks for it, I will
> > implement it (;-)
>
> I'm asking! :-)
>
> I have a few Extendable Options attributes, and it would be extremely nice if they got sorted as users put them
> in. So that when you select the drop-down box, alle options are sorted.
>
>
> Lars
Agreed - that would be nice |