hello, I just upgrade from 2.9 into 3.0.0 in CentOS 6.5

but after upgrade, I can't check elogd services via command line

service elogd status,

always result in missing argument, while it works with httpd or mysqld services and old elogd version.

I try to uninstall and install rom scratch and same result,

Okay I give you screenshoot of that,

you may notice, on check service status and stopping services, error resulted

The init script supplied with elog was originally written for Redhat. It seems like CentOS has slightly changed the init daemon management, but I'm not an expert on that, nor do I have CentOS installed. If somebody comes with a fixed elogd.init for CentOS, I'm happy to include that in the distribution.

/Stefan

The quick fix I found was to uncomment line 10 in the init.d file. (This was tested on a CentOS 6.8 AWS instance.)

. /etc/rc.d/init.d/functions

This will allow the status command to function properly.

Clean install:

[centos@ip-172-31-51-59 ~]$ service elogd status
status: invalid option: -p
 

After uncommenting line 10:

[centos@ip-172-31-51-59 ~]$ service elogd status
elogd (pid  11438) is running...

When you start elog it still won't show that the service started successfully (No 'OK'). If you go to stop the service, it will give you the proper 'OK' indicating it stopped successfully.

So to fix the missing 'OK' (or 'FAILED') we need to update the start section around line 51 as follows:

          touch /var/lock/subsys/elogd
        echo_success
        else
        echo_failure
        fi
        echo
        ;;
 

I've attached my modified init file which I believe corrects the above issues. I will say though that I'm not a programmer so I won't guarantee it's perfect. I haven't checked to see if CentOS 7 works with this modified version. Just checked it on a CentOS 7.2 AWS instance and it also appears to function correctly.

[root@oceana ~]# systemctl status elogd
● elogd.service - SYSV: ELOG is a weblog with integrated database
   Loaded: loaded (/etc/rc.d/init.d/elogd)
   Active: active (running) since Sun 2016-09-18 22:35:44 UTC; 7s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2263 ExecStop=/etc/rc.d/init.d/elogd stop (code=exited, status=0/SUCCESS)
  Process: 2275 ExecStart=/etc/rc.d/init.d/elogd start (code=exited, status=0/SUCCESS)
 Main PID: 2277 (elogd)
   CGroup: /system.slice/elogd.service
           └─2277 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg

Sep 18 22:35:44 oceana elogd[2277]: elogd 3.1.1 built Aug  4 20...0
Sep 18 22:35:44 oceana elogd[2277]: revision
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: CKeditor detected
Sep 18 22:35:44 oceana systemd[1]: Started SYSV: ELOG is a webl....
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: ImageMagick detected
Sep 18 22:35:44 oceana elogd[2277]: SSLServer listening on port....
Hint: Some lines were ellipsized, use -l to show in full.

The old SysV style commands ('service elogd start|stop|status') also function correctly.

[root@oceana ~]# service elogd stop
Stopping elogd (via systemctl):                            [  OK  ]
[root@oceana ~]# service elogd start
Starting elogd (via systemctl):                            [  OK  ]

Ok, I will include this patch in the distribution.

Stefan

How do I make this section Wider or Shorter in the 2.7.8 version?
Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box. 

> How do I make this section Wider or Shorter in the 2.7.8 version?
> Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box. 

Never mind Found it

In Global set

Message Width = 95

Hello,

I've been successfully using elog as a daemon since several years on a Linux machine. For some reasons recently I had to switch to a Windows 7 machine. Here, setting up the elog daemon doesn't work for me:

(a) running the command:

"...\ELOG\elog.exe" -c "...\ELOG\elogd.cfg"

in a windows shell works perfectly fine - logbook is up and running as set up in the cfg-file.

(b) However, starting the windows service manually (start->control panel->system and security->administrative tools->services) that was set up automatically during installation of elog leads to an error message:

"Error 1053: The service did not respond to the start or control request in a timely fashion"

From the service settings I can verify that the service is running exactly the same command that works in (a).

Could someone please share the windows service settings? Thanks in advance.

Cheers, Christian

These problems are usaully related to user rights. Try starting the service under a different (maybe admin) user.

Stefan

Hi Stefan,

you were right - running the service by an authorized user solved the problem.

Thanks a lot.

Cheers, Christian

After registering, elog displays a page with the message:

     Error: Command "Config" is not allowed for user ""

However, the registration is successful. This causes confusion, and results in users registering multiple times.

In the elogd.conf file, I have the directive:

     Allow Config = bergman

Any suggestions?

 I loathe the idea of 'bumping' up one's own posting, but here I go...

Has anyone seen this issue, or have any solution? We've got people who register 8 or more times, since they see the "Error" message with each registration.

Is anyone else seeing this? It's very confusing to new users.

Well, 5 years after opening this issue, with no responses here, I finally got into the source code and fixed it.

The problem seems to be if eLog is configured to prohibit users (non-administrators) from the "Config" option...but on the initial self-registration, the code goes to the Config screen for the user anyway...resulting in the false error message.

So, I [badly] hacked eLog to fix that, add some debugging/log messages, and to correct a typo.

Attached is the patch against release 3.1.1-1. Try not to cringe too much at my code. :)

Hello :)

Is there any way to highlight code (for example php, SQL) in logs entries?

Best Regards

Daniel Sajdyk

A new version 3.1.2 of elog has been released today and can be retrieved through the normal download section. Since it fixes some vulnerabilities, it is recommended to update to this version.

Stefan

Dear all, sorry for asking you another question, but today after I finally recovered all my logbook entries, I updated to elog 3.1.1 and now I have a problem uploading images.

This is what I do:

• Click on the insert "Image" button in the editor toolbar
• In the popup window I select the picture I want to upload and then press "Send to server". I see the file appearing among the attachments at the bottom of the message.
• I click OK, but the popup complains that the Image Source URL is missing. Indeed when I switch to the other tab the URL field is open.

I have tried on your demo logbook and after the image is sent to the server, the URL field is automatically filled.

What am I doing wrong? With 2.9.2 it was working normally.

Thanks again and best regards

Antonio

Can anyone help me? I'm really clueless

Thanks in advance,

Antonio

I entered this image exactly as you described. When I click OK, the dialog disappears. Can you check if it works for you on this server? Maybe with different browsers?

Stefan

Dear Stefan, thanks for your answer. 

I tried to add a picture to this reply but I got the same error message with both Firefox and Chrome. 

For sure the pictures were not included in the message, but I have the feeling they were not even uploaded to the server. 

(I'm on Windows 7) 

Thanks for your help,

Antonio

Dear Stefan, this is to confirm that also from my personal laptop from home I have the same issue. No pictures uploaded to this server from windows 10. 

Which OS & Browser are you using? 

thanks,

Antonio

Okay, I can confirm this bug: with Windows 10 using Firefox 47.0 the dialog hangs as soon as I press "Send it to the server". When it returns, it did not upload anything. That is why it asks for URL after pressing OK.

Quick fix: just attach the image and use the URL of the attachment.

I did it here:

Cheers

Andreas

Thanks Andreas for your contribution and your quick fix. Just a question: how do you get the attachment URL? 

Cheers,

Antonio

If you go on the attached image with the right mouse button, then you'll get a menu. In this menu there should be some entry like "copy image link" (my PC is unfortunately configured in German, I can't look it up).

This copies the URL in the clipboard and you can just paste it in the URL entry of the image button.

ok... that was easy. I though there was a ELOG specific way to link to attachments.

(my computer is also in German :)

Andreas, there is something strange. It looks the problem is "configuration dependent" because I tried to upload a picture on the Linux Demo logbook and there it works. Can you confirm this too? 

Yes, I can confirm that the image button upload does work in the Linux Demo logbook (Windows 10 client host, Firefox 47.0 client) and it still does not work in this Forum.

This is another piece of information to help in the debugging. To my standards logbooks, I have added the "demo". On the demo I can upload pictures while I can't on the other logbooks.

This is indicating that the bug has something to do with the logbook configuration other than with the editor or the image upload plugin.

Thanks for your help,

Antonio

The conflicting option is "Preview attachments". When this is turned off (set to 0), images are not properly uploaded. Could you please confirm it also on your side?

When an attachment is later added to an exisiting entry, we see that the string "Uploaded <date>" has the wrong
time: in our case it is one hour into the future.
I'm testing it now here in the forum.

I can reproduce it in this forum: the Uploaded time should have been 10:35, but it shows 11:35.

Cheers, Andreas