ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67125
|
Fri Sep 23 01:16:30 2011 |
| mike cianci | mike2.cianci@comcast.net | Question | Windows | 2.7.5-2185 | Re: Rename Logbook |
Stefan Ritt wrote: |
mike cianci wrote: |
I have a logbook with data in it that I need to rename and preserve the the existing data (old book) in the newly named book (i.e. can I move all of the data from one book to a new book and than delete the data from the original book)?
As always thank you for your time.
|
There are two ways:
1) Create a new logbook, add the "Copy to" command to the old logbook. Select all entries and copy them to the new logbook, and delete the old one.
2) Change the logbook name in elogd.cfg, by manually editing the file, then rename the subdirectory in your file system from the old to the new name, then restart elogd.
The second solution is much simpler, but you have to manipulate files and directories yourself.
Whatever you do, make sure to back up you files before any operation.
|
Sorry, about this dumb question but with "Copy to = <logbook list> " what is the format of <logbook list>?
Is it just the "logbook Name" or is it the actual path name "http://something/somethingelse"? |
67124
|
Tue Sep 20 04:46:55 2011 |
| Ryan | ryan.hoitt@intelsat.com | Bug report | Linux | 2.9.0-2411 | Memory Leak in V2.9.0-2411 (Mirroring Related) | I have two identical servers (IBM X337) setup on the same LAN with Ubuntu Linux 10.04 LTS with ELOGD running (Compiled from tarbell) with the same exact package install base. (Only difference between the two servers is the hostname, and the ELOGD.CFG global section)
I noticed after setting these servers up today that ELOGD crashed on the server configured to mirror. It looks like there may be a memory leak in the mirroring of ELOG.
SERVER 1 ELOGD.CFG
[global]
Mirror server = http://10.146.1.76
Mirror config = 1
Mirror cron = 0,5,10,15,20,25,30,35,40,45,50,55 * * * *
Mirror user = (* Removed for Web Post *)
port = 80
Allowed encoding = 1
Suppress default = 3
Mode commands = 1
Password file = password.pwd
Self register = 1
Admin user = (* Removed for Web Post *)
Time format = %d-%b-%y %H:%M UTC
Group 2009 = Station Log-09, DAT-09, Hours Logging-09
Group 2010 = Station Log 10, DAT-10, Hours Logging-10
Group 2011 = Station Log, DAT, Hours Logging, Operations Tasks, Viasat-1, OS-2
Group Cable Database = Cable Database
Group Provisioning = Provisioning
Group ECR = ECR
SERVER 1 SYSLOGD (cat /var/log/syslog |grep elog)
Sep 19 12:14:13 riverside-log elogd[8588]: elogd 2.9.0 built Sep 19 2011, 10:32:58
Sep 19 12:14:13 riverside-log elogd[8588]: revision 2411
Sep 19 12:14:13 riverside-log elogd[8588]: Falling back to default group "elog"
Sep 19 12:14:13 riverside-log elogd[8588]: Falling back to default user "elog"
Sep 19 12:14:13 riverside-log elogd[8588]: FCKedit detected
Sep 19 12:14:13 riverside-log elogd[8590]: Falling back to default group "elog"
Sep 19 12:14:13 riverside-log elogd[8590]: Falling back to default user "elog"
Sep 19 12:14:13 riverside-log elogd[8588]: Server listening on port 80 ...
Sep 19 19:55:05 riverside-log elogd[8588]: xmalloc: not enough memory
SERVER 1 (Set to mirror off server 2) Memory Usage over 1 hour (ps aux|grep elog)
elog 8760 11.6 3.4109240 35092 ?
elog 8760 12.2 3.9137852 40204 ?
elog 8760 11.6 4.4165448 45440 ?
elog 8760 10.7 5.4221652 55548 ?
elog 8760 9.9 5.9249752 60552 ?
elog 8760 10.1 6.4278364 65680 ?
elog 8760 9.5 6.8305712 70700 ?
SERVER 2 Memory Usage over 1 hour (ps aux|grep elog)
elog 799 2.1 2.6 31744 27116 ?
elog 799 2.0 2.6 31744 27116 ?
elog 799 2.1 2.6 31744 27116 ?
elog 799 2.0 2.6 31744 27116 ?
elog 799 2.0 2.6 31744 27116 ?
elog 799 2.0 2.6 31744 27116 ?
elog 799 2.1 2.6 31744 27116 ? |
67123
|
Tue Sep 13 13:38:19 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug fix | Linux | 2.9.0-2414 | Re: Elog crashes with URL find npp=0 | > [...] It appears that npp=0 crashes elogd [...]
Here's a patch: search for "npp" in src/elogd.c and add the following line:
if (n_page<=0) n_page = 20;
Here's the diff output for version 2.9.0-2414
*** 20092,20096 ****
if (isparam("npp"))
n_page = atoi(getparam("npp"));
+ if (n_page<=0) n_page = 20;
if (page_mid) { |
67122
|
Tue Sep 13 11:54:16 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 2.9.0-2414 | Elog crashes with URL find npp=0 | Some user wanted to modify the URL by hand and succeeded to crash the elogd process with npp=now
It appears that npp=0 crashes elogd with the following error message:
Program received signal SIGFPE, Arithmetic exception.
0x0808eba2 in show_elog_list (lbs=0xab3c770, past_n=0, last_n=0, page_n=1,
default_page=1, info=0x0) at src/elogd.c:20214
20214 sprintf(str + strlen(str), loc("Page %d of %d"), page_n, (n_msg - 1) / n_page + 1);
I guess this bug is not OS dependent: you can crash every logbook that you can search ;-) |
67121
|
Fri Sep 9 12:54:13 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Other | 2.9.0 | Expiration of ELOG forum accounts | Dear ELOG users,
the ELOG discussion forum at PSI contains in meantime many old accounts with non-functional email addresses. Since this causes some overhead, it has been decided to clean up the current account database. In order to keep your account alive, please log in at the above forum before Friday, Sept. 30th, 2011. If you fail to log in until that date, your account will be automatically deleted. Note that it will be always possible to re-create your account afterwards by simply clicking on "Register as new user", but before that you won't get automatic email notifications any more once your account has be deleted.
Sorry for the inconvenience, but the database contains currently too many wrong email addresses causing some flooding of our mail systems.
Best regards,
Stefan Ritt |
67120
|
Wed Sep 7 16:23:01 2011 |
| Terry Shuck | terry.shuck@atmosenergy.com | Question | Windows | V2.9.0-241 | Re: Password may not contain blanks |
Andreas Luedeke wrote: |
Stefan Ritt wrote: |
Terry Shuck wrote: |
After setting up email addresses for notifications I noticed that the "Full Name" has part of an email address in it. I've tried several ways to correct this however it keeps sending me to a page that says "Password may not contain blanks" and I've not done anything with the password.
Can you tell me how to correct this issue?
I certainly appreciate your help!!
Terry
|
Have you tried deleting and re-creating the account? Otherwise you could stop elogd, edit the password file with a text editor, and restart elogd.
|
You will not loose your logbook data if you have access rights to the file system where the "elogd" program writes it's data.
The easiest way is to edit there password file directly and then restart "elogd".
But even if you do not dare to edit the files directly, you still can solve the issue from the web interface:
- Create a new account, e.g. user "admin2"
- While logged in as "admin", make this user an administrator: go to "Change config file", add "
Admin user = admin, admin2"
- Now log off and then login as "admin2"
- Check that you can do administration, then remove user "admin"
- Create a new user "admin" with proper "Full name" and "Email"
- Now log off and then login as "admin"
- Check that you can do administration, then remove user "admin2"
That should work. Good luck!
|
Fantastic! That worked great. Thanks so much for the help guys!!
Terry |
67119
|
Wed Sep 7 12:37:38 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V2.9.0-241 | Re: Password may not contain blanks |
Terry Shuck wrote: |
Can you tell me how to stop elogd? I've edited that file several times however when I open ELOG in my browser the elogd is back like it was before the edits.
|
Best is if you edit elgod.cfg or the user configuration from inside the web browser (Click on 'config' on the elog page), then you don't have to restart elogd. If you do have to restart it, go to My Computer/Manage/Services, select elogd, then stop and start the service.
- Stefan |
67118
|
Wed Sep 7 12:17:44 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V2.9.0-241 | Re: Password may not contain blanks |
Terry Shuck wrote: |
Anyway if I have to wipe out ELOG and start over to have admin capabilities again, do all of my logbooks have to be rewritten? Can I import existing logbooks into a new ELOG?
|
If you start over, you can just copy the xxyyzza.log files into the new logbook directory and it should be fine. You can also change the config file in your current logbook without starting over. |
|