Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 727 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  68329   Wed Jun 8 16:01:11 2016 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportWindows3.113Re: Self register = 0 not working ,

It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas

rudy wrote:

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

 

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1


Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

 

  68330   Wed Jun 8 17:08:56 2016 Reply rudysylpid2007@gmail.comBug reportWindows3.113Re: Self register = 0 not working ,

Hi Andreas

I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill
Andreas Luedeke wrote:

It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas

rudy wrote:

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

 

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1


Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

 

 

  68331   Wed Jun 8 18:49:28 2016 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportWindows3.113Re: Self register = 0 not working ,

Aparently I've missed that one :-)

In order to test your problem it would be useful to have a minimal config file to reproduce the problem. Yours does not include any actual logbook, only [global *] sections.

Andreas

rudy wrote:

Hi Andreas

I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill
Andreas Luedeke wrote:

It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas

rudy wrote:

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

 

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1


Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

 

 

 

  68332   Thu Jun 9 04:29:14 2016 Reply rudysylpid2007@gmail.comBug reportWindows3.113Re: Self register = 0 not working ,

Hi Andreas, 

Thanks for your help. I will try to do that and if I found how to fix this problems, I will post it at here again.

Andreas Luedeke wrote:

Aparently I've missed that one :-)

In order to test your problem it would be useful to have a minimal config file to reproduce the problem. Yours does not include any actual logbook, only [global *] sections.

Andreas

rudy wrote:

Hi Andreas

I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups

Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL

Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases

[global engineering]
Password file = engineers.pwd
Admin user = stefan

[global administration]
Password file = admin.pwd
Admin user = bill
Andreas Luedeke wrote:

It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas

rudy wrote:

I have Split Elog to Two Top Group [Check the Config Below].

Problem = 

After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.

 

[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1


Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing

[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01

[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01

 

 

 

 

  68339   Tue Jun 21 16:33:56 2016 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.0Re: pdf thumbnails in latest Imagemagick

Hi John,

I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.

Cheers,
Stefan 

John Haggerty wrote:

I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails.  I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing.  This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.

 

  68340   Tue Jun 21 16:44:05 2016 Reply John Haggertyhaggerty@bnl.govBug reportMac OSX3.1.0Re: pdf thumbnails in latest Imagemagick

 

Stefan Ritt wrote:

Hi John,

I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.

Cheers,
Stefan 

John Haggerty wrote:

I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails.  I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing.  This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.

 

Since I posted that, there have been multiple versions of Imagemagick released through brew for the Mac in the last few weeks, and I'm now using 6.9.4-9, which seems to work fine with thumbnails again, indeed, I noticed that as soon as 6.9.4-8 was released, I was back to normal, but thanks for the debugging pointer.

  68342   Mon Jun 27 16:06:55 2016 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.2Re: Unable to set a custom logbook dir on Debian 8 from the repository package

The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers. So better download the current version from bitbucket and compile elogd yourself.

S. Caiazza wrote:

Dear all

I installed elog from the current stable repository on Debian 8 (jessie)

The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.

Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path) 

Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks

And I created a new logbook.

After restarting the elog service the second database is correctly created but both of them are still stored in  /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.

How can I specify the custom folder so that the new logbooks are written there?

 

  68358   Tue Jul 12 21:23:13 2016 Entry Austin Reidarreid3@ncsu.eduBug reportOther3.1.1-Email report has incorrect pictures
My group uses the precompiled Debian binary, and I use ELCode to format my log reports. (I've found it to be the easiest way to generate inline images)

Yesterday, I submitted an entry that renders correctly on the elog itself, but the email report that was sent to my collaborators was quite confusing, because every picture in it was the same. Interestingly, all the images used inline in the report were attached to the original, but they were stripped of their context.

I've attached screen shots of both reports.
Attachment 1: emailedversion.jpg
emailedversion.jpg
Attachment 2: okversion.jpg
okversion.jpg
ELOG V3.1.5-3fb85fa6